From 907c80509df249d492303da488f4b3f4ea6c2439 Mon Sep 17 00:00:00 2001
From: Vuko Vukcevic <v.vukcevic@wikki.co.uk>
Date: Thu, 11 Jul 2019 12:44:40 +0200
Subject: [PATCH] Added comment in PrimitivePatchMeshData

Regarding usage of unsorted variant of meshPoints.
---
 .../PrimitivePatchTemplate/PrimitivePatchMeshData.C   | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/src/foam/meshes/primitiveMesh/PrimitivePatchTemplate/PrimitivePatchMeshData.C b/src/foam/meshes/primitiveMesh/PrimitivePatchTemplate/PrimitivePatchMeshData.C
index b9ad4a1d5..8993cf124 100644
--- a/src/foam/meshes/primitiveMesh/PrimitivePatchTemplate/PrimitivePatchMeshData.C
+++ b/src/foam/meshes/primitiveMesh/PrimitivePatchTemplate/PrimitivePatchMeshData.C
@@ -73,12 +73,11 @@ calcMeshData() const
     // number of faces in the patch
     Map<label> markedPoints(4*this->size());
 
-    // Important:
-    // ~~~~~~~~~~
-    // In <= 1.5 the meshPoints would be in increasing order but this gives
-    // problems in processor point synchronisation where we have to find out
-    // how the opposite side would have allocated points. We'll use unsorted
-    // version to avoid certain ordering problems
+    // Note: foam-extend was relying on strong ordering of meshPoints on
+    // processor patches which causes point ordering errors when doing Dynamic
+    // Load Balancing. Because of this ordering error on two sides of processor
+    // boundaries, point fields ended up having wrong values near processor
+    // boundaries. Revert to unsorted version. VV, 11/July/2019.
     dynamicLabelList meshPoints(2*this->size());
     forAll(*this, facei)
     {