addZones: specifies the name instead of synthesising

ENH: enable custom input of U for devRhoReff and devReff

See merge request !479

Kutalmış Berçin authored 3 years ago and Andrew Heather committed 3 years ago

Previously, for basic incompressible and compressible simulations,
the "force" function object has not been using the user-specified "UName"
for the "devRhoReff" computation (affecting the tangential component),
but using the "U" of the latest available step. In contrast,
the user-specified "pName" has always been being used correctly.

This has been causing issues for users when they wish to use a specific
"UMean" field in various force and forceCoeff function object computations.

ENH: turbulenceFields: various improvements

See merge request !476

BUG: DMD: write snapshot0 at start times

See merge request !482

ENH: linear solvers: add variable-specific debug flags

See merge request !478

Kutalmış Berçin authored 3 years ago and Andrew Heather committed 3 years ago

Introduces a new optional keyword of label type 'log'
to linear-solver dictionaries to enable variable-specific
debug statements. For example, in fvOptions file:

    solvers
    {
        p
        {
            solver GAMG;
            ...
            log    2;
        }

        U
        {
            ...
            log    0;
        }
    }

The meanings of values of 'log' are:

    log    0;    <!--  no output
    log    1;    <!--  standard output
    log    2;    <!--  debug output
    // values higher than 2 are expected to have no effect

This keyword does not directly affect the operations of various
DebugSwitches and backward compatibility has been ensured in exchange
of code cleanness. The related DebugSwitches are:

    DebugSwitches
    {
        SolverPerformance    0;
        GAMG                 0;
        PCG                  0;
        PBiCG                0;
        smoothSolver         0;
    }

Implicit treatment of coupled boundary conditions

See merge request !477

- liquid film, blockMesh changes, multiWorld communicators

- previously reported the WM_PROJECT_VERSION in the top banner
  but this makes it overly sensitive to arbitrary user naming.

  Change to the current API in the comment banner, include the
  WM_PROJECT_VERSION as part of the reported "Build: ..."
  string instead.

improve handling of multiple world communication

See merge request !480

- cleanup initialization (to avoid stealing tokens)

- previously had a patch-size check, which caused a zero-sized patch
  to be "sticky" as uniform Zero regardless of what the original input
  stated (eg, "constant 0.5")

  This was caused by short-circuiting logic that circumvented reading
  on zero-size patches.