azaion/gps-denied-onboard
1
0
Fork 0
mirror of https://github.com/azaion/gps-denied-onboard.git synced 2026-06-22 16:11:13 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update demo replay validation and testing documentation
ci/woodpecker/push/02-build-push Pipeline failed
Details

Browse Source 
- Modified the autodev state to reflect the current testing phase and details of the new `jetson-e2e` tests.
- Enhanced the "How to Test" documentation to provide clearer instructions on the demo replay validation process, including video and tlog alignment steps.
- Updated architectural documentation to include the new demo replay operator flow and its dependencies.
- Documented the removal of deprecated auto-sync features and clarified the operator-facing UI for replay validation.
- Added new entries in the dependencies table for upcoming tasks related to the demo replay flow.

These changes improve clarity and usability for operators and developers working with the demo replay system.
This commit is contained in:
Oleksandr Bezdieniezhnykh
2026-06-20 11:24:43 +03:00
parent 12d0008763
commit 1f634c2604
175 changed files with 20701 additions and 41 deletions
Download Patch File Download Diff File Expand all files Collapse all files
_docs/how_to_test.md
+11 -8
View File
@@ -1,11 +1,14 @@
Testing strategy without real flight.
# Demo replay validation (operator workflow — F11)
upload tlog file
upload video synced with tlog
Upload a flight video and ArduPilot tlog from the same sortie. The suite UI shows two timeline bars: video above, tlog IMU activity below. Drag the video bar to align with takeoff on the tlog, refine the match, then run the demo. The system:
1. Extracts IMU and GPS from the tlog.
2. Aligns video to tlog using your coarse placement plus backend refinement.
3. Exports a canonical aligned CSV (single time base for replay).
4. Seeds satellite corridor tiles from the tlog GPS route.
5. Runs the same GPS-denied pipeline as live flight against the video.
6. Returns estimated GPS fixes, a map, and a PASS/FAIL accuracy verdict.
system should:
1. extract timestamps, imu and gps from the tlog file.
2. usually video and tlog aren't synchronized. So system should synchronize them by itself.
Usual test is done on the quadcopters, so usually it starts from the drone on the ground and ends with the drone on the ground. These sessions are clearly visible in the chart IMU data of the tlog file. So, system can check the duration of the video and events in IMU chart in tlog. Then it can analyze by IMU the moment of actual take off and sync them
3. then make SITL and provide IMU and frames to the gps denied onboard system
Advanced: upload a pre-aligned `(video, CSV)` pair to skip alignment (AZ-959).
Live flight (F3) is unchanged: IMU and frames from the aircraft in real time.