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.
[Schedulers Refactoring] Phase 1: timesteps and scaling #637
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Schedulers Refactoring] Phase 1: timesteps and scaling #637
Changes from all commits
c63e6e8
556e687
ccc6afb
ba351f5
f4e717e
f58846d
1d7a9fc
0d0395b
90b1aaa
606df49
9cfd2dc
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's confusing to me that
get_noise_condition( )
return atime
integer. Also why is this needed for DDIM?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do schedulers expect the
latents
in the final device or in CPU? As per this PR it looks likeLMSDiscreteScheduler
prepares sigmas in the CPU.We could either:
sigmas
etc. if necessary.scheduler.to()
as @anton-l suggested in that PR.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is a bit unrelated to the PR - let's try to put this in a different PR next time ;-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fine with this function! Think it would also be fine to add an
if-statement
here (to only do it if the scheduler is continous)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this works correctly at the moment because the sigmas are changed when doing
self.scheduler.set_timesteps
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here I'm lost -> this function is not intuitive to me.
t
!=noise_condition
for me. Not happy if we need to force schedulers to have this function