Skip to content
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

Closed
taikitanaka3 opened this issue Feb 14, 2022 · 4 comments
Closed

Difficulty of estimating velocity at future time t #383

taikitanaka3 opened this issue Feb 14, 2022 · 4 comments
Labels
component:planning Route planning, decision-making, and navigation. (auto-assigned) type:new-feature New functionalities or additions, feature requests.

Comments

@taikitanaka3
Copy link
Contributor

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.

image

@stale
Copy link

stale bot commented Apr 15, 2022

This pull request has been automatically marked as stale because it has not had recent activity.

@stale stale bot added the status:stale Inactive or outdated issues. (auto-assigned) label Apr 15, 2022
@BonoloAWF BonoloAWF added the type:new-feature New functionalities or additions, feature requests. label Apr 19, 2022
@stale stale bot removed the status:stale Inactive or outdated issues. (auto-assigned) label Apr 19, 2022
@stale
Copy link

stale bot commented Jun 18, 2022

This pull request has been automatically marked as stale because it has not had recent activity.

@stale stale bot added the status:stale Inactive or outdated issues. (auto-assigned) label Jun 18, 2022
@takayuki5168
Copy link
Contributor

@taikitanaka3 Now we calculate the vehicle velocity with motion_velocity_smoother as a library in behavior_velocity_planner. Did this solve this issue?

@stale stale bot removed the status:stale Inactive or outdated issues. (auto-assigned) label Sep 22, 2022
@takayuki5168 takayuki5168 added the component:planning Route planning, decision-making, and navigation. (auto-assigned) label Sep 22, 2022
@taikitanaka3
Copy link
Contributor Author

no, but there is no approach with current architecture so i will close this issue.

@taikitanaka3 taikitanaka3 closed this as not planned Won't fix, can't repro, duplicate, stale Sep 22, 2022
TomohitoAndo pushed a commit to TomohitoAndo/autoware.universe that referenced this issue Oct 5, 2022
TomohitoAndo pushed a commit to TomohitoAndo/autoware.universe that referenced this issue Oct 5, 2022
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>
keiota pushed a commit to keiota/autoware.universe that referenced this issue Aug 17, 2023
…tion#383)

Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com>
YamatoAndo pushed a commit to YamatoAndo/autoware.universe that referenced this issue Aug 8, 2024
…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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component:planning Route planning, decision-making, and navigation. (auto-assigned) type:new-feature New functionalities or additions, feature requests.
Projects
None yet
Development

No branches or pull requests

3 participants