Keep dataloaders, model, meters as members of ClassyTask #8
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.
Summary:
This will make more sense after you review D17515697: I'm hiding ClassyState
from the public API, but in some cases we access state.optimizer, state.model
etc. This diff adds these members to ClassyTask so it can replace the state.
Eventually I want to move these from the state to the task, but for now we
need them in both.
Differential Revision: D17515732