Kit-path parity audit and gap closure
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 385
- Forks
- 88
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 82
Description
Enumerate what the Kit-based teleop path supports (session/blend modes, visualizer features, settings) and verify or close each gap in the kitless path; the umbrella for "everything Kit does, kitless does." Ensure ovphysx and newton libraries work in example environments.
Contributor guide
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 enumerating the Kit-based teleop path's session and blend modes, visualizer features, and settings, then compare them with the kitless path. Check the ovphysx and newton libraries in the example environments; done means each identified gap is verified or closed and library use works there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- robotics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100