-
Notifications
You must be signed in to change notification settings - Fork 668
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
fix(autoware_freespace_planner, autoware_freespace_planning_algorithms): modify freespace planner to use node clock instead of system clock #9152
Conversation
…ng_algorithms packages to use the node clock instead of rclcpp detached clock. This allows the module to make use of sim time. Previously during simulation the parking trajectory would have system time in trajectory header messages causing downstream issues like non-clearance of trajectory buffers in motion planning based on elapsed time.
Thank you for contributing to the Autoware project! 🚧 If your pull request is in progress, switch it to draft mode. Please ensure:
|
…venbrills/autoware.universe into fix/freespace_planner_use_node_clock
planning/autoware_freespace_planner/include/autoware/freespace_planner/utils.hpp
Show resolved
Hide resolved
planning/autoware_freespace_planner/include/autoware/freespace_planner/utils.hpp
Show resolved
Hide resolved
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #9152 +/- ##
==========================================
- Coverage 30.09% 30.07% -0.02%
==========================================
Files 1340 1346 +6
Lines 103652 103720 +68
Branches 40362 40371 +9
==========================================
+ Hits 31190 31195 +5
- Misses 69450 69513 +63
Partials 3012 3012
*This pull request uses carry forward flags. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Hi @mkquda, is there anything else to be re-evaluated? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
There are other parts of autoware that use |
@kosuke55 Only if they are being used to populate headers or are directly/indirectly being used by consuming nodes as a reference of when the message was created in the context of the run either in real system time or simulated time. There are places where a detached clock is used for measuring algorithm processing time which does not need to change. |
@mkquda I forgot to add signoffs to the commit messages, and I am unable to rebase and add the signoffs directly to the pull request due to insufficient permissions. Is there a workaround? |
@maxime-clem @mkquda |
Description
Modified the autoware_freespace_planner and autoware_freespace_planning_algorithms packages to use the node clock instead of rclcpp detached clock. This allows the module to make use of sim time. Previously during simulation the parking trajectory would have system time in trajectory header messages causing downstream issues like non-clearance of trajectory buffers in motion planning based on elapsed time.
How was this PR tested?
Tested in sim.
Effects on system behavior
In the previous version, the use of system time in the free-space planner trajectory header causes the trajectory buffer downstream from clearing and therefore causing the is_steering_converged flag to never reset when simulating causing the system to not change from Parking back to Lane Driving. Now, when use_sim_time is used, the parking trajectory also reflects the correct time and the buffer can be cleared appropriately.