Continuous integration tests for sampling #525
Conversation
This file contains 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
thjsal
changed the title
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.
I added a couple of new GitHub CI tests checking that
unit_hypercube_fracreturns the same value as before.Sampling with UltraNest does not crash. To make this test work I needed to add a requirement that GitHub installs UltraNest version that is newer than 4.0. Otherwise, test failed if using python3.9 or python3.10 (where it installed older UltraNest by default, which seemed inconsistent with the installed Numpy version).
I tried also adding a test for MultiNest, but could not in the end get the test program to find the MultiNest library files. However, I left the MultiNest installation and the corresponding test there as commented out if someone will figure out how to get it working.