open-rmf / open-rmf/rmf

[Other issue]: how do that visualization obstacle in rviz2 and gazebo

Open
#392 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
438
Forks
89
PR merge metrics
No merged PRs in 30d

Description

Before proceeding, is there an existing issue or discussion for this?
Description

image

I searching your repository. so I found rmf_obstacle like picture. I try that. so I want to detail. please..
how do that? /fleet_marker topic in rviz2 change Durability Policy "Transient Local". but error is spawn. like this

[obstacle_visualizer_node-9] [WARN] [1694504262.622905605] [rmf_obstacle_visualizer]: New subscription discovered on topic '/fleet_markers', requesting incompatible QoS. No messages will be sent to it. Last incompatible policy: DURABILITY_QOS_POLICY
[rviz2-10] [WARN] [1694504262.641238936] [rviz]: New publisher discovered on topic '/fleet_markers', offering incompatible QoS. No messages will be sent to it. Last incompatible policy: DURABILITY_QOS_POLICY

I really don't know like this picture. even there is not scan_data. the simulation is on gazebo? obstacle is human. but hmm.. human is not in gazebo. just like sofa, chair, table so on...

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin with the /fleet_markers topic and the rmf_obstacle_visualizer, rviz2, and Gazebo setup described in the report; reproduce the incompatible durability-policy warnings. Done should be a documented, working procedure for visualizing obstacles and configuring compatible QoS, including whether the obstacles appear in simulation.

Written by the indexing model from the issue text.

Assessment

Domain
computer-graphics, robotics
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.