Metric names in additional info are confusing
Open
not urgent
refactoring
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 300
- PR merge metrics
- No merged PRs in 30d
Description
* **I'm submitting a ...**
- [ ] bug report
- [ ] feature request
- [x] support request => Please do not submit support request here, see note at the top of this template.
# Issue Description
* When Issue Happens
The `additional_info` in the BaseTask has `xxx_loss` key and it has various metrics.
However, when the metric property is `greater is better`, then the metric is actually transformed.
For example, `accuracy` is not `accuracy`, but is handled as `error rate`.
The naming rule should be re-considered in the future.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.