| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Writing a xacro file is more about making creating a maintainable file than an efficient one. The only ROS package (AFAIK) that reads xacro files is xacro, which converts them to macroless URDF. So you don't gain anything computationally from making a xacro. In fact, you lose some small bit of efficiency by dynamically generating from a xacro.
However, what you gain is maintainability. By creating macros and constants, you make it easier to edit and add to an existing model. If you're done creating your model, and are confident it won't change, then there's probably no need. Otherwise, you'll probably end up saving time in the long run if you create a xacro.
Another motivation of xacro was to save us from retyping repeated URDF blocks. For example the PR2 caster xacro is defined once and referred to 4 times.
Also, if you find yourself working with subcomponents of a robot a lot, having xacro modules means not having to copy and paste the particular component you are working with from the master URDF file into your own project. Plus, by referring to xacros instead of copy/pasting URDF blocks, any updates to the master URDF is automatically reflected in your project.
Asked: 2011-02-14 15:32:09 -0600
Seen: 1,901 times
Last updated: Feb 16 '11
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
