NVIDIA-NeMo / NVIDIA-NeMo/RL

report rl and optimization step differently

Open
#1,435 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Python
Stars
2k
Forks
561
Avg merge
4d 5h
Merged PRs (30d)
145

Description

when we have off-policy steps in PPO the metric gets averaged across the different steps. This can be very hard to reason about, we should report each optimization step as train/optim_step and every rl step as train/rl_step to avoid this confusion.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.