Dear Nomad developers,
I have some questions about some more potential parsers for Quantum ESPRESSO (QE). I did recently quite a lot of phonons calculation with the PHonon package (User's Guide for the PHonon package) from Quantum ESPRESSO and I would like to upload my results to NOMAD. I mostly need just for the calculation mainfiles to be recognized and few simple information parsed so I can get a DOI pointing to at least a bit searchable/understandable archive. Similarly to the LOBSTER and OpenMX parsers before (that are now integrated thanks to @ladinesa), I’m willing to contribute some code of needed, but most likely I will need some help as the calculations are a bit beyond the simple DFT scheme so I might need some advice how to properly integrate this into NOMAD.
The PHonon package differs a bit from the current phonopy package since it uses Density functional perturbation theory (DFPT) instead of the standard phonopy finite differences approach, the output is basically a list of vibrational frequencies for a bunch of q-points. So that I guess should go into vibrational_frequencies subsection, but that again is not q-point dependent? Here is some example output: ph.out (773.9 KB) Its also not 100% clear to me if the method here should still be DFT and this will be just a workflow parser or if this needs its own new method…
Another program I would like to have a simple parser for (as I have also few cases to upload) is the EPW https://docs.epw-code.org/ (also part of the QE package) it calculates the quantities related to electron phonon interaction. It uses the data from QE PHonon and PW (the main DFT package) and Wannier90 and calculates properties related to the electron-phonon interaction (electron-phonon coupling strenght, anisotropic Eliashberg spectral function, phonon or electrons linewidths and lifetimes from the interaction, etc…). This doesn’t also fit into the current metainfo definitions at all… So yeah suggestions how to proceed welcomed.
@ladinesa Please have a look at this.
As of now quantum espresso in nomad refers to the PWSCF module. I actually need to discuss how to manage this with our “domain experts”. For now, we put the Phonon module under workflowparsers. We do not parse the full method now as the metainfo is not yet defined. We can simply put under method.electronic.method = ‘DFPT’. We do something similar to EPW. We put it under workflowparsers. I surmise this is a single_point workflow. We simply extend the SinglePoint metainfo, with the code-specific names for the properties for now. Should I create an initial parser for you @Pavel_Ondracka to extend?
Great, if you can create a stub parsers that get the general metainfo scheme at least semi-correctly that would be awesome. Than I’ll try to extend it to parse some actual result quantities. EPW should be single_point I assume, here is some example output file just so you have something for the parser matcher:
epw.out (777.2 KB)
This post was flagged by the community and is temporarily hidden.
@ladinesa Do you have any time estimate on the stub parsers?
@mscheidgen On a related note. My most common NOMAD use case is to publish calculations for a manuscripts as an open data. I really like NOMAD, unfortunately every now and than (like previously with the OpenMX and LOBSTER and now with the QE-based calculations) I would like to upload something that doesn’t have a parser. In that regards it is slightly unfortunate, that the datasets are composed of parsed entries and not of files… Now if I upload just results that have no parser I have nothing to create the dataset from.
You could already upload *.archive.json files that use our schema. Basically provide the parser results your self. We work on this more for experiment data and there are not great examples for this. There might be a few complications left and right, but if you have a good case, we could try something.
The upcoming nomad v1.1.0 will also support custom schemas to add data that require a novel data structure.