IanCol's profile - activity

Hi There,

I am following the python publisher/subscriber tutorial located here. I followed the first couple of steps to download and build the code. Then, as instructed, I started a roscore and in a new terminal I ran "rosrun node_example pyttalker.py". That's when the following error came up:

Traceback (most recent call last):
  File "/home/icolwell/node_example/src/pytalker.py", line 14, in <module>
    from node_example.msg import NodeExampleData
ImportError: No module named msg

It appears that python can't find the python headers for the custom ROS message. I did a bit of investigating and these are the results:

1 The output of "rosmsg package node_example" is:

node_example/NodeExampleData

So it appears that ROS is aware that custom messages exist.

2 I also tried to ensure my $PYTHONPATH includes node_example by running "source ~/node_example/devel/setup.bash". Then the output of "echo $PYTHONPATH" was:

/home/icolwell/node_example/devel/lib/python2.7/dist-packages:/home/icolwell/catkin_ws/devel/lib/python2.7/dist-packages:/opt/ros/indigo/lib/python2.7/dist-packages

3 The contents of "~/node_example/devel/lib/python2.7/dist-packages/node_example/msg" is totally empty. Is this correct? I would assume that there should be something there that was built according to CMakeLists.txt but I am not familiar with python modules.

I also looked around online and other people have had similar problems. However, they seemed to be caused by a screwed up package.xml or CMakeLists.txt file. This doesn't seem to be the case here since it is unmodified tutorial code, and it appears that all the correct message generation related dependencies are there.

Does anyone have any idea what is happening here? Or at the very least is someone able to reproduce the same error? I am running Indigo on 14.04.

Any help will be greatly appreciated :D

It appears there is a driver available here: https://github.com/usdot-fhwa-stol/carma-cohda-dsrc-driver/tree/develop/dsr

Thanks! I actually forgot I had asked this question. At the time I believe I was confused about why you'd need parameter

Thanks! I actually forgot I had asked this question. At the time I believe I was confused about why you'd need parameter

In this document: https://docs.ros.org/en/foxy/Concepts...

It mentions the following

Parameters are addressed by node name, node namespace, parameter name, and parameter namespace. Providing a parameter namespace is optional.

What exactly is a "parameter namespace"? I can't seem to find any other references to a parameter namespace in ros2.

ros2 param namespace In this document: https://docs.ros.org/en/foxy/Concepts/About-ROS-2-Parameters.html It mentions th

I happened to solve this rviz issue by following this answer: https://askubuntu.com/a/1069502/688415 Hope this helps ot

For those still looking, you may be interested in this driver: https://autonomoustuff.atlassian.net/wiki/spaces/RW/pages

I've also came across this bug because my CI testing for melodic is now failing, the official install instructions are n

Anyone know why it's deprecated? it's a nice one-line way to create a quaternion.

-b Display messages in a bag file. -p Display messages in a matlab/octave-friendly plotting format. From here.

Ah, maybe that bug is the cause of the issues I was seeing. Unfortunately I didn't capture them, but there were errors c

Autoware open planner only works with vector map? Hi there, I am using the open planner local planner (op_local_planne

Thanks for responding! I did end up hacking up a mess of a bash script, I'll try the python API next time. If it comes o

I am also struggling to figure this out, all I'm trying to do is generate a list of apt package dependencies from a set

ROS Topic Statistics are great for monitoring every topic on the system. Tools such as ARNI rely on topic statistics to be enabled at all times during normal operation.

Does anyone know what kind of performance impact there is to having enable_statistics set to True all the time?

Think of the following use case: I want to know the publish stats (frequency, data age) of a high-density Lidar driver output. I could subscribe to the pointcloud using a monitoring node, but this means the monitoring node would receive the entire pointcloud payload even though it doesn't need it. This seems rather inefficient, all it needs to know is if something was published or not and when.

Is that the purpose of topic statistics? a lightweight way to dump out all topic activity?

Just wondering if enable_statistics is something that was designed for debug only or something that could be left on at all times. I also couldn't find a REP that discusses topic statistics, if I missed something, please let me know.

Thanks!

Thanks! just the clarification I was looking for. I'll try some profiling and see how it looks.

You have a few options: You can use the ROS parameter server with the rosbridge according to this. The parameter serve

Performance impact of enabling topic statistics ROS Topic Statistics are great for monitoring every topic on the system.

Some thoughts of mine: You could simply define your own custom message called LaserScanCW or something. If you only in

Node failure using ROS diagnostics framework I've been reading about the ROS diagnostics framework in order to add some

I also recently ran into this exact same error message when trying to visualize a nav_msgs/Path topic with invalid (all