Fix calculation of the metric score for hyperopt #1031
Merged
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.
The calculation of the metric score now tries to use the metric at the epoch of best validation performance during training if possible, otherwise uses eval stats instead (for instance when the metric used does is only calculated at eval time rather than at training time) and wars the user about the fact that is saving the model is skipped, then the eval statistics are obtained with the model at the last epoch rather than the model at the epoch of best validation performance.
Fix #1030