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
Currently, we are working on a task for fixing and improving Autoware logging system as Autoware creates a noisy debugging environment, making it challenging to identify and address genuine issues.
For more details about the issue, plan how to tackle it, and linked PR, please have a look here.
For this bug, when using planning simulator for a parking scenario, Autoware throws some error messages relevant to motion_velocity_smoother:
[planning.scenario_planning.motion_velocity_smoother]: input trajectory size must > 1. Skip computation. (checkData() at ~/autoware/src/universe/autoware.universe/planning/motion_velocity_smoother/src/motion_velocity_smoother_node.cpp:427)
Checklist
Description
Fixes #5539
Currently, we are working on a task for fixing and improving Autoware logging system as Autoware creates a noisy debugging environment, making it challenging to identify and address genuine issues.
For more details about the issue, plan how to tackle it, and linked PR, please have a look here.
For this bug, when using planning simulator for a parking scenario, Autoware throws some error messages relevant to
motion_velocity_smoother
:[planning.scenario_planning.motion_velocity_smoother]: input trajectory size must > 1. Skip computation. (checkData() at ~/autoware/src/universe/autoware.universe/planning/motion_velocity_smoother/src/motion_velocity_smoother_node.cpp:427)
This video demonstrates the issue.
Expected behavior
Autoware
motion_velocity_smoother
should not having error message while parkingActual behavior
Autoware
motion_velocity_smoother
has error message while parkingSteps to reproduce
motion_velocity_smoother
You may use the PRs mentioned here for having more comfortable logging messages, if you want.
Versions
No response
Possible causes
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: