JdeRobot / JdeRobot/RoboticsAcademy

Testing for the Mobile Robotics exercises in direct ROS 2

Open
#3,911 6 comments 0 reactions 0 assignees View on GitHub
betatesting good-first-issue help wanted
Dominant language
Python
Stars
492
Forks
357
Avg merge
1h 58m
Merged PRs (30d)
25

Description

We would like to check that the Mobile Robotics course exercises work well when they are solved in direct ROS 2 mode, meaning that you write your own ROS 2 node instead of relying only on the HAL API. We want to confirm this both in Python and in C++, and we would really appreciate help from the community.

The exercises we would like tested are

- Basic Vacuum Cleaner
- Follow Line
- Obstacle Avoidance
- Global Navigation
- Laser Mapping
- Montecarlo Laser Localization

What we are asking is simple. Pick any of these exercises, try to solve it and run it in direct ROS 2 mode using Python and also C++, and tell us how it went. If everything works we would love to hear it, and if something does not work we want to know about it.

We are especially interested in three kinds of problems

- Anything in the documentation that is missing, outdated or unclear when you try to solve the exercise in direct ROS 2
- Any import in Python or any dependency in C++ that you needed but were not able to add, or that failed to build or import
- Any other bug or unexpected behaviour you run into

Please note that we are not asking for your solution code. We are only interested in your report and feedback, so there is no need to share how you solved the exercise.

When you report something, please tell us which exercise and which language you were using, describe what you did and what went wrong including the error message or a screenshot if you have one, and mention your environment such as the Docker image or RADI version. Thank you for helping us improve RoboticsAcademy

Contributor guide

Open the contributing guide

Research direction

Choose one listed Mobile Robotics exercise and run it in direct ROS 2 mode with both Python and C++. Start by following the exercise documentation, then record any missing or outdated guidance, import or build problems, and unexpected behavior with the exercise, language, error details, and environment. Done means reporting the results clearly; no solution code is requested.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, python
Domain
documentation, robotics, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.