napari atlas cci
Napari plugin to give a GUI interface to the cci atlas tool.
This is a wrapper around the cci atlas package.
Installation
A standalone version of napari is available at napari.org, and the plugin is available on the napari hub. Just follow the installation instruction from napari. You can install the plugin from the plugin manager.
It is also possible to install the plugin from source code or from pip with pip install napari-atlas-cci. In this case, be sure to isolate the installation in a dedicated environment with napari.
How to use
Browse and load an atlas project. An atlas project is composed of a series of S_ folder, each containing 1 or multiple tiff images.
2D stitching
For 2D stitching, it is possible to process one, multiple or all S_ folder. This will stitch images in a S_ folder in one tiff image. The number of images being processes at the same time is dependent to the number of core in your PC. Be carefull on RAM consumption.
After processing, you can select one S_ folder and display the image in Napari.
Z alignement
It is only possible to process to the z-alignement if all S_ folder has been stitched. The alignement is required to run first a on downsampled image. This downsampling factor can be control in the Options.
Once the initial alignement is completed, a preview image is display. Please confirm that the alignement is correct through the z volume.
It is possible to add correction in the alignement by clicking the "Enter Correction" button. It will create a couple of point layers, called "Fixed points" and "Moving points".
Move to a plane before the shift, and identify one striking feature with the Fixed points layer. Then move one Z-slice up, select the "Moving points" layer and identify the same feature. You can repeat as many time as necessary, however all points need to be paired.
Once done, click on the "Apply correction" button. It will reprocess the downsample image, then display the corrected zstack. Check that the correction happen.
WIP: Small video Youtube to display alignement correction.
Once the data is aligned, it can be processed for the "Final Z Alignement". This step can be time consuming based on the size of the dataset, so please, be patient.
Export and upload
All intermediate files are stored in the root folder of the Atlas project. Individual planes are stored as tiff images, will the alignement is stored as a pickle pandas table. The z aligned files (both the downsample and the final ones) are saved in a ome-zarr format.
For easier data manipulation, it is possible to export the final alignement as a czi file. The other option is to upload the data on Webknossos, which is great for both visualization and fine z-alignement. To do this upload, it is required to have a account on webknossos and to indicate your token for the upload.
Troubleshooting
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.
Metadata
Release files for napari-atlas-cci 1.1.5
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 | |
|---|---|---|---|---|
| napari_atlas_cci-1.1.5.tar.gz | 2.3 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| napari_atlas_cci-1.1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.3 MB
Release files / napari_atlas_cci-1.1.5.tar.gz
| Download URL | napari_atlas_cci-1.1.5.tar.gz |
|---|---|
| Size | 2.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
63327d43b99b71db97352765d5fca07452080648df751d2f766ff15feb336b14
|
|
BLAKE2b-256 checksum How to use checksums |
7902011ecfc0719c176fb14e631fc3ae37256b305d0c63fd7c1ca0b867bf2b49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 21, 2026.
Transparency logRelease files / napari_atlas_cci-1.1.5-py3-none-any.whl
| Download URL | napari_atlas_cci-1.1.5-py3-none-any.whl |
|---|---|
| Size | 25.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3f737363b38f2123d9d76e770fa5cd8f48bc94963bd47129928b3dbc4a5c20f1
|
|
BLAKE2b-256 checksum How to use checksums |
1845a5e145aca63f4d842af760a46772c7ea18c9f4b763aed262528747ee48a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 21, 2026.
Transparency logSecurity for napari-atlas-cci 1.1.5
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for napari_atlas_cci-1.1.5.tar.gz
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 21, 2026.
Transparency logA 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.