DefaultOMEMetadataService: get BigEndian from image index only#27
Open
DefaultOMEMetadataService: get BigEndian from image index only#27
Conversation
images may not have bins attached. This will cause an IndexOutOfBoundsException.
Author
|
I've the feeling it has something to do with: ome/bioformats@9878804. |
|
Thanks @dietzc for the fix, without that I couldn't read any of my images. |
Member
|
@dietzc Sorry for the dropping the ball here. Is this still an outstanding issue which needs to be merged? |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I experienced an
IndexOutOfBoundsExceptionwhen running the following code:The proposed fix doesn't rely on the existence of a bin anymore, rather uses only the
imageindexto get the information about theBigEndian. I've no idea why the other method withindex,binIdxwas called before, maybe @hinerm can comment on this?Also I don't know if this fix has side-effects, I can just say that the
IndexOutOfBoundsExceptionis resolved with this PR. @ctrueden what do you think?