Skip to main content

napari-copick

License MIT PyPI Python Version tests codecov napari hub

A plugin for collaborative annotation in cryoET using copick

interface.png


This napari plugin was generated with Cookiecutter using @napari's cookiecutter-napari-plugin template.

Installation

You can install napari-copick via pip:

pip install napari-copick

To install latest development version:

pip install git+https://github.com/copick/napari-copick.git

Usage

Using a copick config file

napari-copick run --config path/to/copick_config.json

Using dataset IDs from CZ cryoET Data Portal

napari-copick run --dataset-ids 10440 10441 --overlay-root /path/to/overlay_root

You can specify multiple dataset IDs separated by spaces.

GUI Usage

The plugin provides an intuitive interface with two loading options:

  1. Load Config File: Opens a file dialog to select a copick configuration JSON file
  2. Load from Dataset IDs: Opens a dialog to enter CZ cryoET Data Portal dataset IDs and overlay root path

After loading, you'll see a hierarchical tree of the project structure that you can navigate to access tomograms, segmentations, and picks.

Tomogram Handling

napari-copick now handles multiscale zarr arrays directly:

  • Automatically detects and loads all available resolution levels
  • Creates a proper multiscale image stack using napari's native multiscale API
  • Uses dask for efficient lazy loading of large tomogram data
  • Applies appropriate scaling factors based on the voxel size metadata

This direct zarr handling provides better performance and more flexibility compared to relying on external plugins.

Contributing

Contributions are very welcome. Tests can be run with tox, please ensure the coverage at least stays the same before you submit a pull request.

License

Distributed under the terms of the MIT license, "napari-copick" is free and open source software

Issues

If you encounter any problems, please file an issue along with a detailed description.

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.

Reporting Security Issues

If you believe you have found a security issue, please responsibly disclose by contacting us at security@chanzuckerberg.com.

Metadata

Release files for napari-copick 1.11.0

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

Source distribution (sdist)

Source distribution for napari-copick 1.11.0
File Size Uploaded
napari_copick-1.11.0.tar.gz 1.1 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for napari-copick 1.11.0
File Interpreter ABI Platform
napari_copick-1.11.0-py3-none-any.whl Python 3 none any Details

Total release size: 1.2 MB

Release files / napari_copick-1.11.0.tar.gz

Download URL napari_copick-1.11.0.tar.gz
Size 1.1 MB
Tags Source
SHA-256 checksum
How to use checksums
e46c93a275f7ae14e929f7bb74c69e40263ceadde9e3af590b683cacd9b03eac
BLAKE2b-256 checksum
How to use checksums
b2474e24df57c080607891cce672be65a445dc61340739b2105b08ee786ac38a
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 Oct 8, 2026.

Transparency log

Release files / napari_copick-1.11.0-py3-none-any.whl

Download URL napari_copick-1.11.0-py3-none-any.whl
Size 75.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9705d53a3e933a466ac8f40a34377e8d4aa0b009ec28e6e535202b32e3fd88fe
BLAKE2b-256 checksum
How to use checksums
cc5bf93ad07c472a943cebf14bf92974a476dc71e9399e49695cab9e3bcf80fd
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 Oct 8, 2026.

Transparency log
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