[Feature request]: Site Editor live visualization
Maintainers usually reply within 15 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- rust
- Domain
- backend-api-design, frontend, robotics
Research direction
No files or entry points are named. Start by comparing the ROS2-enabled Site Editor approach with the WebSocket or REST bridge, then define how robot positions, planned paths, traffic dependencies, safe operating zones, and optional Nav2 status will reach the visualization. Done means a selected integration approach and a working live visualization for the listed data.
Written by the indexing model from the issue text.
Description
Before proceeding, is there an existing issue or discussion for this?
- I have done a search for similar issues and discussions.
Description
The Site Editor offers a more modern user interface and superior cross-platform packaging and distribution capabilities compared to alternative visualization platforms.
Implementation Considerations
- Visualize real-time robot positions derived from odometry data.
- Display planned paths and cross-agent traffic dependencies.
- Visualize safe operating zone boundaries (bubbles).
- Stretch goal: Incorporate additional relevant Nav2 status information.
Alternatives
- ROS2-Enabled Site Editor Application: One approach is to develop a custom application built on the Site Editor that links with ros2_rust. However, this introduces significant challenges regarding the packaging and distribution of a ROS2 application for end-user debugging.
- WebSocket or REST-Based Bridge to Core RMF Topics: Similar to rmf_web, this approach involves directing the Site Editor to a specified server URI, enabling the real-time streaming of robot positions over the network.
- Dominant language
- Python
- Stars
- 10
- Forks
- 9
- Avg merge
- 3h 21m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from open-rmf/next_gen_prototype
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 8/100
open-rmf/next_gen_prototype#81 ·
Maintainers usually reply within 15 days
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
open-rmf/next_gen_prototype#80 ·
Maintainers usually reply within 15 days
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
open-rmf/next_gen_prototype#66 ·
Maintainers usually reply within 15 days
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
open-rmf/next_gen_prototype#65 · 2 comments ·
Maintainers usually reply within 15 days
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 42/100
open-rmf/next_gen_prototype#57 ·
Maintainers usually reply within 15 days
All issues in open-rmf/next_gen_prototype
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
deepchem/deepchem#5289 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
UKGovernmentBEIS/inspect_evals#2892 · 1 comment ·
Maintainers usually reply within 1 day
-
Versioning docs: say that no output from the 0.46 warning check means nothing is affectedPossibly taken @grelinfo claimed this today. Opendocumentation priority:low size:S
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
alphacrack/readme2demo#293 ·