Skip to content
This repository was archived by the owner on Nov 13, 2017. It is now read-only.

Kei okada's - get default planner from param#625

Merged
sachinchitta merged 5 commits intoindigo-develfrom
k-okada-get_default_planner_from_param
Nov 21, 2015
Merged

Kei okada's - get default planner from param#625
sachinchitta merged 5 commits intoindigo-develfrom
k-okada-get_default_planner_from_param

Conversation

@sachinchitta
Copy link
Copy Markdown
Contributor

No description provided.

@sachinchitta
Copy link
Copy Markdown
Contributor Author

@rhaschke - this param is only used to set the default planner for when the Rviz plugin gets brought up - currently it comes up as "unspecified". Assigning default planners per group would be useful but it should happen separately from this PR. Maybe we should rename this param to "rviz_default_planner_config" to minimize confusion.

instead of loading from `/<ns>/default_planner_config`, use
`/<ns>/move_group/<group>/default_planner_config`, which is the default
location for `planner_configs` too
@rhaschke
Copy link
Copy Markdown
Contributor

My adaption loads the default_planner_config from the move_group's namespace, considering also the selected group when there is a configuration for it. Hence in ompl_planning.yaml, one can now specify:

arm:
  default_planner_config: RRTConnectkConfigDefault
  planner_configs:
    - RRTkConfigDefault
    - RRTConnectkConfigDefault

Obviously, one can overwrite that setting manually in launch files - after loading the yaml defaults.

The same default could be used by the move_group node too.
However, there is a heuristic to choose a config if I remember correctly.
@k-okada Do you like that modification?

... to retrieve default planner config from param server
moved corresponding code from rviz plugin to MoveGroup interface
to facilitate re-use
@sachinchitta
Copy link
Copy Markdown
Contributor Author

Nice change! @rhaschke

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants