Pathfinder
Pathfinding, odometry, trajectory generation, and a whole lot of swag. (by Wobblyyyy)
OdometryCore
Odometry Core Tracking Algorithm Written in Java (by tmthecoder)
Pathfinder | OdometryCore | |
---|---|---|
2 | 4 | |
2 | 3 | |
- | - | |
0.0 | 0.0 | |
over 2 years ago | almost 3 years ago | |
Java | Java | |
GNU General Public License v3.0 only | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Pathfinder
Posts with mentions or reviews of Pathfinder.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-08-17.
-
Robot localization with on-motor encoders
hey, i just figured i’d put this out here in case it helps: meccanum wheels, by nature, have a LOT of slip - that’s how they’re able to move in any direction. i’ve had quite a bit of experience with the math and kinematic behind this (two libraries i’ve written/am writing, Pathfinder and Pathfinder2, as well as a library the other programmer on my team wrote, OdometryCore) and it’s VERY HARD to accurately track the position of a meccanum robot only using the encoders in the wheels. it’s not impossible, but it’s very, very challenging. the more your robot moves, the less accurate it becomes, and it will very quickly report positions that are nowhere near where your robot actually is. you can go for it, but i would strongly encourage you check out three wheel odometry instead - it’s been very accurate and allowed us to do really cool things, like accurately record a robot’s movement and play it back perfectly. you’ll have much more success with three wheel odometry - my team designed a custom odometry system and i’m sure they’d be happy to give you more information if you’d like. best of luck :)
- Where to learn how to set up Odometry??
OdometryCore
Posts with mentions or reviews of OdometryCore.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-09-19.
-
how do you all feel about the physical barrier?
as a result, two libraries were born - Pathfinder2 and OdometryCore. i'll spare you the details, but OdometryCore is a minimal and efficient position tracking system, and Pathfinder2 works some magic on top of that. for example, you can tell your robot to drive to (10, 10) and face 45deg, and it will do exactly that, assuming you calibrate your robot correctly. you're more than welcome to check one or both of those out if you're interested, but yeah - we're the only team i've spoken to that has NOT used roadrunner for odometry.
-
Robot localization with on-motor encoders
hey, i just figured i’d put this out here in case it helps: meccanum wheels, by nature, have a LOT of slip - that’s how they’re able to move in any direction. i’ve had quite a bit of experience with the math and kinematic behind this (two libraries i’ve written/am writing, Pathfinder and Pathfinder2, as well as a library the other programmer on my team wrote, OdometryCore) and it’s VERY HARD to accurately track the position of a meccanum robot only using the encoders in the wheels. it’s not impossible, but it’s very, very challenging. the more your robot moves, the less accurate it becomes, and it will very quickly report positions that are nowhere near where your robot actually is. you can go for it, but i would strongly encourage you check out three wheel odometry instead - it’s been very accurate and allowed us to do really cool things, like accurately record a robot’s movement and play it back perfectly. you’ll have much more success with three wheel odometry - my team designed a custom odometry system and i’m sure they’d be happy to give you more information if you’d like. best of luck :)
-
Odometry Code Help
If it interests you, here's the link: OdometryCore
- Where to learn how to set up Odometry??
What are some alternatives?
When comparing Pathfinder and OdometryCore you can also consider the following projects:
QDriverStation - Cross-platform clone of the FRC Driver Station
Pathfinder2 - Paths, trajectories, splines, the number 2, and a whole lot of swag.
allwpilib - Official Repository of WPILibJ and WPILibC
Open3D - Open3D: A Modern Library for 3D Data Processing
FtcRobotController
TitanUtil - A collection of utility classes to make robot programming easier
ARCoreInsideOutTrackingGearVr - Inside Out Positional Tracking (6DoF) for GearVR/Cardboard/Daydream using ARCore v1.6.0
AutoBuilder - A gui tool for graphically designing and testing autos in FRC
javabot-2022 - A Java rewrite and improvement of Team 2539's 2022 robot code.
ScoutingPASS - A FRC Competition Scouting Application
Pathfinder vs QDriverStation
OdometryCore vs Pathfinder2
Pathfinder vs allwpilib
OdometryCore vs Open3D
Pathfinder vs Pathfinder2
OdometryCore vs FtcRobotController
Pathfinder vs TitanUtil
OdometryCore vs ARCoreInsideOutTrackingGearVr
Pathfinder vs AutoBuilder
OdometryCore vs allwpilib
Pathfinder vs javabot-2022
Pathfinder vs ScoutingPASS