I have measured the pixel noise in the Canon EOS 35 mm camera. This is the same one as used to measure the halo of the moon at large distances (up to 15 degrees) from my Sydney backyard.
60 exposures were taken of a flat white surface, in groups of 10, with 5 exposures times from 1 second down to 1/200th of a second. (A 6th exposure time was discarded due to saturation).
Frames converted from CR2 format to fits format using cdraw and convert:
ls *.CR2 | awk ‘{print “dcraw -T -4 ” $1}’ | bash
ls *.tiff | awk ‘{print “convert ” $1, $1″.fits”}’ | sed -e s/.tiff.fits/.fits/ | bash
the tiff files this produces still have colour information, which I wasn’t expecting. The fits files are of course grey scale, but I suspect they are averaged over the three colours (RGB), so that the apparent photon counts are three times smaller than the actual photon counts.
The standard deviation and mean flux in 9 randomly chosen individual pixels was computed across the of 10 images obtained for each of 5 exposure times. The square root of the mean (times 3) is then plotted versus the standard deviation of the values, yielding 45 noise measurements (i.e. 9 pixels x 5 exposure levels of the pixel = 45). If the noise is anything like Poisson noise, these should lie on the 1:1 line.
This proves to be approximately the case as seen below.
It’s pretty noisy though! (i.e. the noise measurement is noisy).
Inspection of the fits files ds9 shows that there are clear correlations on various scales in both the X and y directions in the images — so the camera is surely introducing smoothing of some sort, so there is only so far one can push this analysis!
Conclusion : Poisson noise is a fair first order approximation for the behaviour of a commercial camera CCD chip.
ImageMagick has an option “-channel” that can be set to R G or B, but I’ll be blowed if I can get it to do anything!
If you read the image in IDL you will get the image as (3,512,512) or (512,512,3) or whatever and the RGB fields are in the 3 dimensions. But without IDL … hm – write a Fortran code that reads TIFF images, and seperate the fields? I wonder if ImageMagick can do the trick? WIll look into this.
First rate stuff sir! Yep, that 777 thing will certainly cause problems like that.
Do you know how to extract a single colour “gun” from the tiffs by any chance?
Sir! I tried your clever awk/convert scripts on my .tiff images – and it failed. I then saw that all my .tiff images have a star after their names when I list their names – but not ‘really’ – i.e. the star is indicating that the files are executable. This has happened due to the ill-advised application of chmod 777 * once upon a time.
So, I applied chmod 644 *.tif and everything was hunkey-dorey! I could thusly convert the TIFF images to fits!