-
Notifications
You must be signed in to change notification settings - Fork 279
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
[yt-4.0] ds bbox selection bug #2612
Comments
Prior to this commit These numbers are equal. But I think that commit was correct and this is a different bug! |
I think the case might be that the particle index is bounding box specific and thus the bounding box could be incorporated into the hash, so it will gen a new particle index with loaded with a new bbox. Otherwise, maybe the loading bounding box should be ignored during index creation and applied afterwards? The particle index is not my area of expertise |
So, after the merge of #2618 the above script works. However, I don't think #2618 has completely solved the problem. In the following test script I test the chunk loading with a bbox and without one and I select a specific range,
which outputs:
The summary is: yt correctly builds a particle index and instead of selecting zero particles, it now select every particle. But, if I remove the bounding box, then it only selects particles in the range I specified. |
You can see without a bbox the yt chunking only returns 1898397 particles, which is the correct amount in that region. However, with a bbox yt just returns every particle in the simulation. This is why the covering_grid and octree work with the patch, because they get given every particle and discard the ones they don't need. Do you have any ideas what is happening here @matthewturk @munkm - I'm lost! |
So I think that what might be happening is that there's an asymmetry in loading vs caching. Without the fix in #2624 , it's possible to load a cache if we have generated one before. So with a bbox it will use the existing EWAH index on disk. |
In that case- I don't think I appreciate the difference between loading and caching... |
Looks like we forgot to close this when we merged #2634 |
Bug report
Bug summary
Building particle index with bounding box and then loading without leads to strange particle selection. After re-loading the particle count in a region is different
Actual outcome
The two numbers should be equal
The text was updated successfully, but these errors were encountered: