Deterministic=True works for version 1.1.4 , but encounters errors for version 1.5.5 #11007
Unanswered
zhiqiangdon
asked this question in
Lightning Trainer API: Trainer, LightningModule, LightningDataModule
Replies: 1 comment 1 reply
-
In Lightning 1.5+, the framework uses torch.use_deterministic_algorithms which has more comprehensive determinism checks compared to the prior cudnn flag. What errors are you seeing? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have found inconsistent behaviors about setting
Deterministic=True
inTrainer()
. My code runs well when using Lightning with Version 1.1.4. However, after upgrading Lightning to Version 1.5.5, running the same code encounters the following error:"RuntimeError: upsample_bilinear2d_backward_out_cuda does not have a deterministic implementation, but you set 'torch.use_deterministic_algorithms(True)'. You can turn off determinism just for this operation if that's acceptable for your application."
I am a little confused why it doesn't throw the error in Version 1.1.4. I understand that bilinear upsampling is not deterministic. Does Version 1.1.4 use deterministic algorithms only for the operations supporting that? Does Version 1.5.5 naively set all operations to use deterministic algorithms, not checking whether they support that or not? How can I use
deterministic=True
in Version 1.5.5 without worrying about errors?Thanks,
Beta Was this translation helpful? Give feedback.
All reactions