-
Notifications
You must be signed in to change notification settings - Fork 1
Add planner name to trajectory info #5
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
Changes from 6 commits
7c28c63
2ae3765
1553120
babbbc6
ee65d3e
42a3c33
b16b438
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -73,7 +73,13 @@ class Connect : public Connecting | |
| WAYPOINTS = 1 | ||
| }; | ||
|
|
||
| using GroupPlannerVector = std::vector<std::pair<std::string, solvers::PlannerInterfacePtr> >; | ||
| struct PlannerIdTrajectoryPair | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks for doing this! My comment was less about the struct vs. pair data structure, and the fact that if you ever had to add more data to this it would be challenging. Same still holds here because the struct has ... and same with the variable names that use this data type, which are still called
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we should keep it like this for now because the name describes what it is and if we add more to this data structure in the future the name can be updated accordingly. Despite the fact that this could also be of datatype pair, I think making it a struct made the code more readable 👍
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sounds good -- I can't think of anything better anyhow. |
||
| { | ||
| std::string planner_name; | ||
| robot_trajectory::RobotTrajectoryConstPtr robot_trajectory_ptr; | ||
| }; | ||
|
|
||
| using GroupPlannerVector = std::vector<std::pair<std::string, solvers::PlannerInterfacePtr>>; | ||
| Connect(const std::string& name = "connect", const GroupPlannerVector& planners = {}); | ||
|
|
||
| void setPathConstraints(moveit_msgs::msg::Constraints path_constraints) { | ||
|
|
@@ -89,10 +95,10 @@ class Connect : public Connecting | |
| void compute(const InterfaceState& from, const InterfaceState& to) override; | ||
|
|
||
| protected: | ||
| SolutionSequencePtr makeSequential(const std::vector<robot_trajectory::RobotTrajectoryConstPtr>& sub_trajectories, | ||
| SolutionSequencePtr makeSequential(const std::vector<PlannerIdTrajectoryPair>& trajectory_planner_vector, | ||
| const std::vector<planning_scene::PlanningSceneConstPtr>& intermediate_scenes, | ||
| const InterfaceState& from, const InterfaceState& to); | ||
| SubTrajectoryPtr merge(const std::vector<robot_trajectory::RobotTrajectoryConstPtr>& sub_trajectories, | ||
| SubTrajectoryPtr merge(const std::vector<PlannerIdTrajectoryPair>& trajectory_planner_vector, | ||
| const std::vector<planning_scene::PlanningSceneConstPtr>& intermediate_scenes, | ||
| const moveit::core::RobotState& state); | ||
|
|
||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.