Guides
How the product works, in the order you use it. Each guide is a set of steps you can follow from start to finish.
What these guides are
Each guide takes one part of Nordic Stars and walks it end to end: what you click, in what order, and what you should see when it works. Where a screen has a name, we use the name that is on the screen. Where a step has a condition attached — a role, a paid boat, an add-on, a file the format needs — the guide says so at the step, not afterwards.
New to the platform? Start with Getting started. It goes from creating an account to a race on the screen with the crew watching, and every later guide picks up from somewhere inside it.
How these pages are written
- Numbered steps where you act. Prose where you need to understand something before you act. Nothing is numbered that you do not actually do.
- Gates are named where they are. Some things need an admin or owner, some need a boat with active coverage, some need an add-on your organisation has to be licensed for. Each is said plainly at the step it blocks, with what to do about it.
- How here, why in the math. When a guide reaches a number the platform computed, it links the math rather than half-explaining it. These pages are the how.
- Only shipped behaviour. If the product does not do something you would reasonably expect, the guide says so instead of leaving you to find out on the water.
Followed a guide and hit a step that does not match the screen? That is a bug in one of the two, and we would like to know which: support@nordicstars.ai.
The guides
Start here
Performance analytics
Importing telemetry
The five ways a day of sailing gets in, what each format needs from you, and how the preview, the commit and the status line work.
Channel mapping
Three kinds of channel name and which is which: the standard registry, your own custom: channels, and whatever your files happen to call things — plus the correction you only make once, the ledger of columns nobody has claimed, and who may change any of it.
The debrief player
Opening a race and reading it: the timeline and its event marks, transport and keyboard, the Explorer, the tuning guide, the HUD and deep links.
Local video and media
Putting your onboard video, photos and audio beside the telemetry — files that never leave your machine, aligned by hand, by the clap of the gun, or by holding a clock up to the lens.
Polars and targets
Giving the boat its numbers: uploading a polar, keeping the tuning tables per mode, importing the team’s own sheet, and what the column chips mean.
Calibration in practice
Entering a correction, measuring one from your own sailing, reading what Analyze found, applying it — and undoing any of it exactly.
The sails log
Setting up the wardrobe, letting the tablet fill the log, typing in what it did not record, correcting rows, and reading the two analysis panels.
Performance reports
Opening a sailing day as a report: the modes and groupings, the manoeuvres, start and race-legs reports, what every layer of a figure is, what a missing figure says, reading a chart as a table, printing to A4 and exporting a PDF.
Race Control
Running a windward/leeward race day
A day whose course arrives over the radio, in order: the polar roles, targets, sails and instrument mapping to set up first, the tablet at the dock, pinging the line and reading the approach, the course laid from one radio call, laylines and board times, the second and third races, FINISH — and what is in the debrief afterwards.
Planning a coastal or offshore race
A race whose course is known days ahead: drawing the plan ashore with marks, rounding sides, exclusion zones and a safety margin, the corridor forecast built for it, routing the course in the browser and adopting the result — then LOAD RACE, NAVIGATION and PATH AHEAD on the tablet, the alarms, sailing through midnight, and the debrief.
Navigation
The navigator’s own section: every race plan the fleet holds in one list, the weather already fetched for each routed plan and what makes a corridor stale, the viewer that draws a forecast on the chart and how to read a wind barb, routing a course in the browser with the tablet’s own engine and comparing the variants that change the answer, the marks the whole organisation reuses and why a plan copies one rather than pointing at it, the chart tools that measure a range and bearing and place a mark from one, the navigator’s log and routes pinned from the boat, the deck channels a boat transmits to its own instruments, and taking a plan away as GPX.
Race plans
Planning a coastal or offshore race ashore: the map, waypoints and rounding sides, exact positions in degrees and decimal minutes, the water to avoid and the depth to keep under the keel, importing the committee’s GPX — and what happens when two people edit one plan.
Weather
What the platform fetches for a boat’s routed plans and what it cannot tell you: the models and the limit each one carries, the corridor margin, taking the bundles at the dock, and reading the staleness line and the barbs at sea.
Your own GRIB, and weather at sea
Importing a forecast file you already have and refreshing the weather once you have left: which GRIB formats the tablet reads and which it declines by name, getting a file across from mail, what the import summary says it left out, and a download built for a satellite link.
Currents and tides
The tidal stream and the height of tide: where each comes from, what the current changes in the routing, in the laylines and on the chart, the units and datums they are stated in — and the limits, including no surge and a grid that does not resolve a harbour.
AIS, alarms and man overboard
The ships around you and the water under you: reading the target list and its CPA, the seven alarms and where to set each one — and the man-overboard button, what one press records, and why clearing it takes two.
Race Control on the boat
Licence to first gun: access and seats, signing in, the setup flow that finds the boat’s telemetry itself, the strip’s four states, the pre-start walk, the course, the live fleet overlay, the tabs, FINISH — and replaying the start afterwards.