Remove speed metrics from default compute objective [WIP] #10107
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 PR removes speed metrics (e.g.
eval_runtime
) from the default compute objective (default_compute_objective
).default_compute_objective
is used when nocompute_objective
is passed toTrainer.hyperparameter_search
.Trainer
adds speed metrics such aseval_runtime
andeval_samples_per_second
to the metrics anddefault_compute_objective
returns the sum of metrics as the objective so these speed metrics will be included in the objective.I still need to add unit test for
default_compute_objective
to avoid having such metrics in the objective in the future.Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
@sgugger