-
Notifications
You must be signed in to change notification settings - Fork 1
Refactored main and restructured code #31
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
Closed
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
…tructure there are still a lot of broken imports and references, so the code does not run yet.
…_main__.py still untested as I have to move the analysis steps to the DA subpackage before this will run
also created a placeholder for the parallel integrator tests planned
the restructuring continues
DA and blending are not covered in the tests, will look into them after refactoring the flow solver
since I removed all initial conditions except this
this is with the new ensemble data structure; the flow solver runs; yet to be tested.
…rrays at the end of the flow solver's looping this is because the tests were failing with a discrepancy.
validation step will be moved to dataclass structure
I will review. Are the docs checks supposed to succeed? |
Thank you. The checks broke due to the renaming of the subpackages. This issue has been resolved with the latest commits. But the pytests are broken now, as I am in the midst of restructuring the diagnostics module to accept more general definitions of test cases. |
now that we have the unstable lamb wave, the actual lamb wave test is now a long 800-time-step run. The internal long wave and travelling vortex use the integrated hydrostatic module, and the rest of the test cases use the analytical hydrostatic state (exponentially decaying pressure). These four flow solver tests took me a minute to run on my laptop, and they produce pretty large output files, especially for the long lamb wave run. Possibly have to improve this in the future.
…round the former was the default and works for most cases, while the latter is necessary for well-balanced numerical tests.
unstable test passed
I am excluding the data assimilation module for now.
I can think of a better approach in the future
I hope the GitHub Actions work now
…e lamb test unstable lamb test is failing on CI as the numerical instability is architecture dependent. So maybe if we relax the checks, we can ensure that the instability develops similarly but also allow for numerical differences.
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.
__main__.py
is now cleaned, and all the initialisation and analysis steps have been moved to their respective modules or subpackages.