Documentation of current state 2024 #53
Comments
afr2903
added a commit
that referenced
this issue
Nov 20, 2024
Fixes #53 Add detailed documentation of the current state of 2024, including the purpose of each ROS node and examples. * **README.md**: Add sections for achievements from 2024, integration, and examples of ROS nodes' purposes. * **ws/src/frida_task_manager/README.md**: Add detailed documentation on the purpose of each ROS node, the technologies used, and examples of their usage. Include a detailed example of a task flow for the `receptionist_task_manager.py` node. * **docker/README.md**: Add examples and detailed explanations of the ROS nodes. * **DOCUMENTATION.md**: Add a new file with a detailed overview of the purpose of each area in the service robot and the technologies used. Include examples of each ROS node's purpose and a detailed example of a task flow for the `receptionist_task_manager.py` node. --- For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/RoBorregos/home/issues/53?shareId=XXXX-XXXX-XXXX-XXXX).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Documentation of current state 2024
Based on the ROS nodes to be executed for the different tasks, clear and thorough documentation should be generated, including the purpose of the area in the service robot and further explanation of the technologies used, with examples.
This is the overview of the robot and the area:
Achievements from 2024
This year, after being accepted to participate in RoboCup 2024 held in Eindhoven, Netherlands, the team focused in developing a robust and reliable set of software modules, tailored to the specific needs for the tasks for the updated rulebook. This approach, had the purpose of showcasing a functional robot for both the Mexican Robotics Tournament (April; Monterrey, Mexico) and the RoboCup (July; Eindhoven, Netherlands).
The robot was renamed as FRIDA (Friendly Robotic Interactive Domestic Assistant), an acronym reflecting the purporse of the robot, and the name in reference to Mexican culture.
With the vast knowledge acquired during the international tournament, the team defined the new objectives for the remainder of the year to be: an increased focus in research and literature review, and centralized and offline refactorization of the software and systems.
Integration
Software Architecture
A new empty repository was created, alongside separate repositories for each area, added as submodules of the first. This allowed us to work of different branches of development in the central computational unit (Jetson AGX inside robot).
Every submodule was containerized, using Docker, to ease the installation process and dependency management.
Task manager
A new package named task_manager was created to handle the flow of each task using general python submodules per area.
There's a Python ROS node for each task, following a state machine architecture.
The text was updated successfully, but these errors were encountered: