It would be helpful to update the stretch_simulation installation guide to be de-coupled from having to set up a robot environment.
Currently to set up stretch_simulation, the user has to run a modified stretch_create_ament_workspace.sh script that sets up a dummy robot ID and fleet path in ~/stretch_user, and also installs the dependencies for all the packages in stretch4_ros2, then runs colcon build. A user running stretch_simulation likely only needs the stretch_simulation and stretch_nav2 packages.
It would be a good idea to identify a more simple path for installation to improve the usability of stretch4_mujoco with ros2.
It would be helpful to update the stretch_simulation installation guide to be de-coupled from having to set up a robot environment.
Currently to set up stretch_simulation, the user has to run a modified stretch_create_ament_workspace.sh script that sets up a dummy robot ID and fleet path in ~/stretch_user, and also installs the dependencies for all the packages in stretch4_ros2, then runs colcon build. A user running stretch_simulation likely only needs the
stretch_simulationandstretch_nav2packages.It would be a good idea to identify a more simple path for installation to improve the usability of stretch4_mujoco with ros2.