Orca: Make loss_creator optional and discuss criterion when fit and eval #7168
Conversation
This file contains 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
hkvision
reviewed
Jan 4, 2023
| @@ -304,6 +304,10 @@ def train_epoch(self, | |||
| self.train_loader.sampler.set_epoch(self.epochs) | |||
| self.logger.debug("Begin Training Step {}".format(self.epochs + 1)) | |||
|
|
|||
| if not self.criterion: | |||
| invalidInputError(False, | |||
| "You must provide a loss_creator.") | |||
There was a problem hiding this comment.
Change the message to You must provide a loss for train and evaluate?
hkvision
approved these changes
Jan 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
When in predict mode, there should be no loss_creator. So we should require loss_creator when fiting or validating instead of init estimator.
#7161