OctoMap / octomap_mapping

ROS stack for mapping with OctoMap, contains octomap_server package
http://www.ros.org/wiki/octomap_mapping
342 stars 280 forks source link

Nodelet version of octomap_server #1

Open ahornung opened 11 years ago

ahornung commented 11 years ago

Apparently there is a problem with the nodelet version of octomap_server, first introduced in this Issue: http://code.google.com/p/alufr-ros-pkg/issues/detail?id=7

Original report (@jihoonl @bit-pirate) in OctoMap/octomap#33

ahornung commented 11 years ago

Remaining issue (or solved?) from Google code / OctoMap/octomap#33

By @bit-pirate

Following up on the issue about not being able to load the nodelet: It's a bit weird. The configuration (macro call, plugin info export etc.) looks fine. However, the nodelet can't be found (e.g. roslaunch throws errors, rospack plugins --attrib=plugin nodelet doesn't list the plufin).

The package path is set correctly and even rosmake runs through without errors. roscd and rospack find all work, but rospack profile hides the whole stack.

Currently, I have no clue what's causing this problem.

PS: I have tested octomap_server from the octomap_stacks-groovy-devel branch.

bit-pirate commented 11 years ago

Haven't used the octomap server in a while. I'll update this issue the next time I get around using it.

czalidis commented 10 years ago

Looks like nodelet_plugins.xml is missing when you install octomap_server from debian packages: Skipping XML Document "/opt/ros/hydro/share/octomap_server/plugins/nodelet_plugins.xml" which had no Root Element. This likely means the XML is malformed or missing.

ahornung commented 10 years ago

Yes, this was fixed in commit 412db167b3e6932701256f0d08663556a011c372, I'm pushing that out to a release now.

The issue here was reported before (in fact, before catkinization) so I'm not sure if it's related (or if it's still relevant at all).

chipironcin commented 10 years ago

Is this issue already patched? You can close the issue if true.

ahornung commented 10 years ago

The nodelet_plugins.xml file is there. I need some feedback that the nodelet launch is indeed working as inteded, then I can close the issue.