To build these combinations with the CI-system, install foamgrid for the tests with parmg, vtk, curvedgeometry and curvedgrid

Correct the stopping criterion in the Riemannian-TR-Solver, Riemannian-PN-Solver and MixedRiemannian-TR-Solver

Do not stop if the correction gets small because the trust region radius gets small or the regularization parameter gets large

They are getting removed now for good after the release of
dune-fufem 2.9.  The code that replaces them has been there
for quite a while, and therefore we can simply use it
without having to worry about compatibility with older
dune-fufem versions.

This makes it possible to use other Assemblers

In case the solve step (which is only done on process 0) goes wrong
communicate it to all processes.

Print out assembly time for each process on each process and
print out the gradient norms only on one process.

Catch an exception that might be thrown by the localEnergy_ and solve the problem again using a smaller trust region.
Also make sure the ADOLC-Tape gets closed properly

Print total time, total assembly time and total time needed for solving at the end of the trust-region solver run

WHITESPACES: Continue with Trust-Region-Algorithm if IPOPT threw an error while solving, treat this case as an 'unsuccessful iteration'

Continue with Trust-Region-Algorithm if IPOPT threw an error while solving, treat this case as an 'unsuccessful iteration'

Lisa Julia Nebel authored 5 years ago and Sander, Oliver committed 5 years ago

This class will gradually replace the current implementations
GlobalP1Mapper and GlobalP2Mapper, because dune-gfe is not
the proper place for infrastructure for distributed computing.
Plus, the stuff in dune-parmg already is more flexible and
powerful.

Automatic testing of the RiemannianTrustRegionSolver class requires
to know what it did on the previous run.  This patch adds
some infrastructure to collect this information.

This makes sequential cosserat-continuum compile again.

It's the same code, but the old name is deprecated.

The interface of Solvers::IterativeSolver used to make its
iterationStep_ member publicly available.  This has changed,
and the iteration step can now only be accessed by a getter
method (which is good).  However, that getter returns a
reference, but not the full smart pointer.

See the discussion at

  https://git.imp.fu-berlin.de/agnumpde/dune-solvers/merge_requests/23

This got introduced in dune-grid 2.6.

- use more shared_ptr
- New MCMGMapper interface from dune-grid 2.6
- basis.indexSet() has been removed from dune-functions

A lot of raw pointers have been replaced by std::shared_ptr.

A lot of data members are inaccessible now, and getters have
to be used.

A small patch is still needed for dune-solvers: The iterationStep_
member is still needed to be public, because the new getter only
grants access to the object, not the pointer to it.

It still tested for the dune-fufem wrapper of a first-order basis, while nowadays
the RiemannianTRSolver class is instantiated with dune-functions bases.