-
Notifications
You must be signed in to change notification settings - Fork 172
Add trajectory_parameterization parameter to CartesianPath & JointInterpolationPlanner #333
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
Add trajectory_parameterization parameter to CartesianPath & JointInterpolationPlanner #333
Conversation
…erpolationPlanner
34e2b57 to
258a407
Compare
rhaschke
left a comment
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.
I think this's simpler than the plugin-based solution.
Sure, it's easier, but less flexible! A plugin-based solution would allow using the other time parameterization methods for MoveIt planning pipelines as well.
I thought this's already the case TimeOptimalTrajectoryGeneration, IterativeParabolicTimeParameterization, IterativeSplineParameterization am I missing something ? |
rhaschke
left a comment
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.
I thought this's already the case TimeOptimalTrajectoryGeneration, IterativeParabolicTimeParameterization, IterativeSplineParameterization.
You are right. I was misled by the too generic name AddTimeParameterization used for the IPTP plugin...
Approving. Depends on moveit/moveit#3021 and moveit/moveit#3023.
|
Edit: I didn't test properly. Please disregrad. |
Codecov Report
@@ Coverage Diff @@
## master #333 +/- ##
==========================================
+ Coverage 53.38% 53.38% +0.01%
==========================================
Files 102 102
Lines 7620 7621 +1
==========================================
+ Hits 4067 4068 +1
Misses 3553 3553
Continue to review full report at Codecov.
|
rhaschke
left a comment
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.
@JafarAbdi, may I ask you to change the API such that the time parameterization is specified as a property of those classes?
Time parameterization is also used by merge(...):
https://github.com/ros-planning/moveit_task_constructor/blob/4fa8c10f4456e893e09212b51a06b3d2ec4e9266/core/src/merge.cpp#L168-L170
which is used by Connect and Merger stages. Do you mind adding this feature there as well?
henningkayser
left a comment
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.
This looks very straight-forward to me. I agree it makes much more sense than using plugins here. Do you think you could address Robert's comments so that this can get merged?
|
@JafarAbdi, I implemented my suggestion (#333 (review)) in #339. Please review. I'm closing here. |
Fix: #330
Depend on moveit/moveit#3021
I think this's simpler than the plugin based solution