reduce logging severity for set_to_none #471
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We want to warn users of an unexpected behaviour with
set_to_none
flag. Normally, bothnn.Module
andOptimizer
let clients choose whether they want to remove the.grad
attribute altogether or just set it to None.We, on the other hand, don't want to remove the attributes - it's more convenient to assume the
.grad_sample
attribute is always present. It's not an absolute requirement, but we did that historically and I don't see a case for changing it now.However, default value for
set_to_none
is False, meaning most users are getting annoying logging notifications on every training step.