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.

Changes between Initial Version and Version 1 of Ticket #11878, comment 3


Ignore:
Timestamp:
02/07/14 12:21:56 (10 years ago)
Author:
rleigh
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #11878, comment 3

    initial v1  
    55There is also a case for including the sizes for *all* dimensions, including the modulo dimensions, in the core model.  Currently we have "SizeA" attributes for the fixed five dimensions.  Maybe we really want a mapping of dimension=>size to make this flexible.  This could be done by having dimensionSizes as a comma-separated list of unsigned integers to keep things in a single attribute.  This would also mean that the "modulo" dimensions can be real dimensions and ZTC can retain their true values rather than being multiplied by the modulo size. 
    66 
     7{{{ 
    78dimensionOrder="XYZCTtzc" 
    89dimensionSizes="512,512,12,4,43,16,1,1" 
     10}}} 
    911 
    1012Note that the unused two modulo dimensions are listed last and set to 1.  They could also be omitted entirely and defaulted to 1.  This could be done for any dimension which would make the simplest case: 
    1113 
     14{{{ 
    1215dimensionOrder="XY" 
    1316dimensionSizes="128,128" 
     17}}} 
    1418 
    1519The above model change would permit efficient representation of modulo dimensionality in the core model.  But the dimensionOrder/Sizes attributes also generalise the fixed set of dimension attributes used at present which would permit future use of higher dimensions with no model changes required: 
    1620 
     21{{{ 
    1722dimensionOrder="XYZCS", where "S" is a site 
    1823dimensionOrder="XYUV", where U and V are tileX and tileY numbers 
    1924dimensionOrder="XYCWS", where W and S are well and site numbers 
     25}}} 
    2026 
    2127This would require corresponding changes to the "FirstA" and "SizeA" attributes to also aggregate them in a single attribute which can handle arbitrary dimension ordering.  These would need to exclude the XY dimensions.  And bioformats and other consumers would also need to be able to cope with this. 

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

We're Hiring!