-
Notifications
You must be signed in to change notification settings - Fork 21
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
The details of model #10
Comments
Hi, This is just a convention. You may simply flip the figure and call the training direction "inverse" and the sampling direction "forward" and nothing would change, that is, the internal operation in the layers would not change. Hope this helps! |
The training process is to sample the noise distribution (the latent space like z in Glow) to the noisy image (the data space like x in Glow). The goal of this work is to get the noise distribution at last (which is the inference in Glow). Therefore, the inverse direction is used as training here which is different from Glow which use the data space to approximate latent space as training. |
What's more, is there the pytorch implementation of Noise Flow? |
Just to clarify, in the noise flow paper, Figure 3, and in the code:
|
Not currently; I hope we can do it in the future. |
In the Glow, data space distribution --> normal distribution which is the training in your comment uses the forward calculation however use the inverse calculation in Noise Flow code (such as _inverse_and_log_det_jacobian function of all layers). |
The training's input is the clean image and noise. The training is along the forward direction , "Sdn->A4->Gain->A4", as the figure 3 in paper while all layers use the inverse calculation (train_multithread function in code).
The sampling's input is the clean image with Gauss. The sampling is along the inverse direction (reversed model) while all the layers use the forward calculation (sample_multithread function in code).
I wonder if my understanding above is correct.
Why does the model operate in the forward direction while using the inverse calculation ?
The text was updated successfully, but these errors were encountered: