SolversLib Docs
QuickstartGitHubContact
0.2.5 (Latest)
0.2.5 (Latest)
  • Welcome
  • Installation
  • Javadocs
  • Features
    • Hardware
      • Motors
      • SolversHardware
    • Gamepad
    • Drivebases
    • Geometry
    • Controllers
    • Utility Functions
  • Pedro Pathing
    • Pedro Commands
      • FollowPathCommand
      • HoldPointCommand
  • Vision
    • EasyOpenCV
  • Kinematics
    • Odometry
    • WPILib Kinematics
      • Differential Drive Kinematics
      • Differential Drive Odometry
      • Swerve Drive Kinematics
      • Swerve Drive Odometry
      • Mecanum Drive Kinematics
      • Mecanum Drive Odometry
  • Pathing
    • Pure Pursuit
    • Trajectory
      • Trajectory Generation
      • Trajectory Constraints
      • Manipulating Trajectories
      • Transforming Trajectories
      • Ramsete Controller
  • Command Base
    • Command System
      • Subsystems
      • Command
      • Command Groups
      • Command Scheduler
      • Binding Commands to Triggers
      • Robot and CommandOpMode
      • Convenience Features
    • Old Commands
  • Support SolversLib
  • Additional Reading
Powered by GitBook
On this page
Edit on GitHub
Export as PDF
  1. Pathing

Trajectory

package com.seattlesolvers.solverslib.trajectory

PreviousPure PursuitNextTrajectory Generation

Last updated 2 months ago

In FTC, there are often games that require an autonomous where robots are moving from one position to another—sometimes repeatedly. A lot of teams implement this motion by moving forward, turning, then moving forward again. Sometimes this is done with a time-base or a unit of known distance.

While these methods are functional, it is better if we can have the robot turn and drive at the same time to optimize the motion. Below is a video showing how this trajectory generation and following works:

You can find the same information in the .

wpilib docs