M31_finally properly processed?
Posted: Fri Jan 08, 2021 9:52 pm
The lack of clear skies had me finally spending time to learn something about how to better process images. So I revisited some frames that I took under fairly dark skies (Bortle 4) on a new moon last September. Originally I had used DSS to stack SC-captured FIT files, PixInsight to process the stack and finally a freeware 16 bit only Photo programme to clean up the final pictures. More experienced folk will groan and know all of the following already ... as well as a great deal more.....
Anyway for me the break from observing has been an opportunity to learn firstly that PixInsight is a better tool than is DSS for calibrating, aligning and stacking images - especially with use of the PI tools to preselect the best subframes. Careful side by side comparisons showed that PI stacking produced noticeably sharper images (even before rejecting frames).
Another interesting observation was around the FWHM analysis of each frame. DSS estimated FWHM pixel values of ca 3.3. which worried me because at 1.55 arcsec per pixel the overall resolution would seem very poor (FWHM arc sec > 5 arcsec) and indicate that either my scope or the seeing was poor (PHD2 tracking seemed fine at < 1 arcsec RMS). PI on the other hand estimated the same frames as FWHM pixel ca. 2.0 which is much better and made more sense --the PI value being self consistent with other measurements and across different scopes and the resolution apparent in the images themselves.
Finally I also bought Affinity Photo - a proper 32 bit capable Photoshop type programme but not so expensive - and, again, a big improvement on using the freeware. Anyway - an overlong preamble - . The main problem I have now is in trying to walk the line between appropriate processing and overdoing it!
The attached image of M31 was ~ 100 minutes (after culling about 10% of the frames) of 46s exposures at unity gain and -5C using an ASI 294 PRO colour camera and a WO Zenithstar 110 mm triplet apo refractor at F 5.6 using a WO 0.8X reducer/ flattener. It was taken on holiday under Bortle 4 skies. I was unusually fortunate to a) go on holiday and get a good clear night and b) have the orientation of M31 right across the diagonal of the sensor - also entirely fortuitous.
https://onedrive.live.com/?cid=330584F8 ... 29&o=OneUp
Happy New year to those on this forum, Tim
Anyway for me the break from observing has been an opportunity to learn firstly that PixInsight is a better tool than is DSS for calibrating, aligning and stacking images - especially with use of the PI tools to preselect the best subframes. Careful side by side comparisons showed that PI stacking produced noticeably sharper images (even before rejecting frames).
Another interesting observation was around the FWHM analysis of each frame. DSS estimated FWHM pixel values of ca 3.3. which worried me because at 1.55 arcsec per pixel the overall resolution would seem very poor (FWHM arc sec > 5 arcsec) and indicate that either my scope or the seeing was poor (PHD2 tracking seemed fine at < 1 arcsec RMS). PI on the other hand estimated the same frames as FWHM pixel ca. 2.0 which is much better and made more sense --the PI value being self consistent with other measurements and across different scopes and the resolution apparent in the images themselves.
Finally I also bought Affinity Photo - a proper 32 bit capable Photoshop type programme but not so expensive - and, again, a big improvement on using the freeware. Anyway - an overlong preamble - . The main problem I have now is in trying to walk the line between appropriate processing and overdoing it!
The attached image of M31 was ~ 100 minutes (after culling about 10% of the frames) of 46s exposures at unity gain and -5C using an ASI 294 PRO colour camera and a WO Zenithstar 110 mm triplet apo refractor at F 5.6 using a WO 0.8X reducer/ flattener. It was taken on holiday under Bortle 4 skies. I was unusually fortunate to a) go on holiday and get a good clear night and b) have the orientation of M31 right across the diagonal of the sensor - also entirely fortuitous.
https://onedrive.live.com/?cid=330584F8 ... 29&o=OneUp
Happy New year to those on this forum, Tim