Skip to content
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

Have you tried to not delayed stacking input (Use delayed stacking for generation, but not on input) #149

Open
zmy1116 opened this issue Aug 4, 2024 · 0 comments

Comments

@zmy1116
Copy link

zmy1116 commented Aug 4, 2024

Hello,

I've gone through the paper and the code. I have question regarding delayed stacking input.

Let's use Y_{c, t} represent the c^th code book for time step t.

I understand that when we delayed stacking generation, we maintain the property that Y_{i,t} is generated after Y_{j,t} for all j>i, while not doing C x T generations (C is num of code books and T is the time steps).

I just don't see the intuition to delay stack the input, adding different residual part of different timestep
[ Y_{1,(t-3)}, Y_{2,{t-2}} Y_{3(t-1)} Y_(4t) ] for input doesn't make too much sense for me.

Is it mainly for ease of implementation? because I understand if the input at each step is sum of all codes at that timestep, since at generation phase, the output of different timestep will be summed and fed back to the transformer as input, we may need to do extra work to differentiate the sum of all codes at the same timestep versus sum of residuals at different timestep.

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant