This release is a pre-release and may not be stable for production use.
run_brer
This project is hosted in a git repository at https://github.com/kassonlab/run_brer
Project documentation is available in the repository or at https://kassonlab.github.io/run_brer/.
The run_brer Python package provides a set of scripts for running BRER simulations using gmxapi.
Details of this method may be found in:
Hays, J. M., Cafiso, D. S., & Kasson, P. M. Hybrid Refinement of Heterogeneous Conformational Ensembles using Spectroscopic Data. The Journal of Physical Chemistry Letters. DOI: 10.1021/acs.jpclett.9b01407
Installation
Requirements
If you're going to use a pip or a conda environment, you'll need:
-
Python 3.X
-
gmxapi for GROMACS 2019 or newer.
- Install GROMACS 2019 and gmxapi 0.0.7, or
- Install current GROMACS and gmxapi >= 0.1
-
The plugin code for BRER.
Otherwise, you can just use a Singularity container!
Singularity
By far the easiest option!
If you have the latest and greatest Singuarity (v > 3), you can pull the container from the cloud repository:
singularity pull library://kassonlab/default/brer:latest
For instructions on using the container, please see the singularity-brer repository.
Conda environment
I suggest running this in a conda environment rather than pip install . The following conda command will handle all the gmxapi and sample_restraint python dependencies, as well as the ones for this repository.
-
conda create -n BRER numpy scipy networkx setuptools mpi4py cmakeIf you want to run the tests, then install
pytestas well. -
Source the environment and then
pip install:
source activate BRER
git clone https://github.com/kassonlab/run_brer.git
cd run_brer
pip install .
Running BRER
Launching a single ensemble member.
An example script, run.py , is provided for ensemble simulations.
Let's work through it piece by piece.
#!/usr/bin/env python
"""
Example run script
for BRER simulations
"""
import run_brer.run_config as rc
import sys
The import run_brer.run_config statement imports a RunConfig object, which handles the following things for a single ensemble member:
- Initializing/setting up parameters for the BRER run.
- Launching the run.
Then we provide some files and directory paths to the RunConfig object.
init = {
'tpr': '/home/jennifer/Git/run_brer/tests/syx.tpr',
'ensemble_dir': '/home/jennifer/test-brer',
'ensemble_num': 5,
'pairs_json': '/home/jennifer/Git/run_brer/tests/pair_data.json'
}
config = rc.RunConfig(**init)
In order to run a BRER simulation, we need to provide :
- a
tpr(compatible with GROMACS 2019). - The path to our ensemble. This directory should contain subdirectories of the form
mem_<my ensemble number> - The ensemble number. This is an integer used to identify which ensemble member we are running and thus, the subdirectory in which we will be running our simulations.
- The path to the DEER metadata. Please see the example json in this repository:
run_brer/data/pair_data.json
Finally, we launch the run!
config.run()
You may change various parameters before launching the run using config.set(**kwargs) . For example:
config = rc.RunConfig(**init)
config.set(A=100)
config.run()
resets the energy constant A to 100 kcal/mol/nm^2 before launching a run.
Launching an ensemble
Right now, the way to launch an ensemble is to launch multiple jobs. We hope to soon use the gmxapi features that allow a user to launch many ensemble members in one job.
Metadata
Release files for run-brer 2.0.0b2
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 |
|---|---|---|---|---|
| run_brer-2.0.0b2.tar.gz | 5.2 MB | Without provenance | Details for run_brer-2.0.0b2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| run_brer-2.0.0b2-py3-none-any.whl | Python 3 | none | any | Details for run_brer-2.0.0b2-py3-none-any.whl |
Total release size: 10.3 MB
Release files / run_brer-2.0.0b2.tar.gz
| Download URL | run_brer-2.0.0b2.tar.gz |
|---|---|
| Size | 5.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
81b51257b60f8cd81be8305fb705ae92aff37d66bef597407d9c4a48b836157f
|
|
BLAKE2b-256 checksum How to use checksums |
216904253adaedfa5d1c62360b1826a78f6f568b2d24b819e82bb4ca44eabe6d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.7.7
|
Release files / run_brer-2.0.0b2-py3-none-any.whl
| Download URL | run_brer-2.0.0b2-py3-none-any.whl |
|---|---|
| Size | 5.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
84f71265db070d11209d6a827a1ba745be363b866bad9b035d4e0443e449fcae
|
|
BLAKE2b-256 checksum How to use checksums |
88910a06a558fecbce67cec4c6d227d84214ad386dd9e19bbeedab4ecc897af4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.7.7
|
Security for run-brer 2.0.0b2
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.