Rework sharding tests #4293
Open
Rework sharding tests #4293
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
….jl into ss/fix-sharding-tests
….jl into ss/fix-sharding-tests
….jl into ss/fix-sharding-tests
….jl into ss/fix-sharding-tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A bunch of correctness issues have been solved.
The sharding tests pass locally. However, over 100 timesteps the difference is not machine precision but rather larger (~1e-11). This is probably expected, given that the split explicit free surface is running O(10) substeps per time step.
For this reason, I have relaxed the tolerance of the tests to
sqrt(eps(Float64)