🎯 OCD Trainer

Gamified dart practice on your own autodarts rig — auto-scoring, many game modes,
central leaderboards + Elo, stats & heatmaps, and at the same time training a fully open dart detection engine.

🎮 all game modes & rules — X01, Cricket, Clock, World, Bermuda, and every drill at a glance.

Runs on (the installer auto-detects yours — nothing to pick):

Raspberry Pi OS Bookworm / Trixie · arm64 Ubuntu 24.04 LTS · amd64

What you need

A 3-camera dart rig — 3 USB cameras + the board. Either a Raspberry Pi 5 (4 GB+, the usual autodarts setup) or an amd64 PC / mini-PC.
OS: Raspberry Pi OS Lite 64-bit — Trixie (Debian 13, recommended) or Bookworm (Debian 12); or Ubuntu 24.04 LTS (amd64). The installer picks the right package automatically.
A tablet or phone on the same network — that's your scoreboard.
Internet on the Pi (to fetch the package + auto-update the model).

The trainer takes over the cameras, so it pauses the autodarts service while it runs. It's a separate practice mode, not a replacement for autodarts — stop the trainer and autodarts comes back.

What your rig sends home

You're lending your board to a research project, not signing up for surveillance. Straight answer on what leaves your Pi. Uploading is on by default (your rig enrolls itself on first start); opting out is one line — comment out DT_CENTRAL_URL in /etc/dart-trainer/config.env and your rig runs fully local. Full detail, including the data-protection notice and your rights: 📊 statistics & your data.

what	why it exists
Throws — the 3 camera frames, the model's guess, your correction	this is the training data. It's the whole point.
Calibration — the solved geometry + its fit quality	so a throw can be re-warped with the calibration that was live when it was captured
Health (every 10 min) — version, model, calibration quality, camera angles, fps, free disk, errors	so "is your rig OK?" is answerable without anyone logging into your Pi
Decision log — the detection loop's own record (dart held / ignored / takeout / errors)	the only thing that can explain "detection is broken" on a rig nobody can SSH into
Feedback — only when you press the button	your text, your rig's state, and a picture of the screen only if you tick the box

Not sent: anything from outside the app — no microphone, no other windows, no files. The screenshot is a render of the trainer page itself. Telemetry is also best-effort: it's dropped rather than queued if it fails, so it can never slow down or block your game.

1 · Install

One line (adds the dart-room APT repo and installs the trainer):

curl -sSL https://dart-room.com/trainer/install.sh | sudo bash

Prefer to do it by hand? Add the repo, then install:

# codename (bookworm/trixie/noble) + arch (arm64/amd64) are auto-detected
curl -fsSL https://dart-room.com/apt/gpg.key | sudo gpg --dearmor -o /usr/share/keyrings/dart-room.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/dart-room.gpg] https://dart-room.com/apt $(. /etc/os-release; echo $VERSION_CODENAME) main" \
  | sudo tee /etc/apt/sources.list.d/dart-room.list
sudo apt update && sudo apt install dart-trainer

No internet on the Pi? dart-trainer-offline is a single package with everything inside (web stack, scoring model) — copy the .deb over and sudo apt install ./dart-trainer-offline_*.deb. Raspberry Pi (arm64) only. Direct download (fill in the version from what's new and your codename): https://dart-room.com/apt/pool/main/d/dart-trainer-offline/dart-trainer-offline_<version>-1+<codename>_arm64.deb — or, on any machine that has the repo configured, apt-get download dart-trainer-offline.

2 · Configure your rig

The defaults are fine for a standard 3-camera autodarts rig — you can skip straight to step 3 and play right away (auto-scoring is on, a unique rig id is assigned automatically, and you set your name on the tablet). Only edit the file below if you want to join the central leaderboards + help train the model (add the token) or set a friendly rig/player name.

sudo nano /etc/dart-trainer/config.env      # then: sudo systemctl restart dart-trainer

Every setting, with its default and a comment, is in /usr/lib/dart-trainer/config.env.template (refreshed on every upgrade; your file is never touched). Rigs installed before 0.7.29 still read the old /opt/dart-trainer/env first — the new file wins key by key.

setting	what it is
`DT_DEVICES`	your 3 cameras, e.g. `0:/dev/video0,1:/dev/video2,2:/dev/video4` (check with `v4l2-ctl --list-devices`)
`DT_PLAYER`	your default name (you can change it on the tablet)
`DT_RIG_ID`	auto by default (a unique id derived from the machine) — leave it, or set a friendly name e.g. `toms-rig`. Keeps every rig cleanly separate in the data.
`DT_PORT`	web port (default `8788`)
`DT_CENTRAL_URL`	the central dataset (`https://dart-room.com/dataset`). Comment it out to run fully local.
`DT_CENTRAL_TOKEN`	normally empty — the rig enrolls itself. Only for a hand-provisioned token, and only here: never on the command line / in `DT_EXTRA`, where every process can read it.
`DT_HUB_URL`	`https://dart-room.com` — online play (needs the `dart-room-bridge` add-on, see step 7). `DT_DART_ROOM=0` switches it off.
`DT_EXTRA`	auto-scoring: `--model-weights /opt/dart-trainer/data/tipnet.onnx`. The model itself is fetched over the air on first run and kept current; clear this line for manual-tap mode (no model).

Central needs no token from you — the rig enrolls itself on first start (new rigs stay quarantined from training until trusted). To run fully local instead, comment out DT_CENTRAL_URL — see statistics & your data.

Your token is yours alone. It's minted for your rig: it can upload your throws and read the leaderboards and the model — and that's all. It cannot read anyone else's data (no other rig's frames, no feedback, no screenshots), it cannot post as another rig, and it can be revoked on its own without touching anybody else's. Keep it out of screenshots and pastebins; if it leaks, say so and we'll mint you a new one in ten seconds. The file is chmod 600 for the same reason.

