jwhendy's profile - activity

I was using this parameter and had been a long time since I updated my system. Everything was working, then it wasn't. I

On other wiki's I've contributed to, there is often a discussion method. I'm happy to help with changes, but being new to ROS I second guess whether or not these changes would be helpful or even accurate. Is this site appropriate, should I be doing this on the discussion forums, other?

As an example, I stumbled on this question about ROS_INFO_STREAM and actually don't think it's a horrible question in principle. I'm quite new, and was looking for a handy equivalence table between ROS_VERBOSITY_TYPE and equivalent rospy.logVerbosity() calls using python. In looking through the wiki on logging, I think it would help to provide the base format up front:

ROS_VERBOSITY_TYPE

As it is, a beginner has to figure out that DEBUG in all of the examples could be any of the other verbosity levels. Also, I noticed that the intro says:

roscpp uses the rosconsole package to provide its client-side API. That API takes the form of a number of ROS_ macros:

rosconsole provides four different types of logging statements, at 5 different verbosity levels, with both printf- and stream-style formatting.

I think the "types" are what are spelled out next, but this yields a list much longer than 4: base, named, conditional, conditional named, once, throttle, delayed throttle, filter.

I could make various changes to remedy this... but it helps to have confirmation that I'm not just experiencing noob confusion and the things that don't make sense are legitimate. Thanks for any suggestions.

@felipeduque just as above. They key is that instead of using the code here, use the code here. Because the static trans

Should ROS msg/srv files end in a newline? I was perplexed on a recent commit preview to see this symbol on github after

Should ROS msg/srv files end in a newline? I was perplexed on a recent commit preview to see this symbol on github after

Thanks for the reasoning. This is indeed a narrow use case. For the purpose of storing metadata, the field name doesn't

It seems that answer is "Yes," so now I know. For this particular scenario it seemed "heavy" to do this when I really ju

@gvdhoom: the question was prompted by the fact that a foo msg corresponding to some Foo.msg can be used as a foo[]. Is

Creating an array/list of existing message type without defining custom message type? Is there a way to create an array

Creating an array/list of existing message type without defining custom message type? Is there a way to create an array

Agreed. I now think that since I downgraded cmake via arch archive binaries, it was likely compiled against previous ver

I just closed that, and this is marked as an answer already.

The tf2 tutorial on static frames abruptly ends without explaining this:

if __name__ == '__ STATIC main__':
    rospy.init_node('my_tf2_broadcaster')

I've never seen __ STATIC main__ and from googling I can't tell if it's a ROS specific thing or general python syntax. I get no hits for it exactly, so I'm wondering if it's a typo. If so and it should be '__main__', I'm still confused as it would appear the second block would never run.

Could someone clarify that section of code?

While maybe not a ROS bug, others are wrestling with this here too.

Ran into this same issue. I also ended up needing to downgrade to boost and boost-libs 1.68.0-2 instead of the current 1

So that's what I meant by misleading. The answer isn't wrong, it just dangled hope before me but when I looked at the li

For the answer, it seems simpler to write the details of the method in addition to linking vs. just linking with ambiguo

I interpreted the question to be about modifying a file. I haven't tried, and wouldn't recommend, but foo = bag(file.bag

Add to an bag you just created in w mode or add to a file by opening and appending? The latter is not possible

In other words, the first sentence is misleading and I think should be "You can't do this in place. You have to create a

In other words, the first sentence is misleading and I think should be "You can't do this in place. You have to create a

Based on the rosbag API link (which only provides the 'w' option for writing, and this erases an existing bag) and the m

I'm very new to ROS and am [slightly] more versed in python than C++, so that's the route I'm currently pursuing in my learning. One option that is shown in the C++ tutorials is how one would set a custom namespace or parent namespace :

You can also specify a parent NodeHandle and a namespace to append:

### adding the initialization call from above
ros::init(argc, argv, "my_node_name");

ros::NodeHandle nh1("ns1");
ros::NodeHandle nh2(nh1, "ns2");

In the python information, I've only ever seen this used, which I take as equivalent to ros::init():

rospy.init_node('my_node_name')

How would one put node my_node_name into a custom or parent namespace using rospy?

Super late, and this is more of a general python question, but you can avoid global variables by just passing things aro

Super late, and this is more of a general python question, but you can avoid global variables by just passing things aro

Thank you for clarifying and the PR was immensely helpful to understanding what was going on. I now see that this is jus

I just learned of the new Jade xacro macros as part of a PR I submitted. In switching to using ${radians(foo)}, the build failed. In comparing to other robots in the kuka_experimental repository, I found a few differences, one of which being the --inorder flag. I was informed that these new Jade macros require --inorder, but I didn't see that on the wiki.

I've updated the wiki on math expressions to suggest using --inorder, but I'm still a bit confused by the behavior and thought I'd bring it here in case there were further doc changes that might be helpful.

For one, I updated two robot macros.xacro files to use ${radians()} for their joint limits. One failed (linked above), and one succeeded. Changing the first to use --inorder fixed the build error. The second still doesn't have it, yet this somehow passes the build?

<launch>
  <param name="robot_description" command="$(find xacro)/xacro.py '$(find kuka_lbr_iiwa_support)/urdf/lbr_iiwa_14_r820.xacro'" />
</launch>

Secondly, the wiki suggests that one can test whether or not this flag affects their xacro files with:

rosrun xacro xacro file.xacro > /tmp/old.xml
rosrun xacro xacro --inorder file.xacro > /tmp/new.xml
diff /tmp/old.xml /tmp/new.xml

I assumed that if --inorder was the source of issues, I'd detect it with this test? In trying that on lbr_iiwa_14_r820_macro.xacro and lbr_iiwa_14_r820.xacro in this branch of kuka_experimental, I get no results for either using diff (identical output).

Could someone with more macros experience help illuminate what's going on here and suggest any changes I could make to the wiki to help others? I found this to be pretty nuanced/subtle, and it caused maybe an hour of trying random things, waiting for a Travis build, and repeating. It'd be nice to help other users avoid this.

Understanding relationship between new xacro macros and --inorder I just learned of the new Jade xacro macros as part of