Skip to main content

NOMAD DOI

nomad-neb-workflows

A NOMAD plugin containing the section definitions of a standard Nudged Elastic Band (NEB) workflow.


This nomad_ plugin was generated with Cookiecutter_ along with @nomad's cookiecutter-nomad-plugin template.

Getting started

Install the dependencies

Clone the project and in the workspace folder, create a virtual environment (note this project uses Python 3.9):

git clone https://github.com/FAIRmat-NFDI/nomad-neb-workflows.git
cd nomad-neb-workflows
python3.9 -m venv .pyenv
. .pyenv/bin/activate

Make sure to have pip upgraded:

pip install --upgrade pip

We recommend installing uv for fast pip installation of the packages:

pip install uv

Install the nomad-lab package:

uv pip install '.[dev]' --index-url https://gitlab.mpcdf.mpg.de/api/v4/projects/2187/packages/pypi/simple

Note! Until we have an official pypi NOMAD release with the plugins functionality. Make sure to include NOMAD's internal package registry (via --index-url in the above command).

The plugin is still under development. If you would like to contribute, install the package in editable mode (with the added -e flag) with the development dependencies:

uv pip install -e '.[dev]' --index-url https://gitlab.mpcdf.mpg.de/api/v4/projects/2187/packages/pypi/simple

Run the tests

You can run local tests using the pytest package:

python -m pytest -sv tests

where the -s and -v options toggle the output verbosity.

Our CI/CD pipeline produces a more comprehensive test report using coverage and coveralls packages. We suggest you to generate your own coverage reports locally by doing:

uv pip install pytest-cov
python -m pytest --cov=src tests

Setting up plugin on your local installation

Read the NOMAD plugin documentation for all details on how to deploy the plugin on your NOMAD instance.

Run linting and auto-formatting

ruff check .
ruff format . --check

Ruff auto-formatting is also a part of the GitHub workflow actions. Make sure that before you make a Pull Request, ruff format . --check runs in your local without any errors otherwise the workflow action will fail.

Debugging

For interactive debugging of the tests, use pytest with the --pdb flag. We recommend using an IDE for debugging, e.g., VSCode. If using VSCode, you can add the following snippet to your .vscode/launch.json:

{
  "configurations": [
      {
        "name": "<descriptive tag>",
        "type": "debugpy",
        "request": "launch",
        "cwd": "${workspaceFolder}",
        "program": "${workspaceFolder}/.pyenv/bin/pytest",
        "justMyCode": true,
        "env": {
            "_PYTEST_RAISE": "1"
        },
        "args": [
            "-sv",
            "--pdb",
            "<path to plugin tests>",
        ]
    }
  ]
}

where ${workspaceFolder} refers to the NOMAD root.

The settings configuration file .vscode/settings.json performs automatically applies the linting upon saving the file progress.

Build the python package

The pyproject.toml file contains everything that is necessary to turn the project into a pip installable python package. Run the python build tool to create a package distribution:

uv pip install build
python -m build --sdist

You can install the package with pip:

uv pip install dist/nomad-neb-workflows-0.1.0

Read more about python packages, pyproject.toml, and how to upload packages to PyPI on the PyPI documentation.

Documentation on Github pages

To deploy documentation on Github pages, make sure to enable GitHub pages via the repo settings.

To view the documentation locally, install the documentation related packages using:

uv pip install -r requirements_docs.txt

Run the documentation server:

mkdocs serve

Template update

We use cruft to update the project based on template changes. A cruft-update.yml is included in Github workflows to automatically check for updates and create pull requests to apply updates. Follow the instructions on how to enable Github Actions to create pull requests.

To run the check for updates locally, follow the instructions on cruft website.

License

Distributed under the terms of the Apache Software License 2.0_ license, "nomad-neb-workflows" is free and open source software

How to cite this work

Schumann, J., Pizarro, J.M., Gajera, U., Rudzinski, J.F., Näsström, H., NOMAD NEB Workflows (all versions) [Computer software]. https://zenodo.org/doi/10.5281/zenodo.XXX

Main contributors

Name E-mail
Udaykumar Gajera
Hampus Näsström
José M. Pizarro
Joseph F. Rudzinski joseph.rudzinski@physik.hu-berlin.de
Julia Schumann

Metadata

Release files for nomad-neb-workflows 1.0.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for nomad-neb-workflows 1.0.3
File Size Uploaded
nomad_neb_workflows-1.0.3.tar.gz 4.0 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for nomad-neb-workflows 1.0.3
File Interpreter ABI Platform
nomad_neb_workflows-1.0.3-py3-none-any.whl Python 3 none any Details

Total release size: 4.0 MB

Release files / nomad_neb_workflows-1.0.3.tar.gz

Download URL nomad_neb_workflows-1.0.3.tar.gz
Size 4.0 MB
Tags Source
SHA-256 checksum
How to use checksums
5f6b728909b420d320c614019f5f8198c2ff98bb8bcc30cf5ae43b8ce4a1f9bc
BLAKE2b-256 checksum
How to use checksums
9b544c70af7ca691b3fb04c6b5eca2f77f167c0d94aa1a77ac8b218ea5616859
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 5, 2025.

Transparency log

Release files / nomad_neb_workflows-1.0.3-py3-none-any.whl

Download URL nomad_neb_workflows-1.0.3-py3-none-any.whl
Size 19.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
31509774b2e306c1b17f1a4308262dd4374d103cf3e41e8dfa63448f86c3d5f7
BLAKE2b-256 checksum
How to use checksums
b9492e22a9e6d3066a0eddc449087dbea284b857240c3ccd5a2baa4b5836c3fd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 5, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

1.0.3 This release

2 release files

1.0.2

2 release files

1.0.1

2 release files

1.0.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page