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
Pure Pursuit vs Ramsete
Motion Magic is Profiled
Path Planning with alternatives
On motor controller vs on RIO PID
Java/C++/LabVIEW pro/con
Command Based vs Not
Dashboards Comparison
All of these should remain as fact based as possible and only include things that would be accepted by "all" parties.
The text was updated successfully, but these errors were encountered:
I think this should be split into separate issues, as I feel the content could be split into individual articles.
I do have overall questions
Who writes what?
I feel that the more technical articles won't get written due to requiring intimate knowledge. You could scrounge up the information from other sources, but it's not a trivial task.
We should avoid vendor specific references.
I'm specifically talking about CTRE Motion Magic vs ProfiledPIDController, I feel like we could abstract this to just "onboard" vs rio-based loops as you already said.
Regarding Java vs C++ vs LabVIEW, we should focus on presentation instead of comparing/contrasting. Bullet point lists can too easily lead into bias and can be complicated or difficult to solve. Presenting this content in a way where it suggests local support and an overview of each language would be a good idea. Honestly, I am in favor of putting this content in ZTR.
Pure Pursuit vs Ramsete
Motion Magic is Profiled
Path Planning with alternatives
On motor controller vs on RIO PID
Java/C++/LabVIEW pro/con
Command Based vs Not
Dashboards Comparison
All of these should remain as fact based as possible and only include things that would be accepted by "all" parties.
The text was updated successfully, but these errors were encountered: