utilities: Updated moveMesh -> setPoints

Mesh manipulation utilities do not need to generate or use mesh-motion fluxes so
it is more efficient to use setPoints rather than moveMesh.
This commit is contained in:
Henry Weller
2022-06-14 14:09:06 +01:00
parent cc4f63fbd6
commit f0d3be60da
21 changed files with 30 additions and 30 deletions

View File

@ -724,7 +724,7 @@ int main(int argc, char *argv[])
// tensors.
Info<< "Doing topology modification to order faces." << nl << endl;
autoPtr<polyTopoChangeMap> map = meshMod.changeMesh(mesh, true);
mesh.movePoints(map().preMotionPoints());
mesh.setPoints(map().preMotionPoints());
if (writeCyclicMatch)
{
@ -754,7 +754,7 @@ int main(int argc, char *argv[])
Info<< "Points changed by average:" << gAverage(diff)
<< " max:" << gMax(diff) << nl << endl;
mesh.movePoints(newPoints);
mesh.setPoints(newPoints);
}
// 3. Remove zeros-sized patches