Skip to content
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

Plugin implementations should be moved out of moveit_core #1925

Open
6 tasks
tylerjw opened this issue Feb 3, 2023 · 6 comments
Open
6 tasks

Plugin implementations should be moved out of moveit_core #1925

tylerjw opened this issue Feb 3, 2023 · 6 comments
Assignees
Labels
E-medium Medium Effort persistent Allows issues to remain open without automatic stalling and closing.

Comments

@tylerjw
Copy link
Member

tylerjw commented Feb 3, 2023

It would greatly simplify moveit_core if it was built as a single library instead of many small libraries linked together. One of the problems with this is that several plugins (not just plugin interfaces) are part of the moveit_core package. This got in the way of refactoring the build scripts for moveit_core into a single library, see #1801

Here is a directory for packages that contain moveit_plugins: https://github.com/ros-planning/moveit2/tree/main/moveit_plugins

Tasks:

  • Migrate collision_detection::CollisionDetectorBtPluginLoader from moveit_core into moveit_plugins.
  • Migrate collision_detection::CollisionDetectorFCLPluginLoader from moveit_core into moveit_plugins.
  • Migrate online_signal_smoothing::ButterworthFilterPlugin from moveit_core into moveit_plugins.
  • Update moveit_plugins package.xml to depend on these new plugins.
  • Search for any tests that previously depended on moveit_core for these plugins and update them to depend on their new packages.
  • Be happy!

I'd be happy to mentor doing this project.

@sameergupta4873
Copy link
Contributor

@tylerjw can i take this issue ?

@AndyZe
Copy link
Member

AndyZe commented Feb 12, 2023

Sorry, I think @ChrisThrasher is already working on it :/

@ChrisThrasher
Copy link
Contributor

I am. It's turning out to be a really complicated problem given how parts of moveit_core depend on parts of these plugins.

@github-actions
Copy link

This issue is being labeled as stale because it has been open 45 days with no activity. It will be automatically closed after another 45 days without follow-ups.

@github-actions github-actions bot added the stale Inactive issues and PRs are marked as stale and may be closed automatically. label Mar 30, 2023
@ChrisThrasher
Copy link
Contributor

I currently have no plans on coming back to this problem. My first attempt was fraught with issues due to moveit_core's complicated internal dependency graph. So long as major parts of moveit_core depend on aspects of these plugins then this refactor will be tricky.

@tylerjw tylerjw added persistent Allows issues to remain open without automatic stalling and closing. and removed stale Inactive issues and PRs are marked as stale and may be closed automatically. labels Mar 30, 2023
@tylerjw
Copy link
Member Author

tylerjw commented Mar 30, 2023

I'm becoming annoyed with this stale bot thing because these issues are less relevant to the project just because we don't have any new status on them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E-medium Medium Effort persistent Allows issues to remain open without automatic stalling and closing.
Projects
None yet
Development

No branches or pull requests

4 participants