-
Notifications
You must be signed in to change notification settings - Fork 153
Peft Bridge #1766
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
Peft Bridge #1766
Conversation
Signed-off-by: yaoyu-33 <[email protected]>
Signed-off-by: yaoyu-33 <[email protected]>
Signed-off-by: yaoyu-33 <[email protected]>
Co-authored-by: ℍ𝕠𝕝𝕝𝕠𝕨 𝕄𝕒𝕟 <[email protected]> Signed-off-by: Yu Yao <[email protected]>
|
@HollowMan6 yes, I think I messed up a bit about the name conversion for fused base names. lemme try to fix |
Signed-off-by: yaoyu-33 <[email protected]>
Signed-off-by: yaoyu-33 <[email protected]>
Signed-off-by: yaoyu-33 <[email protected]>
Signed-off-by: yaoyu-33 <[email protected]>
Signed-off-by: yaoyu-33 <[email protected]>
|
@yaoyu-33 I've opened PR #1788 that targets to The convergence situation is good on dense models for RL on verl, with the gray one representing Canonical LoRA with bridge, blue one representing the normal LoRA with bridge, and yellow one representing the LoRA merge.
The convergence tests for MoE (qwen3-30b-a3b):
|
…when EP > 1 (#1817) Signed-off-by: Hollow Man <[email protected]>
# Conflicts: # src/megatron/bridge/models/conversion/model_bridge.py # tests/unit_tests/models/test_model_bridge_lora.py
Signed-off-by: yaoyu-33 <[email protected]>
Co-authored-by: ℍ𝕠𝕝𝕝𝕠𝕨 𝕄𝕒𝕟 <[email protected]> Signed-off-by: Yu Yao <[email protected]>
Signed-off-by: yaoyu-33 <[email protected]>
Signed-off-by: yaoyu-33 <[email protected]>
|
/ok to test 4da571d |
|
The code cov will be improved in follow-up PRs. Patch coverage in this PR is 78% and overall coverage is still 85%. Will go ahead and merge this. |




What does this PR do ?
Add a one line overview of what this PR aims to accomplish.
Changelog
GitHub Actions CI
See the CI sectionin the Contributing doc for how to trigger the CI. A Nvidia developer will need to approve and trigger the CI for external contributors.
Before your PR is "Ready for review"
Pre checks:
If you haven't finished some of the above items you can still open "Draft" PR.
Additional Information