How dcocoma/frm-g5 works
Project type and purpose
• This is an academic “mono‑repo” for a Mobile Robotics course. It contains six independent lab assignments (Lab1…Lab4, plus Lab2a, Lab2b, Lab2c, Lab3).
• Each lab is a self‑contained exercise demonstrating robotics topics: basic algorithms (Lab1), ROS nodes (Lab2a), Arduino & EV3 integration (Lab2b), simple scripts (Lab2c), sensor data processing with MATLAB (Lab3), and EV3 mission planning (Lab4).
File structure
• Top‑level directories: Lab1, Lab2a, Lab2b, Lab2c, Lab3, Lab4. Each has subfolders “Code” or “src”, “Imgs”, sometimes “Datos” or “Vids”.
• Lab2a: a full ROS/Catkin workspace with src/pruebas (C++ & Python nodes), build/, devel/ and launch files—classic ROS node/topic architecture.
• Lab2b: Arduino sketches (EV3Test, Main, ROSTest), ros_lib.zip, an ev3_arduino Catkin package with Python HMI.
• Lab3: MATLAB code modules for LIDAR & ultrasound, plus CSV data.
• Lab4: EV3 mission scripts (.lmsp).
• Common pattern: each lab is an independent “service” or component.
README for additional insights
• The README only establishes authors and that this is a lab‑practice repository for “Fundamentos de Robótica Móvil” (2024‑I).
Detailed yet modular
• Break out only those subcomponents that have runtime interaction (e.g., publisher node, subscriber node, ROS Master).
• Keep each lab visually separate but show common conventions (all labs under the same repo).
• Avoid over‑splitting—only show directories that represent logical components or services.
Final advice
• Every component is labeled, data flows are clear, and build/deploy boundaries are indicated.