Aakash Ashok Naik

> There are still conflicts, unfortunately :( Just resolved it now , should be fine. test files xD

Hi @janosh , @utf , any ideas how to fix this issue properly for this pydantic error ? https://github.com/materialsproject/atomate2/pull/723/commits/5c88c8fcd04bf4cfc2c2fe8ee7c372c5e32a0c59 Do I need to define again new Models here for all...

> Hi @janosh , @utf , any ideas how to fix this issue properly for this pydantic error ? [5c88c8f](https://github.com/materialsproject/atomate2/commit/5c88c8fcd04bf4cfc2c2fe8ee7c372c5e32a0c59) > > Do I need to define again new Models...

Hi @munrojm, can you please have a look at the updated schema? We have now made it possible to turn off the LobsterPy analysis . So this can be used...

> @naik-aakash the updated doc with and without analysis still still extremely large when parsed. The one example I have is over 200MB uncompressed for both the former and latter....

Hi @utf , if you have any specific comments on the changes. Let us know . Or else it is ready to be merged.

> @naik-aakash did you get something similar recently? > > @badw could you list all version numbers of your different codes? I guess it is some unrelated change in another...

Hi @badw , after a bit more checking in detail into this issue, I think the issue is not specific to PhononFlow, but how the forcefield based jobs are generated....

> If I understand correctly, `custom_model` should be a CHGNet obejct loaded from user's weights. This doesn't seem to be a issue with CHGNet code? Is there anything that is...

Hi @JaGeo, @joabustamante and @kaueltzen, just tagging you all here for updates.