pylibCZIrw 4.1.3

A python wrapper around the libCZI C++ library with reading and writing functionality.

pylibCZIrw - Python wrapper for libCZI

This project provides a simple and easy-to-use Python wrapper for libCZI - a cross-platform C++ library intended for providing read and write access to CZI image documents.

Important Remarks

• At the moment, pylibCZIrw completely abstracts away the subblock concept, both in the reading and in the writing APIs.
• The core concept of pylibCZIrw is focussing on reading and writing 2D image planes by specifying the dimension indices and its location in order to only read or write what is really needed.
• It allows reading data via http/https-protocol enabling cloud storage scenarios.

Example Usage

from pylibCZIrw import czi as pyczi

filepath = "myimagefile.czi"

# open the CZI document to read the
with pyczi.open_czi(filepath) as czidoc:
    # get the image dimensions as a dictionary, where the key identifies the dimension
    total_bounding_box = czidoc.total_bounding_box

    # get the total bounding box for all scenes
    total_bounding_rectangle = czidoc.total_bounding_rectangle

    # get the bounding boxes for each individual scene
    scenes_bounding_rectangle = czidoc.scenes_bounding_rectangle

    # read a 2D image plane and optionally specify planes, zoom levels and ROIs
    image2d = czidoc.read(plane={"T": 1, "Z": 2, "C": 0}, zoom=1.0, roi=(0, 0, 50, 100))

The detailed usage can be inferred from the sample notebooks.

For more detailed information (on the latest version) refer to https://zeiss.github.io/pylibczirw/.

Installation

In case there is no wheel available for your system configuration, you can:

• try to install from the provided source distribution
  For Windows:
  • try to keep paths short on systems with maximum path lengths
  • make Win10 accept file paths over 260 characters
• reach out to the maintainers of this project to add more wheels

Disclaimer

The library and the notebook are free to use for everybody. Carl Zeiss Microscopy GmbH undertakes no warranty concerning the use of those tools. Use them at your own risk.

By using any of those examples you agree to this disclaimer.

Version: 2023.11.20

Copyright (c) 2023 Carl Zeiss AG, Germany. All Rights Reserved.

CHANGELOG

v4.1.3 (2024-08-26)

Fix

• fix: Channel ID and Name in display settings metadata (#37)

This PR inlcudes the latest version ov libczirw to fix #13 Fixes #13 (04316fe)

v4.1.2 (2024-08-06)

Chore

• chore: remove temporary debugging logic to push to PyPI (#30)

[x] I followed the How to structure your PR. [ ] Based on Commit Parsing: In case a new major release will be created (because the body or footer begins with 'BREAKING CHANGE:'), I created a new Jupyter notebook with a matching version. [ ] Based on Commit Parsing: In case a new minor/patch release will be created (because PR title begins with 'feat'/('fix' or 'perf')), I optionally created a new Jupyter notebook with a matching version. [ ] In case of API changes, I updated API.md.

Remove debugging code for temporaily pushing to testpypi until infrastructure properly set up. (3b2ea06)

Fix

• fix: consider only dimensions with size >1 for plane-coordinate (#28)

[x] I followed the How to structure your PR. [ ] Based on Commit Parsing: In case a new major release will be created (because the body or footer begins with 'BREAKING CHANGE:'), I created a new Jupyter notebook with a matching version. [ ] Based on Commit Parsing: In case a new minor/patch release will be created (because PR title begins with 'feat'/('fix' or 'perf')), I optionally created a new Jupyter notebook with a matching version. [ ] In case of API changes, I updated API.md.

Re-write of #16 due to changes in infrastructure.

Fixes #10

---

Co-authored-by: Soyer, Sebastian <[e-mail]> Co-authored-by: soyers <[e-mail]> (264fcb4)

v4.1.1 (2024-07-26)

Chore

• chore: Add codeowners (#27)

Add CODEOWNERS file (dc1717b)

Deps

• deps: bump codecov/codecov-action from 3 to 4 (#2)

Bumps codecov/codecov-action from 3 to 4.

Signed-off-by: dependabot[bot] <[e-mail]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Felix Scheffler <[e-mail]> (dab7b18)

Refactor

• refactor: Megalinter and infrastructure (#19)

[x] I followed the How to structure your PR. [ ] Based on Commit Parsing: In case a new major release will be created (because the body or footer begins with 'BREAKING CHANGE:'), I created a new Jupyter notebook with a matching version. [ ] Based on Commit Parsing: In case a new minor/patch release will be created (because PR title begins with 'feat'/('fix' or 'perf')), I optionally created a new Jupyter notebook with a matching version. [ ] In case of API changes, I updated API.md.

Infrastructure related changes, linting (2e60a2b)

Unknown