heat
heat copied to clipboard
Refactoring of `communication`: separate `mpi4py`-wrappers from `DNDarrays`
Currently, the code wrapping mpi4py
for torch.Tensor
's is contained in heat/core/communication.py
and not fully separated from constructions related to the DNDarray
-class (e.g., computation of chunk sizes is also introduced there).
I would suggest to separate this clearly, which may also make #482 and similar work easier:
- code wrapping
mpi4py
fortorch.Tensor
's becomes an own module of heat - in
heat/core/communication.py
this module can be used
Diclaimer: feel free to discuss other ideas for refactoring and/or that status-quo does not need changes
This issue is stale because it has been open for 60 days with no activity.