Skip to content

Fix: LoopSolver has to execute the criteria regardless of the verbosity mode

Patrick Jaap requested to merge patrick.jaap_at_tu-dresden.de/dune-solvers:fix/loopsolver-criterions into master

In the current implementation this caused different solution behavior depending on the chosen verbosity mode. Plain stop critera were ignored in the SOLVER::QUIET case.

This patch fixed the problem.

Merge request reports