Skip to content

Local Development

When editing bijux-gnss-nav, start from the scientific family, not from the file that happened to fail first.

flowchart TD
    failure["local failure"]
    family["scientific family"]
    docs["family docs"]
    tests["focused proof"]
    public_api["public API check"]

    failure --> family
    family --> docs
    family --> tests
    family --> public_api

Good Local Loop

  • find the owning family in src/formats/, src/orbits/, src/corrections/, src/estimation/position/, src/estimation/ppp/, src/estimation/rtk/, src/models/, or src/time.rs
  • update the crate-local docs if the scientific meaning moves
  • run targeted tests for that family before touching wider suites
  • inspect src/api.rs if the change affects something public

What To Avoid

  • changing several scientific families at once without naming the shared reason
  • using one broad integration test as the only proof for a low-level change
  • widening exports to make local development easier

Local Decision Table

change start with prove with
format parsing Format guide format and reference-product tests
orbit behavior Orbit guide broadcast and precise-orbit tests
correction model Correction guide correction-focused numeric tests
position, PPP, RTK, or RAIM Estimation guide solver and integrity tests
public export Public API public API and guardrail tests

Useful Local Anchors