Skip to content

Expedition / Nav-Computer Setup

Rev: v1.0  ·  Updated: 2026-05-29

TL;DR: Load the official ORR cert polar and the Expedition master sailchart so the nav computer routes on Lupo's real data. Two files to load: the polar (lupo_polar_raw.pol) and the sailchart XML. Always plan offshore at S3 (~10% degradation) — never route at certificate (flat-water) speeds. When a new cert arrives, regenerate and re-sync.

Setup checklist

1. Load the POLAR

Item Value
File newport-bermuda-routing-ai/02_polars/lupo_polar_raw.pol
Nav-computer copy nav/polars/lupo.pol (synced by scripts/sync-polar.sh)
Source 2026 ORR certificate boat-speed polar (Full Measured)
Format Tab-separated TWS × TWA grid (knots) + beat/run VMG table
  • Load lupo_polar_raw.pol into Expedition (or Adrena). The nav-computer working copy at nav/polars/lupo.pol is identical — kept in sync by scripts/sync-polar.sh.
  • Plan at S3 (~10% degradation) per polar_degradation_scenarios.md. Do not route at certificate (flat-water, full-crew) speeds — the cert polar is a clean-water VPP table and will overstate offshore performance.
  • The cert is final/submitted, but in any case routing uses only the boat-speed table (a physical/VPP measurement). The cert rating (GPH / sec-mile) is not used for routing — see ../01_boat_data/orr_cert_summary.md.
  • ⚠️ Beat/run angle coverage — confirm before routing. The grid's tightest row is TWA 52°; the boat's optimal beat (≈37–47°) and optimal run angles live in the .pol's beat/run comment table, which Expedition does not parse. If Expedition is left to find the optimum from the grid alone it will clamp upwind pointing at 52° and badly understate VMG. Fix one of two ways: (a) download the official ORR Performance Package Expedition polar (offshoreracingrule.org/orr/polar-package — includes optimal beat/run), or (b) enter the optimal upwind/downwind angles into Expedition's polar from the beat/run table in lupo_polar_analysis.md. Pre-routing gate — do NOT trust or run any route until you verify the loaded polar reports a ~37–42° beat at 12–20 kt (not a 52° clamp).

2. Load the SAIL CROSSOVER (master sailchart)

Item Value
File data/2026-05-24 Sail and Polar Info for Brandon/LupoDiMare Sailchart MASTER FOR EXPEDITION.xml
Contains Per-sail TWS/TWA polygons (drives the sail overlay)
Cross-reference ../03_sail_crossovers/crossover_notes.md
  • Import the master sailchart XML into Expedition. It defines per-sail TWS/TWA polygons, which drive the on-screen sail-recommendation overlay during routing.
  • Cross-check the loaded crossovers against ../03_sail_crossovers/crossover_notes.md before relying on the overlay offshore.

Regenerating from a new certificate

When a new (e.g. final) ORR cert arrives, rebuild the polar from the cert data rather than hand-editing it:

python scripts/build_polar_from_orr.py   # rebuild lupo_polar_raw.pol from the ORR cert CSV
bash scripts/sync-polar.sh               # propagate to nav/polars/lupo.pol
  • build_polar_from_orr.py reads the ORR cert boat-speed CSV and writes lupo_polar_raw.pol (no hand-transcribed numbers).
  • sync-polar.sh copies the docs polar to the nav-computer path nav/polars/lupo.pol.
  • After regenerating, re-load the polar into Expedition / Adrena and re-confirm the S3 planning default.

Quick reference

Load into nav computer From repo path
Polar newport-bermuda-routing-ai/02_polars/lupo_polar_raw.pol
Sailchart (sail overlay) data/2026-05-24 Sail and Polar Info for Brandon/LupoDiMare Sailchart MASTER FOR EXPEDITION.xml
Planning scenario S3 (~10% degradation) — not cert flat-water speeds

Sources

PRE-RACE RESEARCH — not race-period routing advice. Updated 2026-05-29.