3 · Start & open the scoreboard

dart-trainer            # starts it (pauses autodarts to use the cameras)

On your tablet/phone on the same network, open http://<your-pi-ip>:8788. Steps 4–5 below are one-time buttons inside that web UI.

4 · Calibrate the board (one-time, per rig)

A self-service button now. Auto-scoring needs the mapping from your three cameras to the board — found by automatic board detection (the rings & wires in each image). No checkerboard, no manual alignment.

Clear all darts from the board.
Tap 🎯 Calibrate — it averages a few frames and fits each camera's geometry (~10 s).
A good fit reads ~8 mm with all 20 wires on each camera. Anything worse than 12 mm, or with a wire it had to guess, is rejected and your previous calibration kept — so a bad press can never break a working board. A rejection costs you nothing; accepting a bad fit would cost you every score.
Keeps rejecting? The board must be empty and evenly lit, and nothing (cable, bracket, shadow) may cross a wire in any camera's view. Then press again.

Coming from autodarts? You'll calibrate far less here.
In autodarts, re-calibrating and re-orienting is a constant chore. On this system it is one-time setup, not a routine: calibrate once after installing (or if you bump a camera or rotate the board), confirm orientation, and you're done. Our reference rig played daily for a full week with zero re-calibration and zero re-orientation — the geometry simply doesn't drift the way you're used to. If your scores land where the darts land, don't touch it. The tablet warns you in red on the rare day the board actually shifts; until then, leave Calibrate and Orientation alone.

5 · Confirm orientation (after every calibration)

Which spoke is the 20? It's proposed automatically — a vision model reads the board's numbers — and you just confirm.

Tap 🧭 Orientation. Each camera's board appears with the proposed numbering pre-filled.
Check the 20 sits under the top marker on each; nudge with ◀ ▶ if a camera is off; then Confirm.

⚠ This is the one step people skip — and it silently costs you every score. Calibrating resets the orientation to an automatic guess, and the guess is not reliable. Until you confirm it, the geometry is perfect but the board is scored a whole sector off — a T20 lands as a 5 and nothing looks broken. So: rotate the board (or press Calibrate) → Calibrate → CONFIRM ORIENTATION. The tablet nags you in red until you do.

6 · Play

Enter your name, pick a game (tap ? next to any game for its rules).
Throw — darts auto-record. The visit is three slots; each fills as you throw.
Wrong dart? Tap its slot, then tap the board where it really landed. Missed a dart entirely? Tap an empty slot and place it. Bounced out? Tap its slot, then 💥 Bounce-out — it scored nothing, but it still counts as thrown.
Playing 501? The empty slots show the way out (170 → T20 · T20 · BULL) and re-plan as you throw.
Pull the darts and it resets itself. You can have the UI open on a phone and a tablet at once — both stay in sync.
Something wrong? 💬 Send feedback — it attaches the screen you were looking at and your rig's own state, so we can actually fix it instead of guessing.
Every throw + your corrections upload to the central dataset (tagged to your rig & name) — that's what trains the next model, for everyone.
📊 my stats shows your heatmap, grouping, XP/level, streak and badges; Leaderboard has every game + the H2H Elo board. Since 0.3.83 every dart is recorded with its full story (what you aimed at, busts, checkouts) — what that enables and how the data is handled: statistics & your data.

