Skip to content

Commit 9ca8bd9

Browse files
committed
Put information into tables
1 parent ea889c7 commit 9ca8bd9

File tree

1 file changed

+17
-65
lines changed

1 file changed

+17
-65
lines changed

src/misc/pedro_vs_roadrunner.md

Lines changed: 17 additions & 65 deletions
Original file line numberDiff line numberDiff line change
@@ -1,67 +1,22 @@
11
# Pedro Pathing vs Road Runner
22

3-
**Pedro Pathing** is a path-following library that utilizes a reactive vector follower
4-
that implements translational, heading, and centripetal force correction
5-
to dynamically converge to the target position.
3+
| Feature | Pedro Pathing | Road Runner |
4+
|--------|--------|--------|
5+
| **Path Following** | Path Follower | Trajectory follower using motion profiling | **Visualizer** | Web-based using a nonstandard (0 - 144) coordinate scheme | Code-based using the standard FTC coordinate scheme |
6+
| **Tuning** | Half manual and half automatic | Nearly all automatic |
7+
| **Motor Write Caching** | Used by default | Able to be implemented manually |
8+
| **Paths** | Cubic Bezier curves | Quintic Hermite splines |
9+
| **Bulk Reads** | Able to be implemented manually | Used by default |
10+
| **Logs** | Not built in | Automatic logging of every run |
11+
| **Priority** | Speed | Time consistency |
12+
13+
| Information | Pedro Pathing | Roadrunner |
14+
|--------|--------|--------|
15+
| **Docs** | <https://pedropathing.com> | <https://rr.brott.dev/docs/v1-0/installation/> |
16+
| **Quickstart** | <https://github.com/Pedro-Pathing/Quickstart> | <https://github.com/acmerobotics/road-runner-quickstart/tree/master/> |
17+
| **Visualizer** | <https://visualizer.pedropathing.com> | <https://github.com/acmerobotics/meepmeep> |
18+
| **Library** | <https://github.com/Pedro-Pathing/PedroPathing> | <https://github.com/acmerobotics/road-runner/> |
619

7-
**Links:**
8-
- Docs: <https://pedropathing.com>
9-
- Quickstart: <https://github.com/Pedro-Pathing/Quickstart>
10-
- Library: <https://github.com/Pedro-Pathing/PedroPathing>
11-
- Visualizer: <https://visualizer.pedropathing.com>
12-
13-
**Pros of Pedro:**
14-
- Can make your bot drive faster.
15-
- Excellent correction for unexpected disturbances.
16-
- Has a no-code, browser-based path visualizer.
17-
- Caches motor writes by default.
18-
- Corrects for centripetal force to hold the robot onto curved paths.
19-
- Path curves can be manually set using control points.
20-
21-
**Cons of Pedro:**
22-
- Newer, so potentially buggier.
23-
- Less people use it compared to Road Runner.
24-
- Tuning is mostly manual. <!-- 4 automatically tuned constants, minimum of 32 manually tuned constants -->
25-
- Not necessarily time-consistent; speed is prioritized over consistency.
26-
- Visualizer uses a nonstandard (0 - 144) coordinate scheme.
27-
- Path curves are not automatically optimized, and must be manually set using control points.
28-
- Quickstart code is not under the standard TeamCode package name,
29-
making using SlothLoad and integrating existing projects more difficult.
30-
- Does not bulk read by default.
31-
- No logs, so no replays of each run and much more difficult debugging.
32-
- No AdvantageScope support.
33-
34-
---
35-
36-
**Road Runner** is a motion-profiling-based follower library
37-
that includes a command-based action system and geometry.
38-
39-
It prioritizes time consistency above all else.
40-
41-
- Docs: <https://rr.brott.dev/docs/v1-0/installation/>
42-
- Quickstart: <https://github.com/acmerobotics/road-runner-quickstart/tree/master/>
43-
- Library: <https://github.com/acmerobotics/road-runner/>
44-
- Visualizer: <https://github.com/acmerobotics/meepmeep>
45-
46-
**Pros of Road Runner:**
47-
- Stable, minimal bugs if any.
48-
- Time consistent by default.
49-
- Tuning is almost fully automated, making it difficult to screw up. <!-- 5 automatically tuned constants, 3 manually tuned constants -->
50-
- Extensively tested and used by thousands of teams; almost all possible problems have been solved before.
51-
- Path curves are automatically optimized to create the ideal path based on your robot's constants.
52-
- Uses the FIRST-recommended standard coordinate system consistently.
53-
- Works with SlothLoad immediately.
54-
- Bulk reads by default.
55-
- Built-in custom logs, for easier debugging and full replays of every run.
56-
- [Full AdvantageScope support.](https://github.com/Mechanical-Advantage/AdvantageScope/pull/373)
57-
58-
**Cons of Roadrunner:**
59-
- Prioritizes time consistency above all else, meaning potentially worse correction.
60-
- Slower speed by default.
61-
- Path curves are less flexible then Pedro.
62-
- Path visualizer is code based.
63-
- Does not cache motor writes by default.
64-
- No built-in centripetal force correction.
6520

6621
<!--
6722
@@ -70,8 +25,6 @@ Guidelines for editing this page:
7025
Differences must be objective issues from a neutral point of view, not one sided.
7126
Ideally, people with biases in both directions should agree about these differences.
7227
73-
Each difference will be listed twice, as a pro of one library and as a con of another.
74-
7528
Actively avoid being reductive or summarizing into an overall recommendation;
7629
the idea of the page is that both libraries are good for different needs,
7730
and the reader should decide for themself which library aligns with their priorities.
@@ -83,7 +36,6 @@ If you feel that a library has too many cons, consider fixing the underlying iss
8336
and improving the experience for all users. Let us know (in an issue, PR, or in the Cookbook Discord)
8437
after this happens and we will be happy to remove it from the list.
8538
86-
8739
-->
8840

89-
*Last Updated: 2025-3-29*
41+
*Last Updated: 2025-07-07*

0 commit comments

Comments
 (0)