Skip to content
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

Quantum Espresso phonon parser show some problems at NOMAD staging server. #38

Closed
ondracka opened this issue Dec 17, 2022 · 1 comment
Closed

Comments

@ondracka
Copy link

This is a follow up from https://matsci.org/t/more-parsers-for-quantum-espresso-based-packages/42687/20 the matching problems are resolved when using the NOMAD staging server, however there are still major issues with the parsed results itself.

When file like this example ph.zip (however it looks like all Quantum Espresso Phonon output files I tried have the same issue) is uploaded nothing is parsed and strangely the program is shown as "Quantum Espresso EPW". However it looks like a correct parser was invoked parsers/quantumespressophonon, so I have no clue where the "Quantum Espresso EPW" string could come from... Also no properties are parsed. See this (unpublished) entry https://nomad-lab.eu/prod/v1/staging/gui/user/uploads/upload/id/Nb8MzkFZS3ukypH8SVaVcg/entry/id/F_0vjbaNxRrPn1IhdWg8lI9JJjgR as an example or just try to upload the ph.out testcase to staging server to reproduce.

I'm opening an issue here instead of against https://github.com/nomad-coe/workflow-parsers/ because the parser itself seems to get it right. When I parse it locally using the latest develop branch with nomad parse ph.out all looks fine, including the program name, system and the phonon properties, so it looks like this problem happens at some higher level.

CC @ladinesa

@ladinesa
Copy link
Contributor

I made a mistake in the parser metadata. A fix has already been made.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants