Next: SPY
Up: VECTOR Language Internal Help
Previous: HEADER
Contents
Index
RUN
[VECTOR\]RUN Task_Name [Parameter_File] [/EDIT] [/NOWINDOW] [/WIN-
DOW]
Execute a GILDAS task as a detached process. If no directory is speci-
fied in the task name, the Task is assumed to be in the GILDAS_LOCAL: or
GILDAS_RUN: area. The input parameters are read from the file Parame-
ter_File, which is a SIC procedure with commands from the TASK\ lan-
guage. A * can be used instead to specify a parameter file of name
Task_name.INIT in the current directory.
There are 3 ways to set up the parameter file:
- Window mode: if the variable RUN_WINDOW is YES (default on X-Window
systems), or if the option /WINDOW is specified, a panel appears to
enter all parameters. Help if available by clicking on the prompt
string for each parameter, or on the HELP button. Once all parameters
have been adequately specified, the task can be activated by clicking
OK, or aborted by clicking ABORT.
- Editor mode: if the option /EDIT is specified, your favorite text edi-
tor (see SIC EDIT) is invoked to edit the parameter file.
- No window mode: if the variable RUN_WINDOW is NO, or if the option
/NOWINDOW is specified, you won't be asked to edit the parameter file.
This is useful for non-interactive data processing. This assumes you
have created the parameter file previously, e.g. "by hand" or from a
previous call.
The default name of the parameter file is Task_Name.init in the cur-
rent working directory. If it does not exists yet, a template from the
GAG_TASK: location is used. If this template file does not exist, it may
be that the Task you want to run does not exist either, or is not yet
debugged at all.
Once the parameter file has been prepared in Edit-mode or Window-
mode, the RUN command will prompt you for all missing parameters in the
.INIT command file. Help on the parameter can then be obtained answering
? to the prompt.
The RUN command checks that the Task exists, and only GILDAS Tasks can
be submitted in this way. A second SIC procedure is executed before task
submission to check the validity of input parameters. If any parameter
is invalid, an error is returned and the Task not submitted.
The input file which is created by the RUN command is located in the
GAG_SCRATCH: directory and may be deleted after Task execution. The out-
put of the task is in the file GAG_LOG:Task_Name.gildas, which may be
listed or printed later on. You can set the Sic variable SIC%TEE to YES
for real time logs to the terminal (default NO).
The task execution may be synchronous (the main program waiting for task
completion) or asynchronous (control returns to the main program immedi-
ately). Note that an error status issued by the task does not stop the
main program in the case of asynchronous execution. If the task termi-
nates before you exit from the activating program, a termination message
will be typed on the terminal, giving the termination status.
Task may execute on a remote node rather than on the local machine. The
node name is controlled by logical name GILDAS_NODE. If GILDAS_NODE =
LOCAL, local execution is performed. If not, GILDAS_NODE must be the
node name of the computer on which execution will be performed. No syn-
chronisation is offered for remote execution.
Type HELP TASK for a summary of all available tasks.
Type HELP RUN Task_Name for details on a specific task.
Gildas manager
2015-03-01