-
Notifications
You must be signed in to change notification settings - Fork 243
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
Add test for image names when resolutions are not flattened #4114
Conversation
…tened Some readers report noticeably different image names based on the resolution flattening setting. This allows an alternate image name to be configured, so that both sets of image names can be checked for regressions.
On the positive side, it looks like tests have been failing if and only if the format is multi-resolution which was the expectation. |
As discussed today with @melissalinkert and @joshmoore, I agree the latest state of this PR puts us in a nice compromise between:
Next step here is to update the configuration files for all pyramidal file formats and re-include this PR in the nightly CI builds |
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.
Together with the associated configuration changes for all multi-resolution formats, the non-regression tests has been passing over several execution of the nightly CI builds
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.
The approach taken here seems sensible to me and the new test looks good. With all of the config updates the tests have been passing without any issues.
In most cases, the
Image
names stored in aMetadataStore
will not depend onhasFlattenedResolutions()
. For some pyramid formats (e.g. SVS, CZI), theImage
names are noticeably different.This updates the config file generation to add an
Alternate_Name
representing the unflattenedImage
name, if the unflattenedImage
name is different from the flattenedImage
name for a particular series/resolution. The newtestUnflattenedImageNames
checks this value, and errors if the name provided by an unflattened reader does not match either configured name.I would expect this to cause test failures for SVS, CZI, and potentially others. I am happy for this to be excluded once at least test run has completed (so we know the scope of config changes required).