Toxicity prediction of small ligands scipion plugin
Documentation under development, sorry for the inconvenience Scipion framework plugin for the use of toxCSM software tool.
Install this plugin
You will need to use Scipion3 to run these protocols.
Install the stable version
Through the plugin manager GUI by launching Scipion and following Others >> Plugin Manager
or
scipion3 installp -p scipion-chem-toxCSM
Developer’s version
Download repository:
git clone https://github.com/scipion-chem/scipion-chem-toxCSM.git
Install:
scipion3 installp -p /path/to/scipion-chem-toxCSM --devel
Protocols
This plugin contains the following protocols:
None for now
Packages & enviroments
Packages installed by this plugin can be located in /path/to/scipion/software/em/.
As of today, Scipion does not automatically uninstall the conda enviroments created in the installation process when uninstalling a plugin, so keep this list in mind if you want to clean up some disk space if you need to uninstall this one.
Changelog
All the recent version changes can be found here.
1 maintainer
Metadata
1 maintainer
Release files for scipion-chem-toxcsm 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 |
|---|---|---|---|---|
| scipion_chem_toxcsm-0.2.tar.gz | 20.3 kB | Without provenance | Details for scipion_chem_toxcsm-0.2.tar.gz |
Release files / scipion_chem_toxcsm-0.2.tar.gz
| Download URL | scipion_chem_toxcsm-0.2.tar.gz |
|---|---|
| Size | 20.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b56b255117cd95968bbbe4d7f3d9cac089e73581aa6407f0a3b04b8ac1786194
|
|
BLAKE2b-256 checksum How to use checksums |
9544e736c3de8552e9d052279551c763647cab016c4bc6e75fd1d8a27bff05fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for scipion-chem-toxcsm 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.
