Techniques

Focused notes on navigation-analysis techniques that stand on their own, outside the GNC foundations and any single system study: how to cancel a sensor error instead of estimating it, how to turn a residual into a decision, how to predict a filter's performance without Monte Carlo, when two unknowns are jointly observable, and how you convince yourself a delivered IMU actually meets spec.

Symbols used on this page are defined in the Nomenclature → notation conventions.

The common thread. Each of these is a different answer to the same question — what do you do about an error you cannot measure directly? You can estimate it (filtering), geometrically cancel it (§ rotation), detect that it happened (§ FDI), predict how much it will cost you (§ LinCov), prove you cannot separate it from something else (§ observability), or characterise it on a bench before flight (§ acceptance testing). Real programs use all six.

Cancel it, or detect it

Two techniques that sidestep estimation entirely: make the error average itself away, or catch it the moment it appears.

Predict it, or prove it cannot be separated

Analysis before simulation: what the error budget will be, how the error dynamics behave, and which unknowns are fundamentally indistinguishable from each other.

Verify it on the bench

Before any of the analysis above means anything, the delivered hardware has to behave the way the budget assumed.

Scope & sourcing

These pages are written from the open literature — IEEE/AIAA standards and papers, NASA technical publications, and the standard textbooks (Titterton & Weston, Groves, Farrell, Bar-Shalom, Gustafsson) — and are deliberately generic. They explain the techniques and their mathematics, not any particular organisation's implementation, hardware, or results, and contain no vehicle-specific or vendor-specific data.

Related: Filtering · EKF · IMU & inertial navigation · Star trackers · NASA filter best practices · Rocket Navigation.