diff --git a/src/decompositionMethods/decomposeReconstruct/decomposeTools/finiteVolume/decomposeMesh.C b/src/decompositionMethods/decomposeReconstruct/decomposeTools/finiteVolume/decomposeMesh.C index 3d0fab6bf..2bdf6b4fe 100644 --- a/src/decompositionMethods/decomposeReconstruct/decomposeTools/finiteVolume/decomposeMesh.C +++ b/src/decompositionMethods/decomposeReconstruct/decomposeTools/finiteVolume/decomposeMesh.C @@ -168,6 +168,10 @@ void Foam::domainDecomposition::decomposeMesh(const bool filterEmptyPatches) // that will be created in decomposition when running in parallel forAll (patches, patchI) { + // VV Comment: Why do we need to check whether the neighbour data + // exists? If it is a processorPolyPatch, shouldn't it be impossible + // for the data not to exist? + // Check the processor patch for which neighbour data exists if ( @@ -178,6 +182,10 @@ void Foam::domainDecomposition::decomposeMesh(const bool filterEmptyPatches) const processorPolyPatch& procPatch = refCast(patches[patchI]); + // VV Comment: Shouldn't we make sure that the "new" slave is + // handled here only, and not the "old" slave? E.g. check + // whether ownerProc < neighbourProc? + // DO ONLY SLAVE SIDE if (!procPatch.master()) { @@ -205,7 +213,7 @@ void Foam::domainDecomposition::decomposeMesh(const bool filterEmptyPatches) // remains in the (old) processor patch // If ownerProc and neighbourProc are different, // this will be a new processor boundary created from - // the existing processor face and added afterwards + // the existing processor face and added afterwards if (ownerProc != neighbourProc) { // Search algorithm repeated in processor patches. @@ -274,6 +282,27 @@ void Foam::domainDecomposition::decomposeMesh(const bool filterEmptyPatches) } } + Pout<< "_________________________________________________" << endl; + Pout<< "SLAVE FINISHED" << endl; + forAll (interProcBoundaries, procI) + { + Pout<< "Inter processor boundary for proc: " << procI << nl + << "Neighbouring processors: "; + const SLList