Skip to content

Conversation

jasondaming
Copy link
Member

Summary

Updates the trajectory tutorial to recommend PathPlanner and Choreo instead of the deprecated RAMSETE controller, while maintaining the tutorial's value as a guide for WPILib prerequisites.

Changes

Updated Files

  • trajectory-tutorial-overview.rst: Reframed as WPILib prerequisites, added PathPlanner/Choreo recommendations with feature descriptions
  • index.rst: Added deprecation warning and explained new tutorial focus
  • creating-following-trajectory.rst: Complete rewrite - now guides teams to PathPlanner or Choreo with installation instructions and setup requirements
  • ramsete.rst: Added warning that RamseteCommand has been removed

New Content

  • Detailed PathPlanner features and setup instructions (vendor library installation, required methods, controller selection)
  • Detailed Choreo features and setup instructions
  • Explanation of why RAMSETE was removed
  • Clear guidance on required robot subsystem methods for path following
  • Links to official documentation for both tools

Philosophy

The tutorial now teaches the foundation (characterization, odometry, drive subsystem) that teams need for ANY path planning solution, then directs them to modern third-party tools that are more capable and widely used.

Fixes #2651

The RAMSETE controller and RamseteCommand have been deprecated and
removed from WPILib. This commit updates the trajectory tutorial to:

- Recommend PathPlanner and Choreo as modern path planning solutions
- Reframe the tutorial as WPILib prerequisites for path planning tools
- Provide installation instructions for PathPlannerLib and ChoreoLib
- Explain required robot subsystem methods for path following
- Add deprecation warnings throughout RAMSETE documentation
- Completely rewrite Step 4 to guide teams to third-party tools

The tutorial now focuses on the WPILib foundation (characterization,
odometry, drive subsystem setup) that teams need before using any
path planning tool, then points them to PathPlanner or Choreo docs.

Fixes wpilibsuite#2651
@sciencewhiz
Copy link
Collaborator

Are Pathplanner and Choreo really replacements for teams that have differential drivetrains? I remember seeing a team struggling to get Pathplanner working with their differential drivetrain because the documentation was fairly non-existent. And I think Choreo only supports Holonomic drivetrains.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Replace RAMSETE documentation

2 participants