MARSProgramming / MARSProgramming/m18_autopilot_doglog
propose automation level control
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
automation level control allows us, for an aligning and scoring action, to control what is automated.
In the event of a vision system failure, the operator should be able to use the Shuffleboard to toggle automation off, in which case the only commands that will run are elevator setpoints.
Operator needing to have control has been made obsolete, so the Operator/copilot will instead monitor the shuffleboard for robot state.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the aligning and scoring action, the current vision-system and operator controls, and the Shuffleboard state handling. Define how the automation toggle affects those actions: when off, only elevator setpoints should run, and the operator should monitor robot state through Shuffleboard.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- robotics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100