@@ -95,13 +95,12 @@ Here are our imports! We use PathPlanner to generate/map out and tune our paths,
9595so we can assign robot functionalities to each of the different paths we follow on the field.
9696(See our Path Planning documentation for more on this.)
9797
98- Then, we import the dimensions of the robot, game field, and poses we will incorporate to put
99- our robot in certain positions on the field.
98+ Then, we import the dimensions of the robot, game field, and our poses on field.
10099
101- Of course, we also want to import Driverstation as well as our Commands so we can actually do stuff.
100+ Of course, we also want to import Driverstation and our Commands so we can actually do stuff.
102101
103102.. note ::
104- We are importing *our * commands in line 6, which imports the commands we wrote using the methods from our
103+ We are importing *our * commands in line 6, which imports the commands we wrote using methods from our
105104 subsystems. In line 10, we import the *types * of commands we want to organize our robot commands into.
106105 This may sound a little confusing at first, but we'll get into the different types on a case by case basis.
107106
@@ -149,7 +148,7 @@ Autos can consist of any commands, and they will vary based on the auto you are
149148two instant commands: one that resets the odometry of the drivetrain to the starting pose, and one that sets the
150149boolean for coral in the wrist as true*. Instant commands do whatever is inside the parenthesis *instantaneously *.
151150
152- * We already have a coral preloaded in our reset before the match.
151+ * We already have a coral preloaded in our wrist before the match.
153152
154153The Rest of the Auto
155154======================
@@ -205,10 +204,15 @@ The Rest of the Auto
205204 )
206205
207206 This part gets a little repetitive, but here's the gist:
208- - AutoBuilder.followPath(paths[i]) follows path i in our choreo trajectory
209- - We utilize the fact that the entire auto is in a Sequential Command Group, to run all of the tasks in order:
210- following a path and then doing tasks at the location it ends up at.
211- - You might notice we also use Parallel Command Groups, which run multiple commands in parallel. We use them to follow
212- the paths in our Choreo trajectory while also moving the robot subsystems.
207+
208+ Within each Parallel command group (which run multiple commands in parallel), we
209+ 1. follow a path*
210+ while also
211+ 2. setting the target position of a subsystem depending on what we want the robot to do next
212+
213+ Then, after getting our robot to the correct place with our subsystems in the correct configuration,
214+ we either intake or score the coral.
215+
216+ * AutoBuilder.followPath(paths[i]) follows path i in our Choreo trajectory
213217
214218Congratulations! You have just learned how to code an auto.
0 commit comments