Reason

Many postprocessors which were developed before newer APIs came about do their communication in getValue(). With the finalize() method added, we suggest that communication is done there instead.

Design

Move communication calls from getValue() to finalize() for postprocessors where possible.

Impact

Consistency across postprocessor objects.

The nonlinear solver from the Sundials library KINSol has the following default behavior:

KINSol limits the maximum Newton update if

|| scale * update ||_2 > max(1000 * || scale * u0 ||_2, 1).

This forces KINSol to take more steps than necessary in the linear case.

Providing the option KINSetMaxNewtonStep(kin_mem, max_step) changes the default behavior to

|| scale * upda

The problem is as follows:

Given an optimization model part which contains elements. Gid is specified as output format. If the elements of the optimization model part are not initialized (which may happen e.g. when no internal analyzer is defined), then the function GiDOutputProcess::ExecuteBeforeSolutionLoop will produce a seg-fault when it calls

`__initialize_results --> gid_io.h line 6

I see that here on SourceForge, there are all Documentations in PDF format archived in single downloadable files. However the source is not provided. Did you use LaTeX or any other MarkUp languages to generate these PDFs? I would appreciate if you could do either of these

• add a Documentation folder on [this repository](

Our current example docs online date back to 2016 (and #863); some of the APIs are out of date and around 4 of the examples are missing entirely.

Thanks to @vikramvgarg for noticing this (months ago), pinging @jwpeterson since he's more familiar with the website setup and probably won't procrastinate on this for as long as I have been.

@lberti could you commit the falling sphere case (geo+cfg+json) ?
please add a README.adoc to explain the expected results

@vincentchabannes needs it to test new developments

add_element!(mesh, elid, eltype, connectivity)
Add an element into the mesh. ´elid´ is the element id, ´eltype´ is the type of the element and ´connectivity´ is the connectivity of the element.

At least eltype needs to be defined more precisely. I guess it's a symbol :Seg2, :Tri3 and so on.

Building OGS in Windows Subsystem for Linux - WSL does not work out-of-the-box.

• Test building OGS (needs a Windows machine with WSL installed, win1 is too old for this)
• Fix build
• Document this

This is worth a try as WSL could be a good alternative for Windows-based developers.

Thanks to Mostafa Mollaali for

Hi all,

Can we add the FEM formulation that we use for solving the incompressible and variable-density (low-Mach) Navier-Stokes equations to the docs somewhere?

I did a cursory search on the website/doxygen documentation - but couldn't find it.

The CLI syntax for this example needs to be update to reflect the explicit choice of PML (--pml) or NONREFLECT (--nonreflect) since the latest version does not have a default.