ESP - SIMPARAM

Invalid input for keyword chain S1.S2: S3. Valid options are: S4

An unrecognized value S3 for the parameter represented by the keyword chain has been provided in the cfg file. The keyword chain is formatted as key1.key2, where key1 is the highest level keyword and and key2 the parameter name. The list S4 shows the accepted inputs for that option.

Missing input for keyword chain S1.S2. Valid options are: S3

The parameter represented by the keyword chain requires explicit input by the user, but none has been provided in the cfg file. The keyword chain is formatted as key1.key2, where key1 is the highest level keyword and and key2 the parameter name. The list S3 shows the accepted inputs for that option.

Invalid input for keyword chain S1.S2(#1).S3: S4. Valid options are: S5

An unrecognized value S4 for the parameter represented by the keyword chain has been provided in the cfg file. The keyword chain is formatted as key1.key2(#).key3, where key1 is the highest level keyword, key2 is the second level keyword and key3 is the parameter name. The second level key is accompanied by a number in parentheses pointing to the order in second level keyword list. The list S5 shows the accepted inputs for that option.

Missing input for keyword chain S1.S2(#1).S3. Valid options are: S4

The parameter represented by the keyword chain requires explicit input by the user, but none has been provided in the cfg file. The keyword chain is formatted as key1.key2(#).key3, where key1 is the highest level keyword, key2 is the second level keyword and key3 is the parameter name. The second level key is accompanied by a number in parentheses pointing to the order in second level keyword list. The list S4 shows the accepted inputs for that option.

Missing input for keyword chain S1.S2. The boundary conditions for each of the cordinate directions can be chosen from: S3

The parameter represented by the keyword chain requires explicit input by the user, but none has been provided in the cfg file. The keyword chain is formatted as key1.key2, where key1 is the highest level keyword and and key2 the parameter name. The input for each of the coordinate directions can be chosen from the values shown in the list S3.

Missing input for keyword chain S1.S2(#1).S3. The boundary conditions for each of the cordinate directions can be chosen from: S4

The parameter represented by the keyword chain requires explicit input by the user, but none has been provided in the cfg file. The keyword chain is formatted as key1.key2(#1).key3, where key1 is the highest level keyword, key2 is the second level keyword and key3 is the parameter name. The second level key is accompanied by a number in parentheses pointing to the order in second level keyword list. The input for each of the coordinate directions can be chosen from the values shown in the list S4.

DESIGN operation mode is only available for single fluid phase. For cases with more than one fluid, please use NORMAL or CONSERVATIVE operation modes.

When setting "operationMode" to "DESIGN", only one phase in the "phases" section may be of FLUID type.

More than two FLUID phases detected. The ADAMI surface tension model is not supported for more than two FLUID phases.

The surface tension model "ADAMI" only supports two FLUID phases.

More than two FLUID phases detected. The TARTAKOVSKY2016_F1 surface tension model is not supported for more than two FLUID phases.

The surface tension model "TARTAKOVSKY2016_F1" only supports two FLUID phases.

The simulation cannot start without a valid "simulationParameters" section.

The cfg file must contain a "simulationParameters" section. Please define one and assign appropriate values. Please ensure that there are no typographical mistakes and the cfg file has Linux line endings.

Log output frequency "freq_log" has to be a positive integer value.

The log output frequency "freq_log" is the number of timesteps between log outputs and has to be a positive integer value.

APD attenuation interval "APD_attenuation_interval" has equal start and end points.

APD attenuation interval start and end points must be different. Please use different values. For a sharp cut at the starting value, set the end value to a number smaller than the starting one.

It is not possible to activate "viscTempCoupling" without enabling "energy_transport".

Energy transport must be activated when using temperature viscosity coupling. This means if "viscTempCoupling" is set to true, "energy_transport" must be set to true as well.

"aeroViscMode" and "viscTempCoupling" may not be enabled simultaneously. Please choose only one.

The solver supports either aeration viscosity or temperature dependent viscosity. If "viscTempCoupling" is set to true, "aeroViscMode" may only be set to "NOMODE". If "aeroViscMode" is set to "LOCAL" or "GLOBAL", the value of the keyword "viscTempCoupling" must be false.

The value of "restart_from_step" keyword is less than -1. The starting step of a restart/continue (recon) run must be a non-negative integer.

A restart/continue (recon) run may only start with a non-negative step number. Please set "restart_from_step" keyword's value to a non-negative integer. You may also comment out the keyword-value pair or set "restart_from_step" to -1 to use the latest available recon file.

Output file write interval has to be defined either through "dt_output" or through "t_output_file" for "output_type" other than NOOUTPUT.

If particle output is requested ("output_type" set to anything other than "NOOUPUT"), output times must be defined either through a positive value for output interval "dt_output" or through a file "t_output_file" containing a list of output times.

Time step size factor "dt_factor" must be a positive number.

Time step size factor "dt_factor" must be a positive number. Set "dt_factor" to 1 or remove it from cfg to deactivate.

The specified restart/continue (recon) time is greater than the end time of the simulation.

The current simulation end time "t_end" is smaller than the time stored in the recon file. Please make sure that "t_end" is greater than the simulation time when the requested recon file was saved.

Too many GPU-devices requested. Currently limited to #1 GPUs

The solver supports up to 4096 GPU devices.