17 game modes

X01 (301/501/…) · 501 Head-to-Head (Elo) · Cricket · Count-Up · Around the Clock · Around the World (doubles) · Bob's 27 · Shanghai · High Score 3 · Treble 20 · Treble 20 · until · Group Builder · JDC Challenge · Checkout 121 · Finishing 50 · Checkout Routes · Bermuda Triangle (Halve-It). Rules for each: game modes.

7 · Play online (dart-room.com) — optional

Online 501 against a friend's board, with the match page, recap and board photos on dart-room.com, is a separate add-on: dart-room-bridge. Without it the board plays offline exactly as before (the tablet says offline only).

sudo apt update && sudo apt install dart-room-bridge     # needs dart-trainer ≥ 0.9.84
sudo systemctl restart dart-trainer

On dart-room.com → Account: sign in and press Generate pair code. It shows a short code (XXXX-XXXX).
On the tablet: ⚙ Settings → dart-room.com. Type the code into the code field and tap Pair.
Stay on Account — a Confirm button appears once the board has the code. Press it, copy the pair token, paste it into the pair token field on the tablet, tap Finish. The token stays on Account until the board has it.
Still in Settings, turn on Allow dart-room.com to start matches on this board. From then on you start a match on the site and the board joins by itself — no codes at the oche.

Pairing is one-time per board. The website cannot reach your Pi directly (HTTPS → LAN), which is why the two codes travel through you. No terminal needed (since 0.9.91); if the section is missing from Settings, the dart-room-bridge add-on is not installed or not running. If a code is refused the section tells you why: That code isn’t right (check it on the site), Code expired — generate a new one, or This board is already linked to another account.

Updating

The app: sudo apt update && sudo apt install --only-upgrade dart-trainer (add dart-room-bridge if you play online).
Hands-off: the package ships a game-aware daily updater that waits until no game is running. It is off until you switch it on: sudo systemctl enable --now dart-trainer-autoupdate.timer. It follows whichever channel your sources line has.
The scoring model: nothing to do — it polls and hot-swaps a newer model on its own (between games, no reinstall). Your corrections feed the next model for everyone.

Release channels — main vs beta

The APT repo has two components. Fresh installs get main only (stable). That's what you want for everyday play.

channel	who it's for	when it updates
`main`	everyone by default — friends, production play	only after a version has soaked and is promoted
`beta`	opt-in — people who want the newest detection fixes early	every CI build lands here first (before main)

Opting into beta is one word on the sources line. You can leave anytime by dropping beta again and reinstalling the main package.

# 1) Edit the sources line — add the word "beta" after "main"
#    (codename is usually "trixie" or "bookworm" — leave yours as-is)
sudo nano /etc/apt/sources.list.d/dart-room.list
# before:  … https://dart-room.com/apt trixie main
# after:   … https://dart-room.com/apt trixie main beta

# 2) Upgrade to whatever is currently in beta
sudo apt update
sudo apt install -y --only-upgrade dart-trainer

# 3) Check the version (should match the beta package you wanted)
dpkg -l dart-trainer | tail -1
# or:  curl -s http://127.0.0.1:8788/status | head

Beta is opt-in. Leaving it out of your sources means you stay on the last promoted stable version and never get mid-soak builds by accident. The installer still only enables main — beta is never forced.

Troubleshooting

Cameras busy / no video: make sure autodarts is stopped — sudo systemctl stop autodarts (the trainer does this, but a stuck process can hold the cameras).
Logs: journalctl -u dart-trainer -f (or run dart-trainer in a terminal).
Every score is a whole sector off (T20 reads as 5): the orientation was never confirmed, or a Calibrate reset it. Tap 🧭 Orientation and confirm — see step 5. This is by far the most common one.
Scores are just a bit off: (re)run Calibrate (step 4) on an empty board — then confirm orientation again — or play manual-tap.
The tablet says "offline only" / no online match: the dart-room-bridge add-on is not installed (or was removed by an upgrade) — see step 7.
Something else: tap 💬 Send feedback in the app. It ships the screen you were looking at plus your rig's own logs and state, which is usually enough to diagnose it without touching your Pi.

game modes · statistics · where your data lives · dart-room.com · made for the crew 🎯