Docs
Current software

Memory, World, and Watch Areas

Three public routes cover three different parts of Praxis without a drone or an account. This page records what each route does and how it operates.

Praxis Memory#

Memory uses Scenario 2 from the public NANCY multi-perspective traffic recording. The three web derivatives begin at raw source positions 42.25, 39.90, and 36.45 seconds. Those starts were chosen by hand around the staged fall. After trimming, the derivatives use zero playback offsets on one 11.5 second clock.

One participant was seeded manually in each view and followed within that view with OpenCV CSRT. OSNet x0.25 compares three prepared crops at the 2.0 second case moment. The displayed scores stay fixed so they cannot be mistaken for current-time inference.

Memory boundary

This case does not estimate source offsets, associate people across cameras, or identify a person automatically. The OSNet score is a case-relative appearance comparison, not biometric identification. The vehicle candidate ends when the participant leaves that view.

Praxis World#

World uses Open Forest Observatory mission 000173. The published source mesh contains 4,217,056 vertices and 8,430,086 faces. Praxis ships a uniformly sampled and transformed browser derivative with 263,566 colored points, plus 800 recorded camera positions.

The four inset images come from the published source. They cycle independently and are not presented as matches to the selected position. The capture records, source page, license, and derivative restriction remain visible together.

World boundary

Praxis did not create the published reconstruction. The interface displays recorded positions, not camera orientation, view direction, or frusta. Its coverage replay assigns each displayed point to the nearest recorded position. That ordering is an interface aid, not the chronology of the original reconstruction. Mission 000173 is used for evaluation and visualization only, not model training.

Praxis Watch Areas#

Watch Areas replays a recorded boulevard flight beside registered zone geometry, saved tracks, and timestamped entry events. The timeline keeps the raw view and event layer on one clock, and each event can be opened at its recorded moment.

Watch Areas boundary

The public route uses checked-in geometry and track data from the recorded flight. It does not run the detector or registration pipeline live in the browser.

Source records#

These routes run in the browser and keep their source context visible. They do not represent hardware flight tests, deployment benchmarks, or field validation.