jVMC
This is an impementation of Variational Monte Carlo (VMC) for quantum many-body dynamics using the JAX library (and Flax on top) to exploit the blessings of automatic differentiation for easy model composition and just-in-time compilation for execution on accelerators.
Please report bugs as well as other issues or suggestions on our issues page.
Documentation
Documentation is available here.
Installation
Option 1: pip-install
pip install jVMC
To install jVMC with GPU support, use
pip install jVMC[gpu]
This is assuming, that jax[cuda12] will work for you (see the JAX documentation).
Option 2: Clone and pip-install for development
-
Clone the jVMC repository and check out the development branch:
git clone https://github.com/markusschmitt/vmc_jax.git cd vmc_jax -
pip-install the packagepip install -e ".[dev]"
Test that everything worked, e.g. run 'python -c "import jVMC"' from a place different than vmc_jax.
Online example
Click on the badge above to open a notebook that implements an exemplary ground state search in Google Colab.
Important gotchas
Out-of-memory issues and batching
Memory requirements grow with increasing network sizes. To avoid out-of-memory issues, the batchSize parameter of the NQS class has to be adjusted. The batchSize indicates on how many input configurations the network is evaluated concurrently. Out-of-memory issues are usually resolved by reducing this number. The numChains parameter of the Sampler class for Markov Chain Monte Carlo sampling plays a similar role, but its optimal values in terms of computational speed are typically not memory critical.
Citing jVMC
If you use the jVMC package for your research, please cite our reference paper SciPost Phys. Codebases 2 (2022)
@Article{jVMC,
title={{jVMC: Versatile and performant variational Monte Carlo leveraging automated differentiation and GPU acceleration}},
author={Markus Schmitt and Moritz Reh},
journal={SciPost Phys. Codebases},
pages={2},
year={2022},
publisher={SciPost},
doi={10.21468/SciPostPhysCodeb.2},
url={https://scipost.org/10.21468/SciPostPhysCodeb.2},
}
Metadata
Release files for jVMC 1.5.8
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 |
|---|---|---|---|---|
| jvmc-1.5.8.tar.gz | 50.1 kB | Without provenance | Details for jvmc-1.5.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jvmc-1.5.8-py3-none-any.whl | Python 3 | none | any | Details for jvmc-1.5.8-py3-none-any.whl |
Total release size: 109.8 kB
Release files / jvmc-1.5.8.tar.gz
| Download URL | jvmc-1.5.8.tar.gz |
|---|---|
| Size | 50.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b97a701c54ae890abfd40d433d253912c7ba5dba1d49c7f96947b52167ad8c8b
|
|
BLAKE2b-256 checksum How to use checksums |
7b5a19a1ed7ce7d01b123b9f34336543ae5e8f39f88dc5202c96b22aebb60dbc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.23
|
Release files / jvmc-1.5.8-py3-none-any.whl
| Download URL | jvmc-1.5.8-py3-none-any.whl |
|---|---|
| Size | 59.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fbceaa732f188bdbdca8f14299f5453a6b7062b9f4f24f8287f265c3e04ad22c
|
|
BLAKE2b-256 checksum How to use checksums |
ee76d007b6e483efa8750f5e486e91d03c063081f6ce2289074559fd05b4faaa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.23
|
Security for jVMC 1.5.8
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.