1 Language
                            VECTOR\ Language Summary

    EXPLAIN [Task] : Gives explanation about a GILDAS task
    FITS           : Convert between FITS files and Gildas images
    HEADER         : List the header of a Gildas image
    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
1 EXPLAIN
        [VECTOR\]EXPLAIN [Task [Parameter]]

    Gives  explanation  about  a GILDAS task. If Parameter is specified, EX-
    PLAIN will give help about the parameter. Parameter = * can be  used  to
    list  help  about all parameters of the specified task. Note that if Pa-
    rameter 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 FITS
        [VECTOR\]FITS FitsFile WhichWay GildasFile [/STYLE Style] [/XTENSION
    Number] [/BITS Nbit]

    Convert between FITS files and Gildas images. The FITS command is just a
    wrapper around the FITS_GILDAS and GILDAS_FITS tasks. See those for  de-
    tails.

            [VECTOR\]FITS  OutputFile.fits FROM InputFile.gdf [/STYLE Style]
    [/BITS Nbit]

    Create a FITS file from a Gildas image. The layout of the FITS file  de-
    pends on the specified "Style", although default styles will be used de-
    pending on the Gildas image (e.g. UVFITS is used for UV Tables, STANDARD
    is used for images). The number of bits is controlled by "Nbit", and de-
    faults to -32 for images, and 16 for UV data.

            [VECTOR\]FITS InputFile.fits TO  GildasFile.gdf  [/STYLE  Style]
    [/XTENSION Number]

    Convert  the  InputFile.fits  FITS  file  into a Gildas image in Gildas-
    File.gdf, using the appropriate "Style". A specific  XTENSION  (not  yet
    implemented!) could be used instead of the main FITS header when needed.
1 HEADER
        [VECTOR\]HEADER GildasImage [/EXTREMA]

    List the header of the GildasImage file.

    The /EXTREMA option computes (or recomputes)  and  updates  the  extrema
    section in the header of the GildasImage file.
1 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.

    The parameter file can be prepared in "Window-mode", or using a text ed-
    itor.
        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 but-
    ton.  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 param-
    eter 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 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
    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 syn-
    chronisation is offered for remote execution.
1 SPY
        [VECTOR\]SPY [Task_Name]

    Displays the status of all active GILDAS tasks, or lists 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 exe-
    cuted 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 n-D SIC variable or GILDAS data cube to pro-
    duce  an  output  transposed  SIC  variable or n-D cube according to the
    transposition order specified by Order (21, 312, 213, etc...). For exam-
    ple:
        VECTOR\TRANSPOSE TEST.VLM TEST.LMV 231
    will  transpose  Gildas  data  file.  For files, the transposition takes
    place in RAM memory if the sic logical SPACE_GILDAS (in megabytes  unit)
    is big enough, else it takes place on disk.

        DEFINE REAL A[10,2] B[2,10] VECTOR\TRANSPOSE A B 21
    will  transpose  the A SIC variable to the B SIC variable. SIC variables
    must be of the same type.

    MISSING FEATURE: If A and B are IMAGE variables, the header is not  ade-
    quately transposed.
1 ENDOFHELP



























































