Passing min/max values to OMERO for rendering
Posted: Mon Jun 20, 2016 8:48 pmAll,
Following up on a conversation I had with Melissa at the OME users meeting, I'm posting the following idea and Melissa's initial comments on it:
I expect that such functionality could 1) significantly reduce the import time for large datasets of images when the minmax calculation is not skipped and 2) provide more useful initial rendering settings for those image types (e.g. whole slide images) where the importer automatically skips the minmax calculation.
- Damir
Following up on a conversation I had with Melissa at the OME users meeting, I'm posting the following idea and Melissa's initial comments on it:
DS:
> On my other question about importing rendering settings from images
> (specifically CZI's) if they were recorded by the user: I realize now that
> that may be a bit tricky since the OME data model doesn't seem to have a way
> to capture that type of data. Do you think there is a way around that? Or
> would it require a new revision of the data model?
ML:
There is currently a way around that; Bio-Formats can pass minimum and
maximum pixel values through to OMERO,
even though this isn't formally defined in the data model. I'd expect
we can resolve this without a new version of the data model (unless
something more exotic than min/max values needs to be captured).
I expect that such functionality could 1) significantly reduce the import time for large datasets of images when the minmax calculation is not skipped and 2) provide more useful initial rendering settings for those image types (e.g. whole slide images) where the importer automatically skips the minmax calculation.
- Damir