<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoPlainText">Hi Simon,<o:p></o:p></p>
<p class="MsoPlainText"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText">>As Jason pointed out in his email you should definitely be able to obtain all the information you need via the OMERO API, and we can certainly help you once you get started.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">>Probably the easiest way to get started is to look at one of the language specific pages. Picking Python as an example, the code samples at ><a href="http://www.openmicroscopy.org/site/support/omero5/developers/Python.html#code-samples"><span style="color:windowtext;text-decoration:none">http://www.openmicroscopy.org/site/support/omero5/developers/Python.html#code-samples</span></a><o:p></o:p></p>
<p class="MsoPlainText">>cover the basics of connecting to OMERO, and retrieving/manipulating data. An intro to the full API is at
<a href="http://www.openmicroscopy.org/site/support/omero5/developers/Modules/Api.html">
<span style="color:windowtext;text-decoration:none">http://www.openmicroscopy.org/site/support/omero5/developers/Modules/Api.html</span></a><o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> We are planning to extend OMERO to be able to support our zoomable image and query interface called PivotViewer (for details see
<a href="http://www.cbrg.ox.ac.uk/data/pivotviewer/intro.shtml"><span style="color:windowtext;text-decoration:none">http://www.cbrg.ox.ac.uk/data/pivotviewer/intro.shtml</span></a>) or to view it in action, see the YouTube movie (<a href="https://www.youtube.com/watch?v=BvDOPpRo7KM"><span style="color:windowtext;text-decoration:none">https://www.youtube.com/watch?v=BvDOPpRo7KM</span></a>).<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> We have 3 main goals:<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> 1) Visualise OMERO projects by :<o:p></o:p></p>
<p class="MsoPlainText">> i) Generating indices for PivotViewer by doing an export of metadata (possible from the HDF5 tables) and images from the OMERO database.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">>There are methods for listing images in Projects/Datasets/Screens, and for obtaining the raw images data and metadata. Are the HDF5 tables you refer to created using the OMERO.tables >API, or are they created by yourself? If it's the
latter there are API methods to retrieve the original HDF5 file (or any other type of file you want to store in OMERO).<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><span style="color:black">OMERO.tables. <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText">> ii) Exporting the images + metadata on the fly.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">>Could you expand on what do you mean by "export"? There are examples of rendering images on the fly on the code samples page, for more advanced usage you might want to look at the >source code for OMERO.web.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><span style="color:black">Ok. Currently we use static PNGs/JPGs and create a tiling pyramid which is read by the viewer, but it would be cool to generate these on the fly, caching the images of interest.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText">> 2) Use the results of filtering operations to run OMERO.scripts and see the results in PivotViewer.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">>As you're probably already aware scripts are run asynchronously in a separate process. If you want something more responsive there may be other options.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><span style="color:black">No I didn’t know that. I’d be interested to hear about the other options...<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText">> 3) Use the results of filtering operations to be able to annotate back to the OMERO database. So for example, I might choose a subset of images that I think are badly stained and tag them as 'stained=bad' or similar.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">>This should be straightforward- once you've got a list of images (or any other OMERO objects) you can easily create a tag on them. It's also possible to attach more structured data to ?>an image.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><span style="color:black">Ok. Sounds good. Is there a link where I can find more info about the different data structures available?<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText">> I am trying to pull together enough technical information to define how much work would be required to do this as part of a grant application. Would anyone on this list be able to >help?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">>What kind of interaction do you want to see between OMERO and PivotViewer? Do you see it as a separate standalone application, or part of OMERO.web?
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><span style="color:black">Ultimately it would be good to have as part of OMERO web but I think we have to get a bit more familiar with OMERO’s guts before we look at that. Doing it OMERO.web would be useful since we could use the same
authentication to secure collections, though I guess if both systems are using LDAP this might not be a problem. What other advantages do you think would be in using OMERO.web?</span><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">>Do you need real-time updates- that >could be pretty challenging. However we've done (and are planning a lot more) work on integrating analysis tools into OMERO, so if you come across >any issues don't hesitate to mention >them.<o:p></o:p></p>
<p class="MsoPlainText"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="color:black">I think it would be standalone in the first instance and export the data (images and metadata) from OMERO incrementally and then index it on the file system.
<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="color:black">Thanks for your help so far,<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="color:black">Steve<o:p></o:p></span></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText">> Also, if any developers are interested in collaborating on this project please let me know!<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Kind regards and thanks,<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Steve<o:p></o:p></p>
<p class="MsoPlainText">> =======================================<o:p></o:p></p>
<p class="MsoPlainText">> Head of Computational Biology Research Group Weatherall Institute of
<o:p></o:p></p>
<p class="MsoPlainText">> Molecular Medicine University of Oxford <a href="http://www.cbrg.ox.ac.uk">
<span style="color:windowtext;text-decoration:none">www.cbrg.ox.ac.uk</span></a><o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> _______________________________________________<o:p></o:p></p>
<p class="MsoPlainText">> ome-devel mailing list<o:p></o:p></p>
<p class="MsoPlainText">> <a href="mailto:ome-devel@lists.openmicroscopy.org.uk">
<span style="color:windowtext;text-decoration:none">ome-devel@lists.openmicroscopy.org.uk</span></a><o:p></o:p></p>
<p class="MsoPlainText">> <a href="http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel">
<span style="color:windowtext;text-decoration:none">http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel</span></a><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">The University of Dundee is a registered Scottish Charity, No: SC015096<o:p></o:p></p>
</div>
</body>
</html>