-
Notifications
You must be signed in to change notification settings - Fork 994
[megatron] fix train_iters #6611
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
Summary of ChangesHello @Jintao-Huang, 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 targeted fix to the Megatron training setup by adjusting how the Highlights
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. 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
|
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 aims to correct the calculation of train_iters by ensuring num_generations is only applied for GRPO training. However, the current change introduces a critical issue where non-RLHF training runs (like SFT) will crash with an AttributeError because the rlhf_type attribute is not always present on the arguments object. I have provided a suggestion to fix this by safely accessing the attribute.
| data_parallel_size = mpu.get_data_parallel_world_size() | ||
| step_batch_size = args.micro_batch_size * data_parallel_size | ||
| num_generations = args.num_generations if hasattr(args, 'num_generations') else 1 | ||
| num_generations = args.num_generations if args.rlhf_type == 'grpo' else 1 |
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.
The direct access to args.rlhf_type will cause an AttributeError for training configurations that do not define this attribute, such as SFT. This will lead to a crash in non-RLHF training scenarios.
To prevent this, you should use getattr to safely access the rlhf_type attribute with a default value.
| num_generations = args.num_generations if args.rlhf_type == 'grpo' else 1 | |
| num_generations = args.num_generations if getattr(args, 'rlhf_type', None) == 'grpo' else 1 |
No description provided.