How juanscelyg/mur works
Project type and purpose
• This “MUR” repo is a modular ROS-based robotics system. It includes:
• mur_arm: firmware and launch files for the robot’s manipulator arm (Arduino + ROS)
• mur_control: ROS control nodes, topic definitions, config files and launch scripts for real and simulated operation
• mur_description: URDF/XACRO models, meshes, and upload launches for robot visualization/simulation
• mur_navigation: SLAM and mapping launch files (gmapping, hector_slam)
• mur_server: a WebSocket/rosbridge server and an Angular web GUI to monitor/control the robot remotely
File structure
• Top-level packages correspond to logical subsystems: arm firmware, control logic, robot description, navigation, server/GUI
• mur_control is organized into cfg (dynamic_reconfigure), config (YAML/JSON), launch (sim/real/experiment), msg (custom ROS msgs), scripts (Python ROS nodes), src (common PID+utilities)
• mur_server/gui/udrobot is a standard Angular front-end, talking to ROS via rosbridge (launched by websocket.launch)
• Presence of CMakeLists.xml, package.xml, setup.py indicates pure ROS/Catkin Python and C++ packages
README for additional insights
• But naming and file layout imply a classic ROS multi-node distributed architecture