Akif's profile - activity

You can try adding find_package(PkgConfig REQUIRED) pkg_check_modules(JSONCPP jsoncpp) and changing include_director

Of course, no. We can get a better idea if you can post the output of rostopic info /camera/depth/camera_info for exampl

Possibly you are running RViz or something similar. If you have subscribers, topics will appear. You can check with rost

Maybe you should check logger level for your plugin.

sd, qhd and hd are resolutions of the image. Details are given in iai_kinect2 repo. For topic names, _ir: infrared im

No I don't. To be able to "mean" anything, you need to supply more details (like sensor model, driver you use, topic you

If you are gathering point cloud in one of _optical frames, z coordinate should point forward from the camera. If not, t

Please post your tf tree.

You do not need to reimplement navfn or global_planner in your custom plugin. For example, you can include #include <

Instead of messing with move_base source, as mentioned in the question you have linked, you can write a planner which wi

Instead of messing with move_base source, as mentioned in the question you have linked, you can write a planner which wi

In fact, goal ID is stored in client side but not exposed to public. In GoalHandle, actionlib uses goal ID to cancel a

@Soul Goumey, You're welcome!

@Soul Gourney, You're welcome!

For your first question (since it is also in the title), your local planner should return false from computeVelocityComm

Also check your laser scanner. There may be a problem with readings.

You can try this; visualization_msgs::Marker marker; marker.header.frame_id = "/my_frame"; marker.header.stamp = ros::T

You can try this; visualization_msgs::Marker marker; marker.header.frame_id = "/my_frame"; marker.header.stamp = ros::T