Add globalIndex info to globalMeshData

Requested by @Mattijs - replace the total point/face/cell information with globalIndex to allow reuse in various other places without requiring communication each subsequent time.

changed milestone to %v2406

added enhancement label

assigned to @mark

mentioned in commit 8b793f88

Hi @Mattijs - I update globalMeshData to make the changes, but there are still a few possible refinements.

There is still the hack in there to use a duplicate communicator (bb0898d2 and 865af489). However, I'm not convinced that this is still needed. By changing from a reduce of total point/face/cell numbers to using a globalIndex for the quantities. With these changes we are calling an MPI_Allgather, so not sure where any clashes would now arise.

As we discussed, the names globalMeshCellAddr() are indeed a bit of a mouthful, especially since these are actually part of globalMeshData. So we have mesh.globalData().globalMeshCellAddr()! Might consider relocating these to be demand-driven onto polyMesh directly?

• dup comm: probably right.
• globalMeshData: no real opinion - verbose naming we can live with. How much do you want to move? Also connectivity? Or just numbering?

Numbering should be enough. Complements the regular nCells etc

Sounds good.

closed