-
Notifications
You must be signed in to change notification settings - Fork 37
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
New Mesh: Add ARRM10to60E2r1 mesh #414
Conversation
Hello @xylar! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:
Comment last updated at 2022-08-30 15:12:58 UTC |
a42b390
to
da146bd
Compare
compass/ocean/tests/global_ocean/mesh/arm10to60/dynamic_adjustment/__init__.py
Outdated
Show resolved
Hide resolved
compass/ocean/tests/global_ocean/mesh/arm10to60/namelist.split_explicit
Outdated
Show resolved
Hide resolved
compass/ocean/tests/global_ocean/mesh/arm10to60/namelist.split_explicit
Outdated
Show resolved
Hide resolved
@darincomeau and @milenaveneziani, if you can please figure out the missing pieces while I'm on vacation next week, I can finish this PR up when I get back to work on July 4th (not a holiday for me). I'm still working on building the mesh but it should be done soon(ish). Here is the resolution map and construction history: I don't plan to try to create the initial condition run any of the other tests cases until we resolve the questions above. |
It looks as if critical passages are off by default: https://github.com/MPAS-Dev/compass/blob/master/compass/ocean/tests/global_ocean/mesh/cull.py#L15 Update: What I said is not true. Critical passages are always on: https://github.com/MPAS-Dev/compass/blob/master/compass/ocean/tests/global_ocean/mesh/mesh.py#L90 |
compass/ocean/tests/global_ocean/mesh/arm10to60/namelist.split_explicit
Outdated
Show resolved
Hide resolved
compass/ocean/tests/global_ocean/mesh/arm10to60/namelist.split_explicit
Outdated
Show resolved
Hide resolved
@xylar many thanks for getting this started! @milenaveneziani and I are also on vacation next week, but I was able to address some of the comments. Would you prefer I push to this branch, or leave it to you based on the comments? |
Ah, okay. Then just keep the comments coming today and we'll pick up in a week.
I think having you comment here and me change things is best for now. I imagine the dynamics adjustment will take a bit of trial and error. Probably it would make sense for whoever does that work to then push the final result to the branch at the end. |
restart_times = ['0001-01-01_06:00:00', '0001-01-01_12:00:00', | ||
'0001-01-02_00:00:00', '0001-01-03_00:00:00', | ||
'0001-01-04_00:00:00', '0001-01-07_00:00:00', | ||
'0001-01-31_00:00:00'] |
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.
@darincomeau and @milenaveneziani, as a starting point, I would recommend doing a month of integration like we did for WC14. As is hopefully clear here, we rand for 6 hours, 6 hours, 12 hours, 1 day, 1 day, 3 days and finally 24 days.
'config_dt': "'00:00:30'", | ||
'config_btr_dt': "'00:00:01.5'", | ||
'config_Rayleigh_friction': '.true.', | ||
'config_Rayleigh_damping_coeff': '1.0e-3'} |
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.
For each step (except simulation
), these are the values you'll want to adjust. We could try the same as the WC14 to begin with but likely the time steps will need to be reduced because of the difference in minimum resolution.
Run each damped_adjustment
step in compass on its own (rather than trying to run this as a suite). Monitor the global CFL number and the kinetic energy. If the CFL gets much over 0.1, you're in trouble. If the KE spikes, you're in trouble. Some combination of a shorter time step and more Rayleigh damping typically helps.
1bbd230
to
e0c754b
Compare
@milenaveneziani, I switched from ARM to ARRM and to the 80-layer vertical grid, as you requested. I'm in the car so don't have time or battery life to try this out yet. Maybe give it a try yourself if you have time. |
e0c754b
to
f1de868
Compare
@milenaveneziani, I don't think one more layer will make an appreciable difference based on past experience. We just need to fix Redi so this doesn't happen. |
ok, let's leave it at 15 then. |
The mesh resolution has been ported from legacy COMPASS.
bb1d7ad
to
4e64c3e
Compare
@milenaveneziani, @darincomeau and everyone, I am opening this back up for review after #429 just got merged. I'm happy to run this mesh through its paces again but wanted to make any changes you all might want before doing that. |
Thanks @xylar. To update on the B-case, I'm almost at 20 years (3 months to go) on the Cori run, at which point I'm hoping we'll have enough to be able to approve the mesh, at which point I'll open the E3SM PR. I realize previously we did 50 years, but I'm hoping 20 years will be sufficient. The throughput on Cori has been incredibly slow; as to the Anvil suggestion, I was a bit wary of running a simulation there since this is primarily for a different project, especially given how busy that machine has been lately, and we'd still probably get only about 2 SYPD on a medium size layout. |
@darincomeau, thanks for the update. I can see the challenges with Anvil, though it sounds like 2 SYPD would still be an improvement on what you're getting on Cori. |
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 this is good to go.
Linking the E3SM PR: E3SM-Project/E3SM#5178 |
@xylar here is the path for the ocn grid/IC file we ended up using for E3SM-Project/E3SM#5178
|
Thanks @darincomeau. I created a permanent branch (https://github.com/MPAS-Dev/compass/tree/ARRM10to60E2r1) and tag (https://github.com/MPAS-Dev/compass/tree/mesh_ARRM10to60E2r1) for the version of this mesh you used in E3SM-Project/E3SM#5178. I'll review the E3SM PR as soon as I can. |
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.
@xylar thanks for all this! (Sorry I meant to do this yesterday).
Thanks! merging... |
Add script support for ARRM10to60E2r1 ocn/ice grid Brings in support for the ARRM10to60E2r1 ocn/ice mesh. MPAS-Dev/compass#414 has details on the mesh generation, which is an updated version of the oARRM60to10 mesh. This PR includes all necessary mapping, runoff, and domain files for the following configurations: * ne30pg2_ARRM10to60E2r1 * arcticx4v1pg2_ARRM10to60E2r1 * TL319_ARRM10to60E2r1 (JRA-forced) * T62_ARRM10to60E2r1 (CORE-forced) [BFB] for all currently tested configurations
Add script support for ARRM10to60E2r1 ocn/ice grid Brings in support for the ARRM10to60E2r1 ocn/ice mesh. MPAS-Dev/compass#414 has details on the mesh generation, which is an updated version of the oARRM60to10 mesh. This PR includes all necessary mapping, runoff, and domain files for the following configurations: * ne30pg2_ARRM10to60E2r1 * arcticx4v1pg2_ARRM10to60E2r1 * TL319_ARRM10to60E2r1 (JRA-forced) * T62_ARRM10to60E2r1 (CORE-forced) [BFB] for all currently tested configurations
The mesh resolution has been ported from legacy COMPASS.