Ticket #105 (closed defect: fixed)

Opened 11 years ago

Last modified 11 years ago

xuvtools 1.6.0: file size written in Imaris files is wrong

Reported by: aaron@… Owned by: emmenlau
Priority: major Milestone:
Component: xuvtools Version:
Keywords: Cc: niko@…


Loading datasets stitched with xuvtools 1.6.0 in Imaris results (in many cases, albeit not all) in the wrong 'size' being read. I uploaded an example (original files: L15_naive_m1_Vd1_s<1-3>.STK and resulting stitched dataset: TEST.ims) onto the FTP server for the 'faim' account under /bug_dominique/sizeProblems_FMI.rar.

XuvTools? 1.5.0 works as expected. The correct size of the stitched dataset is 788x804x65, the size read (and reported) by Imaris is 876x529x41. The x dimension is reported even _larger_ than the real one.

As far as I can tell, the pixels are correctly written to the file, but the size information is somehow incorrect. If I read the resulting Imaris file in MATLAB (Qu), where I get the size of the dataset as attributes from /DataSetInfo/Image/, then the loading is correct. Both Imaris and the LOCI tools get the size information from somewhere else, I guess, and both give problems. Imaris cuts away parts of the dataset in y and z and allocated too much space in x, the LOCI tools corrupt the pixels (probably because the reported width is larger than the actual one).

Change History

Changed 11 years ago by emmenlau

  • cc niko@… added
  • status changed from new to closed
  • resolution set to fixed

Should be fixed in r3112 (probably earlier).

Tested with supplied DataSet? L15_naive_m1_Vd1_s<1-3>.STK

Please test, and reopen if bug persists.

Note: See TracTickets for help on using tickets.