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

Clarification on carry variable used during training #123

Open
jren03 opened this issue Apr 29, 2024 · 0 comments
Open

Clarification on carry variable used during training #123

jren03 opened this issue Apr 29, 2024 · 0 comments

Comments

@jren03
Copy link

jren03 commented Apr 29, 2024

Would you mind explaining the purpose of the carry variable used during training? From what I understand, it's a tuple of latent state and latent action.

From this section, it seems like prevlat is replaced with the context from the first sample of each batch. However, why does prevact or carry[1] not replaced in this case? Asked differently, if I were to alternate sampling from two different replay buffers during training, would I need need two different carry variables, or does a shared one suffice since it is getting replaced by context anyway?

Thank you in advance for the help!

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