Reproducing NCSN++ cont. (deep, VE) about score_sde_pytorch HOT 4 OPEN

Thanks for reporting. I remembered testing it before releasing this code repo and got FID 2.20. Could you try the non-deep version and see if you can obtain an FID similar to the one reported in paper? The seed in config files is probably not used anywhere—it's from the JAX repo.

from score_sde_pytorch.

I'm currently running other experiments and will try the non-deep version in 1~2 weeks. Also, I ran sampling with the checkpoint provided in this repo and it has FID 2.20, so I'm thinking the seed might caused the difference in training process.

from score_sde_pytorch.

Hi @yang-song,

I've tried the non-deep version (configs/ve/cifar10_ncsnpp_continuous.py) and the result is

I0620 20:25:37.822132 140001873700672 run_lib.py:402] ckpt-24 --- inception_score: 9.829116e+00, FID: 2.684183e+00, KID: 6.818869e-04

I trained for the same amount of steps and used the same batch size, but its a bit worse than the result from the paper.

from score_sde_pytorch.

Thanks for reporting. I will need some time to run those programs and compare the implementation with our internal code at Google. In the meanwhile, one potential reason is different random seeds causing the optimal checkpoint number (the one that minimizes the FID score) to be different.

from score_sde_pytorch.