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

removing regression introduced in #658 #1040

Merged
merged 1 commit into from
Aug 30, 2018
Merged

removing regression introduced in #658 #1040

merged 1 commit into from
Aug 30, 2018

Conversation

mlautman
Copy link
Contributor

@mlautman mlautman commented Aug 30, 2018

Description

Thisa regressions introduced in #658 which was raised in issue #955

This stops the setup assistant from appending kConfigDefault to planner names and correctly trims kConfigDefault from existing ompl_planning.yaml files.

Checklist

  • Required by CI: Code is auto formatted using clang-format
  • Extended the tutorials / documentation, if necessary reference
  • Include a screenshot if changing a GUI
  • Created tests, which fail without this PR reference
  • Decide if this should be cherry-picked to other current ROS branches
  • While waiting for someone to review your request, please consider reviewing another open pull request to support the maintainers

@gavanderhoorn
Copy link
Contributor

gavanderhoorn commented Aug 30, 2018

Technically this looks ok, but I'm wondering whether removing the kConfigDefault is the right thing to do.

Perhaps @davetcoleman remembers why it was added in the first place.

Copy link
Contributor

@rhaschke rhaschke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I approve this change. For me, the suffix "kConfigDefault" always looked strange. However, it also acts as a reminder, that one can have multiple different configurations for a given OMPL planner - with different parameters.

@gavanderhoorn
Copy link
Contributor

@rhaschke wrote:

However, it also acts as a reminder, that one can have multiple different configurations for a given OMPL planner - with different parameters.

exactly.

The entries in the config files and on the parameter server are not planners, but only sets of configuration items. Removing that suffix makes that slightly less obvious, but perhaps not enough to keep it.

@mlautman mlautman merged commit ed07fc9 into moveit:kinetic-devel Aug 30, 2018
@mlautman mlautman deleted the setup-assistant-planners branch August 30, 2018 16:17
@v4hn
Copy link
Contributor

v4hn commented Aug 31, 2018 via email

mlautman added a commit that referenced this pull request Sep 6, 2018
@mlautman
Copy link
Contributor Author

mlautman commented Sep 6, 2018

@v4hn done 6073eda

@davetcoleman
Copy link
Member

Thanks for this bug fix @mlautman !

pull bot pushed a commit to shadow-robot/moveit that referenced this pull request Sep 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants