cryoem-services
Services and configuration for cryo-EM pipelines.
This package consists of a number of services to process cryo-EM micrographs, both for single particle analysis and tomography, using a range of commonly used cryo-EM processing software. These services can be run independently to process data, or as part of a wider structure for performing live analysis during microscope collection. For live analysis, this package integrates with a package for transferring and monitoring collected data, Murfey, and a database for storing processing outcomes, ISPyB.
To run these services the software executables being called must be installed. These do not come with this package.
Tomography processing
The tomography processing pipeline consists of:
- Motion correction
- CTF estimation
- Tomogram alignment
- Tomogram denoising using Topaz
- Segmentation using membrain-seg
The results of this processing can be opened and continued using Relion 5.0.
Single particle analysis
The single particle analysis pipeline produces a project that can be opened and continued using CCP-EM doppio or Relion.
The processing pipeline consists of:
- Motion correction
- CTF estimation
- Particle picking
- (Optionally) Ice thickness estimation
- Particle extraction and rebatching
- 2D classification using Relion
- Automated 2D class selection using Relion
- 3D classification using Relion
- 3D Refinement and post-processing
- BFactor estimation by refinement with varying particle count
Services currently available
The following services are provided for running the pipelines:
- Utility services:
- ClusterSubmission: Submits wrapper scripts to an HPC cluster
- EMISPyB: Inserts results into an ISPyB database
- Images: Creates thumbnail images for viewing processing outcomes
- NodeCreator: Creates Relion project files for the services run
- ProcessRecipe: Converts recipes into messages suitable for processing services
- Processing services:
- BFactor: Performs the setup for 3D refinement with varying particle count
- CrYOLO: Particle picking on micrographs using crYOLO
- CTFFind: CTF estimation on micrographs using CTFFIND4
- DenoiseSlurm: Tomogram denoising, submitted to a slurm HPC cluster, using Topaz
- Extract: Extracts picked particles from micrographs
- ExtractClass: Extracts particles from a given 3D class
- IceBreaker: Ice thickness estimation with IceBreaker
- MembrainSeg: Tomogram segmentation, submitted to a slurm HPC cluster, using membrain-seg
- MotionCorr: Motion correction of micrographs using MotionCor2 or Relion, optionally submitted to a slurm HPC cluster
- PostProcess: Post-processing of 3D refinements using Relion
- SelectClasses: Runs automated 2D class selection using Relion and re-batches the particles from these classes
- SelectParticles: Creates files listing batches of extracted particles
- TomoAlign: Tomogram reconstruction from a list of micrographs using imod and AreTomo2
- TomoAlignSlurm: Tomogram alignment processing submitted to a slurm HPC cluster
There are also three wrapper scripts that can be run on an HPC cluster using the ClusterSubmission service. These perform 2D classification, 3D classification and 3D refinement using Relion.
Running services
The services in this package are run using
python-workflows.
They consume messages off a RabbitMQ
instance and processing happens in sequences defined by the recipes in the recipes folder.
To start a service run the cryoemservices.service command and specify the service name.
For example, to start a motion correction service:
$ cryoemservices.service -s MotionCorr -c config_file.yaml
The configuration file should contain the following:
rabbitmq_credentials: <file with connection credentials to rabbitmq>
recipe_directory: <directory containing the recipes to run>
ispyb_credentials: <(Optionally) file with credentials for an ispyb database>
slurm_credentials:
default: <(Optionally) credentials for a slurm RestAPI>
graylog_host: <(Optionally) the name of a graylog instance>
graylog_port: <(Optionally) the port used by graylog>
Once started, these services will initialise and then wait for messages to be sent to them.
Messages are sent through a message broker,
currently RabbitMQ is supported using pika transport in python-workflows.
Individual processing stages can be run by sending a dictionary of the parameters,
but the processing pipelines are designed to run through recipes.
A recipe is a specication of a series of steps to carry out,
and how these steps interact with each other.
Recipes for the current processing pipelines are provided in the recipes folder.
To run a recipe in python a dictionary needs to be provided consisting of the recipe name and the parameters expected by the recipe. The following snippet shows an example of the setup needed. This will send a message to a running ProcessRecipe service which prepares the recipe for the processing services.
import workflows.transport.pika_transport as pt
example_message = {
"recipes": ["em-tomo-align"],
"parameters": {
"path_pattern": "micrograph_*.mrc",
"pix_size": "1",
...
},
}
transport = pt.PikaTransport()
transport.connect()
transport.send("processing_recipe", example_message)
Release files for cryoemservices 1.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 | |
|---|---|---|---|
| cryoemservices-1.4.1.tar.gz | 183.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cryoemservices-1.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 424.1 kB
Release files / cryoemservices-1.4.1.tar.gz
| Download URL | cryoemservices-1.4.1.tar.gz |
|---|---|
| Size | 183.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c9994708b445bd41da77f14d1e088cec07e78353517910c5a042fcb49cd55731
|
|
BLAKE2b-256 checksum How to use checksums |
dad64c81a8bd256320d5c2f231f46ce8521aa5eabb42fcbf7dbeb027549c0e59
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 4, 2026.
Transparency logRelease files / cryoemservices-1.4.1-py3-none-any.whl
| Download URL | cryoemservices-1.4.1-py3-none-any.whl |
|---|---|
| Size | 240.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
58ea057d98bc4833c01a1bc2ac4ece0a8917b663e6958af4f913763ad25180a8
|
|
BLAKE2b-256 checksum How to use checksums |
1b956276209bb169e4ab99a91c104d40d982f5eb00749ba6ef3e625210964c73
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 4, 2026.
Transparency log
