Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using RGB-D camera instead of 3D Lidar #16

Open
ta-jetson opened this issue Apr 17, 2024 · 1 comment
Open

Using RGB-D camera instead of 3D Lidar #16

ta-jetson opened this issue Apr 17, 2024 · 1 comment

Comments

@ta-jetson
Copy link

ta-jetson commented Apr 17, 2024

Hey @MihirDharmadhikari @engcang @ShreyanshDarshan,
I want to use a front facing depth camera instead of a 3D Lidar. I want to evaluate the working of the algorithm with limited FoV and range.

I tried to follow @engcang
changes in
#4 (comment)

I changed the SensorParams in global_planner_config.yaml and mbplanner_config.yaml as:

type: kCamera
max_range: 6.0
center_offset: [0.0, 0.0, 0.0]
rotations: [0.0, 0.0, 0.0]
fov: [rad(pi/2), rad(pi/3)]
resolution: [rad(5.0pi/180), rad(3.0pi/180)]

The simulation runs as usual and there is no change in FoV or range of the pointcloud

Screenshot from 2024-04-17 18-39-52

Please let me know if I missed something?
I am actively working on this problem, so any suggestion would be helpful

Thank you,

@MihirDharmadhikari
Copy link
Collaborator

Hi @ta-jetson ,

The parameter that you have changed is used only for volumetric gain calculation. You also need to provide a point cloud from a depth camera to the planner which is set in this parameter. Currently, the M100 does not integrate a depth camera. However, the underlying rotorS simulator has a model of a depth camera which you can add on the M100 similar to this.

Let me know if this helps.

Best regards,
Mihir

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants