Skip to content
Snippets Groups Projects
Select Git revision
  • feature/umfpack-multitype
  • proximal-gradient-solver
  • feature/pn-solver
  • fix-master
  • feature/codespell
  • codespell
  • feature/cholmod-reuse-factorization
  • releases/2.8
  • test
  • fix/loopsolver-criterions
  • feature/multitype-cholmod
  • feature/two-norm
  • feature/replace-unused
  • feature/generic-transfer-operators
  • feature/cholmod-solver
  • releases/2.7-1
  • feature/P0-element-tranferoperators
  • master default
  • flexible-loopsolver-max
  • releases/2.5-1
  • subversion->git
21 results
Compare
Forked from agnumpde / dune-solvers
Source project has a limited visibility.
Patrick Jaap's avatar
Fix: LoopSolver has to execute the criteria regardless of the verbosity mode
Patrick Jaap authored 
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.
c5854e93
History
Patrick Jaap's avatar c5854e93
History
Name Last commit Last update