Development towards 4.0.0 #57
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Added functions to enable/disable collisions with an object vis the allowed collision matrix * Clarified function name, reduced replicated code * Made toggling collisions async * Fix type annotations for consistency * formatting * Added tests * Spelling * Update docstring * Fix unnecessary change
…fector_link` when available (#56) * Update msg * Use `cartesian_speed_limited_link` instead of `cartesian_speed_end_effector_link` when available Signed-off-by: Andrej Orsula <[email protected]> --------- Signed-off-by: Andrej Orsula <[email protected]> Co-authored-by: Apurv Saha <[email protected]>
* added re-use of max_velocity_scaling_factor and max_acceleration_scaling_factor from move_action goal to cartesian_path_request * Removed getter and setter of 'max_cartesian_speed' to avoid confusion as the corresponding value of the MotionPlanRequest.msg (respectively the self.__move_action_goal.request object) is currently not used in moveit2. --> The 'max_cartesian_speed' variable requires the 'default_planner_request_adapters/SetMaxCartesianEndEffectorSpeed' which currently only exists in moveit1.
* Added ability to have cartesian planning calls avoid collisions * Fix bad merge * Allow users to set cartesian jump threshold * Allow users to set cartesian max step * Pass frame_id into the cartesian planning service * Add ability to specify a required fraction for a cartesian plan to succeed * Allowed users to get end effector name and base link name * Add revolute and prismatic jump thresholds * Formatting * Added test cases
* Added a function to move collision objects * Add examples
* Allow scaling of collision meshes * Added trimesh to rosdeps for easier installation * Ran tests with example * Remove trimesh as a required dependency
…ing_scene` To User (#66) * Reinstate Humble compatibility for GetCartesianPath * Expose planning scene to user
|
FYI @amalnanavati, I just did a quick test on a couple of old demos, and everything seems to be functional. Perhaps it is a good time to merge it in and make the release. But I wanted to ask you first as you have worked the most with the codebase. What do you think? |
Signed-off-by: Andrej Orsula <[email protected]>
Signed-off-by: Andrej Orsula <[email protected]>
|
Thanks for checking in! Yeah I’m happy to merge it in; I have no other changes planned at the moment. Of course, more features may arise as I keep using the library, but that could be another release :) |
|
Okay, thanks a lot for all your effort! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cartesian_speed_limited_linkinstead ofcartesian_speed_end_effector_linkwhen available #56max_cartesian_speedproperty is removedGetCartesianPath& Exposeplanning_sceneTo User #66