HydroGeoSphere/Adaptive Timesteps

If required, HydroGeoSphere can modify timestep values as the solution proceeds, based on the transient behaviour of the system (see Equation 3.102). The following instructions can be used to activate this feature, and set targets for specific variables (e.g. pressure head, saturation etc.). These targers are used to modify timestep size as the solution proceeds.

Head control

 * 1) dhead_allowed Maximum allowed absolute change in nodal head during any time step [L].
 * &bull; &bull; &bull;

Water depth control

 * 1) ddepth_allowed Maximum allowed absolute change in nodal surface water depth during any time step [L].
 * &bull; &bull; &bull;

Saturation control

 * 1) dsat_allowed Maximum allowed absolute change in nodal saturation during any time step [L].
 * &bull; &bull; &bull;

Newton iteration control

 * 1) nnri_allowed Maximum allowed number of Newton-Raphson iterations during any time step [L].
 * &bull; &bull; &bull;

Concentration control

 * 1) dconc_allowed Maximum allowed absolute change in nodal concentration during any time step [L].
 * &bull; &bull; &bull;

Mass change control

 * 1) dmass_change_allowed Maximum allowed absolute change in mass during any time step [L].
 * &bull; &bull; &bull;

Mass error control

 * 1) dmass_error_allowed Maximum allowed absolute mass error during any time step [L].
 * &bull; &bull; &bull;

The following controls are used to generate a timestep multiplier according to Equation 3.102. There are limits to how large or small the multiplier can be, and these are set by default to be in the range of 0.5 to 2 respectively. If you want to modify these limits you can do so using the following instructions:

Maximum timestep multiplier

 * 1) val Maximum timestep multiplier value.

Assigns a new value for the maximum timestep multiplier, which defaults to 2.
 * &bull; &bull; &bull;

Minimum timestep multiplier

 * 1) val Minimum timestep multiplier value.

Assigns a new value for the minimum timestep multiplier, which defaults to 0.5. Currently, HydroGeoSphere ignores this parameter and allows any non-zero minimum, no matter how small.
 * &bull; &bull; &bull;