Fix tests for equivalence of DDIM and DDPM pipelines #1069
Merged
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.
Closes #553
DDIM and DDPM pipelines are equivalent only if
DDIMscheduler is called withuse_clipped_model_output=True. Currently it's not possible to pass this argument from the pipeline, and sotest_ddpm_ddim_equality_batchedwas failing. The unbatched versiontest_ddpm_ddim_equalitywas also failing if one changed the random seed (e.g. to 4), as described in the issue.This PR:
use_clipped_model_outputfrom DDIM pipeline to the scheduleruse_clipped_model_output=Trueintest_ddpm_ddim_equality_batchedandtest_ddpm_ddim_equalityAs a result, both tests are passing (each runs for 2 values of the seed)
