dronomy
## The Crisis ROS1 (Robot Operating System 1) reached end-of-life in May 2025.
Core trick
Static analysis catalogs ROS1 API usage across packages, then an LLM rewrites code and retries colcon builds up to three times.
Description
## The Crisis
ROS1 (Robot Operating System 1) reached end-of-life in May 2025. Yet thousands of production robotics codebases — autonomous drone flight stacks, warehouse robots, surgical systems, defense platforms — are still running on it. Security patches have stopped. Community support is gone. The clock is running.
The robotics industry knows it needs to migrate. Nobody has a good way to do it.
README excerpt
# ROS1 → ROS2 Migration Analysis Agent
<img width="714" height="681" alt="Screenshot 2026-04-19 at 10 57 53 AM" src="https://github.com/user-attachments/assets/ceefeb73-38e5-4a60-8c53-1c5818f513d4" />
The dashed red loop shows the eval-correct cycle — when colcon reports errors, the agent reads them, calls o4-mini again, and retries up to 3 times before moving on.
> **AI-Native Development Lifecycle** — Feasibility Analysis Phase
> Agent: `ros1_analyzer.py` | Stack: dronomy.io / Vectorblock / AdaBoost AI
---
## Overview
This agent walks through 4 KumarRobotics MAV repositories, performs a deep static analysis of all ROS1 usage patterns, and generates:
- **Individual markdown report** per repository
- **Master feasibility report** with cross-cutting pain points and migration roadmap
- **JSON data** per repo for downstream processing
The lifecycle follows the **AI-Native Development Lifecycle** diagram:
```
Ideation (you spec the work)
↓
Code Generation (agent writes all analysis code)
↓
Code Review (agent + human review findings)
↓
Validation (agent tests end-to-end)
↓
Build/Test failures → Incident Response → back to Ideation
↑_______________ Agent Orchestrator _______________↑
```
---
## Repositories Analyzed
| Repo | Role |
|------|------|
| `kr_autonomous_flight-master-2` | Full autonomy stack — state machine, planning, estimation, sim |
| `kr_mav_control-master` | MAV control: SO3 controller, trackers, interfaces, simulator |
| `msckf_vio