-
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
code updates for one step cold start #176
code updates for one step cold start #176
Conversation
I don't think we need a special nems.configure.medcoldcmeps_atm_ocn_ice_1step.IN. The test (cpld_fv3_ccpp_mom6_cice_cmeps_1stepcold_atm_flux) can use the existing nems.configure.medcmeps_atm_ocn_ice.IN but in the test you would set the variable use_coldstart = false: In the test: export NEMS_CONFIGURE="nems.configure.medcmeps_atm_ocn_ice.IN" |
I was testing it. So far this is the difference in the two settings that we
need to consolidate:
restart_n, using @[FV3_RESTART_INTERVAL] default value 0 causes issues in
ICE tasks
< case_name = ufs.s2s
< restart_n = @[FV3_RESTART_INTERVAL]
---
case_name = ufs.s2s.cold
restart_n = @[FHMAX]
I can change FV3_RESTART_INTERVAL to be a non-zero value at this time.
…On Thu, Sep 10, 2020 at 9:07 AM Denise Worthen ***@***.***> wrote:
I don't think we need a special
nems.configure.medcoldcmeps_atm_ocn_ice_1step.IN.
The test (cpld_fv3_ccpp_mom6_cice_cmeps_1stepcold_atm_flux) can use the
existing nems.configure.medcmeps_atm_ocn_ice.IN but in the test you would
set the variable use_coldstart = false:
In the test:
nems.configure
export NEMS_CONFIGURE="nems.configure.medcmeps_atm_ocn_ice.IN"
export use_coldstart="false"
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#176 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI7D6TJMX6BM5DUEWE54MJTSFDFRDANCNFSM4RA2MAZA>
.
|
That's right. As long as FV3 considers restart_interval=0 to be equivalent to restart_interval=fhmax we should be fine. The case name determines what string the mediator restart file name will start with. For the 1-step coldstart, we want it to write a mediator file with the case_name "ufs.s2s". |
export TEST_DESCR="Fully coupled FV3-CCPP-MOM6-CICE-CMEPS system - 1 step cold start" | ||
|
||
export CNTL_DIR="RT-Baselines_1stepcold_ccpp_cmeps" | ||
export CNTLMED_DIR="RT-Baselines_1stepcold_ccpp_cmeps" |
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 can also be an empty string since there is no control mediator directory.
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 fine.
Denise/Bin, this PR is ready to merge. |
* update to pre-existing land perts scheme, ready for addition of the new scheme * updates to land perts scheme, so that namelist input and control_type variables are in generic (i.e., variable agnostic) arrays * Phil's ccpp changes * minor bug fix * Comitting stochastic physics updates * Comitting FV3 submodules updates * Updates for minimal set of regression tests. * lndp sub-module clean-up * Updates to tests to include new input parameters for revised land pert scheme (lndp).
Description of changes
This PR contains the code changes for one step cold start.
Specific notes
Issues Fixed (include github issue #):
Are changes expected to change answers?
Specific changes:
Testing performed:
Hashes used for testing:
Co-authored by: Denise Worthen Denise.Worthen@noaa.gov
Dependency:
FV3 PR #168
MOM6 PR #33
s2s PR#176