ChEMBL Structure Pipeline
ChEMBL protocols used to standardise and salt strip molecules. First used in ChEMBL 26.
Check the wiki and paper[1] for a detailed description of the different processes.
Installation
From source:
git clone https://github.com/chembl/ChEMBL_Structure_Pipeline.git
pip install ./ChEMBL_Structure_Pipeline
with pip:
pip install chembl_structure_pipeline
with conda:
conda install -c conda-forge chembl_structure_pipeline
Usage
Standardise a compound (info)
from chembl_structure_pipeline import standardizer
o_molblock = """
Mrv1810 07121910172D
4 3 0 0 0 0 999 V2000
-2.5038 0.4060 0.0000 C 0 0 3 0 0 0 0 0 0 0 0 0
-2.5038 1.2310 0.0000 O 0 5 0 0 0 0 0 0 0 0 0 0
-3.2182 -0.0065 0.0000 N 0 3 0 0 0 0 0 0 0 0 0 0
-1.7893 -0.0065 0.0000 C 0 0 0 0 0 0 0 0 0 0 0 0
1 2 1 0 0 0 0
1 3 1 0 0 0 0
1 4 1 4 0 0 0
M CHG 2 2 -1 3 1
M END
"""
std_molblock = standardizer.standardize_molblock(o_molblock)
Get the parent compound (info)
from chembl_structure_pipeline import standardizer
o_molblock = """
Mrv1810 07121910262D
3 1 0 0 0 0 999 V2000
-5.2331 1.1053 0.0000 C 0 0 0 0 0 0 0 0 0 0 0 0
-4.5186 1.5178 0.0000 N 0 3 0 0 0 0 0 0 0 0 0 0
-2.8647 1.5789 0.0000 Cl 0 5 0 0 0 0 0 0 0 0 0 0
1 2 1 0 0 0 0
M CHG 2 2 1 3 -1
M END
"""
parent_molblock, _ = standardizer.get_parent_molblock(o_molblock)
Check a compound (info)
The checker assesses the quality of a structure. It highlights specific features or issues in the structure that may need to be revised. Together with the description of the issue, the checker process returns a penalty score (between 0-9) which reflects the seriousness of the issue (the higher the score, the more critical is the issue)
from chembl_structure_pipeline import checker
o_molblock = """
Mrv1810 02151908462D
4 3 0 0 0 0 999 V2000
2.2321 4.4196 0.0000 C 0 0 0 0 0 0 0 0 0 0 0 0
3.0023 4.7153 0.0000 C 0 0 0 0 0 0 0 0 0 0 0 0
1.4117 4.5059 0.0000 O 0 0 0 0 0 0 0 0 0 0 0 0
1.9568 3.6420 0.0000 C 0 0 0 0 0 0 0 0 0 0 0 0
1 2 1 1 0 0 0
1 3 1 0 0 0 0
1 4 1 0 0 0 0
M END
"""
issues = checker.check_molblock(o_molblock)
References
[1] Bento, A.P., Hersey, A., Félix, E. et al. An open source chemical structure curation pipeline using RDKit. J Cheminform 12, 51 (2020). https://doi.org/10.1186/s13321-020-00456-1
Metadata
Release files for chembl-structure-pipeline 1.2.4
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 |
|---|---|---|---|---|
| chembl_structure_pipeline-1.2.4.tar.gz | 16.2 kB | Without provenance | Details for chembl_structure_pipeline-1.2.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| chembl_structure_pipeline-1.2.4-py3-none-any.whl | Python 3 | none | any | Details for chembl_structure_pipeline-1.2.4-py3-none-any.whl |
Total release size: 33.5 kB
Release files / chembl_structure_pipeline-1.2.4.tar.gz
| Download URL | chembl_structure_pipeline-1.2.4.tar.gz |
|---|---|
| Size | 16.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e381500ac815ded31cc4841d1fbfe7c089788a07f2fbaa9bb818b52facfa9030
|
|
BLAKE2b-256 checksum How to use checksums |
56294ce697880f4b239dc96e89c371d7a86c43cd08e3f9b54c375510f49f19d8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / chembl_structure_pipeline-1.2.4-py3-none-any.whl
| Download URL | chembl_structure_pipeline-1.2.4-py3-none-any.whl |
|---|---|
| Size | 17.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1bb5121b3714d564610c55e39e214ae6409001d0a50bb48a00831b3f5573c479
|
|
BLAKE2b-256 checksum How to use checksums |
005cb9d714ff6381793e811ef96daa744350e1c5f233e0f15044e1f6160aeeaa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for chembl-structure-pipeline 1.2.4
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.