The running result of configuring the aggregate function in nn.conv.gin_conv
to max
cannot be reproduced!
#8969
-
When I deploy the GIN model in my project, the results can be reproduced when using the default |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 1 reply
-
I have already using SparseTensor and not using global_add_pool instead of torch.nn.functional.adaptive_max_pool1d. And all scripts and platform configurations have not changed. Just modifying the aggregator will cause uncertainty. I guess the problem may not be with the pooling operation #8266. |
Beta Was this translation helpful? Give feedback.
-
Do you mind sharing your model and the input data you are using? |
Beta Was this translation helpful? Give feedback.
-
Here are my demo scripts, running on the Ubuntu Laptop with the key configuration:
The results based on sum, avg and max aggregator are as followed (seed=2020):
Hope your answers and many thanks!! |
Beta Was this translation helpful? Give feedback.
-
Thank you. I can reproduce this. The issue is that |
Beta Was this translation helpful? Give feedback.
Thank you. I can reproduce this. The issue is that
segment_max
is not deterministic in the backward pass if the maximum is shared across neighbors (in which case it picks one element randomly). This is not sadly not super trivial to fix.