MeepMeep Preview

Preview path shape before using field time.

Module 13: Road Runner 1.0 Actions and AutonomousRoad Runner

In this lesson, you will:

01Use simulation for planning.
02Keep constants realistic.
03Validate on real robot.

Concept narrative

MeepMeep helps the team reason about path shape and field interactions before the robot is on the carpet. It is a planning tool, not proof of tuning.

Robot mental model

Simulation catches obvious route mistakes: bad start side, impossible turns, collisions, awkward final headings. The real robot still owns traction, localization, and mechanism timing.

Implementation walkthrough

Build a preview with the same start pose and approximate constraints. Annotate field risks, then run the real robot slowly.

MeepMeepPreview.javaJava

bot.runAction(bot.getDrive().actionBuilder(new Pose2d(12, -63, Math.toRadians(90)))
    .lineToY(-36)
    .strafeTo(new Vector2d(48, -36))
    .build());

Common mistakes and debugging

If simulation and robot disagree, compare start pose, coordinate convention, constraints, and real-world slippage.

Checkpoint

Preview matches intended alliance/start.
Risks are annotated.
Real robot validation follows.
The test record includes the setup, prediction, and observed result.
A teammate can repeat the check from the saved evidence without guessing.

Reflection check

Check your understanding before moving on.

Which result best demonstrates completion of “MeepMeep Preview”?

Why record the test setup, prediction, and observed result?

0 of 2 answered

References

Road Runner 1.0 Builder ReferenceTrajectory/action builder method reference.MeepMeep repositoryOfficial simulator source, releases, and examples.