PathPlanA
Flutter planner app for REBUILT autonomous authoring that exports deploy-backed auto libraries into the FRC 1884 robot workflow.
Project surface
It is the clearest evidence that autonomous tooling in the team stack goes beyond using upstream libraries and extends into team-specific planning software.
Problem
Autonomous authoring becomes harder to maintain when planning only exists as ad hoc edits inside a dashboard or directly in robot code.
Contribution
The public repo shows a dedicated planner surface with local auto galleries, field editing, deploy export, and an explicit integration contract into the Season2026 operator-board and auto queue flow.
Why it matters
It is the clearest evidence that autonomous tooling in the team stack goes beyond using upstream libraries and extends into team-specific planning software.
Contribution context
Team repository. Included as part of the FRC1884 software ecosystem, not as upstream authorship of PathPlanner itself.
Roles
- Toolchain design
- Autonomous authoring workflow
- Planner-to-robot integration
Stack
Domains
Repository
Evidence note
Grounded in the public `FRC1884/PathPlanA` README and integration docs. This is separate from upstream PathPlanner by Team 3015 Ranger Robotics.