You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now assume that, upon Operator application, the sparse points get distributed via _dist_scatter to the 4 ranks and the result is
a c --- b d g --- e f --- h
Now, upon returning from Operator application, via _dist_gather, the sparse points get stored
either as
a c b d g e f h
OR
a b e h c d f g
(to be double checked)
So the layout is different than it was upon data allocation/initialization.
Instead of making sure the layout is deterministically the same, currently the coordinates are rather reshuffled the same way the sparse points are, so that the mapping position -> value is correct
This is horrible. Possible approaches to improve this:
Fix the bug such that upon gather, the layout is as expected
Make SparseFunctions unordered collections (difficult because we do wanna use Data, I imagine...)
The text was updated successfully, but these errors were encountered:
Assume rank0, out of 4 MPI ranks, has 8 items
Now assume that, upon Operator application, the sparse points get distributed via
_dist_scatter
to the 4 ranks and the result isNow, upon returning from Operator application, via
_dist_gather
, the sparse points get storedeither as
OR
(to be double checked)
So the layout is different than it was upon data allocation/initialization.
Instead of making sure the layout is deterministically the same, currently the
coordinates
are rather reshuffled the same way the sparse points are, so that the mappingposition -> value
is correctThis is horrible. Possible approaches to improve this:
Data
, I imagine...)The text was updated successfully, but these errors were encountered: