<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div dir="ltr">
<div>
<div>
<div>Hi Ian<br>
<br>
</div>
It sounds like Ann has a lot of data, so if it requires you to do extra work let's wait.<br>
<br>
</div>
Though here's a crazy idea. Have you comes across <a href="http://nucleotid.es/">
http://nucleotid.es/</a> or <a href="http://bioboxes.org/">http://bioboxes.org/</a> (running bioinformatics algorithms in Docker)? You could create something similar for testing SR reconstruction algorithms...<br>
<br>
</div>
Simon<br>
<div>
<div>
<div><br>
</div>
</div>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 30 July 2015 at 18:24, Munro, Ian <span dir="ltr"><<a href="mailto:i.munro@imperial.ac.uk" target="_blank">i.munro@imperial.ac.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
<div>Hi All</div>
<div><br>
</div>
As I understand it the raw data (ome-tiff) that I uploaded last week could, potentially, be processed with packages other than Thunderstorm to produce localisation data
<div>in other formats.</div>
<div><br>
</div>
<div>Simon: let me know if you think that would be useful and I’ll lean on Kwasi to try.</div>
<span class="HOEnZb"><font color="#888888">
<div><br>
</div>
<div>Ian</div>
</font></span>
<div>
<div class="h5">
<div><br>
</div>
<div><br>
<div>
<div>
<div>On 30 Jul 2015, at 15:53, Seamus Holden <<a href="mailto:seamus.holden@gmail.com" target="_blank">seamus.holden@gmail.com</a>> wrote:</div>
<br>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>Unfortunately no, not to hand.<br>
<br>
</div>
Frame offsets: you can pretty reliably just look at what the frame number in the first line of the dataset is - it is usually unlikely there will be a completely empty first frame. Not bulletproof obviously.<br>
<br>
</div>
Pixel offsets: I will get back to you on this. It was a required part of the LM challenge so Daniel Sage should have the data; I will ask him.<br>
<div><br>
<div class="gmail_quote">
<div dir="ltr">On Thu, 30 Jul 2015 at 11:09 Simon Li <<a href="mailto:spli@dundee.ac.uk" target="_blank">spli@dundee.ac.uk</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div dir="ltr">
<div>Seamus: Do you have the image files used to generate those particle localisations? It's not essential, but it'd be useful.<br>
</div>
<br>
<div>Ann: it'd be useful to have as many different formats and types of superresolution data as possible, ideally the input image and processed output, and if one format has multiple variants it'd be useful to have them all. You can upload them to
<a href="https://www.openmicroscopy.org/qa2/qa/upload/" target="_blank">https://www.openmicroscopy.org/qa2/qa/upload/</a> or if they're very large contact us directly and we can arrange something else.<br>
</div>
<div><br>
</div>
<div>Everyone: Reiterating Seamus and Ian's points about frame and distance offsets, does anyone have this information for different formats? For example where is the origin relative to the image (top-left, centre), are measurements from the centre or corner
of a pixel, 0 or 1 based indexing, etc.<br>
<br>
</div>
<div>Cheers<br>
<br>
</div>
<div>Simon<br>
</div>
<div><br>
</div>
<div>
<div class="gmail_extra"><br>
<div class="gmail_quote"></div>
</div>
</div>
</div>
</div>
<div>
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On 29 July 2015 at 17:26, Seamus Holden <span dir="ltr">
<<a href="mailto:seamus.holden@gmail.com" target="_blank">seamus.holden@gmail.com</a>></span> wrote:<br>
</div>
</div>
</div>
</div>
<div>
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>I have just uploaded output examples of :<br>
<br>
</div>
PeakSelector - Harold Hess NIH software<br>
</div>
QuickPALM<br>
</div>
RapidSTORM (v 2 & v3)<br>
</div>
uTrack - <a href="http://lccb.hms.harvard.edu/software.html" target="_blank">http://lccb.hms.harvard.edu/software.html</a><br>
</div>
Vutara<br>
</div>
<div>DAOSTORM<br>
<br>
</div>
I have also uploaded a Leica GSD file specification but I don't seem to have an example file any more.<br>
</div>
<div><br>
</div>
<div>Mixture of 2D and 3D data. All single colour. RapidSTORM supports a multicolour output format too, but I don't have any examples.<br>
<br>
</div>
<div>Hope that helps.<br>
</div>
<div><br>
</div>
Best <br>
<span><font color="#888888"></font></span></div>
<span><font color="#888888">Seamus</font></span>
<div>
<div><br>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div><br>
<div class="gmail_quote">
<div dir="ltr">On Mon, 27 Jul 2015 at 10:19 Munro, Ian <<a href="mailto:i.munro@imperial.ac.uk" target="_blank">i.munro@imperial.ac.uk</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
<div>Nice work Simon
<div><br>
</div>
<div>Can I draw your attention to a subtlety that I would have missed (from a comment that Seamus made earlier in the thread)</div>
</div>
</div>
<div style="word-wrap:break-word">
<div>
<div><br>
</div>
<div>
<blockquote type="cite">
<div dir="ltr"><span style="font-size:12.8000001907349px">Oh - also - don't forget about the coordinate system of the different softwares - does 0,0 define the corner of a pixel or the middle. Inconsistently chosen between different softwares, and crucial when
you start comparing algorithms.</span><br style="font-size:12.8000001907349px">
</div>
</blockquote>
<br>
</div>
</div>
</div>
<div style="word-wrap:break-word">
<div>
<div>I guess it’s also possible that some of the systems might use 1-n rather than 0-n-1 numbering for either pixels or frames.</div>
</div>
</div>
<div style="word-wrap:break-word">
<div>
<div><br>
</div>
<div>Ian</div>
</div>
</div>
<div style="word-wrap:break-word">
<div><br>
</div>
<br>
<div>
<div>On 24 Jul 2015, at 19:25, Seamus Holden <<a href="mailto:seamus.holden@gmail.com" target="_blank">seamus.holden@gmail.com</a>> wrote:</div>
<br>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>Nice! HD5 makes a lot of sense, great idea! Much more compact than XML.<br>
<br>
</div>
Next week, I promise I will submit the various multi-format test data from lots of different software that we used in PALMsiever development (if I post this then it will force me to do so!).<br>
<br>
</div>
Best wishes<br>
</div>
Seamus<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Fri, 24 Jul 2015 at 18:24 Simon Li <<a href="mailto:spli@dundee.ac.uk" target="_blank">spli@dundee.ac.uk</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div dir="ltr">
<div>
<div>
<div>Hi all<br>
<br>
</div>
Based on the "Common Headers" section of the spreadsheet that Pedro's shared I've written an example python script for storing some of this data in OMERO as a HDF5 table:<br>
<br>
<a href="https://github.com/manics/omero-superresolution-tables" target="_blank">https://github.com/manics/omero-superresolution-tables</a><br>
<br>
</div>
This isn't in any way complete, and there's plenty of scope for extending it, and improving it's useability, but I just throught I'd make a start since Ian Munro provided us with some real data.<br>
<br>
There are some usage instructions in the README file. The sample file is an extract of a larger file from Imperial<b>-
</b>I'm currently trying the script on the full file file with 4 million rows (note some optimisation might be needed on the OMERO side, it's taking a while...). Next step is to consider adding the points as ROIs in OMERO.<br>
<br>
</div>
<div>Enjoy your weekend!<br>
<br>
</div>
Simon<br>
<div>
<div><br>
<div><br>
</div>
</div>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote"></div>
</div>
</div>
<div>
<div class="gmail_extra">
<div class="gmail_quote">On 25 June 2015 at 09:48, Pedro Almada <span dir="ltr"><<a href="mailto:pedro.almada.13@ucl.ac.uk" target="_blank">pedro.almada.13@ucl.ac.uk</a>></span> wrote:<br>
</div>
</div>
</div>
<div>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>Dear all,</div>
<div><br>
</div>
<div>Some of the members of the UK Super-Resolution community have discussed the integration of single-molecule localization microscopy data (PALM/STORM) into OMERO and what became completely clear is the need to have a general way to import the output of the
localization algorithms. We've made a push towards having a general importer and file-standard by looking at the most common commercial and free software available. The early results are available as a public
<a href="https://docs.google.com/spreadsheets/d/1YxC_WBFEvgy5jo__0_DaC6B0kzy9ptOhc2Z284PnRhU/edit?usp=sharing" target="_blank">
google doc</a>.</div>
<div><br>
</div>
<div>Our goals are to follow the BioFormats route and:</div>
<div> - Create an importer capable of reading most localization data</div>
<div> - Establish a standard, flexible format that the importer would write into.</div>
<div><br>
</div>
<div>It's our hope future algorithms would then start using a standard format, since this would finally decouple localization data from the software used to create it. A few advantages to the SR field would come from this:</div>
<div> - Analysis software (eg. clustering) would no longer need to be custom designed for a specific format</div>
<div> - Rendering could finally be decoupled from the localization software, as the output of any algorithm should be compatible with any rendering method.</div>
<div> - Comparison of the output of different algorithms could be efficiently compared analytically and visual biases from different rendering methods would be removed.</div>
<div><br>
</div>
<div>We need to publicly discuss how to implement this, and we believe the OMERO developers community is the correct starting point. For now, it seems the minimum headers common to all datasets are X position, Y position and the frame number of the localized
particle. Other features are immediately useful such as signal intensity/photon-count but not all formats include it.</div>
<div><br>
</div>
<div>There are also questions of implementation. The BIG.EPFL people <a href="http://bigwww.epfl.ch/smlm/methods/index.html?p=metrics" target="_blank">
have tackled this problem </a>in a fashion, by creating an XML generator. It asks the user to name the headers, column separation, etc and an XML is created which is used by their comparison software to read any text based file such as .csv or .xls. However,
some software packages actually generate binary files and not text based files, which means an extra exporting step is necessary. Also, XML has an associated overhead. I would like to see an importer that can handle the binary data, but have no clue as to
how hard that would be to implement (I can share example outputs though).</div>
<div><br>
</div>
<div>What do you think?</div>
<div><br>
</div>
<div>All the best,</div>
<div>Pedro</div>
<div><br>
PhD Student<br>
Quantitative Imaging and Nanobiophysics Group<br>
MRC Laboratory for Molecular Cell Biology<br>
University College London<br>
Gower Street<br>
London</div>
<div>
<div>
<div dir="ltr"><span style="font-family:arial;font-size:small">WC1E 6BT</span><br style="font-family:arial;font-size:small">
<span style="font-family:arial;font-size:small">Telephone: <a href="tel:%2B44%20%280%2920%207679%207806" value="+442076797806" target="_blank">
+44 (0)20 7679 7806</a></span><br>
</div>
</div>
</div>
<div dir="ltr"><br>
</div>
</div>
<br>
</blockquote>
</div>
</div>
</div>
<div>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span style="font-size:10pt">The University of Dundee is a registered Scottish Charity, No: SC015096</span>
</blockquote>
</div>
</div>
</div>
<div>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
_______________________________________________<br>
ome-devel mailing list<br>
<a href="mailto:ome-devel@lists.openmicroscopy.org.uk" target="_blank">ome-devel@lists.openmicroscopy.org.uk</a><br>
<a href="http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel" rel="noreferrer" target="_blank">http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel</a><br>
<br>
</blockquote>
</div>
</div>
</div>
<div><br>
<span style="font-size:10pt">The University of Dundee is a registered Scottish Charity, No: SC015096</span>
</div>
_______________________________________________<br>
ome-devel mailing list<br>
<a href="mailto:ome-devel@lists.openmicroscopy.org.uk" target="_blank">ome-devel@lists.openmicroscopy.org.uk</a><br>
<a href="http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel" rel="noreferrer" target="_blank">http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel</a><br>
</blockquote>
</div>
</blockquote>
</div>
<br>
</div>
_______________________________________________<br>
ome-devel mailing list<br>
<a href="mailto:ome-devel@lists.openmicroscopy.org.uk" target="_blank">ome-devel@lists.openmicroscopy.org.uk</a><br>
<a href="http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel" rel="noreferrer" target="_blank">http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel</a><br>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<div><br>
<span style="font-size:10pt">The University of Dundee is a registered Scottish Charity, No: SC015096</span>
</div>
</div>
</div>
<br>
_______________________________________________<br>
ome-devel mailing list<br>
<a href="mailto:ome-devel@lists.openmicroscopy.org.uk" target="_blank">ome-devel@lists.openmicroscopy.org.uk</a><br>
<a href="http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel" rel="noreferrer" target="_blank">http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel</a><br>
<br>
</blockquote>
</div>
</div>
</div>
</div>
<div><br>
<span style="font-size:10pt">The University of Dundee is a registered Scottish Charity, No: SC015096</span>
</div>
</blockquote>
</div>
</div>
</div>
_______________________________________________<br>
ome-devel mailing list<br>
<a href="mailto:ome-devel@lists.openmicroscopy.org.uk" target="_blank">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>
</div>
<br>
<span style="font-size:10pt">The University of Dundee is a registered Scottish Charity, No: SC015096</span>
</div>
</div>
</div>
<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" rel="noreferrer" target="_blank">http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<span style="font-size:10pt;">The University of Dundee is a registered Scottish Charity, No: SC015096</span>
</body>
</html>