-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Add mypy typing to precision plugins. #6149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
8a08f32
add typing to precision plugins
justusschock 50b695b
Apply suggestions from code review
Borda 2170d0d
yapf
Borda 249563c
Apply suggestions from code review
justusschock 05f4bde
missing annotation marks
justusschock 6cde620
missing annotation marks
justusschock db94b17
missing annotation marks
justusschock c0b67f1
Merge branch 'master' into typing_precision_plugins
Borda 3ee95d9
flake8
Borda File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -12,37 +12,36 @@ | |
| # See the License for the specific language governing permissions and | ||
| # limitations under the License. | ||
| from contextlib import contextmanager | ||
| from typing import Callable, Generator | ||
| from typing import Any, Callable, Generator, TYPE_CHECKING | ||
|
|
||
| import torch | ||
| from torch.optim import LBFGS, Optimizer | ||
| from torch.optim import LBFGS | ||
|
|
||
| from pytorch_lightning.core import LightningModule | ||
| from pytorch_lightning.plugins.precision.mixed import MixedPrecisionPlugin | ||
| from pytorch_lightning.utilities import _NATIVE_AMP_AVAILABLE, AMPType | ||
| from pytorch_lightning.utilities import AMPType | ||
| from pytorch_lightning.utilities.exceptions import MisconfigurationException | ||
|
|
||
| if _NATIVE_AMP_AVAILABLE: | ||
| from torch.cuda.amp import autocast | ||
| else: | ||
| autocast = None | ||
| if TYPE_CHECKING: | ||
| from torch.optim import Optimizer | ||
|
|
||
| from pytorch_lightning.core import LightningModule | ||
carmocca marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
|
|
||
| class NativeMixedPrecisionPlugin(MixedPrecisionPlugin): | ||
|
|
||
| def __init__(self): | ||
| def __init__(self) -> None: | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. why is it necessary to annotate init with None?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
| self.backend = AMPType.NATIVE | ||
| self.scaler = torch.cuda.amp.GradScaler() | ||
|
|
||
| def backward( | ||
| self, | ||
| model: LightningModule, | ||
| model: 'LightningModule', | ||
| closure_loss: torch.Tensor, | ||
| optimizer: Optimizer, | ||
| optimizer: 'Optimizer', | ||
| opt_idx: int, | ||
| should_accumulate: bool, | ||
| *args, | ||
| **kwargs, | ||
| *args: Any, | ||
| **kwargs: Any, | ||
| ) -> torch.Tensor: | ||
| """performs the actual backpropagation | ||
|
|
||
|
|
@@ -65,7 +64,12 @@ def backward( | |
| return closure_loss | ||
|
|
||
| def pre_optimizer_step( | ||
| self, pl_module: LightningModule, optimizer: Optimizer, optimizer_idx: int, lambda_closure: Callable, **kwargs | ||
| self, | ||
| pl_module: 'LightningModule', | ||
| optimizer: 'Optimizer', | ||
| optimizer_idx: int, | ||
| lambda_closure: Callable, | ||
| **kwargs: Any, | ||
| ) -> bool: | ||
| """always called before the optimizer step. | ||
| Checks that the optimizer is not LBFGS, as this one is not supported by native amp | ||
|
|
@@ -83,13 +87,13 @@ def pre_optimizer_step( | |
|
|
||
| return False | ||
|
|
||
| def post_optimizer_step(self, optimizer: Optimizer, optimizer_idx: int) -> None: | ||
| def post_optimizer_step(self, optimizer: 'Optimizer', optimizer_idx: int) -> None: | ||
| """Updates the GradScaler""" | ||
| self.scaler.step(optimizer) | ||
| self.scaler.update() | ||
|
|
||
| @contextmanager | ||
| def train_step_context(self) -> Generator[autocast, None, None]: | ||
| def train_step_context(self) -> Generator[None, None, None]: | ||
| """Enable autocast context""" | ||
| with torch.cuda.amp.autocast(): | ||
| yield | ||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isn't this API change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was named model in all the other plugins and I checked, It is never called by name.
But if we don't do this, MypY complains, that the signature does not match with base class since it has different parameters