Skip to content

Add sigmas to pipelines using FlowMatch - #10116

Merged
yiyixuxu merged 1 commit into
huggingface:mainfrom
hlky:flow-pipeline-sigmas
Dec 4, 2024
Merged

Add sigmas to pipelines using FlowMatch#10116
yiyixuxu merged 1 commit into
huggingface:mainfrom
hlky:flow-pipeline-sigmas

Conversation

@hlky

@hlky hlky commented Dec 4, 2024

Copy link
Copy Markdown
Contributor

What does this PR do?

Part of the fixes for #10113.

Pipelines in this PR all use FlowMatch scheduler which does not currently support passing timesteps so the timesteps argument is non-functional, we replace timesteps argument with sigmas which is currently supported by the scheduler. See #10080 #10112 for example use case of passing sigmas.

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.

@hlky
hlky requested review from DN6 and sayakpaul December 4, 2024 13:29
@HuggingFaceDocBuilderDev

Copy link
Copy Markdown

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@sayakpaul sayakpaul left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! My only comment is that this could be a breaking change and we might want to consider a deprecation. Or maybe that's a stretch.

prompt: Union[str, List[str]] = None,
negative_prompt: Union[str, List[str]] = None,
num_inference_steps: int = 50,
timesteps: List[int] = None,

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Even though these are non-functional but isn't this a breaking change? If so, maybe we should deprecate (with a short cycle, for sure)?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In #10116 for Flux pipelines we replaced timesteps with sigmas but it's a good point. Let's bring in @yiyixuxu for a second opinion.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it doesn't because the flow match scheduler does not accept timesteps

thanks for the fix @hlky!

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That makes sense.

@yiyixuxu yiyixuxu left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks!

@yiyixuxu
yiyixuxu merged commit a2d424e into huggingface:main Dec 4, 2024
sayakpaul pushed a commit that referenced this pull request Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants