pyMonteCarlo
pyMonteCarlo is a programming interface to run identical simulations using different Monte Carlo programs. The interface was designed to have common input and output that are independent of any Monte Carlo code. This allows users to combine the advantages of different codes and to compare the effect of different physical models without manually creating and running new simulations for each Monte Carlo program. The analysis of the results is also simplified by the common output format where results are expressed in the same units.
pyMonteCarlo is currently under development.
Documentation
The documentation contains the installation instructions, tutorials, supported Monte Carlo programs and API.
License
pyMonteCarlo is licensed under Apache Software License 2.0.
Citation
Pinard, P., Demers, H., Gauvin, R., & Richter, S. (2013). pyMonteCarlo: A Common Programming Interface for Running Identical Simulations using Different Monte Carlo Programs. Microscopy and Microanalysis, 19(S2), 822-823. doi:10.1017/S1431927613006107
@article{pinard2013,
author={Pinard, P.T. and Demers, H. and Gauvin, R. and Richter, S.},
title={pyMonteCarlo: A Common Programming Interface for Running Identical Simulations using Different Monte Carlo Programs},
journal={Microscopy and Microanalysis},
volume={19},
number={S2},
publisher={Cambridge University Press},
year={2013},
pages={822–823},
DOI={10.1017/S1431927613006107}
}
Build status
| Package | CI build | Code coverage |
|---|---|---|
| pymontecarlo | ||
| pymontecarlo-gui | ||
| pymontecarlo-casino2 | ||
| pymontecarlo-penepma | ||
| pypenelopetools |
Contributors
- Philippe T. Pinard (London, United Kingdom)
- Hendrix Demers (Montreal, Canada)
- Raynald Gauvin (McGill University, Montreal, Canada)
- Silvia Richter (RWTH Aachen University, Aachen, Germany)
Release notes
1.1.0
- Fix issues with newer releases of dependencies
Copyrights
Copyright (c) 2011 - 2016/06, Silvia Richter and Philippe Pinard
Copyright (c) 2016/06 - , Philippe Pinard
Metadata
Release files for pyMonteCarlo 1.1.0
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 | |
|---|---|---|---|---|
| pyMonteCarlo-1.1.0.tar.gz | 430.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyMonteCarlo-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 526.7 kB
Release files / pyMonteCarlo-1.1.0.tar.gz
| Download URL | pyMonteCarlo-1.1.0.tar.gz |
|---|---|
| Size | 430.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
20b8aa568da3eca66f6852f9bbed6dfade53c71b13c5297108579d5f27c4609a
|
|
BLAKE2b-256 checksum How to use checksums |
1f63b04b46dbbef4c1eac5ddcfbf179532087c6a8640e7d3af7a1763285ac4bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.8.2 pkginfo/1.8.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.7
|
Release files / pyMonteCarlo-1.1.0-py3-none-any.whl
| Download URL | pyMonteCarlo-1.1.0-py3-none-any.whl |
|---|---|
| Size | 96.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
678f44a58f42a2dd4cf34e6d375b7553ade60bedc3280cabb12edd3f4028f7d5
|
|
BLAKE2b-256 checksum How to use checksums |
c44aa5f1bc63813f7fef39786e02ae098d4392a4e5c546e87663c1c285bc7bde
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.8.2 pkginfo/1.8.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.7
|
Security for pyMonteCarlo 1.1.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.
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.