PathSimAnalysis
| Latest release | |
|---|---|
| Status | |
| Community |
Calculates the geometric similarity of molecular dynamics trajectories using path metrics such as the Hausdorff and Fréchet distances.
PathSimAnalysis is bound by a Code of Conduct.
Installation from packages
With conda from conda-forge
Ensure that you have conda installed.
You can install pathsimanalysis from the conda-forge channel with
conda install -c conda-forge pathsimanalysis
or alternatively with mamba if you have it installed:
mamba install -c conda-forge pathsimanalysis
Install from PyPI
The latest release of PathSimAnalysis is available on PyPI and can be installed with:
pip install pathsimanalysis
Installation from source
To build PathSimAnalysis from source,
we highly recommend using virtual environments.
If possible, we strongly recommend that you use
Anaconda as your package manager.
Below we provide instructions both for conda and
for pip.
With conda
Ensure that you have conda installed.
Create a virtual environment and activate it:
conda create --name pathsimanalysis
conda activate pathsimanalysis
Install the development and documentation dependencies:
conda env update --name pathsimanalysis --file devtools/conda-envs/test_env.yaml
conda env update --name pathsimanalysis --file docs/requirements.yaml
Build this package from source:
pip install -e .
If you want to update your dependencies (which can be risky!), run:
conda update --all
And when you are finished, you can exit the virtual environment with:
conda deactivate
With pip
To build the package from source, run:
pip install .
If you want to create a development environment, install the dependencies required for tests and docs with:
pip install ".[test,doc]"
Copyright
The PathSimAnalysis source code is hosted at https://github.com/MDAnalysis/pathsimanalysis and is available under the Lesser GNU Public Licence, v2.1 or any higher version (see the file LICENSE).
Copyright (c) 2023, MDAnalysis
Acknowledgements
Project based on the MDAnalysis Cookiecutter version 0.1. Please cite MDAnalysis when using PathSimAnalysis in published work.
Metadata
Release files for pathsimanalysis 1.2.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 | |
|---|---|---|---|
| pathsimanalysis-1.2.1.tar.gz | 44.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pathsimanalysis-1.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 82.3 kB
Release files / pathsimanalysis-1.2.1.tar.gz
| Download URL | pathsimanalysis-1.2.1.tar.gz |
|---|---|
| Size | 44.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d655409e7ca97a2391a64e2a1835e71d92d6dd375896fb028037b726f699faf5
|
|
BLAKE2b-256 checksum How to use checksums |
8adb6ea7d7e5d21678df8ed00201e1beb6a497cf7e82a9e5c843665ea39ff031
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Jul 23, 2026.
Transparency logRelease files / pathsimanalysis-1.2.1-py3-none-any.whl
| Download URL | pathsimanalysis-1.2.1-py3-none-any.whl |
|---|---|
| Size | 38.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
81e8d0d10278de1af7a13603dddf8c005dad80b9d9588314eeea03803a83f158
|
|
BLAKE2b-256 checksum How to use checksums |
53b6f907aaf02cb62e56df062452ccc278194365c732a70c90c335e7da81c889
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Jul 23, 2026.
Transparency log