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
Why do you add this uniform noise to the inputs? #43
Comments
This is a trick used to convert discrete values of color (e.g., 0..255) to continuous values. |
Hi, I'm having a related question here except it has to do with the line below. Line 172 in 654ddd0
Why do we add the total number of bits/nats needed to encode an image before all the invertible transformations? Thanks in advance! |
Ok, so by looking at the real NVP code, I think I figured this out. This is to account for division by 256, which is also an invertible transformation and has that term above as its logdet of Jacobian. |
@lxuechen I have another explanation. Without adding P.S. This paper https://arxiv.org/abs/1511.01844 (Section 3.1) confirms my explanation. |
glow/model.py
Line 171 in 654ddd0
I find that
https://github.com/taesung89/real-nvp/blob/5ec7a22bbae529e44d60bd6664a7753ae6772dfa/real_nvp/model.py#L42-L47
refers to corrupting data. However, I did not find this step in the GLOW paper.
Is it necessary to add this noise? Will it have any impact on the result? Thanks vary much!
The text was updated successfully, but these errors were encountered: