Clarification on Integrating New Features into Robotics Infrastructure Repository

[Tanishq30052002]

Hello everyone,

I hope this message finds you well. I've encountered a query regarding the project's directory structure and the incorporation of new features.

I've observed that the robots are managed within a separate Git repository distinct from the Robotics Academy's repository. In light of this, would it be advisable for us to integrate any new features directly into the Robotics Infrastructure repository?

Furthermore, I'm curious about how these changes will be reflected in the exercises. Given that modifications will be made locally within the repository, what would be the best practice to ensure these changes are effectively synchronized with the exercises?

I appreciate any insights or guidance you can provide on this matter. Thank you for your time and assistance.

Best regards,
Tanishq

[jmplaza]

All the robot models, scenarios, launch files etc.. are stored in RoboticsInfrastructure repo. This way they can be used from other tools such as VisualCircuit or BT-Studio.

Yes, if you improve a robot model or scenario for one RoboticsAcademy (RA) exercise the changes should be located at RoboticsInfrastructure repo. Also new robot models and new Gazebo worlds are also welcome. From RoboticsAcademy they will be referenced as a robotics universe. Each RA exercise has a robotics universe at least. It may even have several ones, for instance in FollowLine exercise several different circuits. They are referenced in the RA exercise database.

Hope it helps,

[pawanw17]

The method I posted was for a considerably large change/ final testing before making a PR. When I need to do quick testing of my changes, I simply open a RADI in debug mode (--debug ) flag, make changes and
run the application using
./entrypoint.sh
if things turn out well then great else I press Ctrl + c and run ./kill.sh (only present in Humble RADI afaik) and inspect what went wrong

[pawanw17]

I also often use docker exec to open multiple terminals to a RADI for testing and debugging purposes

docker exec -ti <container name> bash

you can find the container name using
docker ps

[Tanishq30052002]

so, you mean you do changes in the container itself. Right?

[pawanw17]

That's right

[Tanishq30052002]

ok