-
Notifications
You must be signed in to change notification settings - Fork 2k
adapt to minimax_m2 #5624
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
Merged
Merged
adapt to minimax_m2 #5624
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
This line appears to have an off-by-one error in the slice index. By slicing up to
exp_idx + 1, the expert index is stripped from the prefix. For example,...experts.1.w1becomes...experts. The downstream logic then incorrectly assumes expert 0 due to the hardcodedpacked_modules_model_mapping.This will cause incorrect quantization behavior for any expert with an index other than 0. This is a critical bug for models with multiple experts.
A more robust solution is to slice up to
exp_idx + 2to preserve the expert index in the prefix (e.g.,...experts.1). This would mean the quantization configuration should be defined per-expert (e.g.,...experts.1.weight), which is a cleaner design. This change would also make theexpertsentry inpacked_modules_model_mappingforminimax_m2unnecessary.