-
Notifications
You must be signed in to change notification settings - Fork 47
Add Step-wise GRPO Advantage #153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @pan-x-c, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request introduces a novel approach to advantage calculation and propagation within the trinity framework. It provides a new strategy that derives a single advantage score from the final step of a trajectory and then broadcasts this score across all steps of that trajectory, aiming to improve how reward signals are utilized for policy updates, particularly in grouped reinforcement learning settings.
Highlights
- New Advantage Strategy: I've introduced a new
StepWiseGRPOStrategyclass, which is a specializedAddStrategydesigned to calculate and apply advantages in a step-wise manner, inspired by the rLLM framework. - Group Advantage Calculation: The strategy includes a
calculate_group_advantagemethod that computes a normalized score for each run based on the reward of its last experience relative to the group's mean and standard deviation. This score represents the overall advantage for that run. - Advantage Broadcasting: A
broadcast_advantagesmethod is implemented to take the single group advantage score calculated for a run and apply it to all experiences within that run's trajectory. It also includes an optionalenable_step_normfeature to normalize advantages by the trajectory length. - Registry Integration: The new
StepWiseGRPOStrategyis registered under the name 'step_wise_grpo' within theADD_STRATEGYregistry, making it discoverable and configurable for use in the system.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces a new StepWiseGRPOStrategy for calculating advantages by broadcasting scores from the last step to all previous steps. The implementation is a good starting point, but I've found a few issues that need attention. There's a critical issue with potential None rewards that could cause a crash, a type mismatch when storing scores, and some leftover debugging print statements. I've also suggested minor improvements to code clarity. Addressing these points will make the new strategy more robust and maintainable.
|
/unittest-module-algorithm |
Summary
Tests
Github Test Reporter by CTRF 💚 |
|
/unittest-module-explorer |
|
/unittest-module-explorer |
Summary
Tests
Github Test Reporter by CTRF 💚 |
Description
As the title says
Checklist
Please check the following items before code is ready to be reviewed.