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

fix: the stopping speed judgments of freespace_planner and mission_planner #7859

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

Try110
Copy link

@Try110 Try110 commented Jul 5, 2024

… are consistent, taking into account the speed in xyz direction

Description

The stopping speed judgments of freespace_planner and mission_planner are consistent, taking into account the speed in xyz direction

Related links

#7834

  • Link

How was this PR tested?

None

Notes for reviewers

This is an accidental bug. The conditions for judging the end of a task are looser than the conditions for judging the completion of a task are used by the mission_planner, which occasionally causes the freespace_planner to judge that the task is completed, but the mission_planner to judge that the task is not completed.

Interface changes

None.

Effects on system behavior

None.

@github-actions github-actions bot added the component:planning Route planning, decision-making, and navigation. (auto-assigned) label Jul 5, 2024
Copy link

github-actions bot commented Jul 5, 2024

Thank you for contributing to the Autoware project!

🚧 If your pull request is in progress, switch it to draft mode.

Please ensure:

@Try110 Try110 changed the title The stopping speed judgments of freespace_planner and mission_planner… fix: The stopping speed judgments of freespace_planner and mission_planner… Jul 5, 2024
@Try110 Try110 changed the title fix: The stopping speed judgments of freespace_planner and mission_planner… fix: the stopping speed judgments of freespace_planner and mission_planner Jul 5, 2024
…nner are consistent, taking into account the speed in xyz direction Signed-off-by: yangzesong <15340400289@163.com>
Copy link

stale bot commented Sep 3, 2024

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 Sep 3, 2024
@stale stale bot removed the status:stale Inactive or outdated issues. (auto-assigned) label Dec 17, 2024
…nner/freespace_planner_node.cpp


fix: removed redundant abs functions

Co-authored-by: Ryohsuke Mitsudome <43976834+mitsudome-r@users.noreply.github.com>
@Try110 Try110 requested a review from mitsudome-r December 19, 2024 03:13
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)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants