[bugfix] add missing header

Header `dune/common/exceptions.hh` is not included but exceptions are used.

See merge request !29

Matrix loadbalance to more

There was a problem when having the global matrix and using load balance
to distribute it. This is fixed by the MR.

These changes should be cherrypicked to the release, too.

See merge request !28

One of the use cases for load balancing a matrix is reading it globally
on one process and then calling the load balancer to distribute it among
the processes. Unfortunately this did not work due to a bug that prevented
the correct remapping of the domain numbers from the load balancers. This
lead to negative rank numbers.

With this commit we use yet unassigned process numbers for domains that
are not yet mapped (due to having no dofs before the load balancing).

[cmake][bugfix] Correct handling of the EXCLUDE_FROM_ALL property:

The signature of `dune_add_test`, that takes the `TARGET` from the user
produced excluded targets if added in a directory that has the directory
property `EXCLUDE_FROM_ALL` set. The correct solution IMO is to not use
that property on test subdirectories anymore (it is a relic from the old
testing magic), because we rely on `dune_add_test` to handle exclusion.

See core/dune-common#21 for details.

See merge request !27

The signature of `dune_add_test`, that takes the `TARGET` from the user
produced excluded targets if added in a directory that has the directory
property `EXCLUDE_FROM_ALL` set. The correct solution IMO is to not use
that property on test subdirectories anymore (it is a relic from the old
testing magic), because we rely on `dune_add_test` to handle exclusion.

See core/dune-common#21 for details.

I had removed it by accident in one of the previous commits.

All blocks have the same size, therefore 'block' is not actually needed.
This is the first step towards getting rid of it.

The recent changes to VariableBlockVector broke the Matrix class -- shame on me
for testing thoroughly enough before pushing.  However, using VariableBlockVector
internally in Matrix was a hack anyway.  So, as a first step towards a cleaner
solution, this patch copies the (old) VariableBlockVector class into the file,
renames VariableBlockVector to DenseMatrixBase, and does some obvious cleanup.
This is still not particularly pretty, but better than before.

This fixes a valgrind warning in the test for VariableBlockVector, where the reference type
is an internal proxy class.

Just as containers from the standard library do.  These types are needed for
proper interface testing of the dune-istl vector interface.  For VariableBlockVector,
in particular, the type used for references is *not* value_type&, and therefore
the more general approach using a separate 'reference' type is needed.

Yes, strictly speaking this is an API change.  But the VariableBlockVector code
has been so buggy until the last few patches that I doubt anyone actually used it.

Previously, a method of the same name was inherited from the base class, which
however returned bogus results.

- much shorter code
- makes the iterators pass the test suite

The FieldVector class resides in dune-common, and is tested there.  However, we also
want to check it against the tests specifying the dune-istl vector interface in vectortest.hh,
therefore we add a second test for FieldVector to the dune-istl module.

Previously, they were inherited from the base class, resulting in the wrong types.

So far, each dune-istl vector class had its own unit test.  They all tested, among
other things, for compliance with the dune-istl vector interface.  This lead, or had
the risk to lead, to subtle differences between the individual tests.  Also, since
there is no formal specification of the interface, it was somewhat unclear what the
interface actually requires.

This patch tries to improve the situation by providing a generic set of tests that
should be passed by anything claiming to be a dune-istl vector.  This will save work,
because it allows to centralize tests that are now distributed across the different
unit tests for the different dune-istl vectors.  Also, it is my hope that these
centralized tests can serve as some form of formalized specification of the dune-istl
vector interface.

Integers do not form a field, hence 'int' is not a sensible field_type.

Required by the RandomAccessIteratorFacade

According to the Dune style rules, names with trailing underscores are reserved
for class data members.

Since the names of method parameters are not part of the API, they can be changed
without prior warning or deprecation period.

Elias Pipping authored 9 years ago and Christoph Grüninger committed 9 years ago

The functionality is retained in the form of a DenseMatrixAssigner
specialisation

See also flyspray/FS#1669

[doc] add reference to KAMG paper

fix #1

See merge request !24

Feature/shorten poweriterationtest

The tests often times out when compiled without optimizations

See merge request !22

The tests often times out when compiled without optimizations

Feature/fs 1538 build and mark skipped tests

The remaining conditional builds are kept because they are used to build tests multiple times, with or without SuperLU, ARPACKPP or UPFPack.

See merge request !21

This implmenets FS#1538 for dune/istl/test