FRC1076 / FRC1076/2019-Competition
Decide if it is okay that speed selector goes from .1 to .9 (fix it
Open
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
The switch has 5 positions that are read via getRawAxis(2).
.1, .3, .5, .7, and .9
If we want to "go to 11", we could make an adjustment when we read it. (adding .1).
Seems like something we should know.
matthew
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the code that reads the speed selector through getRawAxis(2) and inspect how its five positions are interpreted. Confirm the intended selector range with the project context, then verify that the implemented values and behavior match that decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- robotics
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100