Skip to content

Adding workflow infrastructure for wave_stat and wave_stat_pnt jobs #3846

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

Open
wants to merge 12 commits into
base: develop
Choose a base branch
from

Conversation

sbanihash
Copy link
Contributor

@sbanihash sbanihash commented Jun 30, 2025

Description

This PR creates the infrastructure for the wave_stat addition into the global workflow. The PR has been modified to only contain the workflow changes needed for the two new jobs: JGEFS_WAVE_STAT and JGEFS_WAVE_STAT_PNT to be added.

After getting this part merged, the next PR (from this branch ) will contain these four scripts:
scripts/exgefs_wave_stat.sh
scripts/exgefs_wave_stat_pnt.sh
and
ush/wave_ens_stat.sh
ush/wave_ens_bull.sh

Type of change

  • Bug fix (fixes something broken)
  • New feature (adds functionality)
  • Maintenance (code refactor, clean-up, new CI test, etc.)

Change characteristics

  • Is this a breaking change (a change in existing functionality)? YES/NO
  • Does this change require a documentation update? YES/NO
  • Does this change require an update to any of the following submodules? YES/NO (If YES, please add a link to any PRs that are pending.)
    • EMC verif-global
    • GDAS
    • GFS-utils
    • GSI
    • GSI-monitor
    • GSI-utils
    • UFS-utils
    • UFS-weather-model
    • wxflow

How has this been tested?

This PR was tested with the second part of the changes pulled in as well. Without that part the functionality can not be tested. Although checking to make sure other ci tests are not effected is needed.

Output from ci test (C48_S2SWA_gefs) with pulling in second part of changes can be found on dogwood:
/lfs/h2/emc/couple/noscrub/saeideh.banihashemi/Dev_Work/GEFS/INFRST/GW-DEV/new/RUNTESTS/COMROOT/wavestat/gefs.20210323/12/ensstat/products/wave

Checklist

  • Any dependent changes have been merged and published
  • 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
  • I have documented my code, including function, input, and output descriptions
  • My changes generate no new warnings
  • New and existing tests pass with my changes
  • This change is covered by an existing CI test or a new one has been added
  • Any new scripts have been added to the .github/CODEOWNERS file with owners
  • I have made corresponding changes to the system documentation if necessary

@sbanihash
Copy link
Contributor Author

@aerorahul I closed my previous PR, made a new branch from develop, added my changes from the previous branch , made new commits so that this PR is not 100 commits ahead of develop and is easier to follow, and opened this new PR. Hopefully this makes it easier for you to review. Thank you so much for your time reviewing this work during the past few months. Hopefully we could get this one out soon.



###############################################################
source "${HOMEgfs}/ush/load_ufswm_modules.sh"
Copy link
Member

Choose a reason for hiding this comment

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

Is this intentional? Why not use load_fv3gfs_module.sh?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@aerorahul tagging you here for the responses, this is mimicking what we have in other wave jobs such as waveinit and wavepost jobs. Let me know if it needs to be reverted to what Kate suggested. (Probably needs same thing for those jobs as well)

#! /usr/bin/env bash

###############################################################
source "${HOMEgfs}/ush/load_ufswm_modules.sh"
Copy link
Member

Choose a reason for hiding this comment

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

Same question.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

same response

@@ -127,6 +127,7 @@ export APP="{{ APP }}"
export DO_ATM="YES"
export DO_COUPLED="NO"
export DO_WAVE="NO"
export DO_WAVE_STAT="NO"
Copy link
Member

Choose a reason for hiding this comment

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

This is probably ok here but it's within the major switches for the components (wave, ocean, ice, etc.) so I'm wondering if there is a better place for this in here. @DavidHuber-NOAA thoughts?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@DavidHuber-NOAA , Rahul had also mentioned the same comment on the previous PR that was closed. Since this switch will add a whole new job to the runs we kept it here. Let me know if you have a better place for it in mind.

@@ -56,7 +56,7 @@ elif [[ "${step}" = "prep_emissions" ]]; then
export APRUN="${launcher} -n 1"

elif [[ "${step}" = "waveinit" ]] || [[ "${step}" = "waveprep" ]] || [[ "${step}" = "wavepostsbs" ]] || \
[[ "${step}" = "wavepostbndpnt" ]] || [[ "${step}" = "wavepostpnt" ]] || [[ "${step}" == "wavepostbndpntbll" ]]; then
[[ "${step}" = "wavepostbndpnt" ]] || [[ "${step}" = "wavepostpnt" ]] || [[ "${step}" == "wavepostbndpntbll" ]] || [[ "${step}" = "wave_stat" ]]; then
Copy link
Member

Choose a reason for hiding this comment

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

I don't see the wave_stat_pnt job added in any of the env files.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I did not add it since I thought this block is only if we need to define USE_CFP, mpmd , mpexec etc., @aerorahul please let me know if this is a misunderstanding.

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.

3 participants