Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #13262 (new)

Opened 5 years ago

Last modified 5 years ago

RFE: nd2 files with strange characters in metadata

Reported by: mtbcarroll Owned by: dgault
Priority: minor Milestone: n.a.
Component: Bio-Formats Version: n.a.
Keywords: ND2Reader Cc: bf@…
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.


Current showinf (at ad334917) shows various odd metadata for https://www.openmicroscopy.org/qa2/qa/feedback/17260/ including,

Component Count #1: 1
Component Count #2: 1
Component Count #3: 1
Data: i�%���¬����c?�����c�i�%��
Desc: Ti ZDrive
Detector: 0


bZInverted: false
bZPosAbsolute: true
baOpticalPathsCorrections: CLxOpticalPathsCorrectionTable�wstrSystemUUID690734c761a342afacf0cc7a68c6577bvecIdsSizematRows��L
baScanArea: dZoom.����@dAngle	dXOffset��"��~ʿ	dYOffset'1�Z�?dScanAreaAspect�?bIsCrop
bottom: 0
cx: 1
cy: 1

That dCropZoom bit certainly seems to confuse Insight, as shown in the attached screenshot. (On my desktop I'm using a UTF-8 locale.) It might be nice to better handle this non-ASCII character data.

Attachments (1)

insight-metadata.png (22.7 KB) - added by mtbcarroll 5 years ago.
metadata confusing Insight

Download all attachments as: .zip

Change History (2)

Changed 5 years ago by mtbcarroll

metadata confusing Insight

comment:1 Changed 5 years ago by mlinkert

Screenshots of QA 17260 opened in NIS Elements have been uploaded to data_repo/inbox/qa-17260-investigation/. The excitation wavelengths in particular are missing, when Elements shows that they should be 405.0, 488.0, and 561.0 for each of the 3 channels. I'd assume it's related to what's going on here, as both are indicative of one or more metadata blocks being incorrectly parsed (possibly an incorrect starting offset?).

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.67471 sec.)

We're Hiring!