Glossary
Motorsport and Outlap terms used across the docs, from apex and transponder to RMonitor and scope.
| Term | Meaning |
|---|---|
| Apex | The point on a corner where the car is closest to the inside. Also Outlap’s cyan, used for organisers, links and telemetry. |
| API key | A secret that lets software act for a club. Starts with olap_, shown once, scoped. See Authentication. |
| AxWare | Timing and scoring software used for autocross and solo events. |
| Bridge | The Outlap Timing Bridge: a Node script that relays an RMonitor feed to Outlap. |
| Club | The account that owns members, events, keys and payouts. A track is the circuit-operator equivalent. |
| Delta | The live time difference to a reference lap, usually your best. Outlap computes it by position on track. |
| Event | A dated activity with tickets, a waiver, groups and sessions. |
| Feed | A live stream of timing data into an event. It has a status: idle, connecting, live, stale, error or stopped. |
| Flame | Outlap’s orange, used for drivers and calls to action. |
| GNSS | Satellite positioning (GPS and its peers). RaceBox logs it at up to 25 Hz. |
| Ideal lap | The sum of your best sectors across a session. |
| Kerb stripe | The dashed Flame line in Outlap’s design, from the kerbs at a circuit. |
| Lap | A time in milliseconds with optional sector splits, speed and validity. |
| Manifest | The list of who’s attending an event, used at the gate. |
| MCP | Model Context Protocol, a standard for connecting AI assistants to tools. See MCP server. |
| Minor units | Money as integers of the smallest currency unit, such as cents. |
| Out-lap / in-lap | The laps leaving and returning to the pits. Not representative, so logger imports drop them. |
| Paddock | The event tab where attendees, transponders and numbers are managed. Also the area at the circuit. |
| PAX | Handicap index used in autocross to compare cars. |
| Penalty | A time penalty (added to total time) or a points deduction. |
| Race Control | The organiser’s console for an event. See Race Control. |
| RMonitor | A line-based timing protocol over TCP, emitted by MyLaps systems and AxWare. See reference. |
| Scope | A permission on an API key, such as timing:write. |
| Session | A part of an event, such as practice or a race, with its own status and lap numbering. |
| Sector | A section of the lap with its own split time. |
| Sodium | Outlap’s amber, used for clubs and highlights. |
| Start/finish gate | The timing line across the track. Outlap finds it from the file, the circuit database or the lap data. |
| Transponder | A device in the car that a decoder reads each lap. Outlap matches it to a driver. |
| Visibility | Whether an event is public or private. Public events expose a live board and read endpoints. |
| Wristband | A driver’s progression tier shown in the app. |
Was this page helpful?
Reviewed · Contact support