You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the index_for_timestep() method, there's a precision issue when comparing floating-point timesteps with integer schedule_timesteps. The comparison schedule_timesteps == timestep can fail to find matching indices due to floating-point truncation, causing some timestep indices to be missed.
Location: scheduling_flow_match_euler_discrete.py, line 303:
File "/anaconda3/envs/rdt/lib/python3.10/site-packages/diffusers/schedulers/scheduling_flow_match_euler_discrete.py", line 175, in scale_noise
step_indices = [self.index_for_timestep(t, schedule_timesteps) fortin timestep]
File "/anaconda3/envs/rdt/lib/python3.10/site-packages/diffusers/schedulers/scheduling_flow_match_euler_discrete.py", line 175, in<listcomp>
step_indices = [self.index_for_timestep(t, schedule_timesteps) fortin timestep]
File "/anaconda3/envs/rdt/lib/python3.10/site-packages/diffusers/schedulers/scheduling_flow_match_euler_discrete.py", line 292, in index_for_timestep
returnindices[pos].item()
IndexError: index 0 is out of bounds for dimension 0 with size 0
Liang-ZX
changed the title
Bug of comparing floating-point timesteps with integer schedule_timesteps in scheduling_flow_match_euler_discrete.py
Bug of some timestep indices cannot be found in index_for_timestep() of scheduling_flow_match_euler_discrete.py
Jan 15, 2025
Describe the bug
Description
In the
index_for_timestep()
method, there's a precision issue when comparing floating-point timesteps with integer schedule_timesteps. The comparisonschedule_timesteps == timestep
can fail to find matching indices due to floating-point truncation, causing some timestep indices to be missed.Location:
scheduling_flow_match_euler_discrete.py
, line 303:Reproduction
Logs
System Info
diffusers version: 0.32.1
Python version: 3.10
OS: Linux / Ubuntu 22
Who can help?
@yiyixuxu
The text was updated successfully, but these errors were encountered: