The information has been provided by the MatrixDimensions struct since roughly the end of 2010.
Correspondingly, the methods rowdim and coldim have been removed from the istl matrix implementations.
Apparently, we forgot to remove them from the Matrix class.

MultiTypeBlockVector: Fix NaN behaviour of infinity_norm()

As a follow-up to flyspray/FS#1147, in response to dd7e8ed3, this makes `MultiTypeBlockVector::infinity_norm()` `NaN`-aware: In analogy to previous patches for other matrix/vector classes, this patch turns `infinity_norm` into two functions; a straight-forward version for `field_type`s that do not have `NaN` values and a less efficient version for ones that do.

It should be noted, however, that because `field_type` is currently hard-coded to be `double` in `MultiTypeBlockVector`, the `NaN`-aware version will, as long as this is so, always be used.

See merge request !15

[bugfix] fix broken assertion.

This patch fixes the errornous commits
e8d16384
1a2f4d0f

The introduced range checks were plain wring, as they neglected the nested structure of the
BlockVector. We now use `b.dim()` to get the flat size.

This fixes flyspray/FS#1724.

See merge request !12

This patch fixes the errornous commits
e8d16384
1a2f4d0f

The introduced range checks were plain wring, as they neglected the nested structure of the
BlockVector. We now use `b.dim()` to get the flat size.

This fixes flyspray/FS#1724.

Test complex<T> for floating point T only

The issue that I originally filed for dune-common as flyspray/FS#1726 affects dune-istl, too.

See merge request !11

The standard leaves (the effect of instantiating) complex<T> for more
general T unspecified.

flyspray/FS#1147: Fix NaN behaviour of infinity_norm() for istl classes

This is an extension of the work related to flyspray/FS#1147 to dune-istl.

See merge request !10

This includes the behaviour of its rows, thus the
CompressedBlockVectorWindow class

[bugfix] Produce a linker error when pardiso lib is not found

If somebody tries to use pardiso despite it not being found,
he should ge t a linker error instead of an exception.
All other bindings handle it that way.

Fixes flyspray/FS#351

See merge request !4

[cleanup] Use template aliases where they beautify code.

I already wanted to use those when implementing the UMFPack
integration into the overlapping schwarz, but our compiler
requirements were not sufficient at the time.

See merge request !9

I already wanted to use those when implementing the UMFPack
integration into the overlapping schwarz, but our compiler
requirements were not sufficient at the time.

Feature/fix deprecation warnings amgtest

please see flyspray/FS#1526

@markus.blatt can you have a look (somehow I can't assign this request to you)

See merge request !7

Apparently, this has been rotting away for quite some time. Adapt the
calls to the Pardiso library. Use the C instead of the Fortran interface.
Use correct method for determining the block size of the matrix.

Fixup for !2

Bug introduced in the fix of flyspray/FS#1331 and !2
revealed by simply building dune-istl.

See merge request !6

Bug introduced in the fix of flyspray/FS#1331 and !2
revealed my `make build_tests`.

[real_type] use real_type for all norm computations, fix flyspray/FS#1331

I think these are the last places where double has to be replaced. The only remaining places are superlu and umfpack which are not templated and thus are hardcoded to use double.

This patch fixes flyspray/FS#1331

See merge request !2

Some exceptions were caught and did not fail the test.

needed for webpage.

If somebody tries to use pardiso despite it not being found,
he should ge t a linker error instead of an exception.
All other bindings handle it that way.

Fixed flyspray/FS#351

Feature/fs1659 matlab output of dynamic matrix

fixed flyspray/FS#1659

See merge request !3

This enables users to have several build directories like
build-clang, build-gcc5, build-debug, and still get all
of them ignored.

There are some tests, which are hard to port in the paamg directory.
They want to explicitly test _without_ direct solver. Previously,
you simply did not add the flags for the direct solver packages.
add_dune_test relies on all flags, so we need a way to disable components
again. That will be implemented as part of dune_add_executable. For
now, we build the targets ourselves and hand them to dune_add_test.

This enables users to have several build directories like
build-clang, build-gcc5, build-debug, and still get all
of them ignored.