-
Notifications
You must be signed in to change notification settings - Fork 54
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
Plate labels fix #207
Open
will-moore
wants to merge
14
commits into
ome:master
Choose a base branch
from
will-moore:plate_labels_fix
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Plate labels fix #207
Changes from 5 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
8f47d05
Re-enable plate labels
will-moore 32804fa
hard-code etc to get plate labels to show in napari
will-moore 5b42130
Fix get_tile_path to look-up labels/.zattrs
will-moore 3492f0d
Fix PlateLabels and update Plate superclass
will-moore d731b87
Don't pass plate node to first_well_image to avoid recursion
will-moore 180e9d4
Avoid recursion: don't create Node with empty img_path
will-moore 5b8156f
Update tests - remove PlateLabels omission
will-moore 0bdbdbe
Test reading plate labels
will-moore 7bb2cb4
Handle len(first_well_image.data) == 0 for missing Plate labels
will-moore dbbd940
WIP - trying to support plate.zarr/labels node for PlateLabels
will-moore 8ab3ad6
Fix loading of PlateLabels
will-moore 1f1067a
Prevent creation of node at plate.zarr/labels/labels
will-moore 2b71cd7
Use os.path.dirname to fix Windows test failures
will-moore 394d0db
Merge remote-tracking branch 'origin/master' into plate_labels_fix
will-moore File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@joshmoore @sbesson Here I'm creating a Node for an Image as I want a
Multiscales
spec to do the parsing of the datasets, to give me the sizes of each resolution of the pyramid. However, this is leading to recursion errors in the tests (although it seems to work fine for me viewing local data in napari).I don't see a way to reuse that logic in
Multiscales
spec, without creating a Node? But I don't need any Node traversing logic. I guess I want to create aMultiscales
spec with no node. Should I make thenode
optional in the Spec class, or is there another way I should be thinking about this?NB:
get_image_path()
is overridden by thePlateLabels
subclass to point to a labels image, so this works both for images in Wells and their child labels.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for having missed this. Without stepping through your code, I don't know offhand why you're getting the recursion. I assume that the
seen
field is not getting updated and therefore it just keeps looping. Perhaps that's caused by not setting theroot
.What functionality do you want from the
Spec
without aNode
? Could we just refactor that logic somewhere re-usable? (Perhaps statically?)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I just need the
data.shape
of each resolution of the multiscales pyramid, and thedtype
.Before my last commit d731b87 I was passing in a root node (plate node) but that was also giving me recursion errors:
I'll try stepping though my code and see if I can work out the loop...