AlphaBit - OpenML

Road Runner 1.0 Transition Notes

Migration Planning

This page helps teams evaluate RR 1.0 migration with low risk. Use it as a planning document, not as a same-day competition switch plan.

Current State

Regional Decode code currently runs proven RR 0.5.6 autonomous routes.

Pedro references exist primarily in the national code branch.

That means migration should be incremental, not a full rewrite in one sprint.

Step 1

Freeze a Known-Good Baseline

Tag your final stable RR 0.5.6 commit.

Export baseline metrics: endpoint error, cycle time variance, fail count.

Step 2

Port One Short Route Only

Choose the simplest route (single score + park).

Validate route shape and endpoint repeatability before adding mechanism actions.

Step 3

Re-Attach Mechanism Markers

Add intake/shooter markers gradually.

Retune timing windows; old marker offsets rarely transfer perfectly.

Step 4

Run KPI Comparison

KPI	Target
Endpoint error	Equal or better than RR 0.5.6 baseline
Cycle time variance	No increase under repeated runs
Manual interventions	Same or fewer than baseline
Tuning effort	Sustainable for your team size

Step 5

Decide Using Data

Adopt RR 1.0 only if metrics improve and maintenance burden stays manageable.

If not, keep RR 0.5.6 for current season and revisit during offseason.

Do Not

Do not migrate full competition autonomous one week before an event.

Do not reuse constants blindly after framework changes.

Continue to Pedro Pathing Implementation to compare another migration direction.

Choose Language / Alege Limba