Enforce Lightning module as source of truth for automatic optimization #7130
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.
What does this PR do?
This is further cleanup from #4317. This PR deletes the train loop's automatic optimization attribute and enforces all accesses go through the lightning module's property. This ensures we don't have divergence across these fields. Since the lightning module is the sole decider for automatic optimization, it looked very odd that the lightning module itself was referring to this property via
self.trainer.train_loop.automatic_optimization
even thoughself.automatic_optimization
was already defined. Now that the trainer constructor argument forautomatic_optimization
is gone, we can simplify this.Before submitting
PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:
Did you have fun?
Make sure you had fun coding 🙃