This seems to be unused. At least the current benchmarks
do not need this special cases.

CPPCheck warning type: variableScope.

jbathmann authored 5 years ago and Dmitri Naumov committed 5 years ago

Introduced information flow whether the timestep was accepted or not.

This prevents the times in the timestepper and the external loop to diverge
which causes two issues otherwise:
1.) Endless loop at t --> t_end, if max_iter > largest multiplier
2.) Endless loop at t --> t_end, if nonlinear solver fails during
	execution

First removal force the convergence checks to be executed.
Last two changes handle the t being (almost) equal to the
end time.

It contains a boolean for met error norms and a
number of iterations of the solver made.

The number of iterations is needed for
a timestepping scheme.

If 'old' prj-file is used abort with OGS_FATAL.

Otherwise in the staggered scheme a wrong DOF table is used.

New versions of logog do not have an implicit ; after the macros.

Needed for the description of the balance data.

KeitaYoshioka authored 7 years ago and Dmitri Naumov committed 7 years ago

Staggered coupling convergence check is only enforced at the last process id.

Also update the variables' names and some of the docu.