Separate Sigma Schedule

[hlky]

What does this PR do?

This is not a finalised design, just a demonstration of how sigma/noise schedule can be moved out of schedulers, comments and feedback are encouraged.

Usage:

fromdiffusersimportHeunDiscreteSchedulerfromdiffusers.schedulers.sigmasimportBetaSigmas, ExponentialSigmas, KarrasSigmassigma_schedule=ExponentialSigmas()
scheduler=HeunDiscreteScheduler.from_pretrained(
"stabilityai/stable-diffusion-xl-base-1.0",
subfolder="scheduler",
sigma_schedule=sigma_schedule,
)

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.

cc @yiyixuxu

[HuggingFaceDocBuilderDev]

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.

[yiyixuxu]

is there any reason, the flow match sigmas are treated differently from beta/exponential/karras? they all generate a sigma schedule, no?

[hlky]

Beta/exponential/karras are more like a conversion of existing sigma schedule, the original functions are actually called _convert_to_*

[hlky]

FlowMatchEuler currently has what we're calling FlowMatchSD3 here by default, and for other models we pass in sigmas, I think the one for SANA is different again, so it seems these will tend to be model specific, compared to everything in BetaSchedule like timestep_spacing == "linspace"interpolation_type == "linear" which is shared and we rarely pass in sigmas, the exception is Align Your Steps schedules which I don't think is used often. We could inline these like timestep_spacing == "linspace" in BetaSchedule but like this the idea is that we can pass a custom class that just needs a call to return the sigmas if we wanted to in addition to the ones that are built-in, new models, custom schedules and experimentation can be supported easier. We could refactor BetaSchedule in a similar way like LinspaceLinear etc and allow the same level of experimentation, it just seems less likely to be used and the experimentation with this kind of scheduler will be done with conversion, there are a few more less popular from the community that we don't support but again the idea is that it can be passed in as a custom class.

[hlky]

I've added some notes, sana's schedule and combined scale_noise (from FlowMatchEuler) with add_noise, they're the same except 1 extra multiplication for FlowMatch and the signature order is different. Trying to cover most things that will need changing so it can be reviewed at the same time. I'll look at some other schedulers like DDIM in case there's anything specific in those.

[hlky]

This will need to be robust and probably kept for a while unless we can find a way to mass update configs on the Hub. It's working with some scheduler configs already, FlowMatch vs Beta is detected with shift and beta_schedule, I've already found an edge case in SANA's config because we integrated those scheduler changes into DPM so it has beta_schedule and no shift (it was called flow_shift instead).

[hlky]

Important to note here that we don't expect all combinations of sampler + noise schedule to work for all models, especially Flow Match models, above is a table of compatibility with Flux from community UIs (Code for sampling is almost 1:1 between forge, comfy etc.)

[hlky]

Some code to demonstrate how schedulers work at this stage in the refactor.

