I have been chatting to Peter from CloudMakers as I have been using his Atik CCD driver in my INDI setup on an oDroid.
I managed a proper run with it all on Monday night & have only just started to look in detail at the test images I took.
I am use to Pinpoint when solving FITS images & have used Maxim in the past - both of these use XPIXSZ & YPIXSZ for the pixel size. This has allowed the focal length to be calculated along with the solve. INDI uses PIXSIZE1 & PIXSIZE2
What I also notice is happening is, when I binned the image x4, the PIXSIZE1 & 2 remain at 6um's which I presume is normal, and XBINNING/YBINNING is 4...
Problem is, none of my external programs use PIXSIZE1 & 2.
I realise that the FITS "standard" is almost anything but a standard with all the extensions, but would like to get clarity here about this.
For me, XPIXSZ & YPIXSZ would show the "logical" size.... i.e. x1 binning = 6um, x4 binning = 24um, etc... This would be consistent with at least some of the other programs I use.
Phil
I managed a proper run with it all on Monday night & have only just started to look in detail at the test images I took.
I am use to Pinpoint when solving FITS images & have used Maxim in the past - both of these use XPIXSZ & YPIXSZ for the pixel size. This has allowed the focal length to be calculated along with the solve. INDI uses PIXSIZE1 & PIXSIZE2
What I also notice is happening is, when I binned the image x4, the PIXSIZE1 & 2 remain at 6um's which I presume is normal, and XBINNING/YBINNING is 4...
Problem is, none of my external programs use PIXSIZE1 & 2.
I realise that the FITS "standard" is almost anything but a standard with all the extensions, but would like to get clarity here about this.
For me, XPIXSZ & YPIXSZ would show the "logical" size.... i.e. x1 binning = 6um, x4 binning = 24um, etc... This would be consistent with at least some of the other programs I use.
Phil