Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/nomad-coe/electronic-parsers
https://github.com/nomad-coe/electronic-parsers
Last synced: about 1 month ago
JSON representation
- Host: GitHub
- URL: https://github.com/nomad-coe/electronic-parsers
- Owner: nomad-coe
- License: apache-2.0
- Created: 2022-02-19T00:29:26.000Z (almost 3 years ago)
- Default Branch: develop
- Last Pushed: 2024-10-29T09:18:48.000Z (about 2 months ago)
- Last Synced: 2024-10-29T10:02:57.836Z (about 2 months ago)
- Language: Python
- Size: 168 MB
- Stars: 19
- Watchers: 3
- Forks: 7
- Open Issues: 40
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Citation: CITATION.cff
Awesome Lists containing this project
README
[](https://doi.org/10.5281/zenodo.13880705)
This is a collection of the NOMAD parsers for the following electronic codes:
1. [ABACUS](http://abacus.ustc.edu.cn/)
2. [ABINIT](https://www.abinit.org/)
3. [AMS](https://www.scm.com)
4. [QuantumATK](https://www.synopsys.com/silicon/quantumatk.html)
5. [BigDFT](http://bigdft.org/)
6. [CASTEP](http://www.castep.org/)
7. [CHARMM](https://www.charmm.org)
8. [CP2K](https://www.cp2k.org/)
9. [CPMD](https://www.cpmd.org/)
10. [CRYSTAL](https://www.crystal.unito.it/)
11. [DMol3](http://dmol3.web.psi.ch/)
12. [Elk](http://elk.sourceforge.net/)
13. [exciting](http://exciting-code.org/)
14. [FHI-aims](https://aimsclub.fhi-berlin.mpg.de/)
15. [FLEUR](https://www.flapw.de/)
16. [FPLO](https://www.fplo.de/)
17. [GAMESS](https://www.msg.chem.iastate.edu/)
18. [Gaussian](http://gaussian.com)
19. [GPAW](https://wiki.fysik.dtu.dk/gpaw/)
20. [Molcas](http://molcas.org/)
21. [Molpro](https://www.molpro.net/)
22. [MOPAC](http://openmopac.net/)
23. [NWChem](https://nwchemgit.github.io/)
24. [OCEAN](https://feff.phys.washington.edu/OCEAN/index.html)
25. [Octopus](https://octopus-code.org/)
26. [ONETEP](https://www.onetep.org/)
27. [OpenMX](http://www.openmx-square.org/)
28. [ORCA](https://www.faccts.de/orca/)
29. [Psi4](https://psicode.org/)
30. [Qball](https://github.com/LLNL/qball)
31. [Qbox](http://qboxcode.org/)
32. [QuantumESPRESSO](http://www.quantum-espresso.org/)
33. [SIESTA](https://siesta-project.org/siesta)
34. [soliddmft](https://github.com/TRIQS/solid_dmft)
35. [TURBOMOLE](https://www.turbomole.org/)
36. [VASP](https://www.vasp.at/)
37. [w2dynamics](https://github.com/w2dynamics/w2dynamics)
38. [Wannier90](http://www.wannier.org/)
39. [WIEN2k](http://www.wien2k.at/)
40. [YAMBO](https://www.yambo-code.org/)
## Preparing code input and output file for uploading to NOMAD
An *upload* is basically a directory structure with files. If you have all the files locally
you can just upload everything as a `.zip` or `.tar.gz` file in a single step. While the upload is
in the *staging area* (i.e. before it is published) you can also easily add or remove files in the
directory tree via the web interface. NOMAD will automatically try to choose the right parser
for you files.
For each parser there is one type of file that the respective parser can recognize. We call
these files *mainfiles*. For each mainfile that NOMAD discovers it will create an *entry*
in the database, which users can search, view, and download. NOMAD will consider all files
in the same directory as *auxiliary files* that also are associated with that entry. Parsers
might also read information from these auxillary files. This way you can add more files
to an entry, even if the respective parser/code might not use them. However, we strongly
recommend to not have multiple mainfiles in the same directory. For CMS calculations, we
recommend having a separate directory for each code run.
Go to the [NOMAD upload page](https://nomad-lab.eu/prod/rae/gui/uploads) to upload files
or find instructions about how to upload files from the command line.
## Using the parser
You can use NOMAD's parsers and normalizers locally on your computer. You need to install
NOMAD's pypi package:
```
pip install nomad-lab
```
To parse code input/output from the command line, you can use NOMAD's command line
interface (CLI) and print the processing results output to stdout:
```
nomad parse --show-archive
```
To parse a file in Python, you can program something like this:
```python
import sys
from nomad.cli.parse import parse, normalize_all
# match and run the parser
archive = parse(sys.argv[1])
# run all normalizers
normalize_all(archive)
# get the 'main section' section_run as a metainfo object
section_run = archive.section_run[0]
# get the same data as JSON serializable Python dict
python_dict = section_run.m_to_dict()
```
## Developing the parser
Create a virtual environment to install the parser in development mode:
```
pip install virtualenv
virtualenv -p `which python3` .pyenv
source .pyenv/bin/activate
```
Install NOMAD's pypi package:
```
pip install nomad-lab
```
Clone the parser project and install it in development mode:
```
git clone https://github.com/nomad-coe/electronic-parsers.git electronic-parsers
pip install -e "electronic-parsers[dev]"
```
Running the parser now, will use the parser's Python code from the clone project.
## How to cite this work
Ladines, A.N., Chang, T., Daelman, N., Fekete, A., Frodlová, J., Ghiringhelli, L.M., Himanen, L., Ilyas, A., Nakhaee, Ondračka, P., M. Pizarro, Rudzinski, J.F., & Scheidgen, M Atomistic Parsers [Computer software]. https://doi.org/10.5281/zenodo.13880705