wpilibsuite / wpilibsuite/SystemcoreTesting
Built-in vision functionality monopolizes camera
Open
Nobody has claimed this yet.
Limelight
Pending
- Dominant language
- Java
- Stars
- 186
- Forks
- 24
- Avg merge
- 8h 27m
- Merged PRs (30d)
- 9
Description
There should probably be a "None" pipeline type to allow teams to use the camera for custom vision processing or temporarily disable a camera for CPU purposes without needing to unplug it.
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 tracing where the built-in vision pipeline claims and configures the camera, then identify how pipeline types are represented. Done means a None option can leave the camera available for custom vision processing or disable it without unplugging the device, with the relevant behavior covered by tests if the project has them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- computer-vision, embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100