Original David:
do you have any plans to support OME-TIFF as an output format? basically i think it would involve using the Bio-Formats OME-XML Java library to create the OME-XML metadata.
the context is that i'm considering using Omero as a way to store images and manage metadata for our experiments.
However, I've learned that Omero doesn't directly support "sparse" data in the form of individual files, i.e. time series in which not all time points have images for all wavelengths. see https://www.openmicroscopy.org/community/viewtopic.php?f=4&t=8086 for my forum topic. there you'll see that they've proposed a solution (bottom of the page) for me which i will test this week. basically it fills in the images for the "missing" fluorescent time points with references to either the previous available image for that channel or a blank pane. this will allow me to upload the sparse data but still be able to navigate through it in a viewer in an intuitive way.
i didn't see OME-TIFF in the file format list, but naturally i wondered if there were any plans for youscope to support this output type during acquisition itself, in which case i could adopt that instead of this post-processing method.
Original David: do you have any plans to support OME-TIFF as an output format? basically i think it would involve using the Bio-Formats OME-XML Java library to create the OME-XML metadata.
the context is that i'm considering using Omero as a way to store images and manage metadata for our experiments.
However, I've learned that Omero doesn't directly support "sparse" data in the form of individual files, i.e. time series in which not all time points have images for all wavelengths. see https://www.openmicroscopy.org/community/viewtopic.php?f=4&t=8086 for my forum topic. there you'll see that they've proposed a solution (bottom of the page) for me which i will test this week. basically it fills in the images for the "missing" fluorescent time points with references to either the previous available image for that channel or a blank pane. this will allow me to upload the sparse data but still be able to navigate through it in a viewer in an intuitive way.
i didn't see OME-TIFF in the file format list, but naturally i wondered if there were any plans for youscope to support this output type during acquisition itself, in which case i could adopt that instead of this post-processing method.