[PyTorch] Use same API in optimizer zero_grad
as PyTorch optimizers
#1466
+94
−32
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.
Description
The fused optimizers (copied from Apex in #867) have a non-standard API that makes it annoying to swap with the vanilla PyTorch optimizers. This PR deprecates the
set_grad_none
kwarg inFusedAdam
andFusedSGD
in favor of aset_to_none
kwarg inzero_grad
, similar to the vanilla PyTorch API. I've also modified some of the constructor kwargs to be more consistent with PyTorch.Closes #1453.
Type of change
Changes
set_grad_none
kwarg inFusedAdam
andFusedSGD
in favor ofset_to_none
kwarg inzero_grad
FusedAdam
andFusedSGD
constructorsChecklist: