-
Notifications
You must be signed in to change notification settings - Fork 30
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
Set default resolution with variables in tests #141
Set default resolution with variables in tests #141
Conversation
Feature/add comparisons (#4)
merge develop/ufs-s2s-model
MOM_input template for initial condition files
merge fv3atm/develop
This reverts commit 0c8cb0b.
merge to latest develop
Debug mode capablility (#15)
Add debug compilation flag specification at top level (#17)
update to current ufs-weather-app (#19)
nomerg2atm, new MOM6 dev/emc
This reverts commit 57236a6.
Update FV3, NEMS (#21)
Update2020 01 (#23)
Update NEMS,FV3,CICE (#28)
Add CCPP to UFS-S2S-model
Remove IPD tests and CCPP repro tests from the regression test system…
Feature/alt compsetrun (ufs-community#75)
remove coupled appBuilder files and compsets subdirectory
Both Orion and Hera logs are posted, all tests pass. |
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.
Looks good, thanks. You may also to run it on dell?
tests/edit_inputs.sh
Outdated
@@ -10,9 +10,14 @@ function edit_ice_in { | |||
jday=$(date -d "${SYEAR}-${SMONTH}-${SDAY} ${SHOUR}:00:00" +%j) | |||
istep0=$(( ((10#$jday-1)*86400 + 10#$SHOUR*3600) / DT_CICE )) | |||
|
|||
CICEGRID="grid_cice_NEMS_mx"$OCNRES".nc" |
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.
Why are CICEGRID and CICEMASK defined here? I see they are defined in default_vars.sh. Should any overriding be done in individual tests/tests/ files?
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.
Yes, I think you are right.
The other line I was unsure about (even though it works) is setting ICERES in the fv3_conf/*.IN files. Unfortunately we have files with both "025" and "0.25" as resolution identifiers. Is there a better way (or place) to set that variable?
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.
Here is what I think -- this will have to be tested. I leave it up to you to decide:
- Delete CICEGRID and CICEMASK in default_vars
- Move CICEGRID and CICEMASK defined in edit_inputs to
fv3_conf/*.IN
(grid_cice_NEMS_mx@[OCNRES].nc
) - If ICRES always depends on OCNRES, maybe replace ICERES in default_vars with ICERES in
fv3_conf/*.IN
, and remove it fromfv3_conf/*.IN
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.
If you want to test these out, let me know. I can clone your branch and work on them.
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.
That would be a huge help Minsuk, thanks.
ICERES and OCNRES will always represent the same resolution since they're always on the same grid. I can envision: mx025, 0.25
mx050, 0.50
mx100, 1.00
tests/edit_inputs.sh
Outdated
@@ -24,11 +29,24 @@ function edit_ice_in { | |||
} | |||
|
|||
function edit_mom_input { | |||
|
|||
CHLCLIM="seawifs-clim-1997-2010."$NX_GLB"x"$NY_GLB".v20180328.nc" |
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 should probably move this and the FRUNOFF (below) to the individual tests also.
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 NX_GLB and NY_GLB need to be defined in individual tests if need to be overridden since their defaults are defined in default_vars. As to CHLCLIM, maybe define it in fv3_conf/*.in
?
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 just moved the variables CICEGRID, CICEMASK, CHLCLIM, FRUNOFF to default_vars.sh. I guess individual tests can override any one of these if needed in the future. I don't think it's a good idea to move them to fv3_conf/*.in
. Running RT's on Hera with these changes now.
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.
@DeniseWorthen this looks great! The clean up and the removal of NEMS tests is really exciting! I only had the one comment that some of the added things in the 025 MOM6_input might not be necessary, but can certainly be kept.
@@ -82,11 +82,11 @@ WRITE_GEOM = 2 ! default = 1 | |||
TRIPOLAR_N = True ! [Boolean] default = False | |||
! Use tripolar connectivity at the northern edge of the | |||
! domain. With TRIPOLAR_N, NIGLOBAL must be even. | |||
NIGLOBAL = 1440 ! | |||
NIGLOBAL = NX_GLB ! |
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.
If we have another template for _050 do you even want to make these variables? I mean they are now, so we can keep them. But I don't know if it's strictly necessary?
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.
Eventually I was hoping that all the MOM_input templates could be collapsed into one file, even for waves. It may not be possible but that was where I was going w/ this.
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.
Agreed, I didn't see a way to do waves vs no waves without just adding an extra template but would be happy if there was a way to do this. I think there are even more differences between 1/2 and 1/4 than waves and no waves.
Denise, here I only see resolution and CHL_FILE changes, may I ask if
there are other changes required for us to run 1/2 and 1/4 ocean?
…On Thu, Jul 16, 2020 at 9:14 AM Jessica Meixner ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In parm/MOM_input_template_025
<#141 (comment)>
:
> @@ -82,11 +82,11 @@ WRITE_GEOM = 2 ! default = 1
TRIPOLAR_N = True ! [Boolean] default = False
! Use tripolar connectivity at the northern edge of the
! domain. With TRIPOLAR_N, NIGLOBAL must be even.
-NIGLOBAL = 1440 !
+NIGLOBAL = NX_GLB !
Agreed, I didn't see a way to do waves vs no waves without just adding an
extra template but would be happy if there was a way to do this. I think
there are even more differences between 1/2 and 1/4 than waves and no waves.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#141 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI7D6TIZXVLJU2D4XORZFZLR334MFANCNFSM4O2YISDA>
.
|
There are a couple of other differences. There are also quite a few parameter differences (values) in the module_MOM_MEKE nml, MOM_lateral_mixing_coeffs nml, MOM_hor_visc nml and MOM_mixed_layer_restrat nml. Given the number of differences, really may not be possible to have a single template for different resolutions. |
Issue #135
Replaces hard-wired resolution dependent values in tests w/ variables.
Removes nems regression tests from rt.conf, removes rt_35d_nems.conf
Adds MOM_input_template for 1/2 deg resolution
Regression tests for CMEPS on Orion pass
Issue #134