I found that the velocity retrieved by get_get_ego_state_at_iteration(step).agent.velocity has a wrong direction, which has approximately +90 degree offset based on state.center.heading. I understand that the velocity direction may have a slight difference from the heading direction, but 90 degree looks like an impossible value.
Setup
on my personal laptop with Ubunu 20.0 with 32g memory.
Steps To Reproduce
Setup:
DATASET_PARAMS=[
'scenario_builder=nuplan_mini', # use nuplan mini database (2.5h of 8 autolabeled logs in Las Vegas)
'scenario_filter=one_continuous_log', # simulate only one log
"scenario_filter.log_names=['2021.07.16.20.45.29_veh-35_01095_01486']",
'scenario_filter.limit_total_scenarios=2', # use 2 total scenarios
],
Describe the bug
Hi,
I found that the velocity retrieved by
get_get_ego_state_at_iteration(step).agent.velocity
has a wrong direction, which has approximately+90 degree
offset based onstate.center.heading
. I understand that the velocity direction may have a slight difference from theheading
direction, but90
degree looks like an impossible value.Setup
on my personal laptop with Ubunu 20.0 with 32g memory.
Steps To Reproduce
Setup:
Reproduce
First,
python run_simulation +simulation=closed_loop_nonreactive_agents scenario_filter.limit_total_scenarios=1 planner=simple_planner worker=sequential
.Second, set a breakpoint at
simulations_runner.py line 134
.then get the velocity and heading and the diff
then you will see the diff is about 1.57, which is
pi/2
, while applying the same calculation to detected objects, the diff is about0
.Stack Trace
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.