Skip to content
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

Add config_dt for 60km to 3.75km oQU grids #11

Merged
merged 3 commits into from
May 21, 2024

Conversation

gdicker1
Copy link
Contributor

@gdicker1 gdicker1 commented May 15, 2024

This is an attempt to use the namelist files to select the config_dt for mpas-si instead of doing it in an user_nl_mpassi file or by shell commands.

Important context for these values: EarthWorksOrg/EarthWorks#45 (comment)

@gdicker1 gdicker1 requested a review from dazlich May 15, 2024 18:08
@gdicker1 gdicker1 self-assigned this May 15, 2024
@gdicker1
Copy link
Contributor Author

@dazlich, I'm not certain of these values but thought they would be a good "first stab" at the settings. Let me know what you think!

Copy link
Contributor

@dazlich dazlich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these the values that have been used with QPC6? I think QPC6 jets may not be quite so strong as we will get in an F-case or fully-coupled. We may need have different sets for different cases. I know my 30km F simulations require shorter than 450s - I've been using 240s, not sure we can get away with 300s.

@dazlich
Copy link
Contributor

dazlich commented May 15, 2024

Let's find out what Brian Dobbins is using for the 3.75km DYAMOND case and work up from there.

Copy link
Contributor

@dazlich dazlich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oops, these are for the ice (and ocean presumably, too). I should've looked more closely.

These should be 2*mpas_dt, which should also be the coupling interval/cam physics timestep. Do we have defaults set for mpas_dt?

Copy link
Contributor

@dazlich dazlich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just heard from Brian Dobbins about what he is doing - In QPC6 at 3.75km he is using mpas_dt = 20s and a coupling frequency of 60s - this matches config_dt=60. which you suggested. The coarser resolutions match up with reasonable mpas_dt*3. So it looks good to me.

Will you be doing the same for the mpas-ocean?

@gdicker1
Copy link
Contributor Author

Just heard from Brian Dobbins about what he is doing - In QPC6 at 3.75km he is using mpas_dt = 20s and a coupling frequency of 60s - this matches config_dt=60. which you suggested. The coarser resolutions match up with reasonable mpas_dt*3. So it looks good to me.

Thanks for checking on this, I'm glad the first stab was right!

Will you be doing the same for the mpas-ocean?

It looks like we already have some in namelist_defaults_mpaso.xml L37-45. Do you think those are appropriate?

@dazlich
Copy link
Contributor

dazlich commented May 16, 2024 via email

@gdicker1
Copy link
Contributor Author

Except for QU120, the defaults need to be changed for the ocean and set identical to the ones in seaice.

Understood, I'll get this PR merged and open a similar one in EWOrg/MPAS-O. I plan to include these as part of EWOrg/EW #45

@dazlich
Copy link
Contributor

dazlich commented May 16, 2024 via email

@gdicker1 gdicker1 merged commit b28bbe3 into EarthWorksOrg:ew-develop May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants