Skip to main content

cryoRIDGE

RIDGE = Reliability Inferred from Density Gradient Energy

PyPI version License: MIT

Local reliability scores and build zones for cryo-EM maps from half-maps and density features. Python 3.10+.

image
pip install cryoridge
cryoridge          # interactive: two half-map paths → two MRC outputs
cryoridge help     # CLI reference

Interactive mode asks for half-map 1 and half-map 2, prompts you to set the contour in ChimeraX, warns when estimated resolution is outside the model-building band (>4 Å), then writes {stem}_reliability.mrc and {stem}_build_zones.mrc under cryoridge_out/ next to half-map 1.

Pipeline (non-interactive / advanced)

Three commands, in order. Pass your own map paths and output directories.

# 1. Features from a map (.mrc / .map)
cryoridge features map.mrc --out features.npz --float32

# 2. Half-map metrics + correlations
cryoridge analyze \
  --features features.npz \
  --half1 half1.map --half2 half2.map \
  --reference ref.map \
  --contour CONTOUR \
  --out-dir analysis_out

# 3. Reliability score + build-zone MRCs
cryoridge reliability \
  --reference ref.map --half1 half1.map --half2 half2.map \
  --features features.npz \
  --contour CONTOUR \
  --out-dir reliability_out

--contour is the density threshold for the analysis mask (same value in steps 2 and 3). Step 2 (analyze) is optional if you only need the reliability and build-zone MRCs.

Reliability outputs: {label}_reliability.mrc and {label}_build_zones.mrc on your reference grid.

Flag details: cryoridge features --help, cryoridge analyze --help, cryoridge reliability --help.

HPC (ARC)

Default login python3 is too old (3.6). Conda modules load on compute nodes only:

srun -p compute1 -n 1 -t 02:00:00 --pty bash
module load miniconda/24.4.0
conda activate cryoridge    # after one-time: conda create -n cryoridge python=3.12 -y && pip install cryoridge

Batch job — copy scripts/cryoridge_cluster.sbatch.example, set MAP, HALF1, HALF2, REF, CONTOUR, and submit. Each step aborts if the previous one fails.

cp scripts/cryoridge_cluster.sbatch.example run_my_map.sbatch
# edit paths in run_my_map.sbatch
sbatch run_my_map.sbatch

If install fails with empty (from versions:), check python --version (need ≥3.10) and pip install -U pip.

Citation

@software{mohanty2026cryoridge,
  author = {Mohanty, Sarthak},
  title = {cryoRIDGE: Reliability Inferred from Density Gradient Energy},
  year = {2026},
  doi = {10.5281/zenodo.20618526},
  url = {https://doi.org/10.5281/zenodo.20618526},
  version = {0.8.3}
}

MIT — see LICENSE.

Release files for cryoridge 0.8.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for cryoridge 0.8.3
File Size Uploaded
cryoridge-0.8.3.tar.gz 125.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for cryoridge 0.8.3
File Interpreter ABI Platform
cryoridge-0.8.3-py3-none-any.whl Python 3 none any Details

Total release size: 243.8 kB

Release files / cryoridge-0.8.3.tar.gz

Download URL cryoridge-0.8.3.tar.gz
Size 125.0 kB
Tags Source
SHA-256 checksum
How to use checksums
7e13e3671e9b81f8c9044092419cae0e248f574bad1a0e5203f8c5ac09cfe031
BLAKE2b-256 checksum
How to use checksums
cea3297ae9457a49646350ee0f9e9683ef2b5d829d29858a1d726aaa5251cd9d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 7, 2026.

Transparency log

Release files / cryoridge-0.8.3-py3-none-any.whl

Download URL cryoridge-0.8.3-py3-none-any.whl
Size 118.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
61f8b2c888ecceb4f74b9c887024bd9dc63673430d6616dc24ba13eb7372ba2d
BLAKE2b-256 checksum
How to use checksums
efc4dac12aa31980a06598fe940931a3a9db79b339448f10dca1201edc3ff14c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 7, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.8.3 This release

2 release files

0.8.2

2 release files

0.8.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page