Commit bce41668 authored by RealPolitiX's avatar RealPolitiX
Browse files

README update

parent ae403871
# parser-skeleton
# mpes-parser
## About
This is not a real parser, its a skeleton for parsers. To write you own parsers, its
best to fork this skeleton and use it as a template.
Multidimensional photoemission spectroscopy (MPES) experimental data parser for NOMAD-FAIR database.
## Setup and run example
We are currently targeting Python 3.6. Some nomad dependencies might still have problems
with 3.7++. It will definitely not work with 2.x. If you run into troubles, you could
try to ignore some dependencies. Most of them are only used in the DFT context.
Best use a virtual environment:
virtualenv -p python3 .pyenv
source .pyenv/bin/activate
Clone and install the nomad infrastructure and the necessary dependencies (including this parser)
git clone nomad
cd nomad
git submodule update --init
pip install --upgrade pip
pip install --upgrade setuptools
pip install -r requirements.txt
./ -e
pip install -e .
The parsers (among other things) are git submodules. The `./` will run
through all the sub modules and install them as pip packages (be in you virtual env!).
Fork this project on [gitlab](
Rename your fork in its settings/advanced and move it to the nomad-lab namespace.
Choose a name that starts with `parser-`, e.g. `parser-your-parser-name`.
You'll need a []( account.
Add your parser to the nomad project on a separate branch:
git checkout -b your-parser-name
git submodule add dependencies/parsers/your-parser-name
Do the necessary changes:
- []( Change the project metadata
- [skeletonparser](skeletonparser): Change the directory name, i.e. python package name (no uppercases, no `_` please)
- [skeletonparser/](skeletonparser/ Implement your parser, change the class names
- [skeletonparser/](skeletonparser/ Change the module/class names
- [skeletonparser/skeleton.nomadmetainfo.json](skeletonparser/skeleton.nomadmetainfo.json): Change the name, add your metadata definitions.
- []( Change this readme accordingly.
- probably some other things I forgot.
General metadata quantities (those that we can agree on) go to
But we should agree first. In the mean time, just put them in [skeletonparser/skeleton.nomadmetainfo.json](skeletonparser/skeleton.nomadmetainfo.json).
You can browse around `dependencies/nomad-meta-info/meta_info/nomad_meta_info/` to
see example definitions. **You cannot add values or open sections without defining them first!**
## Description of files
The set of important files for the parser are explained in the following,
- [mpesparser](mpesnparser): Change the directory name, i.e. python package name (no uppercases, no `_` please)
- [mpesparser/](skeletonparser/ Parser module initialization.
- [mpesparser/](skeletonparser/ Parser module main run file.
- [mpesparser/mpes.nomadmetainfo.json](mpesparser/mpes.nomadmetainfo.json): MPES metadata definitions.
To run the parser:
cd nomad/dependencies/parsers/your-parser-name
python -m yourparserpythonpackage tests/example.metadata.json
cd nomad/dependencies/parsers/parser-mpes
python -m parser-mpes tests/mpes.metadata.json
## Docs
Click through the [nomad archive page](
to learn about the *meta-info* metadata format and how to define your metadata.
Here is a more involved tutorial (but its pretty DFT and parsing text files specific):
[nomad@fairdi docs](
## FAQ
For any questions, **please open issues** (regarding parser development and using this skeleton)
in this [parser-skeleton project](
We will compile a FAQ from your issues.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment