Print absolute residual when using LineSearch in Newton Solver
Feature request
Print the absolute residual for each step of the newton solver to the console if useLineSearch=true
.
What does this feature / why does DuMux need it: The residual reduction and relative shift can make it look like we are/could be stuck on a saddle point. The information about the absolute residual can, in most cases, avoid this ambiguity.
Newton iteration 1 done, maximum relative shift = 6.4650e-08, residual = 4.2105e-13, residual reduction 1.0000e+00->1.5204e+00@lambda=0.1250
Newton iteration 2 done, maximum relative shift = 5.6569e-08, residual = 3.8752e-13, residual reduction 1.5204e+00->1.3993e+00@lambda=0.1250
Newton iteration 3 done, maximum relative shift = 4.9497e-08, residual = 3.8370e-13, residual reduction 1.3993e+00->1.3855e+00@lambda=0.2500
Newton iteration 4 done, maximum relative shift = 3.7123e-08, residual = 4.1695e-13, residual reduction 1.3855e+00->1.5056e+00@lambda=0.1250
Newton iteration 5 done, maximum relative shift = 3.2482e-08, residual = 3.6522e-13, residual reduction 1.5056e+00->1.3188e+00@lambda=0.5000
Newton iteration 6 done, maximum relative shift = 1.6241e-08, residual = 4.7623e-13, residual reduction 1.3188e+00->1.7196e+00@lambda=0.1250
Newton iteration 7 done, maximum relative shift = 1.4210e-08, residual = 4.2784e-13, residual reduction 1.7196e+00->1.5449e+00@lambda=1.0000
Newton iteration 8 done, maximum relative shift = 4.3042e-13, residual = 4.0635e-13, residual reduction 1.5449e+00->1.4673e+00@lambda=0.5000
Newton iteration 9 done, maximum relative shift = 2.1520e-13, residual = 3.9071e-13, residual reduction 1.4673e+00->1.4108e+00@lambda=0.5000
Which issue does this feature fix (if any)
Anything else we need to know?: I would propose to print this information if there is no reason against it, with the hope to have an even better user experience.