Fix failing GPU tests (due to incorrect unit for rest_radius) #1057
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.
Description
This PR removes the
rest_radius
argument from thePointMutationExecutor
in two tests. Instead, we will just use thePointMutationExecutor
defaultrest_radius
.Motivation and context
This PR fixes the failing GPU test_relative.py tests: test_unsampled_endstate_energies_GPU and test_RESTCapableHybridTopologyFactory_energies_GPU. The tests were failing because
rest_radius=0.2
was being passed to thePointMutationExecutor
, but in #1046, we changedrest_radius
to be a unit-bearing quantity, so it really should berest_radius=0.2 * unit.nanometer
.Resolves #???
How has this been tested?
Change log