Re: Running scripts with an open Virtual Hyperstack

Posted by Greg on Mar 26, 2015; 9:08am
URL: http://imagej.273.s1.nabble.com/Running-scripts-with-an-open-Virtual-Hyperstack-tp5012163p5012183.html

Hi,

so Curtis the fixes improved things for me ! I tried a few scripts and switched some frames, no real RAM flood in sight. When I open a 7Gb virtual stack Fiji stays stable at around 2.4Gb of RAM usage. When I open a 55Gb virtual stack, RAM usage increases to around 5.0Gb, but Fiji is still responsive. Albeit, when I close the virtual stack the RAM gets not freed. But when I reopen a virtual stack, no more RAM gets used. So for me I can totally work/live with that. Reading nd2 files this way is now much more sluggy than reading in the bfconverted ome.tiff files. Switching takes about 1secwith ome.tiff, with nd2 files it sometimes gets stuck and takes up to 3sec.

And @Wayne, as discussed with Curtis in this thread http://imagej.1557.x6.nabble.com/bfconverter-nd2-to-tif-td5012133.html , we have really huge (around 55Gb) Hyperstacks here, so converting them to ImageJ Tiff format does not really work for us, because we do not have enough physical memory to do the conversion!

Greets,
Greg