the fact that some points are on the boundary.
When there is more than one boundary point on the face, it is
arbitrarily picking one, which can distort the surface. Need to give
information about which points are features and decide how to
arbitrate when multiple boundary or feature points are seeking to be
collapsed together.
closer than SMALL when a pointFile is read (and perhaps other
situations). When this is detected, deleting one or both of the points.
Also adding a check that both Delaunay vertices are internal before
looking at them in pointToBeRetained, otherwise there is a risk of a
seg-fault or undefined behaviour.
to a timestep. Passing an instance to the writeMesh functions rather
than a bool.
Adding infrastructure to record and use the fact that some dual
vertices are on the surface, so when points are merged and faces are
collapsed, the boundary points are preferred.
default whern surface does not support volumeType.
BUG: conformalVoronoiMesh. Making test "totalHits >= hitLimit" rather than
"totalHits = hitLimit" to be strictly consistent and always trigger
the iteration termination message.
No longer reading or writing edgeDirections - calculating them on
read.
Properly initialising data in featureEdgeMesh constructor.
Fixing use of extend for treeBoundBox.
Removing writeObj from featureEdgeMesh constructor - calling
explicitly from surfaceFeatureExtract.
So now we can read multiple times (using UIPstream) from PstreamBuffers
PstreamBuffers pBufs
UIPstream str1(procI, pBufs);
str1>> ..
UIPstream str2(procI, pBufs);
str1>> ..
- Added chemical enthalpy access function to top level api.
- Re-worked source term for enthalpy equation(s) in chemistry model, and
- Re-worked heat release calculation
STYLE: Using worded dimensions instead of dimensionSet(...)
Each collocated set of coupled points has a single master assigned to it.
However when doing mergePoints on a patch the master does not have to be
on the patch. So now it returns mesh point labels, not patch point labels.
