-
Notifications
You must be signed in to change notification settings - Fork 569
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
(moveit_py) Add Trajectory Execution Manager #2406
Conversation
@MatthijsBurgh Can you run pre-commit? See here for instructions on how to do that https://moveit.ros.org/documentation/contributing/code/#pre-commit-formatting-checks |
9719861
to
be8b177
Compare
@sjahr done |
be8b177
to
d798100
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #2406 +/- ##
==========================================
+ Coverage 50.39% 50.79% +0.41%
==========================================
Files 391 392 +1
Lines 31996 32170 +174
==========================================
+ Hits 16121 16339 +218
+ Misses 15875 15831 -44
☔ View full report in Codecov by Sentry. |
d37246e
to
cbdf49e
Compare
Sorry for breaking CI again. pre-commit didn't do its jobs correctly. I don't know how, but it is fixed again. |
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 gave this a quick pass, the bindings look all correct to me. I would appreciate if @peterdavidfagan or @JafarAbdi could verify and test this.
moveit_py/src/moveit/moveit_ros/trajectory_execution_manager/trajectory_execution_manager.cpp
Show resolved
Hide resolved
moveit_py/src/moveit/moveit_ros/trajectory_execution_manager/trajectory_execution_manager.cpp
Show resolved
Hide resolved
moveit_py/src/moveit/moveit_ros/trajectory_execution_manager/trajectory_execution_manager.h
Outdated
Show resolved
Hide resolved
Thanks for these updates @MatthijsBurgh, reviewing this is on my list for things to do, hopefully I'll get around to this during the week. I want to first fix the tutorials as these are broken. |
cbdf49e
to
5c1ba00
Compare
Created an issue and referenced it in the code. Updated the copyright headers of only the changed files in this PR. |
🚀🚀🚀 |
4d5c8ba
to
9fc02e0
Compare
@peterdavidfagan friendly ping to merge this PR ;) |
Hi @MatthijsBurgh, I do need to finish reviewing this on my side, I will look to find time this week. |
This pull request is in conflict. Could you fix it @MatthijsBurgh? |
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.
These changes LGTM. I haven't had the opportunity to test all the added functionalities but I would be in favour of merging these changes and addressing any follow ups in issues.
Thanks @MatthijsBurgh for this contribution 🚀.
moveit_py/src/moveit/moveit_ros/trajectory_execution_manager/trajectory_execution_manager.cpp
Outdated
Show resolved
Hide resolved
moveit_py/src/moveit/moveit_ros/trajectory_execution_manager/trajectory_execution_manager.h
Outdated
Show resolved
Hide resolved
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.
Thanks a lot for this contribution (and your patience regarding reviews). Only one thing left to be changed and then this can finally be merged!
Manages the trajectory execution. | ||
)") | ||
|
||
.def("isManagingControllers", &trajectory_execution_manager::TrajectoryExecutionManager::isManagingControllers, |
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.
.def("isManagingControllers", &trajectory_execution_manager::TrajectoryExecutionManager::isManagingControllers, | |
.def("is_managing_controllers", &trajectory_execution_manager::TrajectoryExecutionManager::isManagingControllers, |
Shouldn't the python functions be defined in snake_case
(camelCase
is used for cpp functions)? I think it is done like this everywhere else, so we should be consistent about it. Can you update the other function signatures as well?
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.
We need to update many of the existing cpp methods as there are discrepancies elsewhere in the library which may have lead to @MatthijsBurgh using different conventions.
Not sure if there is an easy way to add this to auto formatter (clang-format) but I agree with the above convention.
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.
Added issue: #2499
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 that got covered by #2177 or do you mean something else @peterdavidfagan? That PR also added clang-tidy checks to warn about cpp function names that don't follow the conventions. But don't think there are checks to catch convention mistakes in .def("...", ..)
.
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.
49052c1 ❤️.
My fork was outdated only seeing these updates now. Thanks so much.
As for .def
I would personally need to become more familiar with clang-tidy
, maybe there is a way to get a rule which also flags .def
. For now I am happy to be more vigilant about this when pushing code or reviewing.
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.
Awesome, thanks for opening the issue though!
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.
So the python functions will be snake_case?
@sjahr I fixed the styling. I think then this one is ready to be merged too, correct? |
* (moveit_py) add trajectory execution manager * (moveit_py) add __bool__ to ExecutionStatus * (moveit_py) Update copyright header of changed files * (moveit_py) add comment referencing issue * Rename init_trajectory_execution_manager -> initTrajectoryExecutionManager * (moveit_py) python functions snake_case * (moveit_py) fix styling --------- (cherry picked from commit 76a488b) # Conflicts: # moveit_py/src/moveit/planning.cpp
Description
Add Trajectory Execution Manager.
Note: I have not been able to test the correct behaviour of all added functions. Also I skipped some functions, which are shown as comments.
Checklist