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

Voxel Grid Creation gives erroneous information on some grid settings #4810

Open
WreckItTim opened this issue Mar 16, 2023 · 1 comment
Open

Comments

@WreckItTim
Copy link

Bug report

  • AirSim Version/#commit: 1.8.1
  • OS Version: Ubuntu 22.04.2 LTS

What's the issue you encountered?

When creating a voxel image from the Blocks (1.8.1 Linux) release, if using a cube with dimensions greater than 250 (125 meters in each direction from origin) - then the voxel grid gives erroneous booleans. For example the images below show the floor and objects in the map when calling:

client.simCreateVoxelGrid((0,0,0), 300, 300, 300, 1, path).

floor:
image

objects:
image

You can see holes in each. I am assuming this happens because I am using a cube outside of some preset rendering boundaries (can't simulate to infinity after all). However it is not intuitive to where the boundaries for each release are. If this is the case, then listing the valid dimensions of each release would be beneficial. Also, if the dimensions are not a cube I think voxels has some wonky behavior...

Here is what the images look like when calling with a valid working-range cube that I empirically found:

client.simCreateVoxelGrid((0,0,0), 250, 250, 250, 1, path).

floor:
image

objects:
image

It's odd that if you use a cube outside of the valid range - that it causes holes within the valid range, as opposed to just not returning booleans for coordinates outside of the valid range. This raises concerns on not just the Voxels but how the simulation operates if the drone wanders somewhere outside of the 125x125x125 cube (rendering, collisions, stability). This might be a source of some instabilities I have been running into? Another problem for another time...

@xxEoD2242
Copy link

Hey @WreckItTim,

I've seen very similar errors but have never had an issue with the agent becoming unstable very far away from the origin. I believe there is a core issue with their Voxel Grid calculation when not doing cubes.

Also, if you are using Numpy, the y axis is the first index (row major) which could cause issues with planning and the like.

Since AirSim is not longer being developed, we continued it here: Colosseum

I've been recently doing work with occupancy maps generated by the voxel grids with multi-agent, which you can see here (it's a longer video): Link. Works so far!

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