[ome-devel] Access settings from importer gui

[Melissa Linkert]

Hi Christoph,

> >That's what the MetadataLevel is for. For example, the BMPReader
> >only populates optional metadata when the MetadataLevel is set to
> >a value higher than MetadataLevel.MINIMUM:
> >However, the ImageJ plugin always sets the metadata level higher
> >than MINIMUM. So while your reader can respect that value, it
> >won't really save any time at the ImageJ level to do so.
> Yes. I was looking into the MetadataLevels enums. But, as you wrote,
> the level is always set to "All" using the importer GUI.
> 
> An alternative is to implement a custom dialog for the reader. I was
> hesitating with that, since it will interfere with the API and,
> perhaps, leads to problems in headless mode!?

The easier plan might be to:

1) have your reader respect the NO_OVERLAYS and MINIMUM MetadataLevels, so
   that ROI data not populated when either of those levels are set

2) have the ImageJ plugin lower the MetadataLevel to NO_OVERLAYS when
appropriate, as noted here:

  http://trac.openmicroscopy.org.uk/ome/ticket/12475

That way your reader allows applications that are not ImageJ to ignore
the ROIs, and the Bio-Formats ImageJ plugin can provide better
performance for all readers that make ROIs optional (of which there are
already several).

Regards,
-Melissa

On Thu, Jul 17, 2014 at 11:19:50AM +0200, Christoph Sommer wrote:
> Hi Curtis,
> >
> >That's what the MetadataLevel is for. For example, the BMPReader
> >only populates optional metadata when the MetadataLevel is set to
> >a value higher than MetadataLevel.MINIMUM:
> >However, the ImageJ plugin always sets the metadata level higher
> >than MINIMUM. So while your reader can respect that value, it
> >won't really save any time at the ImageJ level to do so.
> Yes. I was looking into the MetadataLevels enums. But, as you wrote,
> the level is always set to "All" using the importer GUI.
> 
> An alternative is to implement a custom dialog for the reader. I was
> hesitating with that, since it will interfere with the API and,
> perhaps, leads to problems in headless mode!?
> 
> Cheers,
> Christoph
> 
> 
> >
> >Regards,
> >Curtis
> >
> >
> >On Wed, Jul 16, 2014 at 8:41 AM, Christoph Sommer
> ><christoph.sommer at imba.oeaw.ac.at
> ><mailto:christoph.sommer at imba.oeaw.ac.at>> wrote:
> >
> >    Hey Mellisa,
> >
> >
> >        For what specifically are these settings needed in your
> >        reader?  If we
> >        know the use case, we might be able to suggest an alternative.
> >
> >    In my reader it takes quite some time to extract the ROIs (data
> >    may contain long time-lapse...). Of course, I would try to avoid
> >    reading the ROIs in, when the user actually just wants to look at
> >    the raw pixel data (i.e. "Display ROIs" not checked)
> >
> >    Cheers,
> >    Christoph
> >    PS: thanks for you prompt reply! :)
> >
> >
> >    _______________________________________________
> >    ome-devel mailing list
> >    ome-devel at lists.openmicroscopy.org.uk
> >    <mailto:ome-devel at lists.openmicroscopy.org.uk>
> >    http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel
> >
> >
> 

> _______________________________________________
> ome-devel mailing list
> ome-devel at lists.openmicroscopy.org.uk
> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel