Siril stacking starved of RAM

Software Siril
1

Hello

I am pre-processing 180 60 second OSC subs of M31 with OSC_Preprocessing script. The first problem if one image fails calibration the entire process just stops. Should it not continue and just display a warning at the end?

I was lucky it was the last image that failed so I just continued by runing the remaining commands from the script manually.

When I run stack command Siril drained the PC’s RAM, it is still running and the process so far taken 9.5 GB of RAM and counting.

Is this expected behaviour?

P.S. The process eventually used nearly 14GB but there was a message in the console at the beginning of stacking using 14GB of RAM, I have 32 GB of RAM in total on my machine.

image
image1903×954 897 KB

2

Yes it is. You can modify settings in the Siril preferences if you want.
Also, you can change the number of thread used at the top of the application.

3

Thank you lock042

I will lookup those settings.

Is there any setting to continue processing if the processing of some of the subs fails?

4

First. Do you know why calibration fails? This step should never fail.

5

Here is the error:

05:25:51: Filter Pattern: RGGB
05:25:58: Saving FITS: file pp_light_00016.fit, 3 layer(s), 6224x4168 pixels, 32 bits
05:26:31: Reading FITS: file light_00185.fit, 3 layer(s), 18672x12504 pixels, 32 bits
05:26:31: Image #184: number of layers (3) is not consistent with sequence (1), aborting
05:26:31: Sequence processing failed.
05:26:31: Setting CWD (Current Working Directory) to ‘E:\Astrophoto\M31-2024-08-12’
05:26:31: Script execution failed.

Thank you for looking at this lock042, it is much appreciated

P.S. I can see now what happened - I stacked before in DSS and forgot to remove the stacked file. Either way IMO it would be good if the script just carry on executing if only one file fails. But I understand that may not be a simple change and it is probably not configurable