Oops, accidentally hit delete on the last post attempt:
I use a script that stacks my data into chuncks (about 100 at a time) to create “sub-stacks”. I then stack these substacks with a final stacking program that understands that these are now debayered 32-bit RGB Fits.
Here is a snippet of the code that uses platesolving for creating of a single substack:
#platesolve the lights
seqplatesolve pp_light1 -disto=distortionFile
# Align lights
# First doing: register pp_light1 -2pass -nostarlist
register pp_light1 -2pass -nostarlist -disto=file ./distortionFile
# Now doing: seqapplyreg pp_light1 -framing=max
seqapplyreg pp_light1 -framing=max
This works well, The question is, how do I take advantage of the distortion information in the .FITS header when I stack these substacks together.
If I do nothing, I get this note in the console:
12:57:12: Processing all images in the sequence (87)
**12:57:12: Distortion was found in reference image astrometry but you did not include distortion correction when registering the images**
12:57:12: Apply registration: with the current memory and thread limits, up to 27 thread(s) can be used
So it sees the distortion information, but if I put this in my stacking command line:
# Align lights
# First doing: register
register pp_light -2pass -disto=image -nostarlist
# Now doing: seqapplyreg pp_light -framing=max
seqapplyreg pp_light -framing=max
It says:
13:01:46: You have selected undistortion from current image but it is not platesolved, perform astrometry first or disable distortion
13:01:46: Error in line 25 (‘register’): invalid arguments.
Do I need to re-platesolve these substacks? I tried but it says they are already platesolved so it creates no distortion file and that then also fails.
How do I accomplish distortion correction using the platesolving that is done on these substacks? I see in the .FITS header it appears to have all the distortion information.