10.2 Identifying Valid Runtime Parameters

The values of runtime parameters are initialized either from default values defined in the Config files, or from values explicitly set in the file flash.par. Variables that have been changed from default are noted in the simulation's output log. For example, the RuntimeParameters section of the output log shown in Figure 10.2 indicates that pt_numx and pt_numy have been read in from flash.par and are different than the default values, whereas the runtime parameter checkpointFileIntervalStep has been left at the default value of 0.

Figure 10.2: Section of output log showing runtime parameters values

 

=======================================================
RuntimeParameters:
=======================================================
pt_numx                     =         10 [CHANGED]
pt_numy                     =          5 [CHANGED]
checkpointfileintervalstep  =          0

After a simulation has been configured with a setup call, all possible valid runtime parameters are listed in the file setup_params located in the object directory (or whatever directory was chosen with -objdir=) with their default values. This file groups the runtime parameters according to the units with which they are associated and in alphabetical order. A short description of the runtime parameter, and the valid range or values if known, are also given. See Figure 10.3 for an example listing.

Figure 10.3: Portion of a setup_params file from an object directory.

 

physics/Eos/EosMain/Multigamma
    gamma [REAL] [1.6667]
        Valid Values: Unconstrained
        Ratio of specific heats for gas


physics/Hydro/HydroMain
    cfl [REAL] [0.8]
        Valid Values: Unconstrained
        Courant factor