MISSION 001 · VISDRONE-VID 26.4059°N 92.2335°E ALT 20 M · FOV 60° · NADIR SIH 2026 · STUDENT INNOVATION
AUTONOMOUS RESCUE & ENVIRONMENTAL INTELLIGENCE SYSTEM

7,081 BOXES. 23 PEOPLE. ONE ANSWER.

A detector over a crowded scene returns thousands of boxes. A rescue coordinator needs how many, where, and who first. ARES is everything in between — running on the aircraft, so losing the network costs the video feed and nothing else.

YOLOv12s · 960 PX CONF 0.18 HIGH RECALL BYTETRACK DE-DUP RB3 GEN 2 489/489 ON NPU NO API KEYS
MISSION EVENT LOG · REPLAYLIVE
DEMO_CLIP · 320 FRAMES24 FPS · 1280×720
7,081 DETECTIONS ◆333 TRACK IDS ◆23 SURVIVORS ◆RECALL 0.824 AT CONF 0.18 ◆489/489 LAYERS ON NPU ◆1.8 CM / PIXEL ◆23 M FOOTPRINT ◆2.5 S PERSISTENCE ◆3.1× FASTER TO HALF · SIMULATED ◆ZERO INVENTED DATA ◆
§ 01 — THE HARD PART

DETECTING IS EASY.
COUNTING IS NOT.

A person walks in and out of frame six times. Six people, or one? A detector has no memory between frames — and at a threshold tuned to miss nobody, it also reports every shadow. Watch what that costs, and what removes it.

DE-DUPLICATION · SCHEMATIC DETECTING
PHASE 01 — RAW DETECTION
0
Raw detections
0
Track identities issued
0
Confirmed survivors
SCHEMATIC — NOT MODEL OUTPUT PERSISTENCE FILTER · 2.5 S OF EVIDENCE REQUIRED
0
RAW DETECTIONS · WHOLE CLIP
0
IDENTITIES THE TRACKER ISSUED
0
SURVIVORS THAT HELD 2.5 S
0%
SHORT TRACKS AT THE FRAME EDGE
§ 02 — ARCHITECTURE

FOUR STAGES.
ONE CONTRACT.

Each stage exists because the one before it produces something not yet usable. They exchange a single JSON format — which is what lets three people work independently, and what lets the demo replay a stored file instead of inferring live.

YOLOv12s
1

DETECT

Boxes and confidences at 960 px, threshold 0.18. Finds people — but has no memory between frames.

BYTETRACK
2

TRACK

Persistent IDs across frames, so the same person is never counted twice. Position is still in pixels.

NADIR
3

LOCALIZE

Pixel offset → GPS from known altitude and field of view. 1.8 cm per pixel. Now they are on a map.

⚠ assumes the camera points straight down — § 03
WEIGHTED
4

RANK

Confidence, cluster size and hazard proximity, in a formula printed on screen. Not a black box.

DETECT → TRACK → LOCALIZE → RANK → DASHBOARD
§ 03 — THE ASSUMPTION WE BROKE

STAGE 3 SAYS
STRAIGHT DOWN.

Every pin on the map comes out of one line of trigonometry that assumes the camera points at nadir. A multirotor translates only by tilting — there is no other way for it to make horizontal thrust. So the moment the aircraft moves between search cells, the assumption is false, and every pixel in that frame projects to the wrong place. We went looking for how wrong.

H = 20 m CLUSTER RADIUS · 15 m TRUE POSITION WHERE WE PUT THE PIN
SIDE VIEW · NOT TO SCALE VERTICALLY TILT SWEEP 0° → 30°
Airframe tilt
0.0°
Pin displaced
0.00 m
Of the footprint
0 %
Displacement = H · tan θ  ·  metres against degrees
HALF THE CLUSTER RADIUS · 7.5 m 20 m 10 m 0 0° 22.5° 45°
TiltShift at 20 mOf footprint
5°1.75 m7.6 %
10°3.53 m15.3 %
20°7.28 m31.5 %
30°11.55 m50.0 %
⚠ WHY THIS IS NOT A ROUNDING ERROR

At 20° every pin moves 7.3 m — about half the 15 m radius the cluster term is scored over. That is enough to merge two groups or split one, and group size is a scored term. The error does not stop at the coordinate: it propagates into the order the dashboard tells you to rescue people in.

