Use native flow prediction for DMD critic loss - #57
Open
zjn20030811 wants to merge 2 commits into
Open
Conversation
Author
|
Follow-up in 1d1c610: the repository has a parallel |
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
Why
WanDiffusionWrapperalready returns both the model's flow prediction and its derived x0 prediction. The fake critic uses the wrapper's default shift of 8, while the generator scheduler in the default DMD configurations uses shift 5. Reconstructing flow from x0 with the generator scheduler therefore selects sigma from a different discretized grid and is not an identity operation.For example, at the valid critic timestep 20 the old round trip scales the native flow prediction by about 1.194. Passing the native prediction directly to
FlowPredLosskeeps it in the parameterization produced by the critic and matches thenoise - xtraining target.This addresses the mismatch discussed in #35.
Tests