You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@romainGuiet and I are curious as to the current limitation when exporting time series data as Imaris .ims format. Namely, as to why this is not possible.
Unfortunately, we found the .ims format to be the most compatible across multiple softwares and languages (Java, Python, ImageJ, QuPath, Imaris, Arivis).
And while we're stuck with it, we had hoped to use it for time series.
Best
Oli
The text was updated successfully, but these errors were encountered:
The combination IMS + time series generates one file per time frame in Huygens. Because of this the HRM Queue Manager and File Manager are not able to find the expected output file for the job, which is usually a single file. So, IMS + time series would create a bunch of files in HRM, each one of them with an extra suffix '_txxx.ims', which HRM does not understand. Yet, I think that it should be doable to fix this in the HRM code.
Hello everyone,
@romainGuiet and I are curious as to the current limitation when exporting time series data as Imaris .ims format. Namely, as to why this is not possible.
Unfortunately, we found the .ims format to be the most compatible across multiple softwares and languages (Java, Python, ImageJ, QuPath, Imaris, Arivis).
And while we're stuck with it, we had hoped to use it for time series.
Best
Oli
The text was updated successfully, but these errors were encountered: