OCTOPI 🐙🐙🐙
Object deteCTion Of ProteIns. A deep learning framework for Cryo-ET 3D particle picking with autonomous model exploration capabilities.
🚀 Introduction
octopi addresses a critical bottleneck in cryo-electron tomography (cryo-ET) research: the efficient identification and extraction of proteins within complex cellular environments. As advances in cryo-ET enable the collection of thousands of tomograms, the need for automated, accurate particle picking has become increasingly urgent.
Our deep learning-based pipeline streamlines the training and execution of 3D autoencoder models specifically designed for cryo-ET particle picking. Built on copick, a storage-agnostic API, octopi seamlessly accesses tomograms and segmentations across local and remote environments.
🧩 Core Features
- 3D U-Net Training: Train and evaluate custom 3D U-Net models for particle segmentation
- Automatic Architecture Search: Explore optimal model configurations using Bayesian optimization via Optuna
- Flexible Data Access: Seamlessly work with tomograms from local storage or remote data portals
- HPC Ready: Built-in support for SLURM-based clusters
- Experiment Tracking: Integrated MLflow support for monitoring training and optimization
- Dual Interface: Use via command-line or Python API
🚀 Quick Start
Installation
Octopi is availableon PyPI and can be installed using pip:
pip install octopi
⚠️ Note: One of the current dependencies is currently not working with pip 25.1. We recommend using pip 25.2 or higher,
or uv pip when installing octopi.
pip install --upgrade "pip>=25.2"
Basic Usage
octopi provides two main command-line interfaces:
# Main CLI for training, inference, and data processing
octopi
📚 Documentation
For detailed documentation, tutorials, CLI and API reference, visit our documentation.
🤝 Contributing
Code of Conduct
This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to opensource@chanzuckerberg.com.
🔒 Security
If you believe you have found a security issue, please responsibly disclose by contacting us at security@chanzuckerberg.com.
Metadata
Release files for octopi 1.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| octopi-1.7.0.tar.gz | 10.6 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| octopi-1.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.8 MB
Release files / octopi-1.7.0.tar.gz
| Download URL | octopi-1.7.0.tar.gz |
|---|---|
| Size | 10.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e0ceeca906106ebe131ac27320fa4a8d0f69a10311c15a97934245b8198031c
|
|
BLAKE2b-256 checksum How to use checksums |
3766199557bfa85d0a7d62095a749e12bafbee5c1b157f67eaa48420a9445cb7
|
| 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 Sep 9, 2026.
Transparency logRelease files / octopi-1.7.0-py3-none-any.whl
| Download URL | octopi-1.7.0-py3-none-any.whl |
|---|---|
| Size | 147.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6721fca56171ed12f04916d7a97a7239d0fca4fe702d74e946da2f7769af4c26
|
|
BLAKE2b-256 checksum How to use checksums |
ec05c0944ca74e388422a9d4ddaf96cf80bb8d09f8d4e88764bb591a23ccc061
|
| 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 Sep 9, 2026.
Transparency log