Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Open-source MAVLink fleet operations for PX4: SITL, drone shows, search and rescue, cooperative autonomy, and field validation
| Date | Stars |
|---|---|
| 2026-07-24 | 307 |
| 2026-07-25 | 308 |
| 2026-07-28 | 308 |
| 2026-07-30 | 308 |
| 2026-08-06 | 308 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
15.0
growth rate 0.00%/day
# MDS - Mission-Directed Swarm **Open-source MAVLink fleet operations for PX4 drones, SITL, drone shows, SAR, and cooperative autonomy.** [](CHANGELOG.md) [](LICENSE) [](docs/guides/python-compatibility.md) [](https://px4.io/) [](https://mavsdk.mavlink.io/)  MDS began as MAVSDK Drone Show and now covers a broader PX4-oriented fleet stack: drone-side runtime, GCS/backend services, React operator dashboard, SITL, real companion computers, sidecar connectivity, and mission execution workflows. It is built to stay simple enough for a quick SITL demo while remaining structured enough for serious multi-drone validation, operations, and custom deployments. ## What MDS Covers - **Offline drone shows** with SkyBrush-imported trajectories and synchronized execution - **Smart swarm missions** with live leader-follower coordination and runtime control - **QuickScout SAR / recon** with multi-drone coverage planning and PX4 Mission Mode execution - **Unified operations tooling** with SITL, GCS services, Swarm Trajectory planning, and live/historical logs MDS is a field-operations and research platform, not certified avionics. Flight testing requires qualified operators, local aviation compliance, geofencing, failsafe review, and independent safety validation. ## Start Here | If you want to... | Start here | |-------------------|------------| | run the first demo quickly | [SITL Comprehensive Guide](docs/guides/sitl-comprehensive.md) | | import and launch a drone show | [Drone Show Guide](docs/features/drone-show.md) | | run Smart Swarm from the dashboard | [Smart Swarm Guide](docs/features/smart-swarm.md) | | author, process, and launch a Swarm Trajectory mission | [Swarm Trajectory Guide](docs/features/swarm-trajectory.md) | | point MDS at a customer/private repo | [Custom Repo Workflow](docs/guides/custom-repo-workflow.md) | | install a GCS on a VPS or Ubuntu box | [GCS Setup Guide](docs/guides/gcs-setup.md) | | deploy real drone hardware | [MDS Init Setup Guide](docs/guides/mds-init-setup.md) | | build or ship a validated custom SITL image | [SITL Custom Release Workflow](docs/guides/sitl-custom-release-workflow.md) | | browse everything else | [Documentation Index](docs/README.md) | ## Quick Demo Start with the **[SITL Comprehensive Guide](docs/guides/sitl-comprehensive.md)**. It covers the official SITL archive, validation, bootstrap, dashboard launch, and the current dashboard-first SITL Control workflow. For normal demos, use the dashboard **SITL Control** page to reconcile/start SITL drones instead of copying low-level shell commands from the README. Shell and `make` wrappers still exist for automation and advanced operators; see the **[Operator Makefile Guide](docs/guides/operator-makefile.md)** when you need scripted control. The dashboard launcher keeps the FastAPI backend single-process by default, so telemetry, heartbeats, command tracking, and other in-memory operational state stay coherent during live SITL runs. Backend auto-reload is only for backend code editing; the SITL guide covers that advanced mode. For the stock official SITL package, Mission Config starts from the tracked Azadi Stadium demo origin in `data/origin.sitl.default.json`. If you later set a different origin in the dashboard or via the API, MDS writes a local runtime override to `data/origin.json` on that server. Remove that local file when you want the stock Azadi default to apply again. For the default official HTTPS demo path, the GCS now treats git write-back as disabled by default (`MDS_GIT_AUTO_PUSH=false`). That keeps imports/config saves clean on read-only eval
Excerpt of 10,687 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
matched fp:ad26d2124352dbe8, topic:robotics, name:drone, desc:drone
matched fp:ad26d2124352dbe8, topic:telemetry
matched fp:ad26d2124352dbe8, topic:ai-agents