Add Muon court training recipe - #159
Draft
abcamiletto wants to merge 1 commit into
Draft
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changed
MuonAdamWoptimizer that applies Muon to hidden matrix parameters and AdamW to embeddings, prediction heads, and non-matrix parametersWhy
The court detector tuning showed that the hybrid optimizer and shorter 768px schedule were the best simple training recipe. The previous Torchvision transform hooks were private APIs and no longer run under the Torch version required for native Muon.
Impact
Existing AdamW configurations continue to work. The new court recipe selects
MuonAdamW; optimizer checkpoints preserve both native optimizer states and can be resumed normally.Validation
engineandtrain.pyConvertPILImage,ConvertBoxes, and dynamic image/box padding on Torchvision 0.28