Skip to content, Skip to search

Changes

Coloc 2

382 bytes added, 13:31, 30 July 2015
The auto threshold calculation method can fail if fed inappropriate information: fix typos, clarify, add a little detail
== The auto threshold calculation method can fail if fed inappropriate information ==
That means it does not like images with high zero offset, where no light detected still gives a large non zero pixel value. For instance, from a digital camera's zero offset / bias, or a confocal PMT's offset when incorrectly set). Also a high flat non specific background, which adds causes the same problem. These all add a constant number to the "real proportional" intensity relationship to with the "concentration" of the fluorescent dye. If pixels that contain no real (specific) signal have large intensity values, the algorithm has , no way of knowing thatabout the non zero intensity offset in all pixels, assumes the offset is real signal to be dealt with, and can reach a result for the thresholds where one or both of them is below the value of the lowest intensity value present in that channels colour channel of the image. This means that ALL of that channel's pixels are considered to be colocalised, then the Manders ' Coefficients that you get will reflect that aberrant , unrealistic situation. In these cases, the background and/ or offset should be carefully removed/subtracted before running the Coloc 2 or [[Colocalization Threshold]] plugin. The images below are an example of this situation, using the badly behaved data set: [http://fiji.sc/samples/150707_WTstack.lsm 150707_WTstack.lsm]. Note that the vaules values for M1 and tM1 are the same! This should not be the case. You can see the green channel threshold is wrongly set below the intensity where the image data intensities actually startsstart.
[[Image:BadOffsetConfusesCostesAutoThreshold.png|300px]]