Skip to content

RoboticsMuse Implementation Guide

For multi-team organizations, assign each student:

  • one primary pathway for deep growth
  • one secondary pathway for literacy and collaboration
  • one mentor or lead responsible for advancement sign-off

This prevents narrow specialization while preserving depth.

Advancement Rules

Students should advance only when they can:

  • complete the level assessment without prompting
  • explain why their decisions were correct
  • recover from common mistakes safely
  • document their work so another student can continue it

Recommended evidence for promotion:

  • completed mini-project
  • review notes or rubric
  • photos, CAD, code, or schematics
  • short reflection on mistakes and fixes

Seasonal Pacing

Summer and Early Fall

Use Levels 0-2 to build baseline capability:

  • shop safety and tool certifications
  • onboarding to software, CAD, and control systems
  • short mechanism and drivetrain projects
  • recurring design review practice

Late Fall Pre-Season

Use Levels 2-3 to rehearse integrated work:

  • complete a practice robot or training chassis
  • run mock kickoff and strategy exercises
  • test cross-subteam handoff quality
  • finalize standards for naming, wiring, CAD, and code structure

Build Season

Use Level 2-4 work as production work:

  • assign real subsystem ownership
  • require regular review checkpoints
  • track blockers daily
  • prioritize test data, reliability, and serviceability

Post-Season

Use Level 3-4 work to preserve knowledge:

  • write standards and checklists
  • record lessons learned
  • refactor training projects
  • rebuild weak areas discovered during competition

Review Cadence

Recommended recurring meetings:

Meeting Frequency Purpose
Pathway Lab Weekly Skill instruction and guided practice
Subteam Stand-up 2-3 times per week in season Status, blockers, next actions
Design Review Weekly or milestone-based Challenge assumptions before fabrication
Integration Review Weekly in season Check interfaces across subteams
Retrospective After events and major milestones Capture lessons and update standards

Suggested Shared Rubric

Use a 4-part rubric at every level:

Dimension Question
Technical Accuracy Is the work correct and safe?
Process Discipline Did the student follow standards and review steps?
Troubleshooting Can the student diagnose and recover from issues?
Communication Can the student explain and document the work?

Minimum Standards for Team Leaders

Before the season starts, leadership should define:

  • standard terminology for mechanisms and subsystems
  • documentation locations and file naming
  • expected review checkpoints before fabrication, wiring, and merge
  • training hardware available for students below production level
  • who can approve safety-sensitive tasks

Resource Strategy

Use public references deliberately:

  • WPILib for software, simulation, control system, and wiring references
  • CTRE for vendor-specific motor controller, sensor, and CAN tooling guidance
  • FIRST resources for season materials, official field assets, and team operations context
  • FRC Design for CAD and mechanism design workflow

The strongest programs combine these public references with local examples from previous robots, training boards, and documented failures.