WSP - SIMPARAM

Unrecognized keyword chain: S1.S2 or S1.S2(#1).S3

An unrecognized keyword chain might have been used in the cfg file. Receiving this warning may not necessarily point to a problem. The keyword chain is formatted as key1.key2 for two level and key1.key2(#).key3 for three level keyword chains. key1 is the highest level keyword, e.g. "phases". key2 is the second level keyword, e.g. "phase". key3 is the third level keyword, e.g. "type". In three level keyword chains, the second level key is accompanied by a number in parentheses pointing to the order in second level keyword list. Example: kernel.dxp is printed as a warning since "dxp" is not a recognized second level keyword. Example: phases.phase(2).rho_compr is printed as a warning for a non-FLUID phase 2.

The number of timesteps required to complete the simulation is larger than the maximum number of iterations allowed.

The number of timesteps calculated by the solver to reach the end of the simulation "t_end", starting from "t_start", is larger than the maximum number of iterations allowed. For a restart/continue (recon) run, the time of the recon file is taken as the starting time. The simulation will stop once the maximum number of iterations allowed is reached. The maximum number of allowed iterations is equal to "maxitsteps" if specified, or 1000000000 by default.

The requested time step size is larger than the calculated time step size. The simulation "may" behave unexpectedly.

The solver issues this warning when the time step size requested "dt_simulation" is larger than the time step size calculated by the solver. If this is intentional, the warning may be ignored. In some cases, the simulation may fail with a separate error.

The requested time step size is larger than the calculated time step size. The simulation "may" behave unexpectedly.

The solver issues this warning when the time step size requested "dt_simulation" is larger than the time step size calculated by the solver. If this is intentional, the warning may be ignored. In some cases, the simulation may fail with a separate error.

The starting value of APD attenuation interval "APD_attenuation_interval" is larger than its end value. The attenuation will act as a sharp cut at the starting value.

Using a starting value larger than the end value for APD attenuation interval leads to a sharp cut instead of gradual attenuation. This means there will be no APD effects when kernel volume integral exceeds the specified starting value.

APD attenuation interval "APD_attenuation_interval" has a start value and/or end value that is smaller than zero. APD effects may be negligible.

Using a negative start value and/or end value for APD attenuation interval leads to extreme attenuation or complete suppression of APD effects. The simulation may behave unexpectedly.

APD attenuation interval "APD_attenuation_interval" has a large start value and/or large end value. APD effects may not be attenuated.

Using a large start value and/or end value for APD attenuation interval may lead to negligible change in APD effects. This may have adverse effects on particles close to walls and moving walls when large APD coefficients are used.

Adhesion model is used together with "TARTAKOVSKY2016_F1" surface tension model.

It is recommended to deactivate "adhesionmodel" when using "TARTAKOVSKY2016_F1" surface tension model as both models are supposed to be used mutually exclusive.

It is not possible to enable TEMP field output without enabling "energy_transport".

The solver issues this warning when "output_temp" is set to true but "energy_transport" is set to false. The TEMP output is automatically turned off and the simulation will continue normally.

It is not possible to enable VISCTEMP field output without enabling the appropriate "aeroViscMode" or activating "viscTempCoupling".

The solver issues this warning when "output_visctemp" is set to true with neither "aeroViscMode" nor "viscTempCoupling" activated. The VISCTEMP output is automatically turned off and the simulation will continue normally.

It is not possible to enable KERNELSUM field output without enabling the appropriate "aeroViscMode".

The solver issues this warning when "output_kernelsum" is set to true but "aeroViscMode" is set to "NOMODE". The KERNELSUM output is automatically turned off and the simulation will continue normally.

It is not possible to enable VCORR field output without activating "transportvelocity". Deactivating VCORR field output.

The solver issues this warning when "output_vcorr" is set to true but "transportvelocity" is set to false. The VCORR output is automatically turned off and the simulation will continue normally.

More ranks requested than GPUs available on host S1

This warning means that there are less GPUs available than number of ranks requested during launch. Note that this only accounts for devices visible to the solver. It is strongly recommended to launch with a number of ranks at most equal to the number of GPUs available. While the simulation may proceed, this may lead to decreased performance.