chemo_sanitizer
A set of script using RDKit and MolVS to proceed to the standardization , sanitization and different format conversion. Parallelized.
In this state it take only InChI as inputs and returns sanitized SMILES, InChI, InChIKeys, Short InChIkeys, MolecularFormula, ExactMass and XLogP.
Requirements
Install the conda environment by
conda env create -f environment.yml
Specific requirement
Note that some modules of MolVS are not loaded by default. You will need to edit the MolVS init.py in ~/opt/anaconda3/lib/python3.7/site-packages/molvs/ accordingly. Add these lines to the init.py
from .fragment import LargestFragmentChooser, FragmentRemover
from .charge import Uncharger
Usage
Go to the src folder Then add input and output file path as first and second argument, InChI column header as third argument and finally the number of cpus you want to use.
Example :
cd src
python chemosanitizer.py ~/translatedStructureRdkit.tsv ./test.tsv structureTranslated 6
Metadata
Release files for chemosanitizer 0.0.2
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 |
|---|---|---|---|---|
| chemosanitizer-0.0.2.tar.gz | 9.2 kB | Without provenance | Details for chemosanitizer-0.0.2.tar.gz |
Release files / chemosanitizer-0.0.2.tar.gz
| Download URL | chemosanitizer-0.0.2.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
92e46fa5a7763a3d97585c91b9fd887e2fa2d3f34428feb57d00da7838b84f31
|
|
BLAKE2b-256 checksum How to use checksums |
bece5df5d5c3436eaafe1a3940a29fdcebb2e1fbd522ac77838f739f3b2a4a99
|
| 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/49.2.0.post20200714 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.8.3
|
Security for chemosanitizer 0.0.2
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.