- can be useful when extracting portions of larger field files

Johan Roenby authored 4 years ago and Mark OLESEN committed 3 years ago

DOC: improve header-file content

STYLE: fix stray use of wordReList instead of wordRes

Co-authored-by: Kutalmis Bercin

- the generic constructor could be called twice in pointPatchField::New,
  which results in an attempt to transfer tokens twice.

It was only looking for faces that were used in both
endpoints but not actually checking whether they were indeed
an edge (== consecutive vertex) in all faces. So if one
face had an additional crossing edge and another didn't it
would find more edgeFaces than the proper
'primitiveMesh::edgeFaces()' routine.
This occasionally happened inside snappyHexMesh
(e.g. motorBike tutorial)

On high numbers of cores the extrudeModel/polyLine can
start compiling before blockMesh/lnInclude has been
constructed correctly.

Handle layer addition on acmi

See merge request !434

mattijs authored 4 years ago and Andrew Heather committed 4 years ago

When extruding an edge to a patch face make sure to extrude
all the patch faces connected to that edge and cell. This
will handle cyclicACMI (has duplicate patches - AMI and non-overlap)

mattijs authored 4 years ago and Andrew Heather committed 4 years ago

fvMesh::readUpdate calls polyMesh::readUpdate which updates
the ACMI (including mesh areas etc). So we should not call
polyMesh::clearOut again inside fvMesh::readUpdate to avoid
having to re-do all the ACMI.

INT: reacting*EulerFoam: correct handling of K for energy equation (#2033)

See merge request !438

TUT: DNS, electromagnetics, financial, stressAnalysis: clean up tutorials

See merge request !437

ENH: solarLoad: new load model, timeDependent

See merge request !431

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

ENH: solarLoad, fvDOM: enable time-dependent spectralDistribution
DOC: solarLoad, fvDOM, solarCalculator: improve header documentation
TUT: solarLoadModel, solarDirectionModel: use new shorter entries

- robuster handling of different VTK versions

- compilation changes for avalanche, cfmesh

For example,
```
entry #eval 10 { vector(rand(), 0, 0) };
```

ENH: be more generous and ignore trailing ';' in expressions

STYLE: adjust parse token name for tensor::I

Tomoki, Karatsu authored 4 years ago and Mark OLESEN committed 4 years ago

- previously had a very old (likely irrelevant) setting for solaris
  systems only.

- support site-specific customization.
  Eg, using etc/config.{csh,sh}/prefs.fjmpi

- remove erroneous shell redirects present in cshell files

- less important for VTK (may help in future though) but preserve
  the face point 0 when flipping faces to ensure that the result
  is the same as having called face::reverseFace()

ENH: refactor Function1 to enable fields

See merge request !435

BUG: possible infinteloop in plicRDF and isoAdvector - Fixes #2016

See merge request !436

TUT: discreteMethods: cleanup tutorials

See merge request !432

ENH: new solvers: overPhaseChangeInterFoam and overCompressibleInterDyMFoam

See merge request !425

sergio authored 4 years ago and Kutalmış Berçin committed 4 years ago

- overCompressibleInterDyMFoam: Overset solver for two compressible,
non-isothermal, immiscible fluids using a VOF (i.e. volume of fluid)
phase-fraction based interface capturing approach.
- overInterPhaseChangeDyMFoam: Overset solver for two incompressible,
isothermal, immiscible fluids with phase-change (e.g. cavitation) using
VoF (i.e. volume of fluid) phase-fraction based interface capturing approach.
- adds new tutorials:
  - multiphase/overCompressibleInterDyMFoam/compressibleTwoSimpleRotors
  - multiphase/overInterPhaseChangeDyMFoam/twoSimpleRotors

Signed-off-by: Kutalmis Bercin <kutalmis.bercin@esi-group.com>

- useful when used in a batch process to trap the exit signal,
  e.g. stop the run when the velocity magnitude exceeds a given
  threshold:

    runTimeControl
    {
        type            runTimeControl;
        libs            ("libutilityFunctionObjects.so");
        nWriteStep      1;

        // Optional end 'action'
        satisfiedAction abort; // end; // setTrigger

        conditions
        {
            maxU
            {
                type            minMax;
                functionObject  MinMax;
                fields          ("max(mag(U))");
                value           1e6;
                mode            maximum;
            }
        }
    }