Skip to content
This repository has been archived by the owner on Mar 21, 2021. It is now read-only.

Make a fancy shuffleboard #23

Open
LizzyMilford opened this issue Nov 12, 2018 · 6 comments
Open

Make a fancy shuffleboard #23

LizzyMilford opened this issue Nov 12, 2018 · 6 comments
Assignees
Milestone

Comments

@LizzyMilford
Copy link
Contributor

LizzyMilford commented Nov 12, 2018

Add all specified values to shuffleboard (or smartDashboard) and make a nice, easy-to-read layout. Create a new branch for this. It is stated where you can find chunks of code for each bullet point. Also test where shuffleboard stuff should be created to show up initially (and updated later in some instances).

Necessary on shuffleboard:

  • Camera feed (already on board, may be commented out, in master branch)

  • Auto selection sendable choosers (already on board, in master/clean-up and iterative branches, needs to be tested)

  • Drive encoder strike integer (in iterative branch)

  • PID values (for turning and driving, in any branch and in summer repo)

  • Baby mode sendable chooser (in master/clean-up, needs to be tested)

Nice to have on shuffleboard

  • Display real-time graphs

  • Preferences (PID values and other values)

Leave space for the FRC Driver Station to sit on top or bottom. Save any viable layouts. Check this frequently as more requirements may be added. See @LizzyMilford for more information

@OwenE20
Copy link
Contributor

OwenE20 commented Nov 22, 2018

Added all values relevant to main branch, need to test. Once verified and merged with main, I can add values only relevant to certain branches

@LizzyMilford
Copy link
Contributor Author

Looks good. I am going to go through and changing master to the iterative branch after I update it. Does this sound like a good idea? I thought it would be best to change 2018 and turret to iterative. If so, just be prepared to copy-paste after i finish. I can always do that for you if that doesn't sound fun

@OwenE20
Copy link
Contributor

OwenE20 commented Nov 22, 2018

For documentation purposes, we should try and keep main as close to representative of our season's code as possible. Since iterative is a pretty major overhaul it should be its own thing, If that makes sense

@LizzyMilford
Copy link
Contributor Author

Ok, so leave master in the base it is? Should we keep the iterative branch where it is or make it a new repo?

@OwenE20
Copy link
Contributor

OwenE20 commented Nov 22, 2018

Yeah, leave master as it is. And if we want to practice with an iterative base, we might as well make a new repo imo

@LizzyMilford
Copy link
Contributor Author

Sounds good. I think I will change master for the turret though to make sure that everyone gets practice with iterative

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

No branches or pull requests

2 participants