Change attribute name "f1_score" to "f1 score" due to RubixML change #1022
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.
In version 1.0.0-beta1 of RubixML, the attributes in the Report property changed their style from underscore to spaces (see changelog as well as associated commit). This means that the f1_score were always 0.00 since the bump of RubixML dependency in this commit (
dev-chore/bump-flysystem-v2.1.1is based on RubixML v0.4.2). Can't say if that made the training totally broken or not (@ChristophWurst ?).Example output of a training epoch without change:
Example output of a training epoch with change from this PR:
Closes #1021.