A Python program for automating transition path sampling with aimless shooting, suitable for experts and novices alike.
Full documentation available here. ATESA has been published in the Journal of Chemical Theory and Computation, here. Please cite this paper in any work making use of ATESA.
ATESA automates a particular Transition Path Sampling (TPS) workflow that uses the flexible-length aimless shooting algorithm of Mullen et al. 2015. ATESA interacts directly with a batch system or job manager to dynamically submit, track, and interpret various simulation and analysis jobs based on one or more initial structures provided to it. The flexible-length implementation periodically checks simulations for commitment to user-defined reactant and product states in order to maximize the acceptance ratio and minimize wasted computational resources.
ATESA implements automation for obtaining a suitable initial transition state, flexible-length aimless shooting, inertial likelihood maximization, committor analysis, umbrella sampling (and analysis with the Multistate Bennett Acceptance Ratio), and equilibrium path sampling. These components constitute a near-complete automation of the workflow between identifying the reaction of interest, and obtaining, validating, and analyzing the energy profile along an unbiased and bona fide reaction coordinate that describes it.
At present, ATESA only supports simulations with Amber and CP2K, and TORQUE/PBS or Slurm batch schedulers. If you are interested in using ATESA with another simulation engine or batch scheduler, please raise an "enhancement" issue describing your needs.
Copyright
Copyright © 2022, Tucker Burgin
Acknowledgements
Project based on the Computational Molecular Science Python Cookiecutter version 1.1.
Special thanks to Samuel Ellis and the Molecular Sciences Software Institute (MolSSI).
Metadata
Release files for atesa 1.0.2
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 |
|---|---|---|---|---|
| atesa-1.0.2.tar.gz | 39.6 MB | Without provenance | Details for atesa-1.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| atesa-1.0.2-py3-none-any.whl | Python 3 | none | any | Details for atesa-1.0.2-py3-none-any.whl |
Total release size: 79.7 MB
Release files / atesa-1.0.2.tar.gz
| Download URL | atesa-1.0.2.tar.gz |
|---|---|
| Size | 39.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9a4a75e4e574bc05c9007f8217179ed84358b3342ffbf89f1c2e271ce6ce2a77
|
|
BLAKE2b-256 checksum How to use checksums |
d53f5721ea0da659beca3bc33d327be810f2294ca9e3e77dae789a8e4e8b60ed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.8
|
Release files / atesa-1.0.2-py3-none-any.whl
| Download URL | atesa-1.0.2-py3-none-any.whl |
|---|---|
| Size | 40.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
19d66cd62602b380b2bb5ba948c54b1fcda0a67928182d49ae1a770086d79c7c
|
|
BLAKE2b-256 checksum How to use checksums |
b2b6b0fc189033f0fda0b001e9b2d3bf03e4f592f1dc9721ac8e6a6f60f1b486
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.8
|
Security for atesa 1.0.2
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.