Altitude error barely matters beside it — ground sample distance is linear in height, so a 0.4 m excursion is a 2 % scale error, 0.46 m across the whole frame. Tilt is the term worth engineering against; height hold is not. The angles come from a quadcopter PID study on Swift Pico in MuJoCo — a 1.525 kg airframe, hover at 68.4 % of maximum thrust, no aerodynamic damping, which measured altitude leaving its tolerance band exactly while pitch and roll were making their large corrections. That is a different airframe in a different simulator, so the angles are the right order of magnitude rather than ARES's own numbers; the displacement arithmetic is exact for any airframe. The pins in the demo are not corrected for this and cannot be — they come from stored VisDrone and C2A footage whose true camera attitude is unknown, so the assumption is undischarged in both directions. This is the specific reason IMU fusion is on the roadmap: it is worth about seven metres.

§ 04 — THE DECISION THAT DEFINES IT

A FALSE ALARM COSTS
THIRTY SECONDS.

A missed survivor cannot be recovered. The costs are wildly asymmetric, so the confidence threshold should be too — ours is 0.18, not the conventional 0.5, read off the validation run's precision-recall curve.

F1-OPTIMAL · CONF 0.370.775
ARES · CONF 0.180.824
0RECALL1.0
+91 / 1,000

More survivors found, for every thousand present. That is the entire argument for this system's most important parameter.

THE PRICE OF THAT CHOICE

At 0.18 the detector reports anything person-shaped — a shadow, a bag, a patch of rubble — and the tracker gives each one an identity. That is why 333 identities exist for 23 people.

We measured those short tracks: mean confidence 0.42 against 0.52 for long ones, and only 7% starting or ending at the frame edge. Low confidence, mid-frame, gone in a frame or two is flicker — not someone walking out of shot.

So the filter is persistence, not a higher threshold. A track must hold for 2.5 seconds. Expressed as a duration, because that is 60 frames on this clip and 12 on device at 4.8 FPS.

§ 05 — HONEST SCOPE

WHAT IS BUILT,
AND WHAT IS NOT.

Nothing in the "described" row is simulated, mocked or implied anywhere in the product. We would rather answer hard questions about what is on the screen.

CAPABILITYSTATUSDETAIL
On-device inferenceBuiltYOLOv12s INT8, 100 % on the Hexagon NPU — measured on Qualcomm silicon
Counting & trackingBuiltByteTrack with a measured persistence filter
Geo-tagged mappingBuiltNadir projection from assumed altitude and FOV
Priority rankingBuiltA transparent weighted formula, printed on screen
Command dashboardBuiltWorks with the backend switched off
Offline resilienceBuiltA consequence of on-device inference, not a feature
Adaptive search planningSimulatedA 100-seed study against a lawnmower baseline — § 06. Never flown
RGB + thermal fusionPartialBoth detectors built and measured — thermal recall 0.883 on HIT-UAV. Fusion itself is specified, not built. Public datasets; we own no thermal camera
Hazard classificationNot builtNothing trained. Scope narrowed to 3 of 7 classes — fire/smoke, flood, collapse — and AIDER selected. HAZARDS is empty and the score drops the term
Autonomous nav · SLAMDescribedArchitecture only. Deliberately not built, and not mocked
NO INVENTED DATA

The hazard list is empty

Because the classifier does not exist yet. A fire on the map would make the ranking respond to something we made up, so the scoring drops the term and says it did.

NO INVENTED TELEMETRY

There is no battery gauge

There is no aircraft. The dashboard shows the constants it computed with instead, each tagged assumed, chosen, derived or measured.

REAL MODEL OUTPUT

Borrowed flight, our perception

No drone, so the clip is a public UAV dataset. Every box on it is our trained model's actual output over that footage.

§ 06 — EDGE DEPLOYMENT

A SEARCH UAV DOES NOT
NEED 30 FPS.

It needs to not miss the ground. We measured ours on Qualcomm AI Hub, on real hosted silicon: 4.8 FPS on a Dragonwing RB3 Gen 2 and 16.1 FPS on an IQ-9075, at 960 px INT8, under 7 MB peak memory — with 489 of 489 layers executing on the Hexagon NPU.

The 100 % is the headline, not the frame rate. An attention-centric YOLOv12 maps completely onto the accelerator, with nothing falling back to CPU.

BOARDSILICONINPUTLATENCY · MEDIANFPSPEAK MEMON NPU
Dragonwing RB3 Gen 2 Shipped QCS6490960 209.5 ms4.83 – 7 MB489/489 · 100 %
Dragonwing IQ-9075 EVK QCS9075960 62.3 ms16.12 – 6 MB489/489 · 100 %
Dragonwing RB3 Gen 2 QCS6490640 28.4 ms35.23 – 6 MB489/489 · 100 %
Dragonwing IQ-9075 EVK QCS9075640 14.0 ms71.26.5 MB489/489 · 100 %

Qualcomm AI Hub · hosted physical devices, not emulators · INT8 weights and activations · qnn_context_binary · QAIRT 2.45.0 · measured 26 Aug 2026. We publish the RB3 figure, not the IQ-9075's 16.1 — it is the slower of the two boards and the drone-class one. Quoting the better of two measurements is not reporting.

We published the wrong statistic for a fortnight
RUNMINIMUMMEDIANOVERSTATED BY
RB3 · 960207.6 ms209.5 ms0.9 %
IQ-9075 · 96061.4 ms62.3 ms1.5 %
RB3 · 64026.5 ms28.4 ms7.2 %
IQ-9075 · 64010.48 ms14.04 ms34.0 %
Resolution scaling · not established
COST OF 960 OVER 640RATIO
Pixel count2.25×
Tesla T4 GPU2.62×
Attention's quadratic ceiling5.06×
IQ-9075 NPU4.44×
RB3 Gen 2 NPU7.38×

Left — AI Hub's estimated_inference_time, and the "minimum inference time" on its console, is the fastest of ~100 samples. We quoted it. Every figure on this page is now the median. The gap scales inversely with the measurement: at 200 ms per inference it is under 1 %, at 14 ms it is a third. DEVICE_FPS = 4.8 survived unchanged — which was luck, not diligence.
Right — the IQ-9075 lands inside the band where a mix of quadratic attention and linear convolution belongs; the weaker RB3 is still above it, plausibly memory pressure. Two devices is not a trend. Settling it means benchmarking a pure-convolution YOLOv8n at both sizes on the same board.

FRAME n n + 1 n + 2 n + 3 23 M OF GROUND DRONE ADVANCES SAME PERSON ~22 LOOKS TOTAL
WHAT SATURATES

22 looks per patch

At 4.8 FPS the aircraft gets about 22 looks at every patch of ground before it leaves the frame. Compute stopped being the binding constraint — the hard problem is per-look recall, and that is where the effort went.

WHY NOT FASTER

640 buys nothing

We measured 640 too: 35.2 FPS, about 163 looks. But detection failures across consecutive frames are correlated — a person too small to resolve stays too small. That is 141 extra chances to re-fail, for 4.7 points less recall.

NOT MEASURED

INT8 accuracy

Every latency above is INT8; every accuracy figure is FP32. They are two different models until we measure the quantised one, so we report them separately and say so.

§ 08 — MEASURED

THE NUMBERS.

Trained on combined C2A and VisDrone under one unified person class. Every figure from the validation run — none estimated.

0
PRECISION · OF WHAT IT CALLS A PERSON
0
RECALL · AT THE SHIPPED THRESHOLD
0
mAP50 · SMALL AERIAL TARGETS
0
mAP50-95 · STRICT BOX PRECISION

For context: YOLO12s scores 48.0 mAP50-95 on COCO — mostly large, centred, well-lit objects. ARES scores 57.7 on small humans seen from directly above, from 9.2 M parameters.

ARES command dashboard mid-playback: detection feed, survivor map, priority queue and mission event log
Survivor map with the mission event log below it
Detection overlay: bounding boxes and track identities on the demo clip
§ THE FOOTAGE, HONESTLY

TRAINED ON DISASTER SCENES.
DEMONSTRATED ON A PUBLIC SEQUENCE.

The clip above is a VisDrone urban sequence — dense, annotated, and public. We use it because no annotated disaster video exists at that scale, and we do not own a drone. The model itself is trained on combined C2A + VisDrone, and C2A is people in disaster scenes.

We do not have a figure here of the shipped weights run over C2A stills, because we do not redistribute the dataset and will not render one from imagery we cannot publish alongside it. The fine-tuning runs are in the repository instead — experiments/Perception/C2A/ holds the validation batches, the confusion matrices and the PR curves, which is the same evidence in a form you can check rather than look at.

§ WATCH IT RUN

FOUR RECORDINGS.
NOT SLIDES ABOUT IT.

Every claim on this page has something moving behind it. These are screen recordings of the system running, narrated live — not an edit of a presentation.

The long form is the engineering handbook — thirteen parts, from what a convolution is to why the priority score is a weighted sum you can read rather than a model you cannot.

§ 09 — TEAM

WHO BUILT IT.

DEWANG

Detection model, hazard classifier, on-device benchmark, backend and dashboard.

ROBIN

Tracking, pixel-to-GPS localization, and the rescue priority scoring logic.

UJJAINI

Pitch, presentation and the recorded demo.

§ SIGN OFF

FIND THEM FASTER.
MISS NOBODY.

SMART INDIA HACKATHON 2026 · STUDENT INNOVATION