Handle summary metric semantics more consistently
Open
enhancement
- Dominant language
- Python
- Stars
- 2k
- Forks
- 561
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 145
Description
Currently there are a few places where we handle min/max/averaging of metrics throughout the repo that depend on the name:
* example PR showing one place: https://github.com/NVIDIA-NeMo/RL/pull/1818/changes
* code diff of a bug found
it might be okay to rely on the string name provided the metric naming are consistent throughout
Contributor guide
Assessment
This issue has not been assessed yet.