GitLab

From a discussion in runOPAL#7 (closed) with @rizzoglio_v suggested by @adelmann. The optimiser mechanism of running with a master core that spawns several opal jobs can be adapted to run a scan through a parameter list. Compared to the scan option of runOPAL, an advantage is a single job in a batch system, and possibly better grouping of results. E.g.

dv0: DVAR, VARIABLE="P0", LOWERBOUND=-10.0, UPPERBOUND=0.0, STEP = 0.5;
dv1: DVAR, VARIABLE="P1", LOWERBOUND=-10.0, UPPERBOUND=0.0, STEP = 1.0;

SCAN,     INPUT="tmpl/model.tmpl", 
          OUTPUT="model",
          OUTDIR="results",
          DVARS = {dv0, dv1},
          NUM_MASTERS=1, 
          NUM_COWORKERS=8, 
          SIMTMPDIR="tmp", 
          TEMPLATEDIR="tmpl", 
          FIELDMAPDIR="fieldmaps";

cc: @frey_m