<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap:break-word">
<div>Thanks Lee.</div>
<div><br>
</div>
<div>The features set you calculated for that screen sounds like a good test of our infrastructure. However I'm having trouble downloading the supplementary data from:</div>
<div><a href="http://jbx.sagepub.com/content/early/2013/09/09/1087057113503553/suppl/DC2">http://jbx.sagepub.com/content/early/2013/09/09/1087057113503553/suppl/DC2</a></div>
<div><br>
</div>
<div>Data_S3_reproduce.zip is empty</div>
<div>Data_S2_database.zip seems to be corrupt</div>
<div><br>
</div>
<div>Does it look correct from your end?</div>
<div><br>
</div>
<div>Thanks</div>
<div><br>
</div>
<div>Simon</div>
<div><br>
</div>
<div><br>
</div>
<br>
<div>
<div>On 7 Nov 2013, at 20:55, Lee Kamentsky <<a href="mailto:leek@broadinstitute.org">leek@broadinstitute.org</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div dir="ltr">I promised to roughly describe the CellProfiler use case - we recently published a paper whose data should be available on-line, so I based it on that. Enclosed is what I wrote up as well as the paper and the supplement. The supplement is actually
more important because it has more details about the analysis (and the features).
<div><br>
</div>
<div><br>
<div class="gmail_drive_chip" style="width:396px; height:18px; max-height:18px; background-color:#f5f5f5; padding:5px; color:#222; font-family:arial; font-style:normal; font-weight:bold; font-size:13px; border:1px solid #ddd">
<a href="https://docs.google.com/a/broadinstitute.org/file/d/0Bzg4PoGEku2FTFFBS0ZsZTFoSXc/edit?usp=drive_web" target="_blank" style="display:inline-block; overflow:hidden; text-overflow:ellipsis; white-space:nowrap; text-decoration:none; padding:1px 0px; border:none; width:100%"><img src="https://ssl.gstatic.com/docs/doclist/images/icon_10_generic_list.png" style="vertical-align:bottom; border:none"> <span dir="ltr" style="color:#15c; text-decoration:none; vertical-align:bottom">Ljosa_JBiomolScreen_2013.pdf</span></a></div>
<br>
<div class="gmail_drive_chip" style="width:396px; height:18px; max-height:18px; background-color:#f5f5f5; padding:5px; color:#222; font-family:arial; font-style:normal; font-weight:bold; font-size:13px; border:1px solid #ddd">
<a href="https://docs.google.com/a/broadinstitute.org/file/d/0Bzg4PoGEku2FLVZkTEZqUDJ5X1k/edit?usp=drive_web" target="_blank" style="display:inline-block; overflow:hidden; text-overflow:ellipsis; white-space:nowrap; text-decoration:none; padding:1px 0px; border:none; width:100%"><img src="https://ssl.gstatic.com/docs/doclist/images/icon_10_generic_list.png" style="vertical-align:bottom; border:none"> <span dir="ltr" style="color:#15c; text-decoration:none; vertical-align:bottom">Ljosa_JBiomolScreen_2013_supplement.pdf</span></a></div>
<br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Thu, Nov 7, 2013 at 9:20 AM, Simon Li <span dir="ltr">
<<a href="mailto:s.p.li@dundee.ac.uk" target="_blank">s.p.li@dundee.ac.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
Some notes from our meeting yesterday:<br>
<a href="http://www.openmicroscopy.org/site/community/minutes/minigroup/omero-features-meetings/2013-11-06-omero-features-google-hangout" target="_blank">http://www.openmicroscopy.org/site/community/minutes/minigroup/omero-features-meetings/2013-11-06-omero-features-google-hangout</a><br>
<br>
Summary:<br>
We're thinking of representing features as a 2D array, with metadata stored as key-value maps attached to the array, or individual columns or rows. These keys could describe things such as the feature name (column), sample metadata (row), algorithm parameters,
calculation pipelines, etc.<br>
<br>
This should work as an OMERO API- in order to retrieve features you'd pass in a set of key-value pairs, for instance to specify which features you want and which images/ROIs etc, and OMERO would handle the logic and return the feature table(s) matching those
parameters. Since everyone has different requirements the keys could be anything, however we're trying to define a small set of standard keys- any suggestions are very welcome.<br>
<br>
Outside of OMERO we still need a format for transporting features, so we're thinking some form of HDF5.<br>
<br>
Simon<br>
<br>
<br>
The University of Dundee is a registered Scottish Charity, No: SC015096<br>
_______________________________________________<br>
ome-devel mailing list<br>
<a href="mailto:ome-devel@lists.openmicroscopy.org.uk">ome-devel@lists.openmicroscopy.org.uk</a><br>
<a href="http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel" target="_blank">http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel</a><br>
</blockquote>
</div>
<br>
</div>
<span><AZ_use_case.docx></span></blockquote>
</div>
<br>
<br>
<span style="font-size:10pt">The University of Dundee is a registered Scottish Charity, No: SC015096</span>
</body>
</html>