Day 5 · Week 1

Dashboard Guide — Pre-Season Setup

Use this guide to walk students through the dashboard on Day 5. At this stage, only two sections are active: Stat Loadout and Simulation Lab. The Match Log is locked until Week 2.

Velocity Arena
—
View
→ Pre-trial (auto · Week 1) 1
Summer 2026
1
Iron Raptors 2
Stat Loadout Each stat 1–20 · Total must equal 20
Speed
/ 20
motor power = (pts / 20) × 100
Motor power: 30%
Power
/ 20
charge speed = Power²
Charge speed: 25
Turning
/ 20
arc segments = Turning
Arc segments: 5
Endurance
/ 20
P(t) = 100 − (20 − E) × 1.5 × t
Decay rate: 24.0 / min
Budget 20 / 20 ✓
4
3
Simulation Lab Formula predicted · Bot did · Gap
Round Formula Predicted Observed Gap
R1 Speed Speed 6 → 30% motor power Reached end line in 4.4 sec 0.6 sec slower than predicted
Log each simulation round above
5
Match Log
What to do — in order
1
View control — leave it on Auto

The View toggle controls what sections are visible. On Week 1, Auto hides the Match Log automatically. Do not let students change this.

"If you see anything else — more columns, a Match Log — raise your hand. That means your View is set wrong."
2
Enter your team name first

Type your team name in the Team field before entering any stats. This is how your data is identified when you Save or Load.

"Spelling matters. Iron Raptors will find itself. Iron Rapters will not."
3
Enter all four stats in Stat Loadout

Type your Speed, Power, Turning, and Endurance values. Do not open the dashboard until your team has agreed on the four numbers out loud.

"Before you open your dashboard — tell me your four numbers first. Don't type yet."
4
Budget bar must hit exactly 20

The green bar fills to 20 when your total is correct. If it stops short or goes over, fix a stat before moving on. The bar turns red if you go over 20.

5
Log every round in Simulation Lab

Every row needs three parts. This is the only active data section this week — the Match Log is locked until Week 2.

Gap sentence format — required

Every row in Simulation Lab must have all three parts. A gap with no number does not count.

Formula Predicted
What your math said would happen. State the stat and the predicted outcome.
e.g. "Speed 6 → 30% motor power"
Bot Did
What actually happened — same units as the prediction.
e.g. "Reached end line in 4.4 sec"
Gap — must include a number
The difference. Must have a number. "Slower" alone is not a gap.
e.g. "0.6 sec slower than predicted"
Exit check — 3 questions before running any rounds
  1. Each team calls out their loadout total. Must be 20.
  2. What are the three parts of a gap sentence?
  3. Why do we log the prediction — not just what happened?
Never cut the exit check. Trim the demo if needed — not this.