-
Notifications
You must be signed in to change notification settings - Fork 56
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
Regarding when skip is computed #1
Comments
I started out trying to explain you the reason, but in the middle of it I realized you were right. Following my explanation. According to the paper "For all datasets we add skip connections from the encoder at the last groundtruth frame to the decoder at t, enabling the model to easily generate static background features." So If h, skip = encoder(x[i-1]) # encoder(x[opt.n_past - 1]) We can easily see that happens when |
Hi @wpeebles I read through the code and I agree with you, as well as with @lpcinelli . Of course, the way that the code is set up is unlikely to have too much of an impact. It just means if Lines 308 to 320 in 3f19f0b
Note that setting Based on this discussion, seems like this should also have a Lines 257 to 269 in 3f19f0b
as well as other places that rely on this general pattern. |
In line 311 of
train_svg_lp.py
, what is the reasoning behind setting the condition as:instead of (the only change is the second
<
is swapped to<=
):Since
h = encoder(x[i-1])
, I believe the strict<
will cause theskip
features to be from thet = n_past - 1
frame instead of thet = n_past
frame (wheret
is indexed from 1). Is this intended?The text was updated successfully, but these errors were encountered: