Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: consider only dimensions with size >1 for plane-coordinate #16

Closed
wants to merge 1 commit into from

Conversation

ptahmose
Copy link

@ptahmose ptahmose commented Jul 11, 2024

fix: consider only dimensions with size >1 for plane-coordinate

[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.

Summary of the change(s) and which issue(s) is/are fixed

This is a proposal to address the issue discussed in #10 . To be clear - it is more an side-effect that this change seems to fix the problem discussed there. However - I cannot see any adverse effects from this proposal, so the line of reasoning is: why not change this and as an added benefit, it will make this case work as well.
The root cause (for the problem with #10) I see as "being a malformed CZI".

Relevant motivation and context

Dependencies required for this change

Fixes #10

@ptahmose ptahmose changed the title proposal to fix #10 fix: consider only dimensions with size >1 for plane-coordinate Jul 11, 2024
@ptahmose ptahmose marked this pull request as ready for review July 16, 2024 22:49
Copy link
Contributor

@soyers soyers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for proposing this fix! I fully agree with your argument and also can't see any negative sideffects of this.

@FelixS90
Copy link
Collaborator

Abandoning in favor of #28 due to changes in infrastructure.

@FelixS90 FelixS90 closed this Jul 27, 2024
FelixS90 added a commit that referenced this pull request Aug 6, 2024
[x] I followed the [How to structure your
PR](https://github.com/ZEISS/pylibczirw/blob/main/CONTRIBUTING.md#creating-a-pr).
[ ] Based on [Commit
Parsing](https://python-semantic-release.readthedocs.io/en/latest/commit-parsing.html):
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](https://github.com/ZEISS/pylibczirw/tree/main/doc/jupyter_notebooks).
[ ] Based on [Commit
Parsing](https://python-semantic-release.readthedocs.io/en/latest/commit-parsing.html):
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](https://github.com/ZEISS/pylibczirw/tree/main/doc/jupyter_notebooks).
[ ] In case of API changes, I updated
[API.md](https://github.com/ZEISS/pylibczirw/blob/main/API.md).

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

Fixes #10

---------

Co-authored-by: Soyer, Sebastian <[email protected]>
Co-authored-by: soyers <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

accessing acquisition tiles using pylibCZIrw
3 participants