Closed mkitti closed 2 years ago
Hello Mark, we do not want to include this change because it will create images that may be slow to open in Imaris (Imaris will recreate the pyramid every time that it opens the image). Ims without pyramid should be considered malformed and we do not want them to spread out. An option to create the pyramid once the entire acquisition is completed may be a viable alternative for the library (similar to dumping the acquisition straight to local files, and using the writer library to create an ims file afterwards). Do you have measures on how do the library performs in terms of GB/s with and without pyramid in comparison to the acquisition speed? Thanks, Igor
The hope with this option is that we could use this at acquisition time when both time and space are at a premium and then add the pyramid at a later time post acquisition. I do have some data along these lines from last year, but I will need to find it.
This pull request adds an option to disable the calculation of the multiscale pyramid in order to save time. This is critical in time-sensitive applications when the file is being saved near acquisition.