From fb056103d9064019ba9133c7ca97c1f1e3cc16f9 Mon Sep 17 00:00:00 2001 From: Anyi Lin Date: Fri, 22 Nov 2024 14:24:38 -0500 Subject: [PATCH] fix velocity inaccuracy in TUNING.md --- .../java/org/firstinspires/ftc/teamcode/pedroPathing/TUNING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TeamCode/src/main/java/org/firstinspires/ftc/teamcode/pedroPathing/TUNING.md b/TeamCode/src/main/java/org/firstinspires/ftc/teamcode/pedroPathing/TUNING.md index 4704e42..4ae8b4b 100644 --- a/TeamCode/src/main/java/org/firstinspires/ftc/teamcode/pedroPathing/TUNING.md +++ b/TeamCode/src/main/java/org/firstinspires/ftc/teamcode/pedroPathing/TUNING.md @@ -35,7 +35,7 @@ measurements will be in centimeters. find the rate at which your robot decelerates when power is cut from the drivetrain. This is used to get a more accurate estimation of the drive vector. To find this, you will need to run the `Forward Zero Power Acceleration Tuner` and the `Lateral Zero Power Acceleration Tuner` OpModes. - These will run your robot until it hits a velocity of 10 inches/second forward and to the right, + These will run your robot until it hits a velocity of 30 inches/second forward and to the right, respectively. The velocity can be changed through FTC Dashboard under the dropdown for each respective class, but higher velocities work better. After the velocity has been reached, power will be cut from the drivetrain and the robot's deceleration will be tracked until the robot stops, at