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
ZVI ROI fixes (develop) #476
ZVI ROI fixes (develop) #476
Conversation
Also seek 4 bytes rather than 6 after the label, or else you end up in missing the SourceTag and losing the correct position in the stream.
The layer name is typically absent, but some layers have names. Cope with non-null layer names.
--test zeiss-zvi |
@rleigh-dundee It would be good to have a link to the dev_4_4 PR in here. It is #471. |
I don't think that there's a problem here. For the file in question, I've run
and in the resulting OME-XML, we get:
|
Agreed that the ROIs are there - they can be seen using both ImageJ and Fiji. When taking the images from test_images_roi/zvi/ folder one by one in the order of appearance, we have:
If this is how it should be, than the PR is probably ok. |
Hmm, some of those aren't quite right. Some of the more esoteric types (scale bar, angle, length measurement) are being picked up as a single rectangle which is not right. Something is definitely being mis-parsed there. I'll take a look at exactly what's going on for those types. This also affects 4.4.7/dev_4_4 I'm afraid. I can either open a separate ticket and/or PR for that or fix it for this PR and backport the extra bits to 4.4 after. |
Argh, it's definitely this PR that introduces that was well. It's relating to b3a902d where it's parsing the ROI name as the font name, so it's getting confused when it comes to reading the points. |
There may be a 2 byte pad between the end of the ShapeAttrs block and the start of the Label string. And the string may or may not be null, making it difficult to detect reliably. We allow for a fuzzy match at 0 or 2 bytes after the end of the ShapeAttrs. This padding is typically only found in the initial Shape, and missing in subsequent shapes.
The issues noted with respect to some ROIs not being parsed is now fixed. |
@rleigh-dundee: will any of the commits need to be re-rebased? |
Note: see gh-486 for the backporting of these last fixes. |
Yes, that's the rebased patches, and everything else in this PR was already merged into dev_4_4/ |
--test zeiss-zvi Happy to merge if overnight builds are green. |
ZVI ROI fixes (develop)
Update Windows service docs (see #11448)
As for dev_4_4 (#471)