-
In the example https://nvidia.github.io/warp/_build/html/modules/runtime.html#hash-grids The code creates a query @mmacklin Is this redundant, or is the radius in the hash grid query not really creating a query based on that radius? The doc: https://nvidia.github.io/warp/_build/html/modules/functions.html?highlight=hash_grid_query#warp.hash_grid_query says |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hi @cadop, the HashGrid will give back all points in cells that fall inside the query radius. When there are hash conflicts it means that some points outside of query radius will be returned, and you should check for this in your kernel as well. The reason the query doesn't do the check itself is that usually the first thing kernels do is to compute the distance themselves, so it would be redundant (like you mentioned). I will make this more clear in the docs. Thanks, |
Beta Was this translation helpful? Give feedback.
Hi @cadop, the HashGrid will give back all points in cells that fall inside the query radius. When there are hash conflicts it means that some points outside of query radius will be returned, and you should check for this in your kernel as well.
The reason the query doesn't do the check itself is that usually the first thing kernels do is to compute the distance themselves, so it would be redundant (like you mentioned).
I will make this more clear in the docs.
Thanks,
Miles