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

Update global-workflow scripts for runnng the NG-GODAS application #995

Closed
wants to merge 23 commits into from

Conversation

binli2337
Copy link

@binli2337 binli2337 commented Aug 24, 2022

Description
Although a global-workflow branch at https://github.com/binli2337/global-workflow/tree/add_gefs is available for the NG-GODAS team to do testing for the NG-GODAS (cdeps_datm_mom6_cic6) application, it uses previous workflow-generation scripts located in the ush/rocoto directory.

The above branch has been updated to use new workflow-generation scripts located in the workflow directory. The Python script "workflow_tasks.py" has been updated to use correct forcing files. The global-workflow scripts in ush, scripts and parm/config directories have also been updated for running NG-GODAS application.

Fixes #774
Fixes #785
Fixes #838

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • My changes need updates to the documentation. I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • New and existing tests pass with my changes
  • Any dependent changes have been merged and published

binli2337 added 22 commits June 6, 2022 12:06
parm/config/config.base.emc.dyn
parm/config/config.coupled_ic
ush/rocoto/setup_expt.py
ush/rocoto/setup_workflow_fcstonly.py
 parm/config/config.base.emc.dyn
 parm/config/config.coupled_ic
 ush/rocoto/setup_expt.py
 ush/rocoto/setup_workflow_fcstonly.py
* update  parm/config/config.defaults.datm
* update  ush/rocoto/setup_workflow_fcstonly.py
parm/config/config.base.emc.dyn Outdated Show resolved Hide resolved
parm/config/config.base.emc.dyn Outdated Show resolved Hide resolved
jobs/rocoto/arch.sh Show resolved Hide resolved
jobs/rocoto/arch.sh Show resolved Hide resolved
jobs/rocoto/arch.sh Outdated Show resolved Hide resolved
@@ -23,6 +23,87 @@ common_predet(){
}

DATM_predet(){
echo "SUB ${FUNCNAME[0]}: Defining variables for datm"
Copy link
Contributor

Choose a reason for hiding this comment

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

How much of this is duplicate code of FV3_GFS_predet() that could be abstracted out into a separate function that is called for both cases?

@@ -282,7 +282,49 @@ if [ $type = "gfs" ]; then
fi ##end of gfs
#-----------------------------------------------------

if [ $ATMTYPE = "DATA" ]; then
if [ $DO_OCN = "YES" ]; then
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this just a duplicate of the other DO_OCN, etc. blocks for GFS? Instead of duplicating, can we restructure so those sections are used in both cases?

@@ -9,30 +9,26 @@
## writing model configure file for DATM
## This script is a direct execution.
#####

. $EXPDIR/config.defaults.datm
Copy link
Contributor

Choose a reason for hiding this comment

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

This shouldn't be called here. It was already called in config.base.

ush/parsing_namelists_DATM.sh Show resolved Hide resolved
workflow/setup_expt.py Outdated Show resolved Hide resolved
@binli2337 binli2337 closed this Sep 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants