-
Notifications
You must be signed in to change notification settings - Fork 12
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
Question about the command #9
Comments
Hey! Yes, new command velocities are sampled with probability 0.002 every step, i.e. on average every 10 seconds. You are correct, the minus in front of the sum is wrong. Thank you for noticing it! |
Thank you very much! If my understanding is correct, will the new command velocities change (but at most once) during one episode? And will the command counter (10 sec, as you mentioned) reset when an episode is terminated or truncated? |
There is no counter for the command velocity change. At every step a boolean for changing the command velocity is sampled, like (pseudo code): This means potentially the command velocity could even change 1000 times per episode, i.e. in every step. But with the probability of 0.002 it happens on average every 500 steps, so on average every 10 seconds. This still means it can happen more or less often and as I said there is no counter so it's also not affected by episode resets. |
Congratulations on this excellent work!
Are the command "c_x", "c_y" and "c_yaw" randomly sampled in each episode? Do they change in each episode? And is there a "max truncation timestep" (e.g. 1000) in your settings?
Besides, is there a typo in Table 2. (T13) in the Appendix? There seems to be an extra negative sign here.
Thank you very much.
The text was updated successfully, but these errors were encountered: