Skip to content

Commit 41f5767

Browse files
Finished content
1 parent af026f5 commit 41f5767

File tree

5 files changed

+514
-6
lines changed

5 files changed

+514
-6
lines changed

book/odometry/OdometryTesting.html

+17-2
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,8 @@
2727
<link rel="stylesheet" href="../highlight.css">
2828
<link rel="stylesheet" href="../tomorrow-night.css">
2929
<link rel="stylesheet" href="../ayu-highlight.css">
30+
<link rel="stylesheet" href="../solvers-light-highlight.css">
31+
<link rel="stylesheet" href="../solvers-dark-highlight.css">
3032

3133
<!-- Custom theme stylesheets -->
3234

@@ -132,6 +134,8 @@
132134
<i class="fa fa-paint-brush"></i>
133135
</button>
134136
<ul id="theme-list" class="theme-popup" aria-label="Themes" role="menu">
137+
<li role="none"><button role="menuitem" class="theme" id="solvers-light">Solvers Light</button></li>
138+
<li role="none"><button role="menuitem" class="theme" id="solvers-dark">Solvers Dark</button></li>
135139
<li role="none"><button role="menuitem" class="theme" id="light">Light</button></li>
136140
<li role="none"><button role="menuitem" class="theme" id="rust">Rust</button></li>
137141
<li role="none"><button role="menuitem" class="theme" id="coal">Coal</button></li>
@@ -350,7 +354,7 @@ <h3 id="software"><a class="header" href="#software">Software:</a></h3>
350354
</style>
351355
<hr />
352356
<h3 id="analysis"><a class="header" href="#analysis">Analysis</a></h3>
353-
<p>        Each test program above (<a href="./StraightTest.html">Straight Test</a>, <a href="./SplineTest.html">Spline Test</a>, and <a href="./CombinedTest.html">Combined Test</a>) returns two results at the end of the program - the pose of the robot after each cycle, and a graph that has data plotted after each trajectory is complete.</p>
357+
<p>        Each test program above (<a href="./StraightTest.html">Straight Test</a>, <a href="./SplineTest.html">Spline Test</a>, and <a href="./CombinedTest.html">Combined Test</a>) returns two results at the end of the program - the pose of the robot after each cycle, and a graph that has data plotted after each trajectory is complete. During the program, telemetry of the pose of the most recent trajectory completed and distance the robot has linearly traveled will be displayed - these are the two results that will be plotted in the graph.</p>
354358
<p>        The graph will be made in <a href="https://acmerobotics.github.io/ftc-dashboard/">FTC Dashboard</a>. The y-axis will represent the current error after each trajectory has been completed via this formula:</p>
355359
<math xmlns="http://www.w3.org/1998/Math/MathML">
356360
<msqrt>
@@ -391,7 +395,18 @@ <h3 id="analysis"><a class="header" href="#analysis">Analysis</a></h3>
391395
</mrow>
392396
</msqrt>
393397
</math>
394-
<p>And the x-axis will represent distance travelled linearly. In other words, after each trajectory, a point is plotting representing the error of the robot based off distance traveled.</p>
398+
<p>        On the other hand, the x-axis will represent distance travelled linearly. In other words, after each trajectory, a point is plotting representing the error of the robot based off distance traveled.</p>
399+
<p>        A perfect odometry wheel will always have a y-axis of 0, since there is no error no matter the distance traveled, but most odometry wheels with error will likely have a graph with positive correlation (slope is upwards), as the x-axis (distance traveled) will have a more and more profound effect. This occurs because positional error tends to compound.</p>
400+
<p>        Based off the graph and the points plotted, we can create a line of linear best fit using the formula \( y = mx + b \) from points plotted in Excel/Google Sheets from the data outputted from <a href="https://acmerobotics.github.io/ftc-dashboard/">FTC Dashboard</a>.</p>
401+
<hr />
402+
<h3 id="results"><a class="header" href="#results">Results</a></h3>
403+
<p>In total, the following items will be returned for each odometry wheel tested for each individual test program (<a href="./StraightTest.html">Straight Test</a>, <a href="./SplineTest.html">Spline Test</a>, and <a href="./CombinedTest.html">Combined Test</a>):</p>
404+
<ol>
405+
<li>Pose after each cycle (ideal pose is 0,0)</li>
406+
<li>A graph in Excel/Google Spreadsheet from the data outputted from <a href="https://acmerobotics.github.io/ftc-dashboard/">FTC Dashboard</a> that shows the error after each trajectory has been completed, along with a line of best fit</li>
407+
<li>The slope of the line of the best fit</li>
408+
</ol>
409+
<p>As there are three testing programs, each odometry wheel will have 3 different result files (3 poses, 3 graphs, and 3 line of best fit slopes). These three can be compared to other vendors' odometry wheels to come to a final conclusion.</p>
395410

396411
</main>
397412

book/searchindex.js

+1-1
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

book/searchindex.json

+1-1
Large diffs are not rendered by default.

0 commit comments

Comments
 (0)