Repository navigation
Add conditional frame control to Cosmos2 Video2World - #14908
Open
BeyondBirthday07 wants to merge 1 commit into
Open
BeyondBirthday07 wants to merge 1 commit into
BeyondBirthday07 wants to merge 1 commit into
Conversation
This branch has not been deployed
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 does this PR do?
Fixes #14892
Cosmos2VideoToWorldPipelinecurrently uses the whole input video as conditioning. If a full-length video is passed, all latent frames can become conditioning frames and the pipeline ends up reconstructing the input instead of continuing it.This adds
num_latent_conditional_framesto control how much of the input video is used for conditioning.1(default): use the last 1 input frame2: use the last 5 input framesThis follows the conditioning behavior used by the Cosmos Predict2 reference implementation and the Cosmos 2.5 pipeline.
Added tests for both conditioning modes and for invalid values.
No new dependencies.
Tests
Result: 20 passed, 19 skipped
Before submitting
self-reviewskill on the diff?documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@a-r-r-o-w, @DN6