countparticles
Report the number of particles in each class from a run_data.star file
produced by RELION.
A single-particle cryo-EM reconstruction comes from a set of particle images
corresponding to projections of identical particles in different orientations.
All datasets are heterogeneous, to various degrees, and data analysis involves
classification of particle images. Knowing how many particles contributed to
any given class is important to decide how to follow up after a classification
job. This command-line tool reports a count of particles in each class in a
run_it???_data.star file from a RELION Class2D or Class3D job. It can also
optionally produce a bar plot of these particle counts.
This tool was tested with star files produced by RELION-3.1.0. Earlier versions of RELION are not supported.
Acknowledgments
I would not have been able to put this tool together without the
starfile library.
Installation
I recommend to install this tool in a dedicated conda environment. You can
create one like so (replace ENV_NAME with the name you want to give to this
environment):
$ conda deactivate
$ conda create --name ENV_NAME python=3.9
$ conda activate ENV_NAME
Once the conda environment is active, you can install the tool with the following command:
$ pip install countparticles
Usage
$ countparticles --help
Usage: countparticles [OPTIONS] <run_data.star>
Report the number of particles in each class from a run_data.star file
produced by RELION.
Options:
-p, --plot Optional. Display a bar plot of the particle counts. This
is most helpful with only a few classes, e.g. for typical
Class3D results (but not for typical Class2D results with
many classes).
-o, --output TEXT Optional. File name to save the barplot (recommended file
formats: .png, .pdf, .svg or any format supported by
matplotlib). This option has no effect without the
-p/--plot option.
-h, --help Show this message and exit.
Metadata
Release files for countparticles 1.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 |
|---|---|---|---|---|
| countparticles-1.4.tar.gz | 4.6 kB | Without provenance | Details for countparticles-1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| countparticles-1.4-py3-none-any.whl | Python 3 | none | any | Details for countparticles-1.4-py3-none-any.whl |
Total release size: 9.5 kB
Release files / countparticles-1.4.tar.gz
| Download URL | countparticles-1.4.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c1d91ca86c631e429b0759b54722403f7b0903477b853c7db8655fe4abd5af1f
|
|
BLAKE2b-256 checksum How to use checksums |
b65981bd87496298d747c35577f099ee9d8b4aa59bbe15af414176418a2be8e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Release files / countparticles-1.4-py3-none-any.whl
| Download URL | countparticles-1.4-py3-none-any.whl |
|---|---|
| Size | 4.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c120c7c76f9942558d1a40e6fc2a224fc575b67c48e4602dc7df2b292dd15471
|
|
BLAKE2b-256 checksum How to use checksums |
ae275809cac1fcfd2dfa9b248b222e16b8bef63e620d92003c7d0614258f167b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Security for countparticles 1.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.