You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently using the Intel RealSense D405 camera in a Gazebo simulation environment to replicate real-world scenarios. The purpose of my work is to scan a specific scene and emulate what a robot would see in real life using the camera in Gazebo. However, I am encountering significant inconsistencies between the point cloud data captured by the D405 camera in the simulation and the point cloud data captured in real life.
I am using the following xacro files for the camera setup:
However, the D405 model differs from most of the other RealSense 400 Series models in that its default depth scale is 0.01 because it is designed to specialize in close-range depth sensing.
Hello,
I am currently using the Intel RealSense D405 camera in a Gazebo simulation environment to replicate real-world scenarios. The purpose of my work is to scan a specific scene and emulate what a robot would see in real life using the camera in Gazebo. However, I am encountering significant inconsistencies between the point cloud data captured by the D405 camera in the simulation and the point cloud data captured in real life.
I am using the following xacro files for the camera setup:
_d405.gazebo.xacro
<xacro:macro name="gazebo_d405" params="camera_name reference_link topics_ns depth_optical_frame color_optical_frame infrared1_optical_frame infrared2_optical_frame publish_pointcloud:=true" >
</xacro:macro>
_d405.urdf.xacro
<xacro:macro name="sensor_d405" params="name:=camera topics_ns:=camera parent *origin publish_pointcloud:=true">
<xacro:property name="M_PI" value="3.1415926535897931" />
</xacro:macro>
test_d405_camera.urdf.xacro
Could you please provide guidance on how to better match the simulated point cloud data with the real-world data?
Thank you for your assistance
ros version: noetic
The text was updated successfully, but these errors were encountered: