This assumes we always have a full zyx stack present in each tif file, right? I think that holds true for all VisiView acquisitions, we should however also check the various acquisition modalities that VisiView provides (e.g. there used to be a "separate files" option, I don't remember it it's just splitting time points or also z planes...; also, what happens with 2D time lapse data? When using nd/stk format, all time frames end up in a single stk file; we need to see if that's still the case with ome.tif...)
Let's follow up on this by opening separate issues. Sample data for various modalities should be present on our file storage.
imagejan
commented
1 month ago
This assumes we always have a full zyx stack present in each tif file, right? I think that holds true for all VisiView acquisitions, we should however also check the various acquisition modalities that VisiView provides (e.g. there used to be a "separate files" option, I don't remember it it's just splitting time points or also z planes...; also, what happens with 2D time lapse data? When using nd/stk format, all time frames end up in a single stk file; we need to see if that's still the case with ome.tif...) Let's follow up on this by opening separate issues. Sample data for various modalities should be present on our file storage.
_Originally posted by @imagejan in https://github.com/fmi-faim/faim-hcs/pull/84#discussion_r1466045580_