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
A current pain point is that for parallel queries of faces/boxes/edges, the tree is traversed twice: once to count and allocate, and again to actually store results. This is primarily because we have no threadsafe list or something to append to, across threads.
A simpler scheme, however, is to chunk by the number of threads, create a (C++-like) vector for each, and append to that.
A current pain point is that for parallel queries of faces/boxes/edges, the tree is traversed twice: once to count and allocate, and again to actually store results. This is primarily because we have no threadsafe list or something to append to, across threads.
A simpler scheme, however, is to chunk by the number of threads, create a (C++-like) vector for each, and append to that.
I've setup a implementation:
In
query.py
:And calling it in
celltree.py
:Then benchmarking it:
Unfortunately, results are rather disappointing:
The text was updated successfully, but these errors were encountered: