<html>
<head>
<base href="http://fiji.sc/bugzilla/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDSINFO "
title="NEEDSINFO - Coloc2 apparently no longer being supported"
href="http://fiji.sc/bugzilla/show_bug.cgi?id=1100#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEEDSINFO "
title="NEEDSINFO - Coloc2 apparently no longer being supported"
href="http://fiji.sc/bugzilla/show_bug.cgi?id=1100">bug 1100</a>
from <span class="vcard"><a class="email" href="mailto:ann.wheeler@igmm.ed.ac.uk" title="Ann Wheeler <ann.wheeler@igmm.ed.ac.uk>"> <span class="fn">Ann Wheeler</span></a>
</span></b>
<pre>Specifically:
Coloc2 is 90% done . The issues are all to do with (i) menu functionality e.g.
selecting what to colocalise and which coefficients are needed. This is
implemented in colocalisation threshold (set options checkbox), though this is
mathematically weaker than Coloc2 and colocalisation threshold can't colocalise
ROIs from the ROI manager.
(ii) Results display. In the output results file one needs to know what slice
and ROI the colocalisation coefficients correspond to and be able to only chose
the ones of interest for the study .
(iii) This all needs to be scriptable so if one has 100 - 200 images Fiji can
munch through them and generate an results file exportable to Excel with:
Columns corresponding to:
Slice, ROI, Threshold, 'My favourite colocalisation coefficient', 'Other
colocalisation coefficient', 'AN OTHER parameter as desired'
Rows corresponding to:
Slice 1, ROI1
Slice 1, ROI2
Slice 2, ROI1
Slice 2, ROI2 etc
Not dissimilar to the output of multimeasure for analysing particles. Manders
Coefficient and ICQ in IJ1 can do all of this and are scriptable easily.
(iv) Another thing is the x and y axis of the plots in Coloc2 are not labeled
so it sin't clear which axis corresponds to channel 1 and channel 2 in the
output. I assume it's always consistent. I guess this is a easy fix.
(v) A more delicate matter, These issues have been outstanding for over a year,
which is the reason for additional fuss. Generally all issues of 'plugin not
playing' are promptly addressed in updates, since Fiji as a group of developers
are really good at maintaining tools. So perhaps these Coloc2 coding issues may
be easier to resolve than the 'finding a person who has time to do the coding'
issue.. </pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>