next up previous contents index
Next: Specifying the .INIT File Up: Running Tasks: the VECTOR Previous: Query Mode

EDIT Mode

Commands RUN and SUBMIT execute two SIC command procedures, the Initialization File Task.INIT, which defines all parameters needed for EXAMPLE, and the Checker File Task.CHECK, which verifies that all parameters are valid. In the example above, the EXAMPLE.INIT file is

TASK\REAL "A value between 0 and 1" A$ 
TASK\CHARACTER "Any character string" CHAIN$ 
TASK\REAL "4 Real values" ARRAY$[4]
TASK\FILE "Output file name" FILE$ 
TASK\GO

This is a standard procedure containing commands of a SIC language named TASK $\backslash$. Commands from this language are used to define the   parameters required by the task, and cannot be called interactively. The command syntax is always the same :

TASK\Command "Prompt String" Parameter$[Dimensions] [Value [...]]
where

Once all parameters have been assigned values, RUN  and SUBMIT  commands execute the GILDAS_RUN:EXAMPLE.CHECK file, writing the current parameter values in an auxiliary file which will be used by the task EXAMPLE. If a parameter is incorrect, an error is returned, and the task EXAMPLE not executed.

Instead of supplying the parameters in a query mode, the user can use a text editor to edit the .INIT file using command    

     VECTOR> RUN EXAMPLE/EDIT
or 
     VECTOR> SUBMIT EXAMPLE/EDIT
The parameter values can then be typed after the parameter names in the EXAMPLE.INIT file, using SIC continuation marks (``-'' as the last character of a line) if needed for long command lines. EXAMPLE.INIT will be executed after exiting the editor. If a parameter value is missing, the user will nevertheless be prompted for it after exiting the editor.

The text editor called is user defined by the command SIC $\backslash$SIC EDITOR or the logical name GAG_EDIT.


next up previous contents index
Next: Specifying the .INIT File Up: Running Tasks: the VECTOR Previous: Query Mode
Gildas manager
1999-03-15