- Also fixed bug noted in issue #269
- Previous implementation had all faces together, which made
it difficult (impossible) for external applications to
figure out which geometry was being referred to.
- Provide separate region/patches as follows:
// Patch: <regionName> <patchName>
For example,
// Group: coupleGroup
// Patch: heater minY
8( ... )
The region-name is always present, even if there is only one region.
- This change is a partial reversion to the behaviour in 2.4.x, except
that we can now also handle multi-region geometries.
Changing the leading comment from "# " to "// " facilitates parsing
of the files with OpenFOAM itself if necessary.
- moved control to functionObject (from bc)
- this allows multi-region support
- see heatTransfer/chtMultiRegionFoam/externalCoupledMultiRegionHeater tut
- generalisation of streamed reading/writing of specialised bcs
Updated objects
- corrected Peclet number for compressible cases
- propagated log flag and resultName across objects
New function objects
- new fluxSummary:
- calculates positive, negative, absolute and net flux across face
zones
- new runTimeControl
- abort the calculation when a user-defined metric is achieved.
Available options include:
- average value remains unchanged wrt a given threshold
- equation initial residual exceeds a threshold - useful to abort
diverging cases
- equation max iterations exceeds a threshold - useful to abort
diverging cases
- min/max of a function object value
- min time step exceeds a threshold - useful to abort diverging
cases
- new valueAverage:
- average singular values from other function objects, e.g. Cd, Cl and
Cm from the forceCoeffs function object
