Update moe.sh by Itime-ren · Pull Request #7375 · modelscope/ms-swift
Summary of Changes
Hello @Itime-ren, 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 updates the moe.sh script to optimize the configuration for a Megatron SFT (Supervised Fine-Tuning) job. The changes involve expanding the GPU resources used, redirecting the training dataset to a local file, and adjusting the frequency of evaluation and model saving. Additionally, it introduces integration with Weights & Biases for enhanced experiment tracking.
Highlights
- GPU Resource Allocation: The script now utilizes 4 CUDA devices (0,1,2,3) instead of 2, allowing for potentially faster or larger-scale training.
- Dataset Source Update: The dataset path has been changed from a Swift-specific reference to a local file system path:
/root/autodl-tmp/swift_finetune_data/qwen3_finetune_self_cognition.jsonl. - Training Interval Adjustments: The
eval_intervalandsave_intervalparameters have been significantly reduced from 200 to 5, leading to more frequent evaluation and checkpointing during training. - Wandb Integration: A new argument
--report_to wandbhas been added, enabling integration with Weights & Biases for experiment tracking and reporting.
🧠 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 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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.
| 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 pull request 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. 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
-
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. ↩