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
A recurring problem for some users has been that HCS datasets can produce huge OME-TIFF files which are tricky to work with.
It'd be nice to have the option to split an input zarr into a distinct .tif file per series. I could imagine that this could take the form of a --series argument that allows the user to specify which series to convert. How individual series should be specified is an open question (numerical index or path?).
An alternative might be a --split_series flag which would trigger individualised series export. That could involve spitting out TIF files with sequential names e.g. my_file_s{index}.ome.tif. It's perhaps a bit more messy but saves the user needing to re-run the application for every series in the zarr.
The text was updated successfully, but these errors were encountered:
It's not not an option, but obviously more involved than what #80 does right now. If we have an immediate need for splitting individual channels, timepoints, etc. into separate files or embedding additional metadata into the file names, then I can work on that. Otherwise, I'd rather focus on what's in #80 for now so that @DavidStirling is unblocked.
then I can work on that. Otherwise, I'd rather focus on what's in #80 for now so that @DavidStirling is unblocked.
Definitely understood. Guess I'm most concerned about the API stability. I guess if/when we decided to add the bfconvert like behavior, --split could be deprecated.
A recurring problem for some users has been that HCS datasets can produce huge OME-TIFF files which are tricky to work with.
It'd be nice to have the option to split an input zarr into a distinct .tif file per series. I could imagine that this could take the form of a
--series
argument that allows the user to specify which series to convert. How individual series should be specified is an open question (numerical index or path?).An alternative might be a
--split_series
flag which would trigger individualised series export. That could involve spitting out TIF files with sequential names e.g.my_file_s{index}.ome.tif
. It's perhaps a bit more messy but saves the user needing to re-run the application for every series in the zarr.The text was updated successfully, but these errors were encountered: