Batch execution
See also: Batch execution of CAPRI tasks
Purpose
The aim of the "batch execution" workstep is to start a
pre-defined suite of CAPRI tasks without the need to defining all
settings via the Graphical User Interface and start the task manually
one after another. Instead, a text file uses a specific batch language
to define the settings and start the tasks. Batch execution is useful
to test if all CAPRI tasks based on GAMS in a CAPRI installation are
currently compiling and running without errors. Equally, it can be used
to start a pre-defined set of work steps.
The batch execution facility eases that task by:
- Reporting the tasks started in a HTML file, where all settings are reported, possible errors documented and the GAMS listing files can be accessed.
- Assignes automatically unique ids to each GAMS runs, and generates matching listing files.
- Allows starting the suite at a pre-defined time.
- Allows sending the output files from the GAMS runs into a separate result directory to avoid overwriting existing results. So that the
results from the different task can be compared to the previous ones.
Usage
The batch execution facility has only a few controls:
- Batch file to execute: the file with the batch commands. Use the "Set file" button to change.
- Directory for exp/ref files: these files can be used as input to the "Generate Gams documentation" workstep.
- The check box "Generate EXP and REF files for HTML documentation" will generate the necessary files as input for the Javadoc like technical documentation for CAPRI
- The check box "Only compile the GAMS programs" will ensure that no program will be executed even if the file with the batch commands asked for execution
The three buttons at the bottoms allow starting and interrupting the process:
- Start batch execution: start the process.
- End batch execution after next finalised GAMS step: Let GAMS end on its own and then return
- End batch execution immediately: send a signal to GAMS to stop which will trigger an error code, but let GAMS run a finalisation routine to remove intermediate files
Notes
(1) If the batch command file comprises a "Timer=xx:yy" command, execution may be pending until the predefined time is reached.
(2) The predefined test suite let all work steps run for all Member States which may easily take a full day.