Fix: MPI communication errors due to inconsistent R-coordinates in sparse matrix generation #6233
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Linked Issue
Fix #6229
Description
When generating sparse matrices using
get_R_range
, different MPI processes could produce inconsistent sets of R-coordinates. This led toMPI_ERR_TRUNCATE
errors duringMPI_Allreduce
operations because the data sizes across processes mismatched.My solution is:
Synchronize R-coordinates globally:
• Added
sync_all_R_coor
to aggregate R-coordinates from all processes viaMPI_Allgatherv
, ensuring a consistentall_R_coor
set across all ranks.Fix MPI buffer size handling:
• Corrected buffer size calculations in
MPI_Allgatherv
to account for 3 integers (x, y, z) per R-coordinate, resolvingMPI_ERR_TRUNCATE
.