-
Notifications
You must be signed in to change notification settings - Fork 523
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
Properly handle move_group_capabilities #2694
Comments
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. |
@sjahr / @henningkayser: could you please summarise the status of this issue? With configuration packages generated by the MSA from I'd like to avoid approaches like this one, as it would mean maintaining yet another fork. Edit: @SyZbidi FYI |
I've opened #3018 to fix the current issues that make the exported MSA config not actually run From what I can see, we can't actually use the moveit_config.to_dict() unless we drop support for the launch parameters capabilities/disabled_capabilities (which I have no idea how widely the are used). |
Description
In
moveit_configs_utils/moveit_configs_utils/launches.py
, the capabilities parameter is handled separately instead as part of moveit_config.to_dict() like the other moveit_config parameters.Environment
Steps to reproduce
A temporary fix was made in PR: #2587
@sjahr suggested creating an issue for a more integrated fix
The text was updated successfully, but these errors were encountered: