Research / Protocols
Methods
Models, acceptance criteria and the scope of each result.
01 / Planar point-agent simulation
Solver reliability
Six point agents, 100 steps, seven policies and four conditions; 16 seeds pair old projected and revised control. Independent audits reconstruct swept separation and actuator feasibility. Promotion requires zero revised physical failures, fewer uncertified steps, and progress/cost bounds in every case. Three acceleration excesses and frontier progress/cost failures retain the baseline. Hardening re-audited saved commands; it did not rerun episodes.
Interpretation & source data
Zero collisions is not a pass: three tiny actuator-acceleration excesses remain physical-audit failures, and frontier progress/cost gates fail. The primary baseline is old projected, not repulsion. Hardening v2 rechecked saved finite commands; it did not rerun these episodes or measure new runtime. Descriptive Student-t intervals within this condition/policy; no multiplicity correction or optimality proof.
Download recorded summary ↓02 / Independent Euler point-agent simulator
Imperfect state
An independent Euler simulator compares oracle, naive and uncertainty-aware controllers across six conditions, 16 seeds and 128 steps. Declared bounded errors constrain the aware controller; Gaussian probes are separate calibration, not mission trials. Acceptance requires safety and mission progress. Collisions remain, packet-drop outcomes worsen, and latency/combined progress stalls. This does not validate the frozen field planner.
Interpretation & source data
The uncertainty-aware controller is not safe: collisions remain, packet-drop outcomes worsen, and latency/combined progress stalls. This independent Euler toy simulator does not validate the frozen field planner. No promotion or Gaussian strict certification. Packet loss can worsen outcomes. Bounds assume declared bounded uniform support; Gaussian calibration is not an episode safety study.
Download recorded summary ↓04 / Planar survey simulation · USGS-derived scalar fields
Adaptive survey
Nine USGS patches are frozen into three train, three validation and three test locations. Development selects guarded_early; held-out comparisons use 16 paired seeds per location/horizon. Promotion requires clean selected/lawnmower safety and a negative Bonferroni one-sided RMSE upper bound in all six cells. None passes. Limited-time mean RMSE worsens at every test location. Other intervals are descriptive, not geography-wide inference.
Interpretation & source data
The development-only choice guarded_early fails all six lawnmower RMSE promotion bounds; limited-time mean RMSE is worse at all three test locations. Nine fresh USGS patches are split 3 train / 3 validation / 3 test, not a nationwide geography sample. Infrastructure hardening did not rerun episodes. Paired Student-t intervals are descriptive within each location/horizon; only lawnmower uses the six-cell Bonferroni promotion rule. Adaptive Lloyd bandit uses oracle evaluation reward. Per-patch normalization is not terrain sampling accuracy; DEMs are not obstacle or ecological maps.
Download recorded summary ↓05 / PX4 v1.17.0 · software-in-the-loop, not physical flight
PX4 SITL
Pinned, locally adapted native arm64 PX4 v1.17.0 runs one prerequisite mission, then three concurrent independent SIH worlds. The mission commands takeoff, north waypoint, hover, return, land and normal disarm. Acceptance uses preflight origin, ≤1.5 m position error, ≤1 m/s speed and ≤0.5 s sample gaps. Positions are estimator observations; no hardware or shared-world swarm physics is evaluated.
Interpretation & source data
Actual native arm64 PX4 v1.17.0, pinned and locally adapted—not the point simulator. One single prerequisite then three concurrent independent SIH worlds, NOT shared-world swarm physics. No hardware, external ground truth, real-flight fault injection, or deployment readiness is established. Older flights remain historical and are not pooled.
Download recorded summary ↓Data & measurement
Datasets & calibration
The adaptive-survey fields are nine public USGS 3DEP elevation patches, sampled to 32 × 32 values over 100 m between edge sample centers. Elevation is min–max normalized per patch. Output spacing is not native resolution or terrain accuracy; the source mosaic’s vertical datum remains unresolved.
Units, uncertainty & reproducibility
Elevation in metres is reconstructed as offset + normalized value × scale. Relative relief uses normalized value × scale. DEM-sensing RMSE describes synthetic observations of that field, not physical sensor calibration. DEMs are not obstacle, ecological or risk maps.
Observed area is a sampled footprint fraction. Squared-speed energy is a proxy, not joules. Pair-steps and agent-steps are exposure counts, not independent trials. Missing values remain null; unfinished completion times are not zero. Study-specific tables retain sample sizes and interval bounds.
Imperfect-state calibration uses 100,000 uniform and Gaussian draws plus 4,096 age-propagation probes, separate from the 288 mission episodes. A finite calibration sample cannot certify an unbounded distribution.
Frozen protocols, source snapshots and artifact hashes support reproducibility. A local freeze is not external preregistration, and hashes detect corruption rather than malicious re-signing. Historical executions, replays and unit tests are not additional independent study episodes.
Website
Privacy
The result selectors and terrain atlas use bundled data in your browser. These controls do not upload selections, request your location or contact a terrain service. Reports, recordings, terrain samples and figures are served by this site. Downloads do not require repository access.
Hosted analytics
Hosted page-view analytics are separate from the research controls. Hosting and analytics providers may process page paths and request metadata; locally rendered data does not imply that a hosted visit is anonymous.
Analytics is disabled for local visits and browsers signaling Do Not Track or Global Privacy Control. Query strings and fragments are removed from page-view URLs.
Provider privacy documentation ↗