MINE Databases
The MINE Database contains code for generating (through Pickaxe) and storing and retrieving compounds from a database. Pickaxe applies reaction rules, representing reaction transformation patterns, to a list of user-specified compounds in order to predict reactions.
Documentation
For general information on MINE Databases, please consult JJeffryes et al. 2015..
Documentation is hosted at https://mine-database.readthedocs.io/en/latest/. It gives more detailed descriptions and example uses of the software.
Installation
If a conda environment is desired to be used:
conda create -n mine
conda activate mine
Then, use pip (with or without conda) to install minedatabase:
pip install minedatabase
Running Pickaxe
Running Pickaxe through a python file (recommended)
An example file, pickaxe_run_template.py, provides a framework for running pickaxe through a python file. Feel free to download it and change it to your needs. The starting compounds, rules and cofactors, optional database information, and Pickaxe run options are specified. After running the results are stored in a specified database or written to .tsv files.
This is all explained in more detail in the documentation.
Pickaxe command-line usage (not recommended - see above section)
Pickaxe.py can be called independently to generate predictions with or
without database storage. To list all options call python -m minedatabase.pickaxe -h. Note that due to relative imports, it needs to be run as a module (-m flag) from the MINE-Database directory. To predict metacyc reactions for one generation on compounds in the iML1515 model one would call
python pickaxe.py -C ./data/metacyc_generalized_rules.tsv -r ./data metacyc_coreactants.tsv -g 1 -c ../example_data/iML1515_ecoli_GEM.csv
Metadata
Release files for minedatabase 2.2.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 | Actions |
|---|---|---|---|---|
| minedatabase-2.2.0.tar.gz | 2.2 MB | Without provenance | Details for minedatabase-2.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| minedatabase-2.2.0-py3-none-any.whl | Python 3 | none | any | Details for minedatabase-2.2.0-py3-none-any.whl |
Total release size: 4.3 MB
Release files / minedatabase-2.2.0.tar.gz
| Download URL | minedatabase-2.2.0.tar.gz |
|---|---|
| Size | 2.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1e15c26971af93ecdaa0d34eb94b1214507bdf6f1deead0d2713329b6c70d223
|
|
BLAKE2b-256 checksum How to use checksums |
832739ec8eea6d0ff22c43608b559d48347b8a36355a15159d17127f9be44e18
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.6
|
Release files / minedatabase-2.2.0-py3-none-any.whl
| Download URL | minedatabase-2.2.0-py3-none-any.whl |
|---|---|
| Size | 2.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
79d927142617a80e746dbae1cf7d6195dedd8062e75cf0da2103a95e53d61cbf
|
|
BLAKE2b-256 checksum How to use checksums |
d910d4f3d5bfda64e5c78820d78a20795240b7a5ed909bed1fd66f415717443b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.6
|
Security for minedatabase 2.2.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.