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

dune-solvers

  • Clone with SSH
  • Clone with HTTPS
    • Forked from agnumpde / dune-solvers
    Source project has a limited visibility.
    user avatar
    Do not check for zero entries when restricting occupation patterns.
    Oliver Sander authored and sander committed 
    Because some people restrict patterns for uninitialized matrices.
In that case you get
a) valgrind warnings
b) crashes, if an entry happens to be zero, it is not restricted.

[[Imported from SVN: r6332]]
    2e28a5e3
    History
    user avatar 2e28a5e3
    History
    Name Last commit Last update