updates to use CMEPS for coupled-crow#120
Conversation
jiandewang
commented
Aug 31, 2020
jiandewang
commented
- Updates to build and input files for using CMEPS
- Changes mediator pet counts to only have fv3 computational cores (not the write groups)
- updates to module files for ocean post (which now runs)
- update to CICE5 input.nml in prep to be consistent with CICE6
making readme consistant with user.yaml.default
…i cplwav model_config block. Reinstating config.wave block in JGLOBAL_FORECAST. Pointing EXECwave to HOMEgfs/exec directory for WW3 util executables (changed link_fv3gfs.sh accordingly). Removing debug options from compile.sh line in build_fv3.sh.
…coupled-crow-addWW3jobs
move default value into defaults/
It's better if we have one place to manage default values for configurable variables other than two Default values only for reference. Please throughly test to make sure it could reproduce.
scripts update: CCPP and IPD works
add hard-coded variables into config.fcst (fcst.yaml)
ice variable istep0 bug fix
add FNMSKH conditional clause, coupled vs non-coupled
…ripts Conflicts: workflow/platforms/_sandbox.yaml
…coupled-crow-addWW3jobs
…meps Conflicts: jobs/JWAVE_POST_SBS modulefiles/modulefile.reg2grb2.orion sorc/build_fv3_coupled.sh sorc/build_reg2grb2.sh ush/nems.configure.med_atm_ocn_ice_wav.IN ush/nems.configure.medcold_atm_ocn_ice_wav.IN ush/nems_configure.sh workflow/config/base.yaml workflow/config/fcst.yaml workflow/config/wave.yaml workflow/defaults/settings.yaml workflow/layout/free_forecast_gfs.yaml
…in workflow/platforms/orion.yaml (2) add extra white space in ush/nems_configure.sh in line 56 to eliminate warning in run log (3) correction on restart_n template variable setting in ush/nems.configure.med_atm_ocn_ice.IN
|
@JianKuang-NOAA and @JessicaMeixner-NOAA Thanks PS: Somehow I can't assign you two as reviewers by click the icon of reviewer, there is simply no icon for me to click, normally there is a round shaped icon to the right of "reviewers", don't understand why at this moment. |
|
OK. I will test it. |
|
@jiandewang It seems like this PR needs to first merge with feature/coupled-crow. |
|
@jiandewang @JessicaMeixner-NOAA @binli2337 Also, I suggest we make every PR directly into feature/coupled-crow instead of another PR. Our PR into the trunk are supposed to be independent from each other |
|
@JianKuang-NOAA I think feature/coupled-crow has already been merged in and the branch is up to date. At least that's what it tells me when trying to merge it in. The PRs to and from these branches/PRs are because we are working in our own forks together towards the same goal. While this could probably be broken down into a few PRs, all the work is connected. I'll try to keep my work in smaller chunks in the future. |
|
@JessicaMeixner-NOAA OK. Let me check again. |
jiandewang
changed the base branch from
bugfix/coupled-crow
to
feature/coupled-crow
|
switch to request to merge be merged to feature/coupled-crow |
|
@jiandewang Apologize for the confusion. Now I found that all we need is to point the destination of this PR to feature/coupled-crow instead of bugfix/coupled-crow :) |
|
@JianKuang-NOAA now we are on the same page. My branch is based on Jessica's original branch which is based on feature/coupled-crow, so there shall be no conflict. |
updates to MOM6 input files
|
@JianKuang-NOAA the merging needs to be done by you as what I see is: I guess this is why I couldn't assign reviewers in the formal way last night |
…c-v4 back to master (NOAA-EMC#120) * Bugfixes for CCPP: check for and correct syntax of \htmlinclude lines * Fix formatting (tabs, whitespaces) in tests/rt.conf
Fix Mon_config case statement.
6 participants
