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

frames per state on each step #25

Closed
fferreres opened this issue Nov 9, 2016 · 0 comments
Closed

frames per state on each step #25

fferreres opened this issue Nov 9, 2016 · 0 comments

Comments

@fferreres
Copy link

fferreres commented Nov 9, 2016

Update - I just reviewed estimators.py and saw it uses the 4 frames already.


Denny, I was reading the paper, and not sure if they are feeding the past 4 frames as the "current" state in A3C. I thought they were following the protocols of previous papers, which might mean they feed the past 4 frames. I've also seen some other implementations using 4 frames (current + past 3) as current state.

My question is if your A3C you created allows or include past frames be passed as part of the current state. Karpathy also tried more creative things, like passing the difference of frames (which I liked, since you don't need to feed 2x or n times the features, but it nulls anything that didn't change).

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