huggingface / huggingface/diffusers

Formulation of reverse diffusion process in DDPM ( 1 - alpha_prod_t = beta_prod_t assumption)

Abierto
#9,474 5 comentarios 0 reacciones 0 asignados Ver en GitHub
bug stale
Lenguaje dominante
Python
Estrellas
34.5k
Forks
7.3k
Merge medio
3 d 3 h
PR fusionados (30 d)
91

Descripción

### Describe the bug

I looked into sampling code of DDPM, and I believe there's a mistake:
#### I believe the code makes assumption that 1 - alpha_prod_t = beta_prod_t, which simply isn't true.

Original sampling algorithm:
[original paper](https://arxiv.org/pdf/2006.11239)
![image](https://github.com/user-attachments/assets/ce07bbb7-5a9d-44e6-9f0e-18bf42963317)

x_0 prediction from sample and predicted noise :

Eqn 15 from paper, as referenced in code snippet as well:
![Screenshot 2024-09-19 at 6 26 48 PM](https://github.com/user-attachments/assets/3ce27e0b-515b-4cd3-b722-454594139f83)

code implementation in diffusers:
https://github.com/huggingface/diffusers/blob/1e8cf2763d37fa66cfba2fb87acfe3443068ce43/src/diffusers/schedulers/scheduling_ddpm.py#L446-L449

### Here, it clearly seems like the 1 - alpha_prod_t = beta_prod_t is being used.

investigated from post by @AlejandroBaron in https://github.com/huggingface/diffusers/discussions/9431_

### Reproduction

I haven't tested out code, but this seems fundamental formulation issue.

### Logs

_No response_

### System Info

0.30.3

### Who can help?

@sayakpaul @DN6 @yiy

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Start in src/diffusers/schedulers/scheduling_ddpm.py at lines 446-449, then compare the implementation with Eq. 15 of the linked DDPM paper and the referenced discussion. Verify whether the reported relationship between alpha_prod_t and beta_prod_t is actually assumed, and establish the correct behavior with a reproducible check before proposing a fix.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
python
Área
machine-learning
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.