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

Occupancy grid #36

Closed
kevin-thankyou-lin opened this issue Apr 25, 2021 · 4 comments
Closed

Occupancy grid #36

kevin-thankyou-lin opened this issue Apr 25, 2021 · 4 comments
Labels
enhancement New feature or request

Comments

@kevin-thankyou-lin
Copy link

Thanks for the great project and codebase! Is there a way to get a 3D occupancy grid with which I can do obstacle avoidance trajectory generation?

@JacopoPan JacopoPan added the enhancement New feature or request label Apr 25, 2021
@JacopoPan
Copy link
Member

This is not something currently implemented but I could give it some thought, can you give me a small example of the scenario/output you would like to see? Should the occupancy grid be part of the obs (i.e. do you need it for RL) or could it be an additional entry in info (i.e. you are using the environment simply as a simulation?

@kevin-thankyou-lin
Copy link
Author

Gotcha, I was looking more for something like:

Airsim's Voxel grid construction (microsoft/AirSim#3209)

to get the 'ground truth' 3D state of the world. I'd use it as an additional entry in info - specifically, I'd want to use it for ground truth optimal planning.

I think we could use something like this voxelization tool for the .obj files for the sphere, samurai, etc URDFs (http://www.open3d.org/docs/latest/tutorial/Advanced/voxelization.html).

That said, I think I'm good without an occupancy grid at this stage, but thank you for helping!

@JacopoPan
Copy link
Member

I should give it some thought. Note that collisions are managed by PyBullet (see the collision queries api) using the collision shapes specified in the .urdf file of each drone/object (these could be simple geometries or .dae/.obj meshes). The ground truth position/orientation of any object in the sim can be retrieved with a call to p.getLinkState(), then (knowing the collision shape/mesh of each object) one could use Open3D's voxelization. I have to look into how to use basic geometries and multiple meshes in a single Voxel grid but I suspect it could result in a significative computational overhead.

@kevin-thankyou-lin
Copy link
Author

Sounds good! Yeah, it'd probably result in significant computational overhead.

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

No branches or pull requests

2 participants