dimensionalOS / dimensionalOS/dimos
Dimos Viewer Clicking/Teleop channel should use same grpc rerun connection
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
ATM dimos-viewer (rerun) has a hacked-in secondary websocket connection that connects to our own websocket listener WebsocketVisModule - this requires us to run an extra module, pass secondary port etc. should use the same channel as rerun.
should be able to do rerun.subscribe('click', ...) or something like this
related issue to perhaps keep in mind is rerun interfaces https://github.com/dimensionalOS/dimos/issues/1961
Synced from DIM-831 by summer
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 tracing dimos-viewer's secondary WebsocketVisModule connection and the current Rerun channel used for viewing. Compare how click and teleop events are exposed, then determine how they can use the same grpc Rerun connection. Done means no extra websocket module or secondary port is needed and clicking/teleop events still work through the shared channel.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, python
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100