ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Andrew Price's profile - activity

2020-06-10 22:56:50 -0500 received badge  Nice Answer (source)
2020-02-10 17:41:49 -0500 commented answer How to read a vector<strings> parameter from command line

Has anyone gotten the <param type="yaml"/> syntax to work? It fails for me on Kinetic with: Invalid <node&g

2019-05-24 23:25:20 -0500 answered a question VIDIOC_S_FMT error 5 , Input/output error

Rebooting the computer after installing usb_cam and apt updating worked for me. Initially, running v4l2-ctl --list-forma

2019-04-08 12:36:50 -0500 commented answer Unable to override osrf/ros entrypoint

@arwtyxouymz, that's probably best for another question, and I'm not super familiar with docker-compose. On my machine,

2019-04-06 04:13:14 -0500 received badge  Necromancer (source)
2019-04-06 04:13:14 -0500 received badge  Teacher (source)
2019-04-05 11:44:19 -0500 answered a question Unable to override osrf/ros entrypoint

The immediate shutdown is coming from the set -e flag in the entrypoint. I'm not sure what the problem with the develspa

2019-04-05 08:45:43 -0500 answered a question different encodings of depth image for real & simulated kinect

@PeteBlackerThe3rd is right about the units. The package depth_image_proc has functions to convert between the two versi

2018-07-25 10:36:57 -0500 received badge  Enthusiast
2018-03-17 23:04:34 -0500 commented answer This robot has a joint named "joint_1" which is not in the gazebo model.

Also, Gazebo will round sufficiently small numbers to 0, so you may encounter this problem even with a nonzero mass/iner

2017-10-26 15:39:00 -0500 received badge  Supporter (source)
2012-11-19 18:40:24 -0500 asked a question Displaying Topics as Nodes in rxgraph

Can someone explain for me why topics in rxgraph are shown as edges, rather than a different type of node? For instance, if you only have one publisher and subscriber on a particular topic, then it makes sense to represent that relationship as an edge. However, if you have multiple publishers/subscribers on a topic, it seems like a lot of redundant edges are created, since the underlying relationship is more like a directed hypergraph than a normal digraph. Here's a trivially simple example from rxgraph (sorry, it won't let me upload images directly):

i49.tinypic.com/np1185.png

It would make more sense to me to lay it out like:

i47.tinypic.com/12216w9.png

Service calls would still be regular edges, though.

Forgive me if the answer is obvious; I've only been using ROS for about a week now.


Dot file contents for original:

digraph G {
  rankdir=LR;
  _rosout [label="/rosout", URL="node:/rosout"];
  _rviz_bag [label="/rviz_bag", URL="node:/rviz_bag"];
  _my_pcl_tutorial [label="/my_pcl_tutorial", URL="node:/my_pcl_tutorial"];
  _play_bag [label="/play_bag", URL="node:/play_bag"];
    _play_bag->_rviz_bag [label="/tf"]
    _play_bag->_rosout [label="/rosout"]
    _my_pcl_tutorial->_rosout [label="/rosout"]
    _rviz_bag->_rosout [label="/rosout"]
    _play_bag->_my_pcl_tutorial [label="/camera/rgb/points"]
    _play_bag->_rviz_bag [label="/camera/rgb/points"]}

Dot file contents for suggestion:

digraph G {
  rankdir=LR;
  node [shape="box"];

  _rosout [label="/rosout", URL="node:/rosout"];
  _rviz_bag [label="/rviz_bag", URL="node:/rviz_bag"];
  _my_pcl_tutorial [label="/my_pcl_tutorial", URL="node:/my_pcl_tutorial"];
  _play_bag [label="/play_bag", URL="node:/play_bag"];

  _camera_rgb_points_topic [label="/camera/rgb/points" shape="ellipse"];
  _rosout_topic [label="/rosout" shape="ellipse"];
  _tf_topic [label="/tf" shape="ellipse"];

    _play_bag->_tf_topic
    _tf_topic->_rviz_bag
    _play_bag->_rosout_topic
    _my_pcl_tutorial->_rosout_topic
    _rviz_bag->_rosout_topic
    _rosout_topic->_rosout
    _play_bag->_camera_rgb_points_topic
    _camera_rgb_points_topic->_my_pcl_tutorial
    _camera_rgb_points_topic->_rviz_bag}