Batch Processing

A special form of descriptor is used to specify a group of problems to be run in batch mode.

A single "section" introduced by the word BATCH identifies a descriptor as a batch control file.  Following this header, a sequence of names appears, each name enclosed in quote marks.  Commas may optionally be used to separate the names.  Any number of names may appear on each line of the descriptor.  Each name is the name of a problem descriptor to be run.  Names may include directory paths, which are assumed to originate in the directory containing the batch descriptor.  The ".pde" extension is not required, and will be assumed if omitted.  The list should be closed with an END statement. 

For example,

BATCH                

{ use the correct separators for your operating system }

  "misc\table", "steady_state\heat_flow\slider"

  "steady_state\stress\3d_bimetal"

END

The entire problem list is examined immediately, and any syntax errors in the names are reported. All files named in the list are located, and missing files are reported before any processing begins.

Each problem named in the list is run to completion in sequence.  As the problems run, status information is written to a log file in the directory containing the batch descriptor.  This file has the same name as the batch descriptor, with the extension '.log', and all problems in the list are summarized in this single file.  Graphical output from each problem is written as usual to a unique .PG4 file in the directory with the specific descriptor. After the run is completed, this graphic output may be reviewed by restarting FlexPDE and using the VIEW menu item.

Simple names may be listed without the quotes, but in this case embedded spaces, path separators, reserved words and numeric initials will all cause error diagnostics.