ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2020-11-08 15:47:57 -0500 | received badge | ● Guru (source) |
2020-11-08 15:47:57 -0500 | received badge | ● Great Answer (source) |
2019-07-11 05:08:16 -0500 | received badge | ● Enlightened (source) |
2017-02-13 02:19:42 -0500 | received badge | ● Good Answer (source) |
2017-02-09 03:37:29 -0500 | received badge | ● Nice Answer (source) |
2016-10-26 08:02:25 -0500 | received badge | ● Necromancer (source) |
2016-06-04 02:25:06 -0500 | received badge | ● Teacher (source) |
2016-06-04 02:25:06 -0500 | received badge | ● Necromancer (source) |
2016-06-03 21:50:58 -0500 | answered a question | Alternatives for (not working) nested substitution arguments for roslaunch See my answer to a similar question here: http://answers.ros.org/question/35283... This is now made possible by a feature added to roslaunch version 1.12.1, released April 18, 2016. (ATM the debian repos are at version 1.12.0, so you'll either have to wait or download the github sources) roslaunch 1.12.1 adds support for evaluation of arbitrary python expressions using the syntax |
2016-06-03 19:58:17 -0500 | answered a question | nested substitution args in launch files A solution to this problem has been added to roslaunch version 1.12.1, released on April 18, 2016. (ATM the debian repos are at version 1.12.0, so you'll either have to wait or download the github sources) roslaunch 1.12.1 adds support for evaluation of arbitrary python expressions using the syntax args are available as python variables, so the following is equivalent: |