Open AmericanPresidentJimmyCarter opened 7 months ago
Should the default functionality be a single function or a list of smaller functions do you think?
If it was a list such as [f_a, f_b, f_c]
you could easily hook into any stage by simply funcs.insert(f_a1, 1)
or funcs[1] = f_b_custom
, but that makes the MVP more complex.
You could always decompose the default function to have multiple other functions that are called inside it, which the user can also import and use in their functions if needed.
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.
Model/Pipeline/Scheduler description
Related to #7761 .
This is an effective replacement for the existing sampling loop function and the many, many kwargs that were made to allow the user to control it or inject callbacks into it.
This will give the end user complete control of the sampling loop, allow the repo to add "official inline sampling functions" like report an image to an endpoint so that the user can view intermediate steps, etc.
We can add an argument sampling_functions:
list[Callable]=[default_sampling_function]
into the__call__
as a new, backwards compatible kwarg.This requires a rewrite of all of the pipelines, but as it is a backwards compatible change it can be introduced to any of the more popular pipelines first.