List view
### Final Testing, Documentation, Project Wrap-Up & Community Handover (Week 44-2026 to Week 52-2026) #### Comprehensive System Testing - Perform thorough final testing to ensure the system’s reliability and functionality across all components. #### Finalize Project Documentation - Complete the final set of user guides, technical documents, and API references. #### Readiness for Deployment - Ensure the system is fully ready for deployment, with all components integrated and functioning properly. #### Transition to Community-Driven Development - Handover long-term project management to the open-source community, setting up governance and contribution guidelines. #### Research Paper Preparation & Submission - Finalize and submit research paper on advancements in human-robot interaction, showcasing key developments and innovations. #### Final Project Completion & Community Hand-off - Officially complete the project and transition it to the open-source community for continued development. --- ### Long-Term Community Support - **Continuous Feature Enhancements** – Support community-driven feature additions and improvements. - **Monitoring & Maintenance** – Monitor system performance and handle emerging issues or bugs. - **Future Project Evolution** – Explore further enhancements, collaborations, and potential new development areas.
Due by December 31, 2026### Final Optimizations & Integration (Week 36-2026 to Week 43-2026) #### Final Performance Optimizations - Optimize system speed, stability, and resource usage. #### Ensure Complete Integration - Confirm that all system features are fully integrated and operational for the final testing phase. #### Prepare for Final Testing Phase - Complete preparations for a full-scale deployment testing cycle.
Due by October 25, 2026### Open-Source Community Contributions (Week 28-2026 to Week 35-2026) #### Encourage and Manage Contributions - Engage with the community and manage contributions efficiently through GitHub. #### Community-Driven Testing and Iterative Development - Incorporate community feedback to refine the system and encourage ongoing development.
Due by August 30, 2026•0/3 issues closed### Pre-Release & Final Refinements (Week 20-2026 to Week 27-2026) #### Finalize All Features and Configurations - Ensure that all core features are stable and fully functional. #### Conduct Final Rounds of User Testing - Perform final usability and stress tests with a focus on fixing critical issues. #### Finalize All System Integrations - Finalize integration for web, AI, teleoperation, and other components.
Due by July 5, 2026### Advanced Testing & Community Involvement (Week 12-2026 to Week 19-2026) #### Testing and Validation with InMoov Platform - Perform extensive testing with the InMoov platform, focusing on system integration and functionality. #### Community Contributions via GitHub - Collect community-driven feedback and contributions. - Review pull requests, manage issues, and implement improvements from the community. #### Implement Additional Interface Nodes for Diverse Command Sources - Introduce new interfaces for control, such as mobile apps, voice commands, and custom hardware setups.
Due by May 10, 2026•1/1 issues closed### System Enhancements & Optimization (Week 04-2026 to Week 11-2026) #### Enhance Security Features - Refine security protocols, including encryption, authentication, and secure communication. #### Add Additional Control Sources (Teleoperation, Advanced AI) - Introduce teleoperation for real-time control by humans. - Integrate advanced AI features like natural language processing for intuitive control. #### Improve Integration with InMoov Platform - Improve communication and synchronization between LUCY and InMoov hardware.
Due by March 15, 2026## First Major Release & Documentation (Week 48-2025 to Week 03-2026) ### First Open-Source Release of LUCY ROS 2 Package with Core Functionality - Release the first version of the LUCY ROS 2 package to the open-source community. - Include installation instructions, documentation, and example use cases. ### Full Documentation of the Framework, Nodes, and Usage Instructions - Complete and publish full documentation: technical descriptions of the system, node setup instructions, usage guidelines. ### Collect Early Community Feedback - Actively collect user feedback via GitHub, forums, and early adopters. - Address issues identified in the initial release and improve documentation.
Overdue by 7 day(s)•Due by January 18, 2026## Web Client & AI Interface Integration (Week 40-2025 to Week 47-2025) ### Development of Web Client for Control via Browser - Develop a web-based interface allowing users to control LUCY robot remotely via a browser. - Implement live sensor feedback, control panel for actuators, and basic feedback mechanisms (e.g., button presses, sliders). ### Implement AI Interface Node (Integration with HuRI, GR00T) - Integrate advanced AI models like HuRI and GR00T for improved decision-making and human-robot interactions. - Enable features such as speech recognition, context understanding, and interactive learning. ### Initial Testing of Web-Based and AI-Driven Control - Test AI-based control, ensuring that commands are executed correctly via the web interface. - Perform initial tests of AI-driven responses and human-robot communication.
Overdue by 2 month(s)•Due by November 23, 2025•0/2 issues closed## Simulation Testing & Refinement (Week 32-2025 to Week 39-2025) ### Full Implementation of Simulation Suite - Integrate testing scenarios including interaction with objects, movement, and human presence in simulation. - Perform end-to-end system testing in the simulation environment, iterating based on results. ### Testing & Debugging of Sensor-Actuator Control Loop - Test the responsiveness of actuators based on sensor input, identifying potential delays or inaccuracies. ### Refine Simulation Environment for Better Accuracy - Continue enhancing the accuracy of sensor simulations and robot interactions. - Implement additional testing scenarios for more complex real-world simulations.
Overdue by 3 month(s)•Due by September 28, 2025## Computer Vision Node Development & Integration (Week 24-2025 to Week 31-2025) ### Develop the Computer Vision Node (Movement Detection, Object Detection) - Implement libraries for movement tracking, and object detection. - Integrate computer vision models (e.g., OpenCV, deep learning models) for robot interaction. ### Integrate Sensor Data Flow - Ensure smooth data flow from sensors (camera, LIDAR). ### Initial Testing of Environmental Awareness and Security Functionality - Test security features such as person detection. - Evaluate early performance of computer vision algorithms and sensor-actuator integration.
Overdue by 5 month(s)•Due by August 3, 2025## Controller Manager Implementation (Week 16-2025 to Week 23-2025) ### Implementation of Micro-Controllers Firmwares - Implement actuators control class. - Implement sensors reading class. - Implement USB serial tx/rx communication class. ### Implementation of the CM (Controller Manager) Node and URDF Updating - Implement basic CM node. - Update the URDF: - Add xacro `ros2_control` labels. - Load hardware configuration to fill xacro URDF template with actuators limits. - Test generated custom URDF. ### Implementation of the CM Interfaces and Security Node - Implement USB serial CM interfaces for: - Micro-controllers. - Other peripherals (cameras, speakers, microphones, LIDAR). - Create security node: - Implement control commands verification (check if control command is in the range of hardware configuration limits). - Manipulation specific verification: use fingers pressure sensors to allow hand closing & opening. - Implement general shutdown command and handling. - Implement communication between security node and CM node. ### Simulation Environment Setup - Extend the URDF-based simulation to test actuators control and sensor responses. - Test communication between security node, controller manager node, and digital twin.
Overdue by 7 month(s)•Due by June 8, 2025•5/12 issues closed# Kickoff & Initial Setup (Week 08-2025 to Week 15-2025) Formation of the Project Team - Assemble the project team, consisting of six developers working one day per week. - Assign roles based on expertise (development, testing, project management). Establishment of Project Scope and Goals - Define primary objectives: Human-robot interaction, advanced robotics capabilities, and open-source goals. - Clarify the long-term vision: InMoov platform integration, system performance, and community development. Initial Setup of the Development Environment - Set up cloud-based infrastructure (e.g., GCP, AWS, Azure) and version control (GitHub). - Create shared documentation repository (Docmost). - Provide all developers with access to ROS 2, simulation tools, and cloud resources. - Configure continuous integration (CI) pipelines. - Benchmark of multiple technologies, such as cloud providers: High-Level Design and Planning - Create initial architectural diagrams and technical specifications. - Plan hardware and software integration points for flexibility. - Develop project timeline with milestones, sprint goals, and deadlines. Simulation Setup - Create the URDF (Unified Robot Description Format) file of InMoov using Blender. - Implement the initial simulation environment for InMoov using URDF models.
Overdue by 10 month(s)•Due by March 30, 2025•4/4 issues closed