Topaz plugin
This plugin allows to use Topaz programs within the Scipion framework. It can denoise, pre-process micrographs and pick particles within Scipion.
Topaz is a pipeline for particle detection in cryo-electron microscopy images which uses convolutional neural networks trained from positive and unlabeled examples.
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
It can be installed in user mode via Scipion plugin manager (Configuration > Plugins) or using the command line:
scipion installp -p scipion-em-topazDeveloper’s version
download repository
git clone -b devel https://github.com/scipion-em/scipion-em-topaz.gitinstall
scipion installp -p /path/to/scipion-em-topaz --devel
Topaz software will be installed automatically with the plugin but you can also use an existing installation by providing TOPAZ_ENV_ACTIVATION (see below).
Important: you need to have conda (miniconda3 or anaconda3) pre-installed to use this program.
To check the installation you can run the plugin’s tests:
scipion tests topaz.tests.test_protocol_topaz.TestTopaz
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)”
TOPAZ_ENV_ACTIVATION (default = conda activate topaz-0.2.5): Command to activate the Topaz environment.
Supported versions
0.2.3, 0.2.4, 0.2.5
Protocols
import training model
picking
training
References
Bepler, T. et al. Positive-unlabeled convolutional neural networks for particle picking in cryo-electron micrographs. arXiv (2018).
Metadata
Release files for scipion-em-topaz 3.1.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_em_topaz-3.1.2.tar.gz | 27.9 kB | Without provenance | Details for scipion_em_topaz-3.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| scipion_em_topaz-3.1.2-py3-none-any.whl | Python 3 | none | any | Details for scipion_em_topaz-3.1.2-py3-none-any.whl |
Total release size: 65.2 kB
Release files / scipion_em_topaz-3.1.2.tar.gz
| Download URL | scipion_em_topaz-3.1.2.tar.gz |
|---|---|
| Size | 27.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8ca19383cfebaf6f5797d9cb1cb5f99a58fdc894eba934a4b1c7996cf53802e4
|
|
BLAKE2b-256 checksum How to use checksums |
e47b0514a06062f667b31436fb1640ca44b86bad7ad6f22d3f9c12b69ff3c6fd
|
| 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_topaz-3.1.2-py3-none-any.whl
| Download URL | scipion_em_topaz-3.1.2-py3-none-any.whl |
|---|---|
| Size | 37.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7a6169792f1a57bd731d03f32d2eff344e4c80dcbc11caeeb245287f676fe6e0
|
|
BLAKE2b-256 checksum How to use checksums |
c54075b2964d13935b986622832b8321f52c2849d545ea94e3d6190d132766b6
|
| 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-topaz 3.1.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.