0
$\begingroup$

Rosanswers logo

For some complicated Roslaunch setups, it can be tough to figure out where a parameter came from. I've added the following line to each YAML file and it helps me tremendously. The tag is "source" and the value is the YAML file name:

For example in arm.yaml: source: arm.yaml

When ROSLaunch executes, you'll see the parameters print out something like this and you can immediately tell where the params came from.

  • /arbotix/joints/gripper_joint/max_angle: 0
  • /arbotix/joints/gripper_joint/max_speed: 50
  • /arbotix/source: arm.yaml
  • /arbotix/write_rate: 25

Does anyone see a downside to this or better approach?


Originally posted by corb on ROS Answers with karma: 339 on 2014-12-04

Post score: 0

$\endgroup$

1 Answer 1

0
$\begingroup$

Rosanswers logo

I'd suggest bringing this up with the roslaunch SIG, where it can be discussed in detail. It may be possible to build a feature like this into roslaunch - a few other additions have been made recently to make launch files easier to understand and debug.


Originally posted by Dan Lazewatsky with karma: 9115 on 2014-12-05

This answer was ACCEPTED on the original site

Post score: 1


Original comments

Comment by corb on 2014-12-05:
Thanks - will do

$\endgroup$

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.