<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>
<blockquote type="cite">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>Hi Lars</div>
<div><br>
</div>
<div>I'm aware of some of the issues. We are concentrating on time-domain TCSPC initially. TCSPC because the file formats are common to many sites </div>
<div>& time-domain because that's the area in which our group have some expertise.</div>
<div><br>
</div>
<div>I agree re-fitting is possible but far from ideal.</div>
</div>
</blockquote>
<br>
<blockquote type="cite">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>Ian</div>
</div>
</blockquote>
</div>
<div><br>
</div>
<br>
<div>
<div>On 23 Feb 2012, at 17:18, Kästner, Lars wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
Hi Ian,
<div><br>
</div>
<div>first of all: good to know that FLIM data become an issue for OMERO - something I proposed many years ago and I already gave up the hope it happens ;-)</div>
<div>I am not sure if everybody is aware of the fact that different FLIM-microscopes do not just provide different data formats but in dependence of technology totally different data qualities (e.g. TCSPC, streak camera based, time gated cameras or PMTs, frequency
modulation etc.).</div>
<div><br>
</div>
<div>I share the concerns, but believe a loss of precision is acceptable as an intermediate result. If necessary data can still be reanalyzed (fitted). </div>
<div><br>
</div>
<div>Best,</div>
<div>Lars.</div>
<div><br>
</div>
<div><br>
<div><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">
<div>
<div style="font-size: 12px; ">Dr. Lars Kaestner</div>
<div style="font-size: 12px; ">Reseach Centre for Molecular Imaging and Screening</div>
<div style="font-size: 12px; ">School of Medicine</div>
<div style="font-size: 12px; ">Building 61</div>
<div style="font-size: 12px; ">Saarland University</div>
<div style="font-size: 12px; ">66421 Homburg / Saar</div>
<div style="font-size: 12px; ">Germany</div>
<div style="font-size: 12px; "><br>
</div>
<div style="font-size: 12px; ">ph. +49 6841 1626149</div>
<div style="font-size: 12px; ">Fax +49 6841 1626104</div>
</div>
</span></div>
</div>
<div>
<div>Am 22.02.2012 um 13:16 schrieb Munro, Ian:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div>HI all<br>
<br>
At the recent Dundee meeting I described 3 categories of data required to make OMERO compatible with
<br>
fluorescence lifetime imaging (FLIM).<br>
<br>
1) 'raw' time-resolved intensity data<span class="Apple-tab-span" style="white-space:pre">
</span><span class="Apple-tab-span" style="white-space:pre"></span>(as acquired by the microscope)<br>
2) fitted (floating point) parameter 'images'<span class="Apple-tab-span" style="white-space:pre">
</span>(generated by fitting software)<br>
3) merged RGB maps.<span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"></span><span class="Apple-tab-span" style="white-space:pre"></span><span class="Apple-tab-span" style="white-space:pre"></span><span class="Apple-tab-span" style="white-space:pre"></span>(for
inclusion in papers etc)<br>
<br>
Currently the 2nd type is stored as a .csv image by the fitting code that Donald has already included in OMERO.<br>
There is concern here over this for two reasons:<br>
<br>
1) iIt is inefficient in terms of storage.<br>
2) There will inevitably be a loss of precision.<br>
<br>
Could we change to another format for this (assuming it isn't too late) ?<br>
If so what format?<br>
<br>
Any thoughts welcome.<br>
<br>
Regards<br>
<br>
Ian<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">http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel</a><br>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
</div>
<br>
</body>
</html>