-
Notifications
You must be signed in to change notification settings - Fork 186
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
Split Link Kick into 2 Planners #2242
base: ros2
Are you sure you want to change the base?
Conversation
…ts/robocup-software into line_kick_two_planners
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.
can you fix the two clang-tidy warnings in GH please? just a case style thing
also merge style checks |
automated style fixes Co-authored-by: Squid5678 <[email protected]>
Co-authored-by: Sid Parikh <[email protected]>
FacePoint{plan_request.motion_command.target.position}}; | ||
modified_request.motion_command = modified_command; | ||
|
||
return path_target_.plan(modified_request); | ||
return initial_planner.plan(modified_request); |
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.
looks like you missed the underscore after the variable name so it isn't compiling
} | ||
|
||
void LineKickPathPlanner::process_state_transition() { | ||
// Let PathTarget decide when the first stage is done | ||
// Possible problem: can PathTarget get stuck and loop infinitely? | ||
if (current_state_ == INITIAL_APPROACH && path_target_.is_done()) { | ||
if (current_state_ == INITIAL_APPROACH && initial_planner.is_done()) { |
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.
Same thing here
@@ -45,7 +45,8 @@ class LineKickPathPlanner : public PathPlanner { | |||
|
|||
State current_state_{INITIAL_APPROACH}; | |||
|
|||
PathTargetPathPlanner path_target_{}; | |||
PathTargetPathPlanner initial_planner_{}; | |||
PathTargetPathPlanner final_planner{}; |
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.
fix case style by renaming final_planner
to final_planner_
Description
Splits line kick into 2 planners.
Associated / Resolved Issue
Resolves # or ClickUp card
Design Documents
Link
Steps to Test
Test Case 1
Expected result:???
Key Files to Review
Group 1
Group 2
Review Checklist
(Optional) Sub-issues (for drafts)
Note: if you find yourself breaking this PR into many smaller features, it may make sense to break up the PR into logical units based on these features.