Ferherranz's profile - activity

Hi, I'm trying to compile the package ethzasl_icp_mapping on indigo and I get this error:

*** No rule to make target `/tmp/buildd/ros-indigo-libpointmatcher-1.2.2-0trusty-20140805-1228/obj-x86_64-linux-gnu/libpointmatcher.so', needed by `/datos/ros_ws/ethz-asl/devel/lib/libpointmatcher_ros.so'.  Stop.
make[1]: *** [ethzasl_icp_mapping-indigo_devel/libpointmatcher_ros/CMakeFiles/pointmatcher_ros.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....

I'm using Ubuntu 14.04 and ROS indigo. I've also installed the packages ros-indigo-libpointmatcher and ros-indigo-libnabo.

Please, help!!

Are they absolute to the origin? Do they appear at the place in the map, where they actually belong (i.e. do they match the map)? In that case this is the correct and expected behavior. If you want to see it differently, i.e. focused around the robot, set the Fixed Frame to /base_link.

They always are plotted at the origin while the robot moves and do not match the map. I'm using /map as fixed frame and the points do not move with the robot

Hello, I'm trying to run gmapping over a pionner AT using rosaria and a hokuyo laser. Everything seems to work fine and I'm able to move the robot. However, when the robot acquires the laser measurements they are always plotted in rviz with respect to the origin of coordinates instead of the base_link. I apply some dynamic basic transformations and check that the odometry is represented correctly.

The frame tree is the following: /laser -> base_laser -> base_link -> odom -> map as the basic tf tutorial explains

Do you have any idea about why the laser measurements are fixed with respect to the origin of coordinates while the base_link is moving? Are the transformations chained between them?