Files
Oleksandr Bezdieniezhnykh 72a9df6b57 [AZ-219] [AZ-228] Generalize VIO component layout
Keep VIO package and native bridge paths backend-neutral so BASALT remains an implementation choice rather than a component boundary.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-05-03 12:41:54 +03:00

1.0 KiB

Component Overview Diagram

flowchart LR
    camera[01 Camera Ingest And Calibration]
    vio[02 VIO Adapter]
    wrapper[03 Safety And Anchor Wrapper]
    retrieval[04 Satellite Service]
    verify[05 Anchor Verification]
    cache[06 Tile Manager]
    mav[07 MAVLink And GCS Integration]
    fdr[08 FDR And Observability]
    tests[[Separate E2E Test Suite]]

    navCam[[Nav Camera]] --> camera
    fc[[ArduPilot Plane FC]] --> mav
    satSvc[[Azaion Suite Satellite Service]] --> retrieval
    datasets[[Replay/Public Datasets]] --> tests

    camera --> vio
    mav --> vio
    vio --> wrapper
    wrapper --> retrieval
    retrieval --> verify
    cache --> retrieval
    cache --> verify
    verify --> wrapper
    wrapper --> mav
    wrapper --> cache
    camera --> cache

    camera --> fdr
    vio --> fdr
    wrapper --> fdr
    retrieval --> fdr
    verify --> fdr
    cache --> fdr
    mav --> fdr

    tests --> camera
    tests --> mav
    tests --> cache
    mav --> qgc[[QGroundControl]]
    mav --> fc
    retrieval --> satSvc