-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workflow engine parsers #11
Comments
There might be an acceptable solution that could be realised immediately. We introduce a second parser phase that is run after all parsing/normalising has been completed. This would basically be a formalisation of our current phonopy-hack. Parsers configure if they need a second phase by providing an implementation of Furthermore, we need to provide some utility to easily read the other results, either to copy results or create cross entry archive references. |
Hopping on this, I just tried to upload a
which are sufficient to reconstruct the entire |
It reads only phonon.yaml not phonopy.yaml which I based on name of the mainfile in the phonopy database. I will update the parser to include this also. |
I tried |
The correction is still in beta: https://nomad-lab.eu/prod/rae/beta/gui You can try this and let me know if still does not work. |
that worked 👍 |
Workflow engines like fhi-vibes, Phonopy have underlying codes (vasp, fhi-aims etc.) to calculate desired properties. Typically, all the settings for these codes are not saved by the engines themselves but only a reference to these calculations are provided. In the case of Phonopy, a special normalization layer is added to fetch the information from the reference calculations belonging to the same upload. I personally do not favour this strategy as it will become cumbersome as we integrate more and more workflow engines.
This issue is also on GitLab here
There is a related discussion on matsci here
@lauri-codes @ladinesa
The text was updated successfully, but these errors were encountered: