RRParser
Reaction Rules Parser. If no input reaction files is provided, retrieves the reaction rules from RetroRules.
Input
- rules-file: (string) Filename of reaction rules
- input-format: (string) Valid options: csv, tsv. Format of the input file
- rule-type: (string) Valid options: retro, forward, all. Return the rules that are in reverse, forward or both direction
- outdir: (string) Path where output files will be written
- diameters: (integer list) Valid options: 2, 4, 6, 8, 10, 12, 14, 16. The diameter of the rules to return
- output-format: (string) Valid options: csv, tar.gz. Format of the returned file
Ouput
- output: (string): Path of the output file. Either a compressed tar.gz (containing a csv) or csv list of reaction rules that are in a RetroPath2.0 friendly format
Install
From pip
[sudo] python -m pip install rrparser
From Conda
[sudo] conda install -c brsynth rrparser
Use
Function call from Python code
from rrparser import Parser
outfile = Parser().parse_rules(rule_type, outdir, diameters)
If parameters from CLI have to be parsed, the function build_args_parser is available:
from rrparser import build_args_parser
parser = buildparser()
params = parser.parse_args()
Run from CLI
python -m rrparser.main \
[--rules-file <filename>] \
[--input-format {csv,tsv}] \
[--rule-type {all,retro,forward}] \
--output <folder> \
[--diameters {2,4,6,8,10,12,14,16}] \
--output-format {csv,tar.gz}
Authors
- Thomas Duigou
- Melchior du Lac
- Joan Hérisson
License
This project is licensed under the MIT License - see the LICENSE file for details
How to cite RetroRules?
Please cite:
Duigou, Thomas, et al. "RetroRules: a database of reaction rules for engineering biology." Nucleic acids research 47.D1 (2019): D1229-D1235.
Metadata
Release files for rrparser 2.0.5
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 |
|---|---|---|---|---|
| rrparser-2.0.5.tar.gz | 5.8 kB | Without provenance | Details for rrparser-2.0.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rrparser-2.0.5-py3-none-any.whl | Python 3 | none | any | Details for rrparser-2.0.5-py3-none-any.whl |
Total release size: 12.1 kB
Release files / rrparser-2.0.5.tar.gz
| Download URL | rrparser-2.0.5.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1fd035bdfc473f05fbe2e6cd4254a1227b9dcf4340ed146966f4163886866dcc
|
|
BLAKE2b-256 checksum How to use checksums |
e3f36391a26e96c6c461133fdc0f87ab28d9ea769afc108785175e97962d8a89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/47.1.0 requests-toolbelt/0.9.1 tqdm/4.49.0 CPython/3.8.5
|
Release files / rrparser-2.0.5-py3-none-any.whl
| Download URL | rrparser-2.0.5-py3-none-any.whl |
|---|---|
| Size | 6.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fa0cc67875e10293e7189e07aee2960040e70673db777105c598c34820c9aa85
|
|
BLAKE2b-256 checksum How to use checksums |
e1e52b272fabae54303d8a4fc7ece84a2147b9e663ca864ad5a31ef9e6c1f0ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/47.1.0 requests-toolbelt/0.9.1 tqdm/4.49.0 CPython/3.8.5
|
Security for rrparser 2.0.5
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.