Configuration

Aspherix® Calibration settings are stored in config files, which are described in this section.

dalilama.conf

The file dalilama.conf holds global settings necessary to run Aspherix® Calibration in cluster mode. This file is located in the following subfolder of the Aspherix® installation directory: share/aspherix_calibration/etc. The available settings are listed below (see also Cluster Mode documentation for more information).

Setting name	Description
`maxConcurrentEval`	Maximum number of concurrent iterations to be run
`clusterCmdLineTemplateDalilama`	Template used to assemble the commands to submit the Aspherix® Calibration jobs to the cluster queue
`clusterCmdLineTemplateSimulation`	Template used to submit the simulations to the cluster queue
`clusterCmdLineDefs`	File name defining the above-mentioned templates

case.conf

Each calibration case directory contains a file called case.conf in which settings necessary for the cases are stored. Additionally, the etc/ dir contains a file case.conf.global in which default settings for all cases can be given. Note that case.conf settings take precedence over case.conf.global settings.

Important case.conf(.global) settings are:

Setting Name	Valid Options	Description
runMode	`direct`, `shellScript`	sets whether a case is run through a shell script or directly by invoking the Aspherix binary. CFDEMcoupling cases only work in run mode `shellScript`.
commandLineDefs	a filename found in the `etc/` directory	sets definitions for the command line template used to execute cases in `shellScript` mode
commandLineTemplate	A template as described in command line templates	Template used to def
initDirectModes	`serial`, `mpi`, `serial serial ... serial`, `mpi mpi ... mpi`	sets whether the initialization simulation(s) is (are) performed in serial or in parallel (active only when `runMode` is `direct`
initDirectScripts	`name_init.asx`, `init1.asx init2.asx ... initN.asx`	name(s) of the input script responsible for the initialization simulation(s)
runDirectModes	`serial`, `mpi`, `serial serial ... serial`, `mpi mpi ... mpi`	sets whether the iteration simulation(s) is (are) performed in serial or in parallel (active only when `runMode` is `direct`
runDirectScripts	`name_run.asx`, `run1.asx run2.asx ... runN.asx`	name(s) of the input script responsible for the iteration simulation(s)

command line templates

Several functionalities of Aspherix® Calibration require the definition of command line templates. A simple example for such a template is

bash %c > %d/%l

where the sequences starting with the % sign are placeholders to be filled by Aspherix® Calibration. The three sequences in the above example are predefined with the following meanings:

sequence	meaning
%c	The command to start an actual simulation
%d	The run directory of a simulation
%l	The name of a logfile: `init.log` for initialization, `simCycle.log` for the calibration cycle

If further replacement sequences are needed, these can be defined in a file which has to reside in the etc/ subdirectory of Aspherix® Calibration. The file can contain definitions of the form settingName %sequence where valid sequences consist of the % character and exactly one letter, lower- or uppercase. So, %x and %R are valid, but neither %foo nor %a1 are. An example file could look like

exampleSetting %x
anotherExampleSetting %Y
yetAnotherSetting %u

During assembling of the actual command, Aspherix® Calibration then looks for settings with the names in the first columns in both global and case settings, and replaces the %[a-zA-Z] sequences with the values found for the respective settings. Note that the settings have to be defined if an escape sequence is defined.