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

@ -534,7 +534,7 @@ int main(int argc, char *argv[])
if (map().hasMotionPoints())
{
mesh.movePoints(map().preMotionPoints());
mesh.setPoints(map().preMotionPoints());
}
cutter.topoChange(map());
@ -580,7 +580,7 @@ int main(int argc, char *argv[])
}
// Move master point to destination.
mesh.movePoints(newPoints);
mesh.setPoints(newPoints);
List<pointEdgeCollapse> allPointInfo;
const globalIndex globalPoints(mesh.nPoints());
@ -606,7 +606,7 @@ int main(int argc, char *argv[])
if (map().hasMotionPoints())
{
mesh.movePoints(map().preMotionPoints());
mesh.setPoints(map().preMotionPoints());
}
// Not implemented yet:
@ -651,7 +651,7 @@ int main(int argc, char *argv[])
if (map().hasMotionPoints())
{
mesh.movePoints(map().preMotionPoints());
mesh.setPoints(map().preMotionPoints());
}
cutter.topoChange(map());