Cryoassess plugin
This plugin provides a wrapper for Cryoassess software tools for automatic micrograph and 2D classes assessment.
Installation
You will need to use 3.0+ version of Scipion to be able to run these protocols. To install the plugin, you have two options:
Stable version
scipion installp -p scipion-em-cryoassess
Developer’s version
download repository
git clone -b devel https://github.com/scipion-em/scipion-em-cryoassess.gitinstall
scipion installp -p /path/to/scipion-em-cryoassess --devel
Cryoassess software will be installed automatically with the plugin but you can also use an existing installation by providing CRYOASSESS_ENV_ACTIVATION (see below). You also have to download training models separately (see below).
Important: you need to have conda (miniconda3 or anaconda3) pre-installed to use this program.
Configuration variables
CONDA_ACTIVATION_CMD: If undefined, it will rely on conda command being in the PATH (not recommended), which can lead to execution problems mixing scipion python with conda ones. One example of this could can be seen below but depending on your conda version and shell you will need something different: CONDA_ACTIVATION_CMD = eval “$(/extra/miniconda3/bin/conda shell.bash hook)”
CRYOASSESS_ENV_ACTIVATION (default = conda activate cryoassess-1.0.0): Command to activate the cryoassess environment.
The deep-learning models can be downloaded from authors’ website and the folder with models is set with:
CRYOASSESS_MODELS (default = software/em/cryoassess-models)
Verifying
To check the installation, simply run the following Scipion test:
scipion test cryoassess.tests.test_protocols_cryoassess.TestCryoassess
Supported versions
1.0.0
Protocols
assess micrographs
assess 2D classes
References
High-Throughput Cryo-EM Enabled by User-Free Preprocessing Routines. Yilai Li, Jennifer N.Cash, John J.G. Tesmer, Michael A.Cianfrocco. Structure 2020, Volume 28 (7), Pages 858-869.e3
Metadata
Release files for scipion-em-cryoassess 3.4.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 |
|---|---|---|---|---|
| scipion_em_cryoassess-3.4.1.tar.gz | 24.5 kB | Without provenance | Details for scipion_em_cryoassess-3.4.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| scipion_em_cryoassess-3.4.1-py3-none-any.whl | Python 3 | none | any | Details for scipion_em_cryoassess-3.4.1-py3-none-any.whl |
Total release size: 53.8 kB
Release files / scipion_em_cryoassess-3.4.1.tar.gz
| Download URL | scipion_em_cryoassess-3.4.1.tar.gz |
|---|---|
| Size | 24.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a7b01e2535b3d9e580dace09c9591d6b304783147c8fc7e92193744285d65760
|
|
BLAKE2b-256 checksum How to use checksums |
5138a9c15ec979ddfc469165d8de5cf2aacb01292acfed44a0d3edea6531609e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.18
|
Release files / scipion_em_cryoassess-3.4.1-py3-none-any.whl
| Download URL | scipion_em_cryoassess-3.4.1-py3-none-any.whl |
|---|---|
| Size | 29.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7f51399437d7f18f693e5fc62f05e815ab09da3202be692e8a7ee13af5fd36e0
|
|
BLAKE2b-256 checksum How to use checksums |
11982d3ccefe2a4a8aeba29424ca7238f4209e3b89de7272589ee7a12de84af7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.18
|
Security for scipion-em-cryoassess 3.4.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.