MolVS: Molecule Validation and Standardization
MolVS is a molecule validation and standardization tool, written in Python using the RDKit chemistry framework.
Building a collection of chemical structures from different sources can be difficult due to differing representations, drawing conventions and mistakes. MolVS can standardize chemical structures to improve data quality, help with de-duplication and identify relationships between molecules.
There are sensible defaults that make it easy to get started:
>>> from molvs import standardize_smiles
>>> standardize_smiles('[Na]OC(=O)c1ccc(C[S+2]([O-])([O-]))cc1')
'[Na+].O=C([O-])c1ccc(CS(=O)=O)cc1'
Installation
To install MolVS with Anaconda Oython, simply run:
conda install molvs
Alternatively, try one of the other installation options.
Documentation
Full documentation is available at http://molvs.readthedocs.io.
Contribute
Feature ideas and bug reports are welcome on the Issue Tracker.
Fork the source code on GitHub, make changes and send a pull request.
License
MolVS is licensed under the MIT license.
Similar projects
There are a number of projects with similar goals that take differing approaches:
1 maintainer
Metadata
1 maintainer
Release files for MolVS 0.1.1
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 |
|---|---|---|---|---|
| MolVS-0.1.1.tar.gz | 61.9 kB | Without provenance | Details for MolVS-0.1.1.tar.gz |
Release files / MolVS-0.1.1.tar.gz
| Download URL | MolVS-0.1.1.tar.gz |
|---|---|
| Size | 61.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3679713d95774f69625e42b7e83b161be48df8d994768ba2786440f085497474
|
|
BLAKE2b-256 checksum How to use checksums |
08dcd948e83b97f2c420cb6c7e2143ae349560d3b5b061945f1b2a4eefb0231c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for MolVS 0.1.1
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.
