fix: ensure custom timesteps are consistent with sigmas in FlowMatchEulerDiscreteScheduler#14036
Open
KartavyaDikshit wants to merge 2 commits into
Open
fix: ensure custom timesteps are consistent with sigmas in FlowMatchEulerDiscreteScheduler#14036KartavyaDikshit wants to merge 2 commits into
KartavyaDikshit wants to merge 2 commits into
Conversation
added 2 commits
June 22, 2026 11:05
…ulerDiscreteScheduler Signed-off-by: KartavyaDikshit <kartavyaniraj.dikshit2021@vitstudent.ac.in>
…ulerDiscreteScheduler Signed-off-by: KartavyaDikshit <kartavyaniraj.dikshit2021@vitstudent.ac.in>
|
I already committed a pr there: #14011 |
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
2 participants
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.
Resolves #14013
When custom timesteps were provided to set_timesteps with shift != 1, the timesteps array would diverge from the sigmas array after internal computation. This fix ensures custom timesteps are processed consistently with the shift factor, matching the behavior of auto-generated timesteps.
Signed-off-by: KartavyaDikshit kartavyaniraj.dikshit2021@vitstudent.ac.in