KIMMDY
Reactive MD pipeline for GROMACS using Kinetic Monte Carlo / Molecular Dynamics (KIMMDY)
Installation
Note: KIMMDY requires GROMACS to be installed.
Some reactions need a GROMACS version patched with PLUMED.
The gromacs version name should then contain MODIFIED or plumed.
While it is possible to install KIMMDY with just pip install kimmdy,
this can take a while due to dependency resolution.
We recommend installing KIMMDY with uv instead:
uv tool install -p 3.11 kimmdy[all]
This installation includes all official reaction plugins and analysis tools.
To install only the most basic functionality, run:
uv tool install -p 3.11 kimmdy
You can also pick the plugins you want, the available extras are:
reactions: makeshomolysis,hat-naiveanddummyreactionreactions available.grappa: allows parametrization of any system on-the-fly.hat: hydrogen atom transfer reaction pluginhydrolysis: hydrolysis reaction plugindimerization: dimerization reaction plugin
To uninstall KIMMDY again, use
uv tool uninstall kimmdy
Documentation
The documentation is available here.
Getting started
Head over to the getting started tutorial.
Development
Development setup
Clone kimmdy, the default reaction and parameterization plugins, then install kimmdy as editable module via
git clone git@github.com:graeter-group/kimmdy.git --recurse-submodules
cd kimmdy
uv sync --extra all
To load or update the submodules, run:
git submodule update --init --recursive
Run kimmdy either using uv run kimmdy, or activate the virtual environment uv has created:
source .venv/bin/activate
kimmdy --help
Conventions:
- code style: black
- docstrings: numpy
- Conventional commit messages when possible for pretty release notes.
For more information, head to the documentation
Metadata
Release files for kimmdy 8.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| kimmdy-8.3.1.tar.gz | 47.9 MB | With provenance | Details for kimmdy-8.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| kimmdy-8.3.1-py3-none-any.whl | Python 3 | none | any | Details for kimmdy-8.3.1-py3-none-any.whl |
Total release size: 48.0 MB
Release files / kimmdy-8.3.1.tar.gz
| Download URL | kimmdy-8.3.1.tar.gz |
|---|---|
| Size | 47.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e3ed36c1015c94c433e07165c9e5fa9318c6444cc4648e4ac021cf58cee6c4fb
|
|
BLAKE2b-256 checksum How to use checksums |
83385865720e27abea3c6c898862e9baf0813f420b6c6c8e0fd49f0a8616d6b7
|
| 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 Jan 2, 2026.
Transparency logRelease files / kimmdy-8.3.1-py3-none-any.whl
| Download URL | kimmdy-8.3.1-py3-none-any.whl |
|---|---|
| Size | 122.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
230d8fb94cbd93b921d45ee742400c2023fad88136f7c23cf08367eef11e8b68
|
|
BLAKE2b-256 checksum How to use checksums |
2fd2d32b536221223ab324a13d92e55141baa3318a9cb0a6ed93630a4971c453
|
| 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 Jan 2, 2026.
Transparency logSecurity for kimmdy 8.3.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for kimmdy-8.3.1.tar.gz
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 Jan 2, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.