BUG: cyclicACMI: different construction order. See #1953.

This makes the initialisation order of dynamicMesh consistent
with plain ones using the virtual mechanism. It does not
solve the cyclicACMI construction order yet.
This commit is contained in:
Mattijs Janssens
2020-12-21 14:54:59 +00:00
committed by Andrew Heather
parent 18cd5d864e
commit 14a471f937
34 changed files with 468 additions and 107 deletions

View File

@ -60,6 +60,12 @@ namespace Foam
interfaceTrackingFvMesh,
IOobject
);
addToRunTimeSelectionTable
(
dynamicFvMesh,
interfaceTrackingFvMesh,
doInit
);
}
@ -1553,9 +1559,13 @@ void Foam::interfaceTrackingFvMesh::correctContactLinePointNormals()
// * * * * * * * * * * * * * * * * Constructors * * * * * * * * * * * * * * //
Foam::interfaceTrackingFvMesh::interfaceTrackingFvMesh(const IOobject& io)
Foam::interfaceTrackingFvMesh::interfaceTrackingFvMesh
(
const IOobject& io,
const bool doInit
)
:
dynamicMotionSolverFvMesh(io),
dynamicMotionSolverFvMesh(io, doInit),
aMeshPtr_(new faMesh(*this)),
fsPatchIndex_(-1),
fixedFreeSurfacePatches_