RUN
Keywords: sic

Next: SPY Up: VECTOR Language Internal Help Previous: HEADER /TELESCOPE Contents Index

##
RUN

            [VECTOR\]RUN TaskName [Parameter_File] [/EDIT] [/NOWINDOW] [/WINDOW]

        Execute a GILDAS task as a detached process.

        See also:
          HELP TASK for a summary of all available tasks.
          HELP TASK GroupName for a summary of tasks in a group.
          HELP RUN TaskName for details on a specific task.

        Input file (*.init):
          The input parameters are read from the file Parameter_File.  It  is  a
          SIC  procedure with commands from the TASK\ language. The default name
          of the parameter file is TaskName.init in the current working directo-
          ry.  If  it  does  not  exists  yet,  a  template  duplicated 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.

          There are 3 ways to set up the input 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
                editor (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.

          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 file.

        Parameter file (*.par):
          A temporary parameter file derived from the init file  is  created  by
          the RUN command in the GAG_SCRATCH: directory. It may be deleted after
          Task execution. See also HELP SPY.
          At this stage a second SIC procedure is executed before  task  submis-
          sion  to  check  the validity of input parameters. If any parameter is
          invalid, an error is returned and the Task not submitted.

        Log file:
          The  output  messages  of  the   task   are   logged   in   the   file
          GAG_LOG:TaskName.gildas.  The Sic variable SIC%TEE controls wheter the
          messages should be printed in real time (YES) or after the task execu-
          tion  (NO).  Default  is  NO. Beware the 'tee' program does not always
          propagate task execution errors (this behavior  is  system-dependent),
          which  means  the  command flow may continue even if a task fails, re-
          sulting in later troubles.

        Task location:
          If no directory is specified in the task name, the task is assumed  to
          be in the GILDAS_LOCAL: (if defined). Else it is searched in TASK#DIR:
          default locations.

        Asynchronous execution:
          The task execution may be synchronous (the main  program  waiting  for
          task  completion) or asynchronous (control returns to the main program
          immediately). Note that an error status issued by the  task  does  not
          stop  the  main  program in the case of asynchronous execution. If the
          task terminates before you exit from the activating program, a  termi-
          nation  message  will be typed on the terminal, giving the termination
          status.

        Remote execution:
          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 per-
          formed. No synchronisation is offered for remote execution.