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

feat(mission_planner): add normal reroute implementation #3461

Merged
merged 14 commits into from
May 23, 2023

Conversation

purewater0901
Copy link
Contributor

@purewater0901 purewater0901 commented Apr 19, 2023

Description

Add normal reroute implementation to the mission planner

🤖 Generated by Copilot at e07f7a8

This pull request enhances the mission_planner component to support dynamic rerouting based on user or system inputs. It adds new functions and types to handle vector map and reroute messages, and a new parameter to configure the reroute time threshold. It also improves the readability and consistency of the existing code.

Related links

Tests performed

Notes for reviewers

Interface changes

Effects on system behavior

Pre-review checklist for the PR author

The PR author must check the checkboxes below when creating the PR.

In-review checklist for the PR reviewers

The PR reviewers must check the checkboxes below before approval.

  • The PR follows the pull request guidelines.
  • The PR has been properly tested.
  • The PR has been reviewed by the code owners.

Post-review checklist for the PR author

The PR author must check the checkboxes below before merging.

  • There are no open discussions or they are tracked via tickets.
  • The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

Signed-off-by: yutaka <purewater0901@gmail.com>
Signed-off-by: yutaka <purewater0901@gmail.com>
@github-actions github-actions bot added the component:planning Route planning, decision-making, and navigation. (auto-assigned) label Apr 19, 2023
Signed-off-by: yutaka <purewater0901@gmail.com>
@codecov
Copy link

codecov bot commented Apr 19, 2023

Codecov Report

Patch coverage has no change and project coverage change: -0.51 ⚠️

Comparison is base (010523f) 15.10% compared to head (17cf422) 14.60%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3461      +/-   ##
==========================================
- Coverage   15.10%   14.60%   -0.51%     
==========================================
  Files        1332     1287      -45     
  Lines       94823    90476    -4347     
  Branches    27009    28211    +1202     
==========================================
- Hits        14321    13210    -1111     
+ Misses      64813    63100    -1713     
+ Partials    15689    14166    -1523     
Flag Coverage Δ *Carryforward flag
differential 15.08% <0.00%> (?)
total 14.62% <ø> (-0.49%) ⬇️ Carriedforward from 4b5ecb8

*This pull request uses carry forward flags. Click here to find out more.

Impacted Files Coverage Δ
...on_planner/src/mission_planner/mission_planner.cpp 0.00% <0.00%> (ø)

... and 442 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

Comment on lines 168 to 173

// update (initialize) route
if (!initialize_route_) {
original_route_ = std::make_shared<LaneletRoute>(route);
initialize_route_ = true;
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

move this process to on_set_route?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed in 4e921cc, seems ok

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@isamu-takagi
assume that change_route is called after set_route, if change_route is called first original_route is not set. is it ok?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

or change_route should change original_route?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change_route interface only works after setting the route. So please add a check if the route state is SET.

Signed-off-by: yutaka <purewater0901@gmail.com>
Signed-off-by: yutaka <purewater0901@gmail.com>
purewater0901 and others added 9 commits April 20, 2023 22:36
Signed-off-by: yutaka <purewater0901@gmail.com>
Signed-off-by: yutaka <purewater0901@gmail.com>
Signed-off-by: yutaka <purewater0901@gmail.com>
Signed-off-by: yutaka <purewater0901@gmail.com>
Signed-off-by: yutaka <purewater0901@gmail.com>
Copy link
Contributor

@kosuke55 kosuke55 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@purewater0901 purewater0901 merged commit 140866a into main May 23, 2023
@purewater0901 purewater0901 deleted the feat/add-reroute-implementation branch May 23, 2023 07:19
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.

3 participants