Ticket #222 (closed enhancement: fixed)
Opened 2007-11-28T13:41:06-06:00
Last modified 2007-12-04T12:30:58-06:00
SDT reader should fully parse SETUP metadata block
Reported by: | curtis | Owned by: | melissa |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | bio-formats | Severity: | non-issue |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
Currently the SDT reader parses the SETUP string from the header into an original metadata key called SETUP. Ideally, the reader would look at each individual line of this block and parse them into separate metadata keys. The format appears to be [name,type,value] where type is a one-character code indicating data type such as B for byte, I for integer or S for string.
This new logic would also obviate the need for some of the existing parsing logic that looks for certain specific keys within the SETUP block -- see source:trunk/loci/formats/in/SDTInfo.java@3015#L485 for specifics.
Note that most of our SDT files were produced by WiscScan, which omits this block. However, we do have some data with the SETUP block -- for an example, see sdt/long/slice1_810nm_40x_z1_pcc100_scanin_20s_01.sdt.
Change History
comment:1 Changed 2007-12-04T12:30:58-06:00 by melissa
- Status changed from new to closed
- Resolution set to fixed
r3443