Convention for Directory Structure of CustomRobots

I am trying to achieve the Noetic-RADI with minimal changes to the existing Melodic-RADI.


This error is resolved by modifying the GAZEBO_MODEL_PATH in the Dockerfile as the models are located at different relative directory locations in melodic and noetic branches. Can we maintain a convention for the directory tree of CustomRobots? This is a minor point, but I feel it will reap compounded benefits later on with multiple exercises.

Yes, in the future we will converge towards the same convention for melodic and noetic branches of CustomRobots. For now it is important to have a prototype of noetic-RADI running, with the current organization of noetic branch of CustomRobots repository as is. We will face the convergence iterating that running noetic-RADI.

1 Like