Frustrated...going backwards

[admin]

Thank you,

BITPIX = -32 means that the data have been converted to 32-bit floating point
NAXIS = 3 means that the data have been separated into three channels

This is more evidence ASIAIR is - likely - converting and debayering your frames to full-color RGB.

[Pscm]

Just in case I misinterpreted the request,
This is a singular file un-stacked FITS file created by the ASIAIR:
SIMPLE = T / file does conform to FITS standard BITPIX = 16 / number of bits per data pixel NAXIS = 2 / number of data axes NAXIS1 = 6016 / length of data axis 1 NAXIS2 = 4016 / length of data axis 2 EXTEND = T / FITS dataset may contain extensions COMMENT FITS (Flexible Image Transport System) format is defined in 'AstronomyCOMMENT and Astrophysics', volume 376, page 359; bibcode: 2001A&A...376..359H BZERO = 32768 / offset data range to that of unsigned short BSCALE = 1 / default scaling factor CREATOR = 'ZWO ASIAIR' / Capture software EXPOSURE= 300. / Exposure time in seconds DATE-OBS= '2019-10-27T01:50:49.586' / Image created time XORGSUBF= 0 / Subframe X position in binned pixels YORGSUBF= 0 / Subframe Y position in binned pixels FOCALLEN= 477 / Focal length of telescope in mm INSTRUME= 'Nikon DSC D5300' / Camera model BAYERPAT= 'RGGB ' / Bayer pattern XBINNING= 1 / Camera X Bin YBINNING= 1 / Camera Y Bin CCDXBIN = 1 / Camera X Bin CCDYBIN = 1 / Camera Y Bin XPIXSZ = 3.89 / pixel size in microns (with binning) YPIXSZ = 3.89 / pixel size in microns (with binning) IMAGETYP= 'Light ' / Type of image ISO = '200 ' / ISO Value

[Pscm]

Based on Admin's comment in between my two posts, if I am reading correctly it would appear that DSS is doing something to the files as the singular unstacked file looks a bit different?

[admin]

Just in case I misinterpreted the request,
This is a singular file un-stacked FITS file created by the ASIAIR:
SIMPLE = T / file does conform to FITS standard BITPIX = 16 / number of bits per data pixel NAXIS = 2 / number of data axes NAXIS1 = 6016 / length of data axis 1 NAXIS2 = 4016 / length of data axis 2 EXTEND = T / FITS dataset may contain extensions COMMENT FITS (Flexible Image Transport System) format is defined in 'AstronomyCOMMENT and Astrophysics', volume 376, page 359; bibcode: 2001A&A...376..359H BZERO = 32768 / offset data range to that of unsigned short BSCALE = 1 / default scaling factor CREATOR = 'ZWO ASIAIR' / Capture software EXPOSURE= 300. / Exposure time in seconds DATE-OBS= '2019-10-27T01:50:49.586' / Image created time XORGSUBF= 0 / Subframe X position in binned pixels YORGSUBF= 0 / Subframe Y position in binned pixels FOCALLEN= 477 / Focal length of telescope in mm INSTRUME= 'Nikon DSC D5300' / Camera model BAYERPAT= 'RGGB ' / Bayer pattern XBINNING= 1 / Camera X Bin YBINNING= 1 / Camera Y Bin CCDXBIN = 1 / Camera X Bin CCDYBIN = 1 / Camera Y Bin XPIXSZ = 3.89 / pixel size in microns (with binning) YPIXSZ = 3.89 / pixel size in microns (with binning) IMAGETYP= 'Light ' / Type of image ISO = '200 ' / ISO Value

Thank you, that is indeed different to how I interpreted your earlier post. This appears to be a mono image with Bayer pattern still in place. As such, ASIAIR could not have color balanced this image yet, as there are no color channels to balance. Subsequently stacking these images in DSS likely will/should keep DSS from color balancing, as it is not will likely not know/detect this Bayered mono image came from a Nikon DSC D5300.

Using the ASIAIR-produced FITS files for stacking in DSS is likely a good way to go.

[Pscm]

Thanks for the info. Just for my curiosity how can you tell it is mono?

[admin]

Thanks for the info. Just for my curiosity how can you tell it is mono?

The clue is NAXIS = 2
This usually means that a dataset is stored mono (e.g. only one sample per X/Y coordinate). For an image, two (mandatory) axes are X and Y. Any third axis (making NAXIS equal 3, rather than 2) is usually the channel (red, green blue), which is missing in this instance. There are some rare exceptions (I believe Images Plus is one such exception) where the three channels are stored as three consecutive (separate) mono datasets, but it is generally not done this way.