1 EXPLAIN
        [VECTOR\]EXPLAIN [Task [Parameter]]

    Gives explanation about  a  GILDAS  task.  If  Parameter  is  specified,
    EXPLAIN will give help about the parameter. Parameter = * can be used to
    list help about all parameters of  the  specified  task.  Note  that  if
    Parameter is absent, EXPLAIN accesses the topic "Summary".

    The GILDAS tasks can only be activated from the VECTOR\  language,  with
    commands  RUN  or  SUBMIT.  The VECTOR\ language is included in programs
    VECTOR, GRAPHIC and other reduction programs such as MAPPING.

    From within RUN and SUBMIT commands, you can get help upon  the  current
    Task  by  typing  GOLD ? in the editor, or by answering ? to a prompt in
    non editing mode.

1 Language
    EXPLAIN [Task] : Gives explanation about a GILDAS task
    RUN Task       : Activate a GILDAS task
    SPY [Task]     : Look at current status of detached Tasks
    SUBMIT Task    : Submit a GILDAS Task in batch queue GILDAS_BATCH
    TRANSPOSE      : Transpose data cubes
    WAIT [Task]    : Wait for Task completion

1 RUN
        [VECTOR\]RUN   Task_Name   [Parameter_File]   [/EDIT]    [/NOWINDOW]
    [/WINDOW]

    Execute a GILDAS  task  as  a  detached  process.  If  no  directory  is
    specified  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 Parameter_File, which is a SIC procedure with commands from the
    TASK\ language. A * can be used instead to specify a parameter  file  of
    name Task_name.INIT in the current directory.

    The parameter file can be prepared in "Window-mode",  or  using  a  text
    editor.
            In Window-mode, activated implicitely in the RUN_WINDOW variable
    is  YES  (default  on  X-Window  systems), or explicitely if the /WINDOW
    option 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.

    The text-editor mode is activated using the /EDIT option.  The parameter
    file  of default name Task_name.INIT is edited before submission, taking
    a template in GILDAS_RUN: area if no version of this file already exist.
    If  this template file does not exists, it may be that the Task you want
    to run doesnot exists 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 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
    output of the Task is in the file GAG_LOG:Task_Name.GILDAS, which may be
    listed  or printed later on. Task execution may be synchronous (the main
    program waiting for task completion) or asynchronous (control returns to
    the  main  program  immediately). If the Task terminates before you exit
    from the activating program, a termination message will be typed on  the
    terminal, giving the termination status.

    Use the EXPLAIN command for help on available Tasks.

    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
    synchronisation is offered for remote execution.

1 SPY
        [VECTOR\]SPY [Task_Name]

    Displays the status of all active GILDAS tasks, or list the last  output
    from the specified task.
1 SUBMIT
        [VECTOR\]SUBMIT  Task_Name  [Parameter_File]   [/EDIT]   [/NOWINDOW]
    [/WINDOW]

    The SUBMIT command is similar to the RUN command, except that  the  Task
    is  submitted  to  a  batch  queue (named GILDAS_BATCH) instead of being
    executed as a detached process. See RUN command for details.



    Use the EXPLAIN command for a documentation on available Tasks.
1 TRANSPOSE
        [VECTOR\]TRANSPOSE Input Output Order

    This command  takes  an  input  3-D  data  cube  to  produce  an  output
    transposed  3-D  cube  according to the transposition order specified by
    Order (312, 213, etc...). For example:
        VECTOR\TRANSPOSE TEST.VLM TEST.LMV 231
1 WAIT
        [VECTOR\]WAIT [Task_name]

    Place the current program in a  wait  state  until  the  specified  Task
    (started  by  command RUN) terminates. By default, the last started Task
    is used.  WAIT  *  waits  until  all  tasks  complete.  Waiting  can  be
    interrupted by pressing ^C.

    It may be used to synchronize complex procedures  where  the  result  of
    some  task  is  used  as  input  by  others. For batch jobs sent through
    command SUBMIT, this synchronization is  normally  ensured  by  the  job
    limit of the GILDAS_BATCH batch queue.

1 END