Scipion plugin for cryoCARE
This plugin allows to use cryoCARE -trains a denoising U-Net for tomographic reconstruction according to the Noise2Noise training paradigm- tomography methods into Scipion framework.
Installation
The plugin can be installed in user (stable) or developer (latest, may be unstable) mode:
1. User (stable) version::
scipion3 installp -p scipion-em-cryocare
2. Developer (latest, may be unstable) version::
Clone the source code repository:
git clone https://github.com/scipion-em/scipion-em-cryocare.git
Install:
scipion3 installp -p local/path/to/scipion-em-cryocare --devel
Protocols
The integrated protocols are:
Load a previously trained model.
Generate the training data.
Training: uses two data-independent reconstructed tomograms to train a 3D cryoCARE network.
4. Predict: generates the final restored tomogram by applying the cryoCARE trained network to both even/odd tomograms followed by per-pixel averaging.
Tests
The installation can be checked out running some tests. To list all of them, execute:
scipion3 tests --grep cryocare
To run all of them, execute:
scipion3 tests --grep cryocare --run
Tutorial
The test generates a cryoCARE workflow that can be used as a guide about how to use cryoCARE. The even/odd tomograms required to use cryoCARE can be generated inside Scipion with:
Plugin scipion-em-motioncorr: protocol “align tilt-series movies”.
Plugin scipion-em-xmipptomo: protocol “tilt-series flexalign”.
References
Cryo-CARE: Content-Aware Image Restoration for Cryo-Transmission Electron Microscopy Data. Tim-Oliver Buchholz et al., 2019 IEEE 16th International Symposium on Biomedical Imaging (ISBI 2019).
Contact information
If you experiment any problem, please contact us here: scipion-users@lists.sourceforge.net or open an issue.
We’ll be pleased to help.
Scipion Team
Metadata
Release files for scipion-em-cryocare 4.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 |
|---|---|---|---|---|
| scipion_em_cryocare-4.2.4.tar.gz | 58.0 kB | Without provenance | Details for scipion_em_cryocare-4.2.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| scipion_em_cryocare-4.2.4-py3-none-any.whl | Python 3 | none | any | Details for scipion_em_cryocare-4.2.4-py3-none-any.whl |
Total release size: 119.6 kB
Release files / scipion_em_cryocare-4.2.4.tar.gz
| Download URL | scipion_em_cryocare-4.2.4.tar.gz |
|---|---|
| Size | 58.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
712ce9e6d5bcf2abee59a774a71964ce03f35616820f8d12a924a78193e3d44d
|
|
BLAKE2b-256 checksum How to use checksums |
ee0b2a7f69fc497c986a06eab68a957e5e761f82c5cf5ec921fd0289d91152d4
|
| 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_cryocare-4.2.4-py3-none-any.whl
| Download URL | scipion_em_cryocare-4.2.4-py3-none-any.whl |
|---|---|
| Size | 61.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4698420f980bb0275bffabe53c140fa619c9b1e66225146d3148f89e72670226
|
|
BLAKE2b-256 checksum How to use checksums |
1fbb73057d80b26f3c9d7d546c7f521197358eec9831aaf50eeeef0c856c91db
|
| 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-cryocare 4.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.