-
Notifications
You must be signed in to change notification settings - Fork 558
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
Update ompl_interface with latest version of OMPL #2994
base: main
Are you sure you want to change the base?
Conversation
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.
LGTM.
Would be good to see if lines https://github.com/moveit/moveit2/pull/2994/files#diff-18741df7cbb95f9292a57457e88318346213653f65f3932a5a03a1eaf7b2655bR27-R30 are still needed |
@@ -12,3 +12,7 @@ repositories: | |||
type: git | |||
url: https://github.com/moveit/moveit_resources.git | |||
version: ros2 | |||
ompl: |
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.
Should we wait till the new ompl version is released?
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 guess the ompl crew would be willing to release although they still have at least one unresolved regression lying around.
But I'm not sure it's so difficult to support both ompl cmake interfaces here for now. We do that in MoveIt.
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 feel like incurring a source build of OMPL is probably not ideal for build times, so I'd prefer waiting for that new release to be available via binaries before merging this PR.
@@ -12,3 +12,7 @@ repositories: | |||
type: git | |||
url: https://github.com/moveit/moveit_resources.git | |||
version: ros2 | |||
ompl: |
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 guess the ompl crew would be willing to release although they still have at least one unresolved regression lying around.
But I'm not sure it's so difficult to support both ompl cmake interfaces here for now. We do that in MoveIt.
According to OMPL's build documentation |
It was my intent to preserve them for backwards compatability, but the reality on ompl |
This PR should get us closer to fixing the accidental breakage of the old variables in find_package. https://github.com/ompl/ompl/pull/1182/files#diff-148715d6ea0c0ea0a346af3f6bd610d010d490eca35ac6a9b408748f7ca9e3f4R10 We need to then add this back into the export, along with the other variables. |
This pull request is in conflict. Could you fix it @MarqRazz? |
Thanks for keeping this moving @sjahr! |
@MarqRazz I'd just merge it now, since there aren't any CI failures related to the PR. Any concerns? |
Actually we need to release OMPL for this change to work right. I have not tested this against the latest release to ROS2. @mamoll I would be happy to help get the OMPL release to ROS updated. Is there anything I can help with? @JafarAbdi also said he was will to help maintain the release. |
Ok, I'll wait for now 👍 Let me know when it's ready |
@MarqRazz @mamoll @JafarAbdi Any updates? |
Thanks for keeping this up to date @sjahr! I have reached out the the ompl-release repo and Mark Moll and we are working on adding additional maintainers. |
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.
LGTM
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #2994 +/- ##
==========================================
- Coverage 45.67% 45.66% -0.01%
==========================================
Files 714 714
Lines 62295 62295
Branches 7530 7530
==========================================
- Hits 28445 28438 -7
- Misses 33684 33690 +6
- Partials 166 167 +1 ☔ View full report in Codecov by Sentry. |
Wait... @MarqRazz I just read the original issue and now that OMPL 1.6.0 is out for Jazzy, the source build can be removed and this should work, yeah? |
OMPL 1.6 has been released since Jan. 7th 2023 and is currently the latest release of the library (this is the same version that is available in Humble). The breaking change this PR is attempting to fix was merged into OMPL on Oct. 2023. I poked around in the ompl-release repo for Jazzy and I'm not sure which upstream OMPL commit these rebases were made on
FYI we do have a PR open to make a 1.7 release of OMPL but it is taking a little time to ensure that everything is ready to cut a new version. I am also proposing a new versioning approach that bumps the source version after cutting a release so there is less confusion which version is released vs source. If anyone has thoughts here about version numbering please come chime in on the conversation! |
Gotcha. My preference would be to then release the OMPL 1.7.0 binaries and then update this PR to use those binaries. But if you/others would prefer to bring in the latest version sooner and do the source build for now, my preference isn't strong. Just note that we wouldn't be able to cut a new release of MoveIt until the OMPL binaries were in, hence my hesitation. Edit: anyway, the tutorials images check I think is failing, but it should go green after this PR makes it to main. |
👍 Mine too which is why I have been holding off on this PR. I was also only planning on releasing OMPL 1.7 to Rolling/Jazzy and leaving everything else on 1.6. |
Description
I'm working on debugging some issues and require building MoveIt2 and OMPL from source. This PR updates the package
moveit_planners_ompl
to work with the latest changes made in OMPL and it's more modern approach to exporting/linking the library but will require building it from source until a new release is made (I am working on getting it released and will keep this PR updated with the status).I was also having issues with OMPL but that package was recently updated to properly work with Colcon. Here is a link to the issue.
Big thanks to @JafarAbdi and @mamoll for helping me debug some of these issues and getting this updated! 🥇
Checklist