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

Document the Design Decision Behind Technical Decisions #1366

Open
jasondaming opened this issue Jun 3, 2021 · 2 comments
Open

Document the Design Decision Behind Technical Decisions #1366

jasondaming opened this issue Jun 3, 2021 · 2 comments

Comments

@jasondaming
Copy link
Member

jasondaming commented Jun 3, 2021

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.

@Daltz333
Copy link
Member

Daltz333 commented Jun 3, 2021

I think this warrants further discussion on the implementation and benefits before moving forward. This is overall a good idea.

@Daltz333
Copy link
Member

Daltz333 commented Jun 4, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants