It does not seem to be necessary anymore, but it was in a previous PL release which could not automatically convert custom objects to CUDA. I will remove the device transfer calls.
It is indeed recommended in the PL doc. However, I made some tests and it seems to work just fine with a single Accuracy() object. Hopefully, @tchaton can clarify.
It just saves a little bit of memory performing the ReLU in-place.
You are right that built-in metrics already support this :)
Hi, I have a couple of doubts about lightning example of GIN provided here: https://github.com/rusty1s/pytorch_geometric/blob/master/examples/pytorch_lightning/gin.py
Sequential
container? https://github.com/rusty1s/pytorch_geometric/blob/c786c02845df216ada316f6f535a72b565c9a424/examples/pytorch_lightning/gin.py#L68-L75sinc_dist=True
shouldn't be set when using built in metric api likeAccuracy
as explained in lightning docs here https://github.com/rusty1s/pytorch_geometric/blob/c786c02845df216ada316f6f535a72b565c9a424/examples/pytorch_lightning/gin.py#L109-L110 @tchaton