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
I just encountered that the scatter operation with mul reduction leads to wrong values when I cast my input-tensor to dtype short. I am unsure if this is a bug in torch, torch-geometric, torch-scatter, or my brain, so posting it here, since I am importing pyg's scatter method. (Apologies for the oddly-large demo data, I pulled it straight out of my workflow)
Thanks for reporting this issue! A quick workaround would be to uninstall torch_scatter from your env or to disable the flag in your script by writing:
🐛 Describe the bug
I just encountered that the scatter operation with
mul
reduction leads to wrong values when I cast my input-tensor to dtypeshort
. I am unsure if this is a bug in torch, torch-geometric, torch-scatter, or my brain, so posting it here, since I am importing pyg's scatter method. (Apologies for the oddly-large demo data, I pulled it straight out of my workflow)provides this output:
The CPU version values are the correct values as I can verify via other facts for this data (and it is the majority solution).
Versions
Python: 3.11.9
OS: Ubuntu 22.04
pip list
Package Version
...
torch 2.4.0
torch-geometric 2.6.1
torch_scatter 2.1.2
torchaudio 2.4.0
torchmetrics 1.4.0.post0
torchrl 0.5.0
torchvision 0.19.0
...
The text was updated successfully, but these errors were encountered: