The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
This is not a standard for package layout, but for naming.
If there is a standard, it would be REP-144 - ROS Package Naming. Under section Naming Rules, it says:
Special Suffixes:
- a package containing the URDF and meshes of a robot should be named
<name_of_the_robot>_description, e.gpr2_description
So this basically says: packages with robot models should be called X_description.
That is most likely what the tutorial you linked refers to.
| | 2 | No.2 Revision |
This is not a standard for package layout, but for naming.
If there is a standard, it would be REP-144 - ROS Package Naming. Under section Naming Rules[Naming Rules](REP-144 - ROS Package Naming, it says:
Special Suffixes:
- a package containing the URDF and meshes of a robot should be named
<name_of_the_robot>_description, e.gpr2_description
So this basically says: packages with robot models should be called X_description.
That is most likely what the tutorial you linked refers to.
| | 3 | No.3 Revision |
This is not a standard for package layout, but for naming.
If there is a standard, it would be REP-144 - ROS Package Naming. Under section [Naming Rules](REP-144 - ROS Package Naming, it says:
Special Suffixes:
- a package containing the URDF and meshes of a robot should be named
<name_of_the_robot>_description, e.gpr2_description
So this basically says: packages with robot models should be called X_description.
That is most likely what the tutorial you linked refers to.
Edit:
Thanks. I'm lost with this. It's hard to start learning ROS.
Note btw: I just referred to the REP as it's a convenient document. The custom / convention of naming pkgs with robot models in them description packages has existed since long before REP-144 was written.
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.
