-
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
Difficulty of estimating velocity at future time t #383
Comments
This pull request has been automatically marked as stale because it has not had recent activity. |
This pull request has been automatically marked as stale because it has not had recent activity. |
@taikitanaka3 Now we calculate the vehicle velocity with motion_velocity_smoother as a library in behavior_velocity_planner. Did this solve this issue? |
no, but there is no approach with current architecture so i will close this issue. |
…velop sync main for develop
updates: - [github.com/psf/black: 22.3.0 → 22.6.0](psf/black@22.3.0...22.6.0) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
…tion#383) Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com>
…ndation#383) * chore(perception): add COLCON_IGNORE * delete COLCON_IGNORE * Delete COLCON_IGNORE * Delete COLCON_IGNORE * Delete COLCON_IGNORE * Delete COLCON_IGNORE * Delete COLCON_IGNORE
Currently there are behavior and motion planning modules. Each modules publishes it's own planed velocity (eg. slow down or stop velocity). But this velocity planing is done sequentially from behavior to motion so behavior planning modules doesn't know how motion planing modules plan velocity.
The text was updated successfully, but these errors were encountered: