[misc] change default values of topk/topp#8442
Conversation
Summary of ChangesHello, 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 modifies the default behavior of text generation by setting Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe 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 by creating a comment using either
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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request updates the default values for top_k and top_p parameters used in rollout sampling for RLHF training. The top_k default is changed from 50 to -1 (disabling top-k filtering), and top_p is changed from 0.9 to 1.0 (disabling top-p filtering). Corresponding documentation in both Chinese and English has been updated to reflect these new defaults and their meanings. There is no feedback to provide.
When computing the rollout importance sampling ratio in GRPO, we set vLLM's logprobs_mode to 'processed_logprobs' to get temperature-scaled log probabilities.
However, these logprobs are also affected by top_k and top_p filtering (which sets unselected token probabilities to zero), causing a significant discrepancy between rollout logprobs and training logprobs.