DNA Loop Extrusion by SMCCs in LAMMPS
Loop extrusion simulation
Installation
Below are instructions to install the smc-lammps python package
and a separate LAMMPS executable used to perform simulations.
Python
From PyPI
The code is available as a package on PyPI.
pip install smc-lammps
From Source Using uv (recommended)
git clone https://github.com/LucasDooms/SMC_LAMMPS.git
cd SMC_LAMMPS
uv sync --no-dev
# alternatively, to include optional dependencies
uv sync --all-groups
source .venv/bin/activate
or use uv run <command> without activating the environment.
From Source Using pip
git clone https://github.com/LucasDooms/SMC_LAMMPS.git
cd SMC_LAMMPS
python3 -m venv .venv
source .venv/bin/activate
# get exact versions (recommended)
pip install -r requirements.txt
# or, install from pyproject.toml file
pip install -e .
LAMMPS
You will need a LAMMPS executable with the MOLECULE, EXTRA-MOLECULE, and RIGID packages.
See https://docs.lammps.org/Install.html for more information.
Simple example:
git clone https://github.com/lammps/lammps --depth=1000 mylammps
cd mylammps
git checkout stable # or release for a more recent version
mkdir build && cd build
cmake -D CMAKE_INSTALL_PREFIX="$HOME/lammps" -D PKG_MOLECULE=yes -D PKG_EXTRA-MOLECULE=yes -D PKG_RIGID=yes ../cmake
cmake --build . -j8
make
make install
export PATH="$HOME/lammps/bin:$PATH"
(Optional) VMD
To use the src/smc_lammps/post_process/visualize.py script, you will need VMD,
see https://www.ks.uiuc.edu/Development/Download/download.cgi?PackageName=VMD.
Docker Installation
Alternative: install smc-lammps and LAMMPS in a docker container
You can also use docker to run the code.
Either download the image using
docker pull ghcr.io/lucasdooms/smc-lammps:latest
or build it locally with docker build -t smc-lammps .
(replacing ghcr.io/lucasdooms/smc-lammps with smc-lammps for the instructions below).
Now you can run an interactive session using
docker run -it -v .:/data ghcr.io/lucasdooms/smc-lammps
Or, to run directly (see Usage)
docker run -v .:/data ghcr.io/lucasdooms/smc-lammps smc-lammps ...
To run a jupyter notebook session, use
docker run -it -v .:/data -p 127.0.0.1:8888:8888 ghcr.io/lucasdooms/smc-lammps jupyter notebook --allow-root --no-browser --ServerApp.ip=0.0.0.0 /data
and open the displayed link http://127.0.0.1:8888/tree?token=... in your browser.
Note: the docker image does not include VMD.
Usage
- Create a directory for your simulation using
smc-lammps mysim. - Define all parameters in
mysim/parameters.py(seesrc/smc_lammps/generate/default_parameters.pyfor all options). - Run
smc-lammps [flags] mysim, providing the directory of the parameters file. Use the-gflag to generate the required parameterfile and datafile.
Examples
smc-lammps mysim -grto generate and run.smc-lammps mysim -grpvto generate, run, post-process, and visualize.smc-lammps mysim -grvnto generate, run, and visualize while ignoring errors.smc-lammps mysim -vto visualize.smc-lammps mysim -vfto visualize a perspective following the SMC.smc-lammps mysim -cto continue a run from a restart file.
Help
Show help with smc-lammps --help.
Shell Completion
To get shell completion when using smc-lammps on the command-line run the following:
- For bash or zsh, use
eval "$(register-python-argcomplete smc-lammps)" - For fish, use
register-python-argcomplete --shell fish smc-lammps | source
Development
Enable dev dependencies
uv sync --dev
Tests
Run all tests using
pytest
Documentation
Dependencies
To build the documentation, you will need to install graphviz, e.g. sudo apt update && sudo apt install graphviz on Debian/Ubuntu.
Build
Build the documentation using
make -C docs html
(or sphinx-build -b html docs/source docs/build/html)
Now open docs/build/html/index.html in a browser or use python -m http.server -d docs/build/html and browse to http://localhost:8000.
Autobuild
To view new changes made to the documentation automatically, you can use sphinx-autobuild
sphinx-autobuild -b html --watch src/smc_lammps docs/source docs/build/html
Doctests
Run the doctests using
make -C docs doctest
Authors
Original code by Stefanos Nomidis (https://github.com/sknomidis/SMC_LAMMPS).
Modifications by Arwin Goossens.
All commits in this repository by Lucas Dooms.
Released under MIT license.
Metadata
Release files for smc-lammps 0.2.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| smc_lammps-0.2.3.tar.gz | 203.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| smc_lammps-0.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 299.2 kB
Release files / smc_lammps-0.2.3.tar.gz
| Download URL | smc_lammps-0.2.3.tar.gz |
|---|---|
| Size | 203.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
33fab28af0c445f2e4b47692df4ec1785b0abd566573fff1fd8f7b637f3c6e6c
|
|
BLAKE2b-256 checksum How to use checksums |
9ba7873702e9e93c1c569da4cb5fec1770e3bdf35f310f8ad87ee314c7bd2aa9
|
| 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 Jun 15, 2026.
Transparency logRelease files / smc_lammps-0.2.3-py3-none-any.whl
| Download URL | smc_lammps-0.2.3-py3-none-any.whl |
|---|---|
| Size | 95.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ab92a35975b71180266a66556681ddbb608a7ce128b812503e565c26135b12a3
|
|
BLAKE2b-256 checksum How to use checksums |
f6074819a06b73b000f0e9690d2b7f0468cf816f81c4b13634b17ec8d2cec41b
|
| 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 Jun 15, 2026.
Transparency log