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

Memory overwrite #13

Closed
RDTm opened this issue Sep 10, 2014 · 1 comment
Closed

Memory overwrite #13

RDTm opened this issue Sep 10, 2014 · 1 comment

Comments

@RDTm
Copy link
Collaborator

RDTm commented Sep 10, 2014

The memory is of a fixed length, so when we reach 100000 transistions in memory, we need to start overwriting the first transitions. This is not implemented so far.

Attention should be put to figuring out how to deal with extracting transistions from minibatch once part of the transitions have been overwritten. For example: If we have overwritten transistions till position 10 in memory and minibatch asks for transition nr 11, then the 3 previous "images" in the memory do not correspond to what actually happened before the transition 11. SO we either
1)give a repetition of the 11th image instead of img 10, img9 and img8... as we do in the case when we are asked transistions in the beginng of new game. Downside of it is that actually such transition (same image for 4 frames and then an action) never takes place.
or
2) we forbid the minibatch to ask transitions at that location. Considering we have another 1M of transitions to choose from, frobidding to select 3 of them, seems like no problem.

@RDTm RDTm modified the milestone: Whole system coded Sep 10, 2014
@RDTm
Copy link
Collaborator Author

RDTm commented Oct 21, 2014

seems we ficed it for now

@RDTm RDTm closed this as completed Oct 21, 2014
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