maliput / maliput/delphyne_gui
Display plugin for Maliput
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This is an issue to track developing a display plugin for Maliput. The starting point here could be the simple agent info plugin: https://github.com/ToyotaResearchInstitute/delphyne-gui/blob/master/visualizer/display_plugins/agent_info_display.cc
* [Milestone 3 Planning](https://docs.google.com/document/d/1UWfuwDBfYKSq-Jj4dM1AK6BiaV3v3DHA3PECetmGhdw/edit#heading=h.7o75ni93uzsf)
* [Design Doc](https://docs.google.com/document/d/1szeE4G9UTK_bk0SI8FOtGpoEYt4CS5wnDmeeIbx9rj8/edit)
Success Criteria:
* [ ] Maliput Plugin: enabled for all of our demos
- Essentially port the standalone viewer to an agent display plugin
- Success is getting to the same feature parity as the standalone one
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 with visualizer/display_plugins/agent_info_display.cc as the proposed plugin example, then read the linked Design Doc and Milestone 3 Planning document. Compare the standalone Maliput viewer's capabilities with the agent display plugin requirements. Done means the plugin reaches feature parity with the standalone viewer and is enabled for all demos.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100