molcrafts-molrs
Python bindings for the molrs molecular modeling toolkit.
Install with pip install molcrafts-molrs and import molrs. Full docs:
https://docs.molcrafts.org/molrs/.
Install
pip install molcrafts-molrs
Requires Python 3.12+.
Quick start
import molrs
# SMILES → atomistic graph (class API under molrs.io)
mol = molrs.io.smiles.read_smiles("CCO").to_atomistic()
# 3D coordinates
from molrs.conformer import Conformer
mol, report = Conformer().generate(mol)
# Force field: typify → pairs → potentials
from molrs.ff.typifier import Mmff94Typifier
from molrs.ff.potential import intramolecular_pairs
from molrs.ff.compile import PotentialCompiler
typifier = Mmff94Typifier()
typed = typifier.typify(mol)
frame = typed.to_frame()
ff = typifier.forcefield() # a copy of exactly the types typify assigned
frame["pairs"] = intramolecular_pairs(frame, ff)
pots = PotentialCompiler(ff).compile(frame)
energy, forces = pots.evaluate(frame)
assert forces.shape == (frame["atoms"].n_rows, 3)
Package layout
The top level is the subsystems, plus the core data classes a user handles
directly (molrs.Frame is molrs.core.Frame: Frame,
Block, Trajectory, Box, MolGraph, Atomistic, CoarseGrain, the
entity classes, Element, Topology). Everything else has one path, named
after its Rust owner.
| Import | Owns |
|---|---|
molrs.core |
Frame, Block, Trajectory, frame metadata; Box and its Cell, neighbour search, regions, TriMesh, Trace; MolGraph, Atomistic, CoarseGrain and their live views, Element, Topology; Unit, Quantity, UnitPreset, UnitRegistry |
molrs.core.keys / .schema / .constants |
the column vocabulary, its specifications, and every physical and engine constant |
molrs.io |
Every file reader and writer: one door per format and direction, read_<fmt>(source) / write_<fmt>(sink, frame) (a source is a pathlib.Path, bytes or molrs.io.Text; a sink a pathlib.Path or a bytearray); each format's classes in its own submodule — the multi-frame <Fmt>Reader / <Fmt>Writer of io.pdb, io.xyz, io.gro, io.mol2, io.cif, io.sdf, io.dcd, io.trr, io.xtc, io.lammps, and the force-field reader / writer classes of io.lammps, io.gromacs, io.amber, io.openmm_xml; io.smiles, io.cgsmiles, io.mrec |
molrs.io.mrec |
*.mrec store pieces: MrecFile (per-section reads), streaming SequenceSchema, MrecWriter, MrecReader, ForceFieldSection, pack_mrec_zip, validation (a whole record is written by molrs.io.write_mrec) |
molrs.ff.* |
forcefield, potential, typifier, charge, ir, params, clpol_scaling |
molrs.optimize |
Lbfgs, OptimizationReport |
molrs.md |
Integrators and the MD driver |
molrs.compute |
One class per molrs::compute type, under its core name (flat): RDF, MSD, correlations, fits, spectra, order, clusters, … |
molrs.conformer |
3D generation |
molrs.perceive |
Rings, aromaticity, SMARTS, reactions |
molrs.builder |
Structure builders, site-graph assembly, Coarsener |
An analysis is configured when it is built and given its data when it
computes: Steinhardt(l=[6]) then .compute(...). The constructor takes
configuration only, every optional setting is None unless given (all
defaults live in the core; Msd.spec() lists them), and compute takes the
data as keyword arguments named after the core input's fields. Msd, Vacf
and Rdf are streams, as in the core: acc = Msd(max_lag).accumulator(),
acc.push(positions, dt=...) per frame, then acc.finish(). A result is a read-only object that the next compute accepts as is —
LinearFit(0.2, 0.8).compute(correlation=msd_result, channel=0).
Kernels take dt in the time unit of your trajectory, and time-valued
results come back in that unit. MSD needs unwrapped coordinates
(Unwrap produces them). VACF is the unbiased (C(\tau)) used for
Green–Kubo D and VDOS.
Development
maturin develop --release
pytest -q
Metadata
Release files for molcrafts-molrs 0.19.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| molcrafts_molrs-0.19.0-cp312-abi3-win_amd64.whl | CPython 3.12 | abi3 | Windows x86-64 | Details |
| molcrafts_molrs-0.19.0-cp312-abi3-pyemscripten_2026_0_wasm32.whl | CPython 3.12 | abi3 | PyEmscripten 2026.0+ WebAssembly | Details |
| molcrafts_molrs-0.19.0-cp312-abi3-manylinux_2_28_aarch64.whl | CPython 3.12 | abi3 | Linux glibc 2.28+ ARM64 | Details |
| molcrafts_molrs-0.19.0-cp312-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.12 | abi3 | Linux glibc 2.17+ x86-64 | Details |
| molcrafts_molrs-0.19.0-cp312-abi3-macosx_11_0_arm64.whl | CPython 3.12 | abi3 | macOS 11.0+ ARM64 | Details |
| molcrafts_molrs-0.19.0-cp312-abi3-macosx_10_12_x86_64.whl | CPython 3.12 | abi3 | macOS 10.12+ x86-64 | Details |
Total release size: 56.4 MB
Release files / molcrafts_molrs-0.19.0-cp312-abi3-win_amd64.whl
| Download URL | molcrafts_molrs-0.19.0-cp312-abi3-win_amd64.whl |
|---|---|
| Size | 11.3 MB |
| Tags | CPython 3.12 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
fa2bf11fd0881ea95642dfde52ed87b64b909378e004ae1fd320fffcc5dbd6f3
|
|
BLAKE2b-256 checksum How to use checksums |
0914ce900e59ed0eb14bc073e995ca4e3a90a98dd8e7f0e625bb8b968d3c6079
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 21, 2026.
Transparency logRelease files / molcrafts_molrs-0.19.0-cp312-abi3-pyemscripten_2026_0_wasm32.whl
| Download URL | molcrafts_molrs-0.19.0-cp312-abi3-pyemscripten_2026_0_wasm32.whl |
|---|---|
| Size | 4.3 MB |
| Tags | CPython 3.12 PyEmscripten 2026.0+ WebAssembly abi3 |
|
SHA-256 checksum How to use checksums |
8a513705ff5ad1fce70a38c8784f264cae34f816c562305f49493ea5719f4148
|
|
BLAKE2b-256 checksum How to use checksums |
2b025f104ca1349e4b43a6ecb84897928b26b248d186df119b0c536158e9b7cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 21, 2026.
Transparency logRelease files / molcrafts_molrs-0.19.0-cp312-abi3-manylinux_2_28_aarch64.whl
| Download URL | molcrafts_molrs-0.19.0-cp312-abi3-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 10.0 MB |
| Tags | CPython 3.12 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
5a432922a9f132209f0e4cf03d02175fa9442368fc16c7acae387ffc58fd98a0
|
|
BLAKE2b-256 checksum How to use checksums |
9ccc08649a3dcf71a57dc6d9e3526a9ca73852406b6e6dd28fe5048dee1c3e1b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 21, 2026.
Transparency logRelease files / molcrafts_molrs-0.19.0-cp312-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | molcrafts_molrs-0.19.0-cp312-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 10.9 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
c75a4ef041722d62055e84b727481d9510215255e48dcf44eed55b17f7d16b1d
|
|
BLAKE2b-256 checksum How to use checksums |
70f00acacc8f2b1f575965526baa3e14a4f43943bb3fe6d2cb0d6e9a9993037a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 21, 2026.
Transparency logRelease files / molcrafts_molrs-0.19.0-cp312-abi3-macosx_11_0_arm64.whl
| Download URL | molcrafts_molrs-0.19.0-cp312-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 9.6 MB |
| Tags | CPython 3.12 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
366990c3b6aa79e02bfd2a2f468287fdff43bc9b00f648131767eb2ab2d69e6d
|
|
BLAKE2b-256 checksum How to use checksums |
0fe25ce392174df96d3b7b3b245df0537ab2cee73674c61d3a546cbc57e25ffc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 21, 2026.
Transparency logRelease files / molcrafts_molrs-0.19.0-cp312-abi3-macosx_10_12_x86_64.whl
| Download URL | molcrafts_molrs-0.19.0-cp312-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 10.5 MB |
| Tags | CPython 3.12 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
fea202aefa7a0298c37cf4b2f1de0f80e5b364ef8f1143c78cc43f701bd42d34
|
|
BLAKE2b-256 checksum How to use checksums |
72dc1ed6f01790bd4a172e96226d2b54091bcee1f7b6d10b12c49fd6017b5391
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 21, 2026.
Transparency logSecurity for molcrafts-molrs 0.19.0
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 6 files in this release have been uploaded with provenance metadata.
Attestation for molcrafts_molrs-0.19.0-cp312-abi3-win_amd64.whl
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 Oct 21, 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.
