Henning Kayser

@SammyRamone would you mind filing a PR to fix this? ;)

I'll take a look at this fairly soon. Especially in preparation for and possibly during GSoC, we should have a clear migration strategy.

@medvedevigorek thanks for reporting this! I think the observed behavior is in line with the removal of supporting multiple collision backends at the same time https://github.com/ros-planning/moveit2/pull/364 (which had its own...

@quizzy5889 thanks for reporting this. Collision checking should definitely work with both plugins. I think Bullet had some lack of support for distance checking, but I haven't tested this recently....

I'm not following. What's wrong with the node name in rdf_loader in particular? The code doesn't look like it's producing invalid names to me.

> @henningkayser Thanks for your attention to this PR!! I could have explained it more clearly... > > For example, `abc.def` containing `.` is a valid name for a parameter,...

It's ok to add try catch blocks, but IMO it would be much better to replace the exceptions with assertions. The named cases are broken API contracts (=coding errors) and...

You're right, the default values are really not ideal here. We're currently working on refactoring all of MoveIt's parameters to use proper declaration and defaults using the [generate_parameter_library](https://github.com/PickNikRobotics/generate_parameter_library). See https://github.com/ros-planning/moveit2/pulls?q=is%3Apr+generate_parameter_library...

@stephanie-eng have there been any results for this issue yet?

@edetleon thanks for this report. Did you clone the panda_moveit_config package into your workspace as well as described in the Getting Started section? This issue has been fixed a while...