gerkey's profile - activity

My guess is that you're not linking against pcl_visualization. Here's a minimal program containing your code, along with

I don't have a Kinetic install handy for testing, but from tracing the errors, it would seem that this xacro invocation

I don't have a Kinetic install handy for testing, but from tracing the errors, it would seem that this xacro invocation

I don't have a Kinetic install handy for testing, but from tracing the errors, it would seem that this xacro invocation

parameter error when running Can you have a look at this error I am trying to run a Clearpath grizzly environment using

@tryan's two points are right: for a single camera you should use the camera_controller plugin, and you should put the p

After a trip into the basement where they keep the Ark of the Covenant, I found an email that I sent to Jeremy Leibs and

I don't have a Jade setup to test with, but I was able to remap playback on Indigo.

You want to use the remap tag inside the node tag. E.g.:

<launch>
  <arg name="file"/>
  <node pkg="rosbag" type="play" name="playback" ns="myNamespace" args="—clock $(arg file)">
     <remap from="/myTopic" to="/playback/myTopic"/>
  </node>
</launch>

That should result in the recorded topic /MyTopic being published as /playback/myTopic. To be honest, I'm not certain exactly how the remap interacts with the namespace specification (my initial testing suggests that the namespace into which you put rosbag play doesn't affect the scoping of its published topics).

At the command-line, I was able to remap topics in the usual way, using the same syntax that you suggested.

If these techniques aren't working for you on Jade, then please open an issue: https://github.com/ros/ros_comm/issues .

From CMake, I would use the result from find_package() without REQUIRED. For example, if you know that you need roscpp:

find_package(roscpp QUIET)
if(NOT roscpp_FOUND)
  message(STATUS "Couldn't find roscpp, so not building ROS-specific functionality. Did you source the ROS setup.sh file?")
else()
  message(STATUS "Found roscpp installed at ${roscpp_DIR}, so building ROS-specific functionality.")
  include_directories(${roscpp_INCLUDE_DIRS})
  #....
endif()

You can do the same for each ROS package that you need, if they're all optional. Or you could use a common package like roscpp as a global indicator to turn on or off ROS support, and just make all the others REQUIRED.

Of course, as @jackie said, you first need to have configured your environment so that find_package() can locate ROS packages. But I think that that's better than trolling through the file system looking for ROS. Among other things, it leaves it open to the user to not configure his or her environment to be able to locate ROS packages, thereby disabling the optional ROS support.

That code is pretty old, so it's hard to know, but I would guess that the purpose is to avoid the chance of receiving a SIGPIPE due to something bad happening to a socket, which could happen pretty often, given how many sockets we might be using and the variety of network conditions we're running in. As you point out, the default behavior for SIGPIPE is to terminate the program, so if we expect to receive it, then we either need to ignore it or catch it.

I don't see a problem with your workaround of unmasking SIGPIPE and catching it yourself. But you should know that you might get SIGPIPEs that are generated due to roscpp's sockets, as opposed to your own resources.