Currently, the code only handles XYZCT information. It looks like OME-XML doesn't have natural support for multiple positions, but I'll need to handle them regardless since the extra TiffData nodes are in XML. So in order:
The design I'm developing in #1 should degrade gracefully (i.e. only load the TiffDatas corresponding to the current file) in the case of multiple positions. This should be a simple check: if number of TiffDatas is longer than the product of ZCT dimensions then this is likely a multiple position file and then I would match TiffData uuids with the uuid of the current file.
In the future it might be nice to have positions as another dimension. It looks like Micromanager at least seems to embed StageLabel nodes in the XML under Image that gives me a name and the order of positions so that be a way to get this to work.
tlnagy
commented
7 years ago
Currently, the code only handles XYZCT information. It looks like OME-XML doesn't have natural support for multiple positions, but I'll need to handle them regardless since the extra
TiffDatanodes are in XML. So in order:The design I'm developing in #1 should degrade gracefully (i.e. only load the
TiffDatas corresponding to the current file) in the case of multiple positions. This should be a simple check: if number ofTiffDatas is longer than the product of ZCT dimensions then this is likely a multiple position file and then I would matchTiffDatauuids with the uuid of the current file.In the future it might be nice to have positions as another dimension. It looks like Micromanager at least seems to embed
StageLabelnodes in the XML underImagethat gives me a name and the order of positions so that be a way to get this to work.