-
-
Notifications
You must be signed in to change notification settings - Fork 41
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 state format #36
Comments
Hi, we follow previous works to include both command info and target point as input. We do not have such ablations, but I agree that the vehicle mostly relies on the target point. You can try yourself to see whether removing the command affects the performance. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi~ author, I wanna ask if measurement state is well designed for the best metric?
For example, is command info (like "turn left") is a must? can I just use a target point (x,y) and ego speed V as ego measurement state input? because I think the target point position already contains the command info( 'turn' or 'go straight' ).
The text was updated successfully, but these errors were encountered: