When testing the current implementation of heat.meshgrid, PyTorch throws the following warning
UserWarning: torch.meshgrid: in an upcoming release, it will be required to pass the indexing argument.
that indicates that some changes will be necessary in the future...
(In the current implementation of Heats meshgrid, there is even a comment # pytorch does not support the indexing keyword: switch vectors and subsequent code that seems to be only due to the fact that at that time PyTorch didnt accept indexing arguments for its meshgrid...)
Optional: our meshgrid only works if at most one of the input arrays is distributed... can we maybe provide a workaround? (e.g., leaving the largest input array splitted and making all others unsplit?)
When testing the current implementation of
heat.meshgrid
, PyTorch throws the following warningthat indicates that some changes will be necessary in the future... (In the current implementation of Heats meshgrid, there is even a comment
# pytorch does not support the indexing keyword: switch vectors
and subsequent code that seems to be only due to the fact that at that time PyTorch didnt accept indexing arguments for its meshgrid...)Optional: our
meshgrid
only works if at most one of the input arrays is distributed... can we maybe provide a workaround? (e.g., leaving the largest input array splitted and making all others unsplit?)