Home > User Interface > Analyses > Analysis Processing > Batch Execution Mode

Batch execution mode

Once you have defined one or several analyses and created the corresponding Analysis input files (.LOG) and Simulation results files (.DSS), you may run these analyses in batch (quiet mode) rather than in interactive mode.

Batch processing allows handling a large number of simulations efficiently.

Batch processing may be either handled through the Batch Processing tool available in the user interface or through external text-based command files.

Batch processing tool

Analysis input files (.LOG) and simulation results files (.DSS) may be loaded into the Batch processing tool.

The Batch Processing tool may be opened from the Tools menu by selecting the Batch processing item. Once opened, you may load the LOG and DSS files either by pressing the Load files button, or by selecting and dragging the files to the Batch processing form.

The Batch processing tool offers enhanced productivity through multi-threaded execution of batch jobs, and automatically reports the status of every batch jobs.

External command files

Text-based command files may be used to perform analysis tasks in batch mode. To this purpose, you must create one or several text-based command files (.CMD) with all the instructions required to run DeepLines FE engine and extract the post-processing requests defined within the Predefined results* associated with your analyses.

Command files must be given the .CMD extension, and can be either created by hand or with the GUI. To this purpose, you may use the Generate all button in the Launch DeepLines solver dialog box - this is the dialog that is displayed when you are about to launch an analysis with the GUI. Clicking this button will create an ASCII batch command file with the instructions required to launch all the analyses included in the selected set of analyses. (These are selected from the Launching dialogue box as described in Interactive Mode.)

Warning

When using an Hydrodynamic database file (.HDB), you must check that the file is correctly placed on your hard-drive or local network so that DeepLines FE engine is able to open the file prior to launching the analysis. By default, the .HDB files must be stored in a folder named "HDB" placed in the same directory as the Analysis input file (.LOG). If necessary, you may change this address by hand under the *FPFDX keyword.

An example of the contents of a command file is shown below :

Example

    C:\PRINCIPIA\DeepLines\DeepLinesV5R3\Exec\DeepLinesV5R3.exe Analysis_1.log
    C:\PRINCIPIA\DeepLines\DeepLinesV5R3\Exec\DeepLinesGUI.exe -console Analysis_1.dss
    C:\PRINCIPIA\DeepLines\DeepLinesV5R3\Exec\DeepLinesV5R3.exe Analysis_2.log
    C:\PRINCIPIA\DeepLines\DeepLinesV5R3\Exec\DeepLinesGUI.exe -console Analysis_2.dss
    C:\PRINCIPIA\DeepLines\DeepLinesV5R3\Exec\DeepLinesV5R3.exe Analysis_3.log
    C:\PRINCIPIA\DeepLines\DeepLinesV5R3\Exec\DeepLinesGUI.exe -console Analysis_3.dss

Double clicking the file above from MS Windows Explorer would launch the 3 analyses named Analysis_1, Analysis_2 and Analysis_3, and also run the GUI to extract associated Predefined results.

Note

It may be interesting to group all the instructions for the solver and then those for the GUI. in that case, the example file above would write:

Example file

    C:\PRINCIPIA\DeepLines\DeepLinesV5R3\Exec\DeepLinesV5R3.exe Analysis_1.log 
    C:\PRINCIPIA\DeepLines\DeepLinesV5R3\Exec\DeepLinesV5R3.exe Analysis_2.log 
    C:\PRINCIPIA\DeepLines\DeepLinesV5R3\Exec\DeepLinesV5R3.exe Analysis_3.log 
    C:\PRINCIPIA\DeepLines\DeepLinesV5R3\Exec\DeepLinesGUI.exe -console Analysis_1.dss 
    C:\PRINCIPIA\DeepLines\DeepLinesV5R3\Exec\DeepLinesGUI.exe -console Analysis_2.dss 
    C:\PRINCIPIA\DeepLines\DeepLinesV5R3\Exec\DeepLinesGUI.exe -console Analysis_3.dss