BUG: meshes with differing pointsInstance and facesInstance were not decomposed correctly.

In case of differing pointsInstance and facesInstance it will
- read the points belonging to the facesInstance
- construct and write the mesh belonging to the facesInstance
  (so with the old, facesInstance, points)
- additionally write the current points to pointsInstance
This commit is contained in:
mattijs
2010-02-08 11:12:52 +00:00
parent dd2b8a8200
commit 379eac4f74
3 changed files with 125 additions and 13 deletions

View File

@ -55,6 +55,9 @@ class domainDecomposition
{
// Private data
//- Optional: points at the facesInstance
autoPtr<pointIOField> facesInstancePointsPtr_;
//- Mesh decomposition control dictionary
IOdictionary decompositionDict_;