-
Notifications
You must be signed in to change notification settings - Fork 19
Port merry-go-round testcase from compass #284
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
Conversation
|
@andrewdnolan Looking great so far! Just a few minor suggestions |
2989d96 to
03aaea4
Compare
|
Analysis task now works as of bd2fc01 and achieves a convergence of ~1.74: |
Not per se correct, but needed to that the area calculation for error norm has correct dimensions. Stopped computing converg. rates for tracers 2 & 3 following compass.
Needed for specifiying the culled mesh, as compared to the base mesh as used in all the previous test cases.
The number of vertical layers, for the base resolution, is now read from the config file. Then that's scaled by the refinement factor.
Run the viz step first, so that even if convergence fail the viz step is run. Usefull for diagnosing problems if not converged
Co-authored-by: Carolyn Begeman <[email protected]>
More detailed plotting for default task. Includes cross sections of verticala and horizontal velocity, in addition to the tracer and difference in the tracer.
e99b707 to
764ee71
Compare
|
Sorry about the delay in this. But I have now ported the documentation, which can be viewed here: https://portal.nersc.gov/cfs/fanssie/anolan/merry_go_round/html/test/index.html @cbegeman you might be able to help with a better description of the vertical coordinate in the user guide. Sorry my description is so brief, I'm don't have the best grasp of the vertical coordinate details in mpas-ocean. |
TestingTesting and development have been done on polaris setup --clean -n 96 97 98 99 -w $PSCRATCH/merry_go_round
cd $PSCRATCH/merry_go_round
salloc --nodes 1 --qos interactive --time 00:30:00 --constraint cpu --account e3sm
source load_polaris_env.sh
polaris serial Outputpolaris.log@cbegeman I'm still unable to get convergence in just time, per the failure in the |
| The mesh is planar and the resolution is specified by config option | ||
| `convergence:base_resolution`, which defaults to 5 m. The horizontal |
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.
I think it might be confusing for folks that in order to change the resolution for the default task they need to change options in the convergence section. I would prefer that we have a new section merry_go_round_default that has any options that are used only by the default case (which may be just resolution).
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.
Thanks for suggestion! I totally agree, that seems less confusing.
I don't think it's your responsibility to debug this. I think we just add only the tests that pass to the test suites. I think we minimally need the default test in the pr suite and the convergence_both test in the convergence suite. |
|
Compass contained some x offsets in the function that defines the initial velocity. These led to artifacts: I have changed the IC to remove those artifacts and receive much smaller errors: And convergence that is close to the theoretical value of 2: |
cbegeman
left a comment
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.
Now that the initial condition is fixed, this is ready to go in. Thanks for all your work on this @andrewdnolan!




The merry-go-round test group is used for testing the vertical advection scheme only using tracers. This PR ports the
Defaulttest case from themerry_go_roundtest group fromcompass. This PR also adds convergence tests in space and both space and time.Checklist
api.md) has any new or modified class, method and/or functions listedTestingcomment in the PR documents testing used to verify the changes