Depending on the Dune version, the boundary markers are present on
all processes (<= 2.6) or on the root process only (>= 2.7). Try to
handle this in a flexible way in the corresponding data handle:
Determine if the minimum size over all processes of the boundary
markers vector is zero. If yes, assume that the root process contains
all markers and broadcast them.

Currently, it isn't possible to refine a parallel UGGrid that has
been read by a GmshReader, see dune-grid issue #83. Therefore, don't
refine in the corresponding test.

* Always compare the last vtu file
* Set maximum time step size lower
* Set Newton and linear solver tolerance lower

Dennis Gläser authored 6 years ago and Timo Koch committed 6 years ago

this jump should be independent of the choice for xi, which is why
here we test if for different values of xi the same reference solution
is obtained.

Sina Ackermann authored 6 years ago and Simon Emmert committed 6 years ago

* 2 Latex-errors and 2 ingroup-errors left

Sequential will get an extra commit

sequential gets an extra commit

Bernd Flemisch authored 6 years ago and Timo Koch committed 6 years ago

Introduce an optional parameter `ignoreState` that defaults to `false`.
Warn once if nearest-vertex interpolation is used.
Introduce helper class `SolutionEvaluator` to avoid code duplication and
hide implementation details, particularly the SFINAE detection of
`priVars.state()`.

Kilian Weishaupt authored 6 years ago and Timo Koch committed 6 years ago

* use only one executable

Kilian Weishaupt authored 6 years ago and Timo Koch committed 6 years ago

* use only one executable