AUTO-SYNC Index refreshed every 12h · Evidence-linked
Data release v20260914_020943 Generated 2026-09-14 Methodology Report missing resource
Data checked 2026-08-13. Data may be stale - beyond the review cycle. Review cycles are documented on the Methodology page. Methodology

ctu-mrs/mrs_uav_core

Algorithm Tier A slam_vio BSD-3-Clause
Official confirmed

MRS UAV Core is CTU MRS's ROS metapackage for UAV control, state estimation, trajectory generation and tracking, bundling PX4 integration and simulation tooling.

Engineering Snapshot

Use cases & tasks 7
Best suited for
  • ROS-based UAV autonomy development
  • Teams needing a bundled control, state estimation, trajectory, and PX4 integration stack
  • Research/testbed systems that also require simulation tooling
Primary tasks
  • UAV state estimation integration
  • Trajectory generation and tracking
  • PX4-based UAV control integration
  • Simulation tooling for UAV autonomy
Stack & ecosystem
Resource type
Algorithm
Ecosystem
control · deployment · drone · estimation · generation · trajectory
License & compliance
License
BSD-3-Clause (Inferred)
Lifecycle & freshness Show
Maintenance
Active
Latest version
Not recorded
Last activity
2026-07-16
Last checked
2026-08-13
Verification
Official confirmed

What It Solves

Assembling a complete UAV autonomy system typically requires separately integrating state estimation, trajectory generation/tracking, PX4 control, and simulation tooling; MRS UAV Core is a ROS metapackage that bundles these concerns for CTU MRS UAV systems.

Primary use cases

  • UAV state estimation integration
  • Trajectory generation and tracking
  • PX4-based UAV control integration
  • Simulation tooling for UAV autonomy

Secondary use cases

  • Reference architecture for ROS/PX4 UAV metapackages
  • Educational platform for UAV autonomy stack composition

When to Use

Consider when

  • You are building a ROS-based UAV autonomy stack
  • You need maintained integration of control, estimation, trajectory, and simulation components
  • You want a metapackage approach to reduce wiring effort around PX4
  • You can audit exact dependencies and compatibility before adoption

Verify before adopting

  • Exact ROS distribution and PX4 firmware versions supported
  • License confirmation (currently inferred BSD-3-Clause)
  • Latest version/release and changelog availability
  • Simulation tooling dependencies and hardware requirements
  • Compatibility with your UAV platform and sensors

Start Here

github https://github.com/ctu-mrs/mrs_uav_core github https://github.com/ctu-mrs/mrs_uav_system

Adoption Checklist

  • Needs verification Exact ROS distribution and PX4 firmware versions supported
  • Needs verification License confirmation (currently inferred BSD-3-Clause)
  • Needs verification Latest version/release and changelog availability
  • Needs verification Simulation tooling dependencies and hardware requirements
  • Needs verification Compatibility with your UAV platform and sensors

Each check stays "needs verification" until an official source confirms it; unconfirmed items are never marked verified.

Known Limitations & Unknowns

Known limitations

  • No latest version or release date in the resource record
  • License is inferred, not explicitly confirmed
  • No benchmark, performance, or production-readiness data in source_refs
  • Supported hardware and ROS/PX4 compatibility are not listed in the record
  • Maintenance status is based only on repository activity

Not publicly verified

  • Exact ROS distribution compatibility
  • PX4 version compatibility
  • Concrete hardware and sensor requirements
  • Full dependency graph and installation procedure
  • Detailed scope of components inside the mrs_uav_core metapackage

Alternatives & Related Tools

Related tools

How is it used?

Start from the recorded entry points below, then validate against the technical checklist.

Technical checklist

  • OK License identified Recorded: BSD-3-Clause
  • OK Maintenance signal Active
  • OK Verification status Official confirmed
  • OK Source evidence attached 1 source record(s)
  • NEEDS REVIEW Latest version recorded Not recorded

Official Links

Metadata & Governance

License BSD-3-Clause — Inferred
Commercial modelUnknown
Maintenance statusActive
Verification status Official confirmed — Confirmed via the official repository API responses in SourceRefs below.
Latest versionNot recorded
Latest releaseNot recorded
Last activity2026-07-16
Last checked2026-08-13
First seenNot recorded

Dataset facts

Facts above come from the official dataset card only; unconfirmed fields stay unknown.

Related Resources & Dependencies

Recent Activity

Related Knowledge

Guides

Collections