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
Sprint 4 bug fixes, part 2 #328
Sprint 4 bug fixes, part 2 #328
Conversation
Reported by Marc Lartaud.
When a writer is 'closed', the current ifdCounts map has all present entries reset to 0. This map is referenced in populateImage, but if you change output files (multi-file dataset), the stored IFD count is used to populate the TiffData elements in each series. Each subsequent file would cause the old TiffData IFDs to be replaced with a new sequence beginning at the old maximum. Also, the IFDs for series 0 were being reduced by 1. This caused each IFD in series 0 to be identical. Signed-off-by: Luke Stuyvenberg <stuyvenberg@wisc.edu>
The global minimum and maximum values are only available if every plane in the series has been read. In some cases (e.g. if "Specify range..." was specified), we need autoscaled images but have not read all of the planes. Fixes #10088.
Fixes #10092.
Reported by Nicolas Brouilly.
--test tiff |
Fixes QA #4832/#4833.
--test leica-tcs That's the last of the fixes that I intended to add to this PR, so it's now ready for review. |
This is what 49a3ec6 should have done.
Looks fine, builds fine. I can't see that hudson ran the commit tests though, it looks like it failed to start the job properly. |
I had to remove a bunch of jobs from the queue this morning (nearly everything that was scheduled to run Sunday night), as BIOFORMATS-per-commit-test build 257 got stuck and was holding everything up. Everything should be back to green Monday evening/Tuesday morning. |
I've run all four of the above tests by hand in the meantime. Zero failures, so should be OK to merge. |
Merging Tuesday afternoon, assuming |
Sprint 4 bug fixes, part 2
I want to add a few more commits here, but am opening the PR now in order to respond to email/forum posts.
Fixes for tickets #10040 and #10088 will be added in the next couple of days.