You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue:
Pathplanner's path is a little too close together for pure pursuit, and it takes a long time to generate and copy. Its better to just switch to generating paths internally.
Rather than using Pathplanner, I think it would be better to visualize bezier curves using something like Louis' Chassim a few years ago. It'll be more lightweight and allows us to display a vex field for even easier visualizaton.
How to approach:
Transfer lib4253's pathing components into HolonomicLib
The text was updated successfully, but these errors were encountered:
I see where you are heading, but I feel like it would be redundant if we copied the pathing from lib4253 over. Instead, I feel like it would be much cleaner to make HolonomicLib's pathing compatible with lib4253's path generation.
Issue:
Pathplanner's path is a little too close together for pure pursuit, and it takes a long time to generate and copy. Its better to just switch to generating paths internally.
Rather than using Pathplanner, I think it would be better to visualize bezier curves using something like Louis' Chassim a few years ago. It'll be more lightweight and allows us to display a vex field for even easier visualizaton.
How to approach:
Transfer lib4253's pathing components into HolonomicLib
The text was updated successfully, but these errors were encountered: