No edit summary
(small update)
Line 7: Line 7:


<!--T:20-->
<!--T:20-->
Since its early days, Siril can take user inputs as textual [[Siril:Commands|commands]], from the command line. Recently, [[Siril:Commands#Commands_history|more commands have been added]], enabling for a basic automated processing of images. Commands can be stored in a file that we call '''script''', and they are executed one after the other. Some commands can be used in scripts, some cannot, this is indicated in the help of the command line from the graphical user interface of siril.
Since its early days, Siril can take user inputs as textual [[Siril:Commands|commands]], from the command line. Recently, [[Siril:Commands#Commands_history|more commands have been added]], enabling for a basic automated processing of images. Commands can be stored in a file that we call '''script''', and they are executed one after the other. Some commands can be used in scripts, some cannot, this is indicated in the help of the command line from the graphical user interface of Siril.


<!--T:3-->
<!--T:3-->
Since release [[Siril:0.9.9|0.9.9]], Siril can execute scripts from a file. Since [[Siril:0.9.10|0.9.10]], [[Siril:Commands|commands]] can also be taken from a [[Siril:Commands#Command_stream_.28pipe.29|named pipe]].
Since release [[Siril:0.9.9|0.9.9]], Siril can execute scripts from a file. Since [[Siril:0.9.10|0.9.10]], [[Siril:Commands|commands]] can also be taken from a [[Siril:Commands#Command_stream_.28pipe.29|named pipe]] and more recently from the standard input too.


==Using scripts== <!--T:5-->
==Using scripts== <!--T:5-->
There are two ways to start a script manually:
There are three ways to start a script:
* using the '''@''' keyword on the command line, followed by the script name, as explained [[Siril:Commands#Introduction|here]],
* from the graphical user interface, using the '''@''' keyword on the command line, followed by the script name in the current working directory, as explained [[Siril:Commands#Introduction|here]],
* or use the Scripts menu.
* from the graphical user interface, using the Scripts menu,
* from the command line interface (<tt>siril-cli</tt> executable), using argument <tt>-s</tt> followed by the script's path (see the man page for more info).


<!--T:6-->
<!--T:6-->
Line 33: Line 34:
* delete the 2 lines in the field as described below
* delete the 2 lines in the field as described below
* click on 'Apply'
* click on 'Apply'
* close and restart SiriL
* close and restart Siril
[[File:Preferences-Scripts_EN.jpg]]
[[File:Preferences-Scripts_EN.jpg]]


==Getting scripts== <!--T:8-->
==Getting scripts== <!--T:8-->
* Since release [[Siril:0.9.10|0.9.10]], scripts are provided with the installation.
* Since release [[Siril:0.9.10|0.9.10]], scripts are provided with the installation.
* Since release [[Siril:0.99.4|0.99.4]], a new command 'convert' allows the execution of universal scripts that are available for DSLR (RAW files) and Astro cameras (FITs files).
* Since release [[Siril:0.99.4|0.99.4]], a new command 'convert' allows the execution of universal scripts that are available for DSLR (RAW files) and astronomy cameras (FITS files).




<!--T:15-->
<!--T:15-->
'''Default scripts (automatically installed with SiriL):'''
'''Default scripts (automatically installed with Siril):'''


<!--T:9-->
<!--T:9-->
Line 71: Line 72:


<!--T:17-->
<!--T:17-->
We also suggest users to use [https://gitlab.com/free-astro/sirilic Sirilic] to generate scripts or [https://gitlab.com/free-astro/sirilic Sirilot] to provide a more suited way to manage all the files required for such a processing.
We also suggest users to use [https://gitlab.com/free-astro/sirilic Sirilic] to generate scripts or to provide a more suited way to manage all the files for multi-session processing.


</translate>
</translate>

Revision as of 23:35, 17 January 2022

Other languages:


Siril scripts

Since its early days, Siril can take user inputs as textual commands, from the command line. Recently, more commands have been added, enabling for a basic automated processing of images. Commands can be stored in a file that we call script, and they are executed one after the other. Some commands can be used in scripts, some cannot, this is indicated in the help of the command line from the graphical user interface of Siril.

Since release 0.9.9, Siril can execute scripts from a file. Since 0.9.10, commands can also be taken from a named pipe and more recently from the standard input too.

Using scripts

There are three ways to start a script:

  • from the graphical user interface, using the @ keyword on the command line, followed by the script name in the current working directory, as explained here,
  • from the graphical user interface, using the Scripts menu,
  • from the command line interface (siril-cli executable), using argument -s followed by the script's path (see the man page for more info).

The scripts menu only appears if some scripts have been found in the script search directories defined either by default or by the user in the preference menu.

If you don't see the Scripts menu (or if you don't see the default scripts in the list):

Please use the following procedure:

  • click on the 'Burger' icon then on 'Preferences'

  • click on the 'Scripts' section
  • delete the 2 lines in the field as described below
  • click on 'Apply'
  • close and restart Siril

Getting scripts

  • Since release 0.9.10, scripts are provided with the installation.
  • Since release 0.99.4, a new command 'convert' allows the execution of universal scripts that are available for DSLR (RAW files) and astronomy cameras (FITS files).


Default scripts (automatically installed with Siril):

  • Mono_Preprocessing.ssf: script for monochrome DSLR or Astro camera preprocessing, uses biases, flats and darks, registers and stacks the images. To use it: put your files (RAW or FITs) in the folders named 'lights', 'darks', 'flats' and 'biases' (in the SiriL default working folder), then run the script. When the script ends, you get a monochrome file named result.fit.
  • OSC_Preprocessing.ssf: same script as above but for One-Shot Color (OSC) DSLR or Astro camera. To use it: put your files (RAW or FITs) in the folders named 'lights', 'darks', 'flats' and 'biases' (in the SiriL default working folder), then run the script. When the script ends, you get a RGB file named result.fit.
  • OSC_Preprocessing_WithDrizzle.ssf: same script as above with resize of images by 2x2. Beware, this script takes much more time and disk space. To use it: put your files (RAW or FITs) in the folders named 'lights', 'darks', 'flats' and 'biases' (in the SiriL default working folder), then run the script. When the script ends, you get a RGB file named result.fit.
  • OSC_Extract_Ha.ssf: script for OSC DSLR or astro camera preprocessing, for use with Ha filter or dual-band filter. This script extracts the Ha layer of the color image. To use it: put your files (RAW or FITs) in the folders named 'lights', 'darks', 'flats' and 'biases' (in the SiriL default working folder), then run the script. When the script ends, you get a monochrome file named Ha_result.fit.
  • OSC_Extract_HaOIII.ssf: same script as above, but extracts Ha and OIII layers of the color image. To use it: put your files (RAW or FITs) in the folders named 'lights', 'darks', 'flats' and 'biases' (in the SiriL default working folder), then run the script. When the script ends, you get 2 monochrome files named Ha_result.fit and OIII_result.fit. You can also use the menu 'Image Processing' then 'RGB compositing' and put Ha_result in Red layer and OIII_result in Green and Blue layers to get an HOO image.


Other scripts:


We encourage users creating their own scripts to publish them and make a link in this page with a basic description of what they do.

We also suggest users to use Sirilic to generate scripts or to provide a more suited way to manage all the files for multi-session processing.