OpenLVC and FlightGear Workflow
OpenLVC and FlightGear Workflow
| Field | Value |
|---|---|
| Distribution | BSS — OpenC5ISR |
| Product | OpenC5ISR |
| Release | 0.15.1 |
| Deployment | openc5isr.bss.dev |
| Source | /srv/bss/releases/OpenC5ISR-v0.15.0-20app |
| Evidence | Reference LVC integration test |
| Source fingerprint | 93926e8c834f1ed79c9017a4096f70c76d73ce4f870f104fbd0cf54b2bed50ee |
| Status | Generated baseline — human review required |
Verification boundary: This page combines platform design guidance with static evidence from the release. It does not prove that every detected interface is enabled, reachable, secure, or operational in the deployed environment.
Objective
Demonstrate a virtual FlightGear entity entering the same operational representation used by live tracks, then being observed, correlated, tasked and replayed without hiding its simulation provenance.
Procedure
- Start a controlled FlightGear scenario with known aircraft, position, heading, speed and scenario time.
- Start the OpenLVC bridge and verify its input/output endpoint and entity identifier.
- Verify OpenTrack receives updates with correct coordinates, altitude, velocity, time and LVC provenance.
- Display the entity in OpenCOP and compare against the FlightGear state.
- Create an observation/follow/intercept task and verify state transitions without issuing unsafe real-world effects.
- Record scenario/event stream for OpenAAR-MR and replay the segment.
- Verify live and virtual entities remain distinguishable by source/provenance while sharing common semantics.
Pass criteria
Track error remains within test tolerance; update rate/time mapping is stable; provenance is explicit; task workflow completes; replay reproduces the operational sequence; no virtual input crosses a prohibited live-effect boundary.
Maintainer Notes
Add human-reviewed deployment notes, corrections, decisions, screenshots, and links here. Content outside the generated block is preserved on future runs.