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:
@ -11,6 +11,6 @@
|
||||
{
|
||||
// Read new points
|
||||
io.readOpt() = IOobject::MUST_READ;
|
||||
mesh.movePoints(pointIOField(io));
|
||||
mesh.setPoints(pointIOField(io));
|
||||
}
|
||||
}
|
||||
|
||||
@ -23,5 +23,5 @@ if (ioPoints.headerOk())
|
||||
)
|
||||
);
|
||||
|
||||
mesh.movePoints(newPoints);
|
||||
mesh.setPoints(newPoints);
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user