-
Notifications
You must be signed in to change notification settings - Fork 1
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
Tests using physical simulations #247
Conversation
…an from dummy run
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is really great! Thanks @nichollsh.
We should consider to extend this test to a resume simulation for a later stage of planet evolution (again, for a couple of iterations). It will not increase the coverage but check code behaviour in another range of parameters.
Yes I definitely agree. I think particularly once we have also looked into #193. |
Thanks @lsoucasse! |
We currently have tests using the Dummy simulations. This checks that the module coupling works okay and the dummy modules are working.
It is absolutely necessary to add tests for the physical modules. This PR introduces some initial tests for these, although they will surely be subject to change in the future. It runs PROTEUS with JANUS+Aragog+MORS+CALLIOPE for a few model steps. It does not run until convergence as this would take too long. Workflow runtime is about 5 minutes. Closes #237.
This increases the coverage from 45% to 59%. We could get this to ~65% if we included an AGNI test, but this would probably be quite slow.
Implementing these physical tests required adding installation steps for SOCRATES and Aragog to the CI workflow. These use caching to speed things up.
Includes a few bug fixes:
GitHub records that a lot of files were changed, but most of these are changes to the test data. Apologies for the many random commits - it took some work to get the CI workflow working properly. The key thing with this is the order in which the modules are checked-out.