fromdiffusersimportEulerDiscreteScheduler, EulerAncestralDiscreteScheduler, HeunDiscreteSchedulerfromdiffusers.schedulers.schedules.beta_scheduleimportBetaSchedulefromdiffusers.schedulers.schedules.flow_scheduleimportFlowMatchSchedule, FlowMatchSD3, FlowMatchFlux, FlowMatchSANA, FlowMatchHunyuanVideo, FlowMatchLinearQuadraticfromdiffusers.schedulers.sigmas.beta_sigmasimportBetaSigmasfromdiffusers.schedulers.sigmas.exponential_sigmasimportExponentialSigmasfromdiffusers.schedulers.sigmas.karras_sigmasimportKarrasSigmasimportnumpyasnp# mapped from FlowMatchEulerDiscreteScheduler# Euler sampling with Flow Match scheduleeuler=EulerDiscreteScheduler.from_pretrained("black-forest-labs/FLUX.1-dev", subfolder="scheduler")
# Heun sampling with Flow Match scheduleheun=HeunDiscreteScheduler.from_config(euler.config)
# Euler Ancestral actually gives noisy output with Flow Matchancestral=EulerAncestralDiscreteScheduler.from_config(euler.config)
# currently, if this is used in Flux pipeline `base_schedule` is set to `FlowMatchFlux`# SD3 base scheduleeuler._schedule.base_schedule=FlowMatchSD3()
# SANA base scheduleeuler._schedule.base_schedule=FlowMatchSANA()
classFlowMatchCustom:
def__call__(self, num_inference_steps: int, **kwargs) ->np.ndarray:
sigmas=np.linspace(1.0, 1/num_inference_steps, num_inference_steps)
half=num_inference_steps//2sigmas[half:] =sigmas[half:] *1.2returnsigmaseuler._schedule.base_schedule=FlowMatchCustom()
# configs contain `base_schedule` as `str`flow_schedule=FlowMatchSchedule(
shift=13.0,
use_dynamic_shifting=False,
base_schedule="FlowMatchSD3"
)
# we can also use the class directlyflow_schedule=FlowMatchSchedule(
shift=13.0,
use_dynamic_shifting=False,
base_schedule=FlowMatchCustom()
)
# Euler sampling with Beta scheduleeuler=EulerDiscreteScheduler.from_pretrained("stabilityai/stable-diffusion-xl-base-1.0", subfolder="scheduler")
# Euler sampling with Beta schedule and Karras sigmaseuler=EulerDiscreteScheduler(
schedule_config=BetaSchedule(
beta_end=0.012,
beta_schedule="scaled_linear",
beta_start=0.00085,
timestep_spacing="leading",
),
sigma_schedule_config=KarrasSigmas(),
)
# Euler sampling with Beta schedule and Beta sigmaseuler._sigma_schedule=BetaSigmas()
# Euler sampling with Beta schedule and Exponential sigmaseuler._sigma_schedule=ExponentialSigmas()

Tests with black-forest-labs/FLUX.1-dev

Euler

Base	Beta	Exponential	Karras

Euler Ancestral

Base	Beta	Exponential	Karras

Heun

Beta	Exponential

Note: Base Heun and with Karras were tested, just lost the files from when I ran the test.

[hlky]

Hi @ukaprch. Thanks for your interest in Flow Match scheduling support. We know this is highly anticipated and we appreciate your patience while we work on it 🤗

[yiyixuxu]

I think the idea is to separate sigma class out from the schedulerclass, it will be separate part of pipeline (i.e. you can change scheduler without change sigma, e.g. we change it at run time etc) - is it possible?

the current scheduler already accept sigmas but it is still depends on the scheduler config to convert to k-sigmas etc

this API here it is still part of the scheduler, just make it more configurable I think

sigma_schedule = ExponentialSigmas()
scheduler = HeunDiscreteScheduler.from_pretrained(
"stabilityai/stable-diffusion-xl-base-1.0",
subfolder="scheduler",
sigma_schedule=sigma_schedule,
)

the ideal design should not require much change to current scheduler class IMO

[hlky]

That is what I was looking at initially, while you've been working on Modular I've added a further experimental design.

We can make sigma as in Beta, Exponential, Karras a separate part of the pipeline, it has to passed into the scheduler though as these conversions run before concatenate final (zero, min).

diffusers/src/diffusers/schedulers/sigmas/beta_sigmas.py

Line 27 in 3b47229

classBetaSigmas:

diffusers/src/diffusers/schedulers/sigmas/exponential_sigmas.py

Line 22 in 3b47229

classExponentialSigmas:

These can be used if we add a ConfigMixin etc.

Afaik some scheduler configs do specify use_karras_sigmas=True so will need to find a way to set e.g. KarrasSigmas on pipeline.

We could also do the same for Flow Match base schedules, add a ConfigMixin etc., the class computes sigmas that are passed into scheduler instead of just code in the pipelines like now.

diffusers/src/diffusers/schedulers/schedules/flow_schedule.py

Lines 44 to 46 in 3b47229

	classFlowMatchFlux:
	def__call__(self, num_inference_steps: int, **kwargs) ->np.ndarray:
	returnnp.linspace(1.0, 1/num_inference_steps, num_inference_steps)

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread.

Please note that issues that do not follow the contributing guidelines are likely to be ignored.