Trouble processing 2x2 binned images in ISIS.
Posted: Tue Aug 19, 2014 9:12 pm
Hello.
In taking spectra of dim targets (such as Nova Cyg 2014) with my Alpy600, I saw that the snr was low when comparing my results with others. At the advice of Francois Tessyier, I tried binning my images 2x2, something I had never before tried. Sure enough, the images are coming out much cleaner, however, when I process those binned images in ISIS, I notice that the value for the X coordinate of the 5852.49 line in my neon spectrum shifts from 407 (as determined by clicking on that line) to 470 when using the calibration assistant. This results in a high calibration error (around 22). I cannot see how to prevent this "jump" from happening.
I am applying 2x2 binned flats, darks, and cosme files to the target images, so those should all be good. This issue does not occur when using 1x1 binned images as my rms values are then generally around .2-to .3. Is there something I need to do in ISIS when binning images that will keep this from happening? The only change made is that I am now trying to process 2x2 instead of 1x1 images.
Cheers,
Keith Graham
In taking spectra of dim targets (such as Nova Cyg 2014) with my Alpy600, I saw that the snr was low when comparing my results with others. At the advice of Francois Tessyier, I tried binning my images 2x2, something I had never before tried. Sure enough, the images are coming out much cleaner, however, when I process those binned images in ISIS, I notice that the value for the X coordinate of the 5852.49 line in my neon spectrum shifts from 407 (as determined by clicking on that line) to 470 when using the calibration assistant. This results in a high calibration error (around 22). I cannot see how to prevent this "jump" from happening.
I am applying 2x2 binned flats, darks, and cosme files to the target images, so those should all be good. This issue does not occur when using 1x1 binned images as my rms values are then generally around .2-to .3. Is there something I need to do in ISIS when binning images that will keep this from happening? The only change made is that I am now trying to process 2x2 instead of 1x1 images.
Cheers,
Keith Graham