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

act and learn input ranges #7

Open
salamanders opened this issue Oct 21, 2015 · 1 comment
Open

act and learn input ranges #7

salamanders opened this issue Oct 21, 2015 · 1 comment

Comments

@salamanders
Copy link

  1. Should all state inputs to act be 0<=stateX<1?
  2. Should all reward inputs be 0<=reward<1?
  3. Is there any way to get out "nope, that wasn't a good reply. I want a second opinion!" (second place answer, etc)
@gb96
Copy link

gb96 commented Mar 17, 2019

  1. I have been having some success with categorical state inputs. Since my categories are represented as strings I ended up implementing a string hashcode for state inputs since I quickly learned that state inputs needed to be numeric. My string hashcodes are integers in the thousands and they seem to be working with the library, so I think your suggested [0, 1) range for inputs is overly constrained.
  2. I have been providing integer rewards between -100 and 100, and these seem to be working too, however I have been encountering NaN in the net weights after calls to learn(), so maybe I should try a smaller range?

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

2 participants