GitLab

This way, types that implement AutonomousValue can specify into what
type they are copied. This can be applied e.g. for proxy types such as
the BlockVectorWindow used in ISTL's VariableBlockVector.

For types that do not implement AutonomousValue, the behavior should
not change.

Port bcqfconstrainedlinearization.hh to 'if constexpr'

See merge request !15

It is not supported by Dune 2.8 anymore.

Minor updates

See merge request !14

Otherwise use Functional::Vector

Merge branch 'feature/proper-generic-copyOrReference-in-BoxConstrainedQuadraticFunctional' into 'master'

Properly forward constructor to CopyOrReference members.

See merge request !11

Update CI config to clang-7

See merge request !13

The old image is no longer updatet

Update gitlab-ci.

See merge request !12

Bugfix: Set empty ignore nodes for IterativeSolver

See merge request !10

This was missing after the code shift to the external class.
It caused a segmentation fault when TNNMG is used with an
IterativeSolver/LinearSolver object.

The type cannot be deduced by the compiler.

move implementation details of linear correction out of TNNMGStep

See merge request !9

This simplifies the `iterate()` method such that it fits on a single
screen.

address compiler warnings and deprecations

See merge request !8

This addresses warnings that passing a raw pointer is deprecated.

[cleanup] remove autotools build system

See merge request !7

Add 'ConstrainedMatrix' and 'ConstrainedBitVector' to linearizations

See merge request !6

The extended TNNMG step requires these typenames for the LinearSolver constructor.
For the build-in linearizations the contrained types are the same as the unconstrained ones.

This is just a modified version of the NonlinearGSTest using the newer TNNMGStep.
Up to now, commits that lead TNNMGStep based implementations to fail would not be covered by the CI.

Allow TNNMG to use Solvers::LinearSolver object

See merge request !5

Clang complains that this must be initializes from a constexpr
(which is maybe not the case here). However, there's no need for
constexpr here, so let's calm down clang and make the test pass again.

While I'd like the tested interface more, it's not implemented
yet leading to a failing test