Apply get_metric_with_all_outputs on train step
#210
Merged
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
illian01
changed the title
get_metric_with_all_outputs on train step
deepkyu
reviewed
Oct 31, 2023
deepkyu
reviewed
Oct 31, 2023
deepkyu
approved these changes
Oct 31, 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
Please include a summary in English, of the changes in this pull request. If it closes an issue, please mention it here.
Closes: #209
You should link at least one existing issue for PR. Before your create a PR, please check to see if there is an issue for this change.
PRs from forked repository not accepted.
Change(s)
get_metric_with_all_outputsmethod of base pipeline and all tasks.get_metric_with_all_outputsin train phase.Changelog
If you PR to
devbranch, please add a brief summary of the change to the Upcoming Release section of theCHANGELOG.mdfile and include a link to the PR (formatted in markdown) and a link to your github profile.For example,
Code Formatting
If you PR to either
masterordevbranch, you should follow the code linting process. Please check your code withlint_check.shin./scriptsdirectory.For more information, please read the contribution guide in
CONTRIBUTING.md.