You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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: