Add batched EnergyDensityEstimator short statistical integration test #5207
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds an application level short test for the batched EnergyDensityEstimator
However on my system the test fails because after 250 blocks the paticle moves start moving out of the period cell. The legacy energy estimator doesn't check that the coordinate to cell mappings land in the grid, but I now bound check this access so the test fails. Even if i don't I segfault eventually because overflow writes are occurring.
These out of bounds particles are pretty rare but it seems certain at least on my test system that they will occur in a run the size of the short run.
This seems to point to a likely bug in the particle moves. I will explore further tomorrow.
This PR though make it possible to run the EnergyDensityEstimator with the full app which was actually impossible without the fix to the virtual write function.
What type(s) of changes does this code introduce?
Delete the items that do not apply
Does this introduce a breaking change?
What systems has this change been tested on?
dgx 2
Checklist
Update the following with a yes where the items apply. If you're unsure about any of them, don't hesitate to ask. This is
simply a reminder of what we are going to look for before merging your code.