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

Split Link Kick into 2 Planners #2242

Open
wants to merge 11 commits into
base: ros2
Choose a base branch
from
Open

Conversation

Squid5678
Copy link
Contributor

Description

Splits line kick into 2 planners.

Associated / Resolved Issue

Resolves # or ClickUp card

Design Documents

Link

Steps to Test

Test Case 1

  1. Step 1
  2. Step 2
  3. Step 3

Expected result:???

Key Files to Review

Group 1

  • File 1
  • File 2

Group 2

  • File 3
  • File 4

Review Checklist

  • Docstrings: All methods and classes should have the file appropriate docstrings which follow the guidelines in the "Contributing" page of our docs.
  • Remove extra print statements: Any print statements used for debugging should be removed
  • Tag reviewers: Tag some people for review and ping them on Slack

(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.

  • Step 1
  • Step 2

Copy link
Contributor

@sid-parikh sid-parikh left a 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

@sid-parikh
Copy link
Contributor

also merge style checks

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);
Copy link
Contributor

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()) {
Copy link
Contributor

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{};
Copy link
Contributor

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_

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants