This change set brings changes from @majosm's fork (https://github.com/majosm/mirgecom/commit/a444cdd7c8618caa79b14e93adf752e0c4f86c3d), which makes mesh partitioning a node-local affair. Each physical compute node gets the mesh data (read from gmsh or generated) and locally partitions and distributes the mesh partitions among the ranks local to the physical compute node.
Questions for the review:
[ ] Is the scope and purpose of the PR clear?
[ ] The PR should have a description.
[ ] The PR should have a guide if needed (e.g., an ordering).
[ ] Is every top-level method and class documented? Are things that should be documented actually so?
[ ] Is the interface understandable? (I.e. can someone figure out what stuff does?) Is it well-defined?
[ ] Does the implementation do what the docstring claims?
[ ] Is everything that is implemented covered by tests?
[ ] Do you see any immediate risks or performance disadvantages with the design? Example: what do interface normals attach to?
This change set brings changes from @majosm's fork (https://github.com/majosm/mirgecom/commit/a444cdd7c8618caa79b14e93adf752e0c4f86c3d), which makes mesh partitioning a node-local affair. Each physical compute node gets the mesh data (read from gmsh or generated) and locally partitions and distributes the mesh partitions among the ranks local to the physical compute node.
Questions for the review: