Am watching a drizzle integration roll buy after NSG did the regular integration.
Some, not all, but some frames are doing this during the Drizzle run after NSG's integration. I used NSG's integration process (initialized with the icon I usually use), and did not notice any errors in that, but see infrequent but not an insignificant number of these red errors rolling by (I'm capturing the log so once it finishes I can look more closely).
Any suggestions what it means and where I look if it may be something I did?
And does it imply a bad run that I need to start over in some fashion?
I did SFS (with approval in case I decided later not to use NSG), then star align with drizzle, then filter by filter did NSG using a reference from SFS (that I also looked at manually) based on mostly star count and FWHM, then integration (auto-run) and then drizzle integration (load up the drz/nml files and run). I saw this in at least a couple filters then turned on logging so I do not have logging for all 5 (LRGB+Ha).
Ah... it just finished the drizzle integration, and it does show 19 failures (174 success), so it is flagging these subs as failures (see below):
View attachment 13848
So I dredged out a failure from the log, there is little detail, or more precisely the log shows no additional details:
Code:
[2022-03-05 18:17:13] * Parsing drizzle data file 183 of 193:
[2022-03-05 18:17:13] T:/Stage/M82/Registered/LIGHT_M 82(1)_2022-02-28_05-48-22_Ha-5nm_300.00s_SET-TEMP_-10.00C_Gain_100_Offset_50_Bin_1x1_2800mm_-10.00C_0059_c_cc_a_r.xdrz
[2022-03-05 18:17:13] *** Error: Missing required LocationEstimates element.
[2022-03-05 18:17:13]
[2022-03-05 18:17:13] * Applying error policy: Continue on error.
[2022-03-05 18:17:13]
The file is present in the DrizzleIntegration input data pain, properly shows the n for normalization data present, and all three files (xsif, xnml and xdrz) are present in the folder as expected, and the original input files have not moved either.
What does this mean, and is it a sign I did something wrong in NSG? Or a bug?