Script command stubs in log output
It would be great to draft a Siril script by using Siril's graphical user interface. This could be done easily if the log output would include a script-command-equivalent of the operation that is being performed, not only the output of that operation.
For example, my typical Siril session looks line this:
- add a bunch of RAW DSLR images
- name the sequence
- click the debayer checkbox
- hit Convert
- (wait 10 minutes over which I'll start doing something else and will return to Siril graphical interface much later when I have a break in whatever else I'm doing)
- go to the Align tab and click the button to align the images using "Global star alignment"
- (wait 20 minutes over which I'll start doing something else and will return to Siril graphical interface much later when I have a break in whatever else I'm doing)
- go to the stack tab, indicate that I want to reject 10% of images with the worst FWHM, hit stack button
- (wait 20 minutes over which I'll start doing something else and will return to Siril graphical interface much later when I have a break in whatever else I'm doing)
- Now I have my stacked image and I repeat the whole thing for the next set of images, typically I have 5 such sets per night.
The problem is that the procedure that takes 50 minutes of computer time takes a couple of hours of wall time as I have to interact with the graphical interface multiple times with long breaks between the interactions. (It is obviously impractical to stare at the program for 20 minutes while it's working. Having a pop-up notification that an operation is complete is not a perfect solution either, as the pop-ups are distracting). The obvious solution would be writing a script. However (being an inexperienced Siril user) I don't know the Siril script language. The example scripts are pretty self-explanatory, however they are too basic for what I'm trying to do (how do I debayer the images? how do I set FWHM rejection at 90%?). Many settings are obvious in the graphical interface, but it is totally unclear (again for me, being an inexperienced user) how to translate them to the parameters of the scriptable commands.
It would be helpful if at each click of a button (such as Convert, Align, Stack) the log would indicate how the corresponding command with the current settings would have looked like in a script.