Incorrect warning message while live stacking
Stacking program, astrometric (plate) solver, fits file viewer
Brought to you by:
han59
Menu
▾
▴
I have never tried live stacking before but tried it this evening just to see how it worked.
It seems to be working just fine except I got this warning when starting:
08:57:55 Analysing lights
08:58:03 Analysing lights done.
08:58:30 Using local variable database. Online version can be set in tab Photometry
08:58:30 Added 7 annotations.
09:00:32 Analysing lights
09:00:37 Analysing lights done.
09:38:45 Using local variable database. Online version can be set in tab Photometry
09:38:45 Added 7 annotations.
09:38:58 Using star database V50
09:38:58 65 stars, 50 quads selected in the image. 44 database stars, 34 database quads required for the square search field of 0.6°. Search window at 141% based on the number of quads. Step size at 100% of image height.
09:38:58 19 of 19 quads selected matching within 0.007 tolerance. Solution["] x:=-0.022848x+ -1.051678y+ 1133.034554, y:=-1.051789x+ 0.022823y+ 1616.456150
09:38:58 Solution found: 08: 32 52.8 +13° 11 20 Solved in 0.2 sec. Δ was 3.1'. Mount Δα=-2.5', Δδ=1.8'. Used stars down to magnitude: 13.2
09:39:08 Using local variable database. Online version can be set in tab Photometry
09:39:08 Added 6 annotations.
09:42:39 Using star database V50
09:42:39 273 stars, 217 quads selected in the image. 183 database stars, 145 database quads required for the square search field of 0.6°. Search window at 100% based on the number of quads. Step size at 100% of image height.
09:42:39 75 of 75 quads selected matching within 0.007 tolerance. Solution["] x:=-0.022909x+ -1.051796y+ 1133.682252, y:=-1.051775x+ 0.022644y+ 1616.931164
09:42:39 Solution found: 08: 32 52.9 +13° 11 20 Solved in 0.3 sec. Δ was 0.5". Mount Δα=-0.6', Δδ=2.3'. Used stars down to magnitude: 15.7
09:42:43 Using local variable database. Online version can be set in tab Photometry
09:42:43 Added 6 annotations.
09:43:43 Using star database V50
09:43:43 175 stars, 139 quads selected in the image. 117 database stars, 93 database quads required for the square search field of 0.6°. Search window at 100% based on the number of quads. Step size at 100% of image height.
09:43:43 43 of 43 quads selected matching within 0.007 tolerance. Solution["] x:=-0.022905x+ -1.051823y+ 1133.109174, y:=-1.051706x+ 0.022429y+ 1617.188675
09:43:43 Solution found: 08: 32 52.9 +13° 11 20 Solved in 0.3 sec. Δ was 0.5". Mount Δα=-0.6', Δδ=2.3'. Used stars down to magnitude: 15.0
09:43:46 Using local variable database. Online version can be set in tab Photometry
09:43:47 Added 6 annotations.
19:39:41 Loading master dark file /Users/bill/Desktop/Photometry/Calibration/Dark/master_dark_15x120s_at_-10C_2023-12-30.fit
19:39:41 █ █ █ █ █ █ Warning dark gain (100.00) is different then the light gain (1.000E+02)! █ █ █ █ █ █
19:39:41 Loading master flat file /Users/bill/Desktop/Photometry/Calibration/Flat/master_flat_corrected_with_flat_darks_V_20xF_15xFD_2023-12-31.fit
19:39:41 Adding file: 1 "/Users/bill/Desktop/Photometry/Ekos/TT_Cnc/Light/V/TT_Cnc_Light_V_120_secs__004.fits" to average. Using 15 darks, 20 flats, 15 flat-darks
Since a gain of 100 is the same as 1.00E+2, it seems this shouldn't be displayed
Hi Bill,
That is an interesting one. I think it is compared as a string. I will look later. But how did you manage to get gain stored differently in the header of the light and dark? Are ther written by the same program version?
Han
Maybe the fault is in ASTAP using different conversions.
Hi Bill,
I tested it here. If the string value is identical in the dark and light there is no warning message. So I assume the 1.000E+02 is written in this format in the header of the light
In ASTAP the gain is processed as a string so as text. Changing that could could be risky. It has also to read ISO setting and if somebody decided to add a unit it will not work. It is only a warning and should not reoccur if the same program version is used for creating both the lights and darks.
Han
Yes they are different. ASTAP created both the master flat and the master dark.
Here is the header of the Dark:
SIMPLE = T / file conforms to FITS standard
BITPIX = -32 / number of bits per data pixel
NAXIS = 2 / number of data axes
NAXIS1 = 3120 / length of data axis 1 [pixels]
NAXIS2 = 2088 / length of data axis 2 [pixels]
EXTEND = T / FITS dataset may contain extensions
BZERO = 0 / offset data range to that of unsigned short
BSCALE = 1 / default scaling factor
XBINNING= 1 / horizontal binning [pixels]
YBINNING= 1 / vertical binning [pixels]
XPIXSZ = 3.76 / pixel width [microns]
YPIXSZ = 3.76 / pixel height [microns]
EXPTIME = 120.00 / exposure time [s]
CCD-TEMP= -10 / CCD temperature [C]
IMAGETYP= 'Dark '
GAIN = 100.00 / Gain
OFFSET = 10.00 / Offset
DATE-OBS= '2023-12-30T23:08:42.389' / UTC date that FITS file was created
INSTRUME= 'ZWO ASI2600MM Pro' / instrument name
ROWORDER= 'TOP-DOWN' / Image row order
APTDIA = 100.00 / Aperture diameter (mm)
FOCALLEN= 736.00 / Focal length (mm)
SITELAT = '40 08 25'
SITELONG= '254 50 30'
OBJCTRA = '17 49 05'
OBJCTDEC= '90 00 00'
FILTER = 'V'
DARK_CNT= 15 / Number of dark image combined
COMMENT 7 Dark temperature tolerance setting was 1 degrees Celsius
COMMENT 1 Written by ASTAP. www.hnsky.org
DATAMIN = 0 / Minimum data value
DATAMAX = 65535 / Maximum data value
CBLACK = 0 / Black point used for displaying image.
CWHITE = 65535 / White point used for displaying the image.
END
The Light was created my INDI/Ekos.
Here is the header of the Light:
SIMPLE = T / file does conform to FITS standard
BITPIX = 16
NAXIS = 2 / number of data axes
NAXIS1 = 3120 / length of data axis 1
NAXIS2 = 2088 / length of data axis 2
EXTEND = T / FITS dataset may contain extensions
COMMENT FITS (Flexible Image Transport System) format is defined in 'Astronomy
COMMENT and Astrophysics', volume 376, page 359; bibcode: 2001A&A...376..359H
BZERO = 32768.000000000000
BSCALE = 1.000000000000
ROWORDER= 'TOP-DOWN' / Row Order
INSTRUME= 'ZWO CCD ASI2600MM Pro' / Camera Name
EXPTIME = 1.200000E+02 / Total Exposure Time (s)
CCD-TEMP= -9.900E+00 / CCD Temperature (Celsius)
PIXSIZE1= 3.760000E+00 / Pixel Size 1 (microns)
PIXSIZE2= 3.760000E+00 / Pixel Size 2 (microns)
XBINNING= 1 / Binning factor in width
YBINNING= 1 / Binning factor in height
XPIXSZ = 3.760000E+00 / X binned pixel size in microns
YPIXSZ = 3.760000E+00 / Y binned pixel size in microns
FRAME = 'Light ' / Frame Type
IMAGETYP= 'Light Frame' / Frame Type
FILTER = 'V ' / Filter
FOCALLEN= 7.370E+02 / Focal Length (mm)
APTDIA = 1.000E+02 / Telescope diameter (mm)
SCALE = 1.052494E+00 / arcsecs per pixel
SITELAT = 4.014028E+01 / Latitude of the imaging site in degrees
SITELONG= -1.051583E+02 / Longitude of the imaging site in degrees
AIRMASS = 1.243169E+00 / Airmass
OBJCTAZ = 1.298800E+02 / Azimuth of center of image in Degrees
OBJCTALT= 5.352373E+01 / Altitude of center of image in Degrees
OBJCTRA = ' 8 32 47.46' / Object J2000 RA in Hours
OBJCTDEC= '13 12 10.63' / Object J2000 DEC in Degrees
RA = 1.281978E+02 / Object J2000 RA in Degrees
DEC = 1.320295E+01 / Object J2000 DEC in Degrees
PIERSIDE= 'WEST ' / West, looking East
RADECSYS= 'FK5 ' / RADECSYS
SECPIX1 = 1.0524938915E+00 / SECPIX1
SECPIX2 = 1.0524938915E+00 / SECPIX2
CDELT1 = 2.9235941430E-04 / CDELT1
CDELT2 = 2.9235941430E-04 / CDELT2
CROTA1 = 2.7123889012E+02 / CROTA1
CROTA2 = 2.7123889012E+02 / CROTA2
DATE-OBS= '2024-03-02T02:59:26.023' / UTC start date of observation
COMMENT Generated by INDI
GAIN = 1.000E+02 / Gain
OFFSET = 1.000E+01 / Offset
OBJECT = 'TT Cnc ' / Object
OBSERVER= 'Bill Tschumy' / Observer
TELESCOP= 'Takahashi Tak FC-100DF 737@F\7.4' / Telescope
CALSTAT = 'DF'
CTYPE1 = 'RA---TAN-SIP' / TAN (gnomic) projection + SIP distortions
CTYPE2 = 'DEC--TAN-SIP' / TAN (gnomic) projection + SIP distortions
EQUINOX = 2000.0 / Equatorial coordinates definition (yr)
LONPOLE = 180.0 / no comment
LATPOLE = 0.0 / no comment
CUNIT1 = 'deg ' / X pixel scale units
CUNIT2 = 'deg ' / Y pixel scale units
CRPIX1 = 1560.5 / X reference pixel
CRPIX2 = 1044.5 / Y reference pixel
CRVAL1 = 128.227564457 / RA of reference point
CRVAL2 = 13.1976631984 / DEC of reference point
CD1_1 = 6.32317422148E-06 / Transformation matrix
CD1_2 = 0.000292101899577 / no comment
CD2_1 = -0.000292130247886 / no comment
CD2_2 = 6.31725343645E-06 / no comment
A_ORDER = 3 / Polynomial order, axis 1
A_0_0 = 0 / no comment
A_0_1 = 0 / no comment
A_0_2 = 4.18122667925E-09 / no comment
A_0_3 = -4.5637088615E-12 / no comment
A_1_0 = 0 / no comment
A_1_1 = 4.38289271228E-08 / no comment
A_1_2 = 4.5272471374E-11 / no comment
A_2_0 = -1.57502099679E-08 / no comment
A_2_1 = 2.16673126685E-11 / no comment
A_3_0 = 9.30049037274E-12 / no comment
B_ORDER = 3 / Polynomial order, axis 2
B_0_0 = 0 / no comment
B_0_1 = 0 / no comment
B_0_2 = -4.5321327383E-08 / no comment
B_0_3 = 1.28062242336E-10 / no comment
B_1_0 = 0 / no comment
B_1_1 = -9.82258722501E-10 / no comment
B_1_2 = -3.39035262439E-11 / no comment
B_2_0 = 1.43968989233E-08 / no comment
B_2_1 = 5.56968737715E-11 / no comment
B_3_0 = 1.00177912286E-11 / no comment
AP_ORDER= 3 / Inv polynomial order, axis 1
AP_0_0 = 2.79069202697E-07 / no comment
AP_0_1 = -2.15872153004E-09 / no comment
AP_0_2 = -4.18082823091E-09 / no comment
AP_0_3 = 4.5625204673E-12 / no comment
AP_1_0 = -6.2691058788E-09 / no comment
AP_1_1 = -4.38188905529E-08 / no comment
AP_1_2 = -4.52486354161E-11 / no comment
AP_2_0 = 1.57496916382E-08 / no comment
AP_2_1 = -2.16612742908E-11 / no comment
AP_3_0 = -9.29542149344E-12 / no comment
BP_ORDER= 3 / Inv polynomial order, axis 2
BP_0_0 = 1.36049042792E-06 / no comment
BP_0_1 = -3.81110180915E-08 / no comment
BP_0_2 = 4.52968966929E-08 / no comment
BP_0_3 = -1.27965672635E-10 / no comment
BP_1_0 = 4.06414731922E-10 / no comment
BP_1_1 = 9.82533947151E-10 / no comment
BP_1_2 = 3.38829738762E-11 / no comment
BP_2_0 = -1.43937608009E-08 / no comment
BP_2_1 = -5.56638771437E-11 / no comment
BP_3_0 = -1.00152608193E-11 / no comment
END
So yeah, a string compare isn’t going to work.
I don’t think I get this warning when just doing a normal stack, so it must be slightly different code used for he live stack.
Bill
Han,
Did you see this final message from me? The two strings are different but comperable. String compare won't work
Hi Bill,
But why is INDI writing it scientific for the dark and as an integer for the light? The dark was written at 2023-12-30 and the light 2024-03-02.. For the moment I assume that new darks will have an header with this "100" as gain. So then the problem will go away. If not I have make the program smarter then it is now. Can you check if new darks solve this minor problem?
Han
I believe I used ASTAP to create the master darks. INDI was used for the lights.
The date in the master dark is taken from the darks. I still hope it is going away when you make new darks and light. Tell me how it is going when you make new ones.