[recipe, doc] feat: add MiniMax H3 FlowGRPO V1 sync recipes - #501
Draft
NancyFyong wants to merge 3 commits into
Draft
[recipe, doc] feat: add MiniMax H3 FlowGRPO V1 sync recipes#501NancyFyong wants to merge 3 commits into
NancyFyong wants to merge 3 commits into
Conversation
Provide T2VA and FL2VA V1 sync launchers so MiniMax H3 can use TransferQueue and ReplayBuffer without changing its established FlowGRPO model, reward, pipeline, or CPS SDE settings. AI assistance (pi coding agent) was used for this change. Co-authored-by: pi coding agent Signed-off-by: NancyFyong <2742092809@qq.com>
knlnguyen1802
left a comment
Collaborator
There was a problem hiding this comment.
For all v1 recipes, we need to verify the reward curve again
NancyFyong
marked this pull request as draft
August 31, 2026 13:04
Collaborator
Author
I will switch to "open" after the reward phase. Thankyou |
7 tasks
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.
Summary
Add production MiniMax H3 FlowGRPO V1 sync launch recipes for both
supported GPU paths:
run_minimax_h3_t2va_lora_v1.sh; andrun_minimax_h3_fl2va_lora_v1.sh.They are mechanical counterparts of the existing V0 recipes. Each preserves
all model, LoRA, reward, pipeline, and CPS FlowGRPO settings, and changes only:
The MiniMax H3 README documents both launchers and explains that V1 sync uses
TransferQueue and ReplayBuffer.
separate_asyncis intentionally out of scope:it needs dedicated actor/rollout resource pools plus checkpoint-engine
synchronization, so it is not a mechanical entrypoint switch.
Why this is not duplicate work
The relevant V1 tracking issue is #389. Duplicate-work checks found V1 work for
Qwen-Image (#489) and OPD (#493 and #495), but no open PR or launcher for
MiniMax H3 FlowGRPO V1, T2VA, or FL2VA. In particular, no existing branch adds
run_minimax_h3_t2va_lora_v1.shorrun_minimax_h3_fl2va_lora_v1.sh.This PR adds recipes only. It does not modify MiniMax H3 adapters, FlowGRPO
losses, the V1 trainer, or GPU smoke registration.
Tests
Passed:
A mechanical comparison also confirmed that each V1 launcher retains every V0
runtime setting after normalizing the approved entrypoint, V1 flags, and
experiment-name changes.
No GPU training run was performed: this PR is intentionally limited to
production recipes and does not add a GPU smoke. The existing TinyRandom
T2VA+FL2VA FlowGRPO E2E coverage is tracked separately in #447.
Reward Results
AI assistance and review
AI assistance (pi coding agent) was used for this change. The human submitter
has reviewed every changed line and is responsible for this contribution.