<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Hi Eliana,
<div class=""><br class="">
</div>
<div class="">
<div>
<blockquote type="cite" class="">
<div class="">On 22 Aug 2017, at 13:26, Eliana Andreica <<a href="mailto:eliana.andreica@gmail.com" class="">eliana.andreica@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">Hello David,
<div class=""><br class="">
</div>
<div class="">Thank you for your answer. </div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
following up on behalf of David who is on leave for a few days.<br class="">
<div>
<blockquote type="cite" class=""></blockquote>
<br class="">
</div>
<blockquote type="cite" class="">
<div class="">
<div dir="ltr" class="">
<div class="">I will take a look at the new options tab PR, maybe take it for a spin in my local copy.</div>
<div class=""><br class="">
</div>
<div class="">About the use of flattened resolutions, we still have some questions. The first being about the utility of multiple resolutions in Bio-Formats. Does OMERO use the pyramid (with its original resolutions) in image rendering? (As far as we know,
Fiji doesn't; please correct us if we are wrong.) In other words, why would you prefer option 2 over option 1 (from my previous email)? </div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>The Bio-Formats sub resolution API [1] is definitely used by several consumers OMERO [2]</div>
<div>amongst other for accessing and rendering multi-resolution pyramidal images. Modifying the</div>
<div>coreMetadata on any reader would be a breaking change from a data layout perspective.</div>
<div><br class="">
</div>
<div>It is true that the Bio-Formats ImageJ plugin currently does not expose this particular API. Most</div>
<div>of the work on pyramidal images has been primarily driven by OMERO. But this limitation</div>
<div>has been raised to our attention lately [3].</div>
<div><br class="">
</div>
<div>From our perspective, enabling some configuration allowing to use the existing API i.e.</div>
<div><br class="">
</div>
<div>reader.setFlattenedResolutions(false);</div>
<div>reader.setResolution(0);</div>
<div><br class="">
</div>
<div>has the advantage of addressing your RFE while remaining fully compatible with all other usages.</div>
<div><br class="">
</div>
<div>Best,</div>
<div>Sebastien</div>
<div><br class="">
</div>
<div>[1] <a href="https://docs.openmicroscopy.org/bio-formats/5.6.0/developers/wsi.html" class="">https://docs.openmicroscopy.org/bio-formats/5.6.0/developers/wsi.html</a> </div>
<div>[2] <a href="https://downloads.openmicroscopy.org/omero/5.3.3/api/ome/io/bioformats/BfPixelBuffer.html" class="">https://downloads.openmicroscopy.org/omero/5.3.3/api/ome/io/bioformats/BfPixelBuffer.html</a> </div>
[3] <a href="https://trello.com/c/xWnT2XZC/67-imagej-plugin-flattened-resolutions" class="">https://trello.com/c/xWnT2XZC/67-imagej-plugin-flattened-resolutions</a></div>
<div><br class="">
<br class="">
<blockquote type="cite" class="">
<div class="">
<div dir="ltr" class="">
<div class="">I will be back with feedback (and probably more questions) after I know more about the new tab.</div>
<div class=""><br class="">
</div>
<div class="">Thank you,</div>
<div class="">Eliana Andreica</div>
</div>
</div>
</blockquote>
<br class="">
<div>That’s great. We’ll make sure we notify you once the ongoing work is merged if you want to build</div>
<div>on top of it.</div>
<div><br class="">
</div>
<div>Best,</div>
<div>Sebastien</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On Mon, Aug 21, 2017 at 4:40 PM, David Gault (Staff) <span dir="ltr" class="">
<<a href="mailto:d.gault@dundee.ac.uk" target="_blank" class="">d.gault@dundee.ac.uk</a>></span> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word" class="">
<div class="">Hi Eliana,</div>
<div class=""><br class="">
</div>
<div class="">Firstly, thank you for raising this feature request for discussion as it is always great to have the community getting involved in these decisions.</div>
<div class=""><br class="">
</div>
<div class="">The storing of multi-resolution pyramids as a series when opened with ImageJ/Fiji is not always ideal. As you mentioned it is also not limited to Imaris but also affects many other formats. As such we would ideally prefer a solution that would
be used across formats rather than on an individual level.</div>
<div class=""><br class="">
</div>
<div class="">From some initial testing it would seem that the second solution using '<span class=""><span style="white-space:pre-wrap" class="">setFlattenedResolutions(<wbr class="">false)’ could be a straight forward solution that could be implemented in
the Bio-Formats plugin and used across formats. Ideally this should also be configurable as you put forward in the third solution. We have recently been working on an unrelated PR (</span></span><a href="https://github.com/openmicroscopy/bioformats/pull/2891" target="_blank" class="">https://github.com/<wbr class="">openmicroscopy/bioformats/<wbr class="">pull/2891</a><span style="white-space:pre-wrap" class="">)
which will add a new options tab to the Bio-Formats plugin configuration window for the purpose of cross reader import options. Perhaps this new Bio-Formats options tab would be a good place to add a configuration option for flattened resolutions. I have attached
a screenshot with a mocked up an example of how this new options tab could be used.</span></div>
<div class=""><span style="white-space:pre-wrap" class=""><br class="">
</span></div>
<div class=""><span id="cid:256B300A-4872-4EA7-8DDC-FB753AD0B7AC@Home"><Screen Shot 2017-08-21 at 15.34.46.png></span></div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">With Thanks,</div>
<div class="">David Gault</div>
<br class="">
<div class="">
<blockquote type="cite" class="">On 18 Aug 2017, at 15:33, ANDREICA Eliana <<a href="mailto:e.andreica@bitplane.com" target="_blank" class="">e.andreica@bitplane.com</a>> wrote:</blockquote>
<blockquote type="cite" class="">
<div class=""><br class="">
</div>
<div class="">
<div style="word-wrap:break-word" class="">
<pre style="white-space:pre-wrap" class="">Hello,
I should start by saying that this is a feature request (that we will implement if approved), not a bug report.
The current behavior of the ImarisHDF reader is to show a series dialog for the multi-resolution pyramid(s) contained in an IMS file. The pyramid is not a series in the usual series sense as it just contains different resolutions of the same image. We believe that generally, users are interested in the full resolution image. Therefore we (at Bitplane) propose to open the full resolution image without showing the series dialog.
We considered three alternative ways to get rid of the series dialog and propose these here:
1) We keep in core metadata only the highest resolution of the (first) pyramid.
2) We use setFlattenedResolutions(false) and populate core metadata with a pyramid of as many low resolution versions of the highest resolution image as is possible from the IMS file (sometimes not possible to use all resolutions from IMS since the IMS pyramid may downsample Z). These actions will make getSeriesCount() return 1, so that the series dialog will not show. It is not entirely clear to us whether it is of value for any part of Fiji to store the lower resolutions of the pyramid.
3) We don't modify the number of series. We make the series dialog optional (with the default = off), by adding a new checkbox, "Show lower resolutions", under Memory Management. I implemented that in my local copy, just to see what it would involve. Of course, a new checkbox for only one format (and conditioned so that its state is read only in case of that format) is not particularly desirable. We are just mentioning this alternative here, because maybe there are some other formats that would benefit from it? We don't know.
Please let us know if you think Bio-Formats could accommodate our feature-request and which of the three alternatives you would prefer. We will then open a pull request for that option.
We are aware of the windowless option in Bio-Formats, but with this request we intend to improve the workflow for users who use File->Open. We are also aware of the possibility of enabling ImageJ2 but we would like to deliver this to the majority of users asap.
Thank you,
Eliana Andreica
</pre>
<div class=""><br class="">
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
<br class="">
<span style="font-size:10pt" class="">The University of Dundee is a registered Scottish Charity, No: SC015096</span>
</div>
<br class="">
______________________________<wbr class="">_________________<br class="">
ome-users mailing list<br class="">
<a href="mailto:ome-users@lists.openmicroscopy.org.uk" class="">ome-users@lists.<wbr class="">openmicroscopy.org.uk</a><br class="">
<a href="http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users" rel="noreferrer" target="_blank" class="">http://lists.openmicroscopy.<wbr class="">org.uk/mailman/listinfo/ome-<wbr class="">users</a><br class="">
<br class="">
</blockquote>
</div>
<br class="">
</div>
_______________________________________________<br class="">
ome-users mailing list<br class="">
<a href="mailto:ome-users@lists.openmicroscopy.org.uk" class="">ome-users@lists.openmicroscopy.org.uk</a><br class="">
http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users<br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
<br>
<span style="font-size:10pt;">The University of Dundee is a registered Scottish Charity, No: SC015096</span>
</body>
</html>