polyPatch: Removed unnecessary constructors and clone functions
Poly patches should not hold non-uniform physical data that needs mapping on mesh changes (decomposition, reconstruction, topology change, etc ...). They should only hold uniform data that can be user-specified, or non-uniform data that can be constructed on the fly from the poly mesh. With the recent changes to mappedPatchBase and extrudeToRegionMesh, this has now been consistenly enforced, and a number of incomplete implementations of poly patch mapping have therefore been removed.
This commit is contained in:
@ -1032,7 +1032,6 @@ labelList addRegionPatches
|
||||
// << " between regions " << e
|
||||
// << " trying to add patches " << names << endl;
|
||||
|
||||
|
||||
mappedWallPolyPatch patch1
|
||||
(
|
||||
names[0],
|
||||
@ -1042,7 +1041,6 @@ labelList addRegionPatches
|
||||
regionNames[e[1]], // sampleRegion
|
||||
mappedPatchBase::NEARESTPATCHFACE,
|
||||
names[1], // samplePatch
|
||||
point::zero, // offset
|
||||
mesh.boundaryMesh()
|
||||
);
|
||||
|
||||
@ -1064,7 +1062,6 @@ labelList addRegionPatches
|
||||
regionNames[e[0]], // sampleRegion
|
||||
mappedPatchBase::NEARESTPATCHFACE,
|
||||
names[0],
|
||||
point::zero, // offset
|
||||
mesh.boundaryMesh()
|
||||
);
|
||||
fvMeshTools::addPatch
|
||||
|
||||
Reference in New Issue
Block a user