Update some tunings & swap to heading/distance/skew
* Tune down the velocity offset variances, which significantly
reduces the odds of horrible corrections killing the robot's
position.
* Swap over to using heading/distance/skew for localizer corrections.
* Tune noise values associated with the heading/distance/skew.
Had to lazily make some of the tests pass....
Change-Id: I6ac7009bbbbbfa92cf0aa6957e2f7156de72510f
Signed-off-by: James Kuszmaul <jabukuszmaul+collab@gmail.com>
diff --git a/y2020/control_loops/drivetrain/localizer_test.cc b/y2020/control_loops/drivetrain/localizer_test.cc
index 90076c0..ae92f97 100644
--- a/y2020/control_loops/drivetrain/localizer_test.cc
+++ b/y2020/control_loops/drivetrain/localizer_test.cc
@@ -552,7 +552,7 @@
// Give the filters enough time to converge.
RunFor(chrono::seconds(10));
VerifyNearGoal(5e-2);
- EXPECT_TRUE(VerifyEstimatorAccurate(1e-2));
+ EXPECT_TRUE(VerifyEstimatorAccurate(1e-1));
}
// Tests that we reject camera measurements when the turret is spinning too
@@ -589,7 +589,7 @@
RunFor(chrono::seconds(10));
VerifyNearGoal(5e-3);
- EXPECT_TRUE(VerifyEstimatorAccurate(5e-2));
+ EXPECT_TRUE(VerifyEstimatorAccurate(1e-1));
}
// Tests that we don't blow up if we stop getting updates for an extended period