Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Choreo to PathWeaver replacements #2800

Merged
merged 1 commit into from
Oct 16, 2024

Conversation

spacey-sooty
Copy link
Contributor

No description provided.

@calcmogul
Copy link
Member

calcmogul commented Oct 15, 2024

I'd link to both PathPlanner and Choreo, since Choreo can't do on-the-fly planning while PathPlanner can, and Choreo and PathPlanner have interop.

@TheTripleV
Copy link
Member

No library wars pls

Just include both?

@spacey-sooty
Copy link
Contributor Author

No library wars pls

That wasn't the intention, Choreo is bundled in the installer whereas pathplanner isnt so imo it made more sense to recommend it.

I can link to both

@rzblue
Copy link
Member

rzblue commented Oct 15, 2024

It still reads as pathplanner being an afterthought/lesser alternative

@spacey-sooty
Copy link
Contributor Author

It still reads as pathplanner being an afterthought/lesser alternative

IMO since choreo is in the installer we should first recommend that then suggest pathplanner if people need features it offers

@spacey-sooty spacey-sooty changed the title Change recommended swerve trajectory planner to Choreo Add Choreo to PathWeaver replacements Oct 16, 2024
@spacey-sooty spacey-sooty force-pushed the recommend-choreo branch 2 times, most recently from 90ea64f to 3757a01 Compare October 16, 2024 03:08
Signed-off-by: Jade Turner <spacey-sooty@proton.me>
@jasondaming jasondaming merged commit bd63608 into wpilibsuite:main Oct 16, 2024
10 checks passed
@spacey-sooty spacey-sooty deleted the recommend-choreo branch October 16, 2024 04:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants