Having problems with Comets

Software Siril
1

Siril -1.2.0 - Windows 11 - 130 Canon .CR2 images of Comet Lemmon

I always have to go back and read the comet processing tutorial because its usually a year or more between decent comets. I have sucessfully processed comets in the past but now I have a problem.

Process all with Script.
Change working directory to \process.
Open pp_light.seq
Select reference image (usually the first one)
Open the reference image alone and use photometric color calibration.
Save the reference image.
Open pp_light.seq and check that the reference image is selected and is indeed color corrected.
All OK so far…
Register with Global Star Alignment (Deep Sky)
Stack with Windsorized Sigma Clipping, Additive with scaling.
The result looks OK with decent stars and comet mostly removed.
At this point I have successfully created a movie using the suggested 1600 x 1600 and boxselect. And the images in the movie are color correct.

The next step is where things go wrong

Load again r_pp_light,seq and Registration, choose Comet/Asteroid.
Choose the first frame and select.
Choose the last frame and select. (xy and velocity look OK)
Here’s the problem. Only the first frame is color corrected - all frames in r_pp_light shoiuld be color corrected I think?
Clicking Go Register results in only the first frame being registered.

Any ideas where this is going wrong?
Geoff

2

A normalization must be missing somewhere, don’t you export the sequence at some point? Like written in this section Siril - Working with Comets

3

Well, that very clear description written by Cecile Melis is what I am following, everything works just fine (inc making a movie) right up until I get the “Comet alignment and stacking” section. After reloading the registered sequence I note that only the reference image is color corrected.
As I said, very strange because I have done this succesfully in the past…

4

Hi Geoff,

It sounds like your processing manually, and the process is missing the command to apply your calibration to the sequence. In a script it would be done with the seqapplyreg command, but in the manual processing you very likely would need to select a switch or press a button somewhere. I suggest going through the steps just before the errors again to see, if the it is available there.

5

Thanks guys I think I figured it out, I got some better data and made it work!