Skip to content

Use of ICs for SFS Beta Version#3839

Closed
NeilBarton-NOAA wants to merge 49 commits into
NOAA-EMC:developfrom
NeilBarton-NOAA:sfs_ICS
Closed

Use of ICs for SFS Beta Version#3839
NeilBarton-NOAA wants to merge 49 commits into
NOAA-EMC:developfrom
NeilBarton-NOAA:sfs_ICS

Conversation

@NeilBarton-NOAA
Copy link
Copy Markdown
Contributor

Description

These updates allow g-w to run with ICs used for testing in the SFS forecast-only framework. It supplies sample yaml files and needed updated. In addition, it add the archiving tasks for SFS.

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)? NO
  • Does this change require a documentation update? NO
  • Does this change require an update to any of the following submodules? NO
    • EMC verif-global
    • GDAS
    • GFS-utils
    • GSI
    • GSI-monitor
    • GSI-utils
    • UFS-utils
    • UFS-weather-model
    • wxflow

How has this been tested?

Testing performed on GAEAC6 in forecast-only model

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

Comment thread scripts/exglobal_cleanup.sh Fixed
@@ -0,0 +1,19 @@
experiment:
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Neil, These new case files look strong (along with their overwriting defaults). Do you have these sfs cases tested in automated scripts yet?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@TerrenceMcGuinness-NOAA we've been using these edits for testing SFS and will be automated for the reforecasting effort.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

What framework will you be using for automation? global-workflow is currently developing framework in VLab's GitLab that uses these case files.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@TerrenceMcGuinness-NOAA I'm not sure if this answers your question, but to run the full set of SFS runs, which is currently November 1st and May 1st start dates, we add

${YEAR}${MONTH}010000 ${YEAR}${MONTH}010000 24:00:00

to the rocoto .xml file before the rocoto run as rocoto does not support (to my knowledge) starting once a month on the first.

Comment thread parm/ufs/fv3/diag_table Outdated
"ocean_model", "LwLatSens", "LwLatSens", "@[MOM6_OUTPUT_DIR]/ocn%4yr%2mo%2dy%2hr","all",.true.,"none",2
"ocean_model", "Heat_PmE", "Heat_PmE", "@[MOM6_OUTPUT_DIR]/ocn%4yr%2mo%2dy%2hr","all",.true.,"none",2

# scalar fields
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@jiandewang - Can you look at this from a GFS perspective --- I don't know if we want to add these fields or not for GFS at this stage of development....

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@JessicaMeixner-NOAA:

  1. Adding this output is a trivial (almost nothing in CPU costs and disk usage) addition.
  2. For any simulation that is < 1 mon, this output isn't going to help with anything - particularly if you have never used a metric that factors in global means and their time evolution.

Hope this helps make your choices!

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

GFS simulations are less than <1 month, so why are we adding any cost/disk for that case?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Compute and disk space are things that we would want to not add to for GFS - even if it's small if it's not going to be needed.

I think we need to find a way to toggle this on/off.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

PmE can be always derived from precipitation and latent heat fluxes saved in the atmos output.

@jiandewang
Copy link
Copy Markdown
Contributor

We can remove heat_PME.
For the first one we are using it to get net heat flux in post job by adding SW. But in fact each component (LH, SH and LW) are also in output list so it will require a bit work on ocean post code if we remove the first one.

@NeilBarton-NOAA
Copy link
Copy Markdown
Contributor Author

@sanAkel I'm tagging Santha as these additions are his suggestion for evaluation

NeilBarton-NOAA and others added 4 commits August 18, 2025 11:00
Co-authored-by: Rahul Mahajan <aerorahul@users.noreply.github.com>
Co-authored-by: Rahul Mahajan <aerorahul@users.noreply.github.com>
Comment thread ush/forecast_postdet.sh Fixed
Comment thread ush/forecast_postdet.sh Fixed
Comment thread ush/forecast_postdet.sh Fixed
@DeniseWorthen
Copy link
Copy Markdown

DeniseWorthen commented Aug 20, 2025

@NeilBarton-NOAA Is this test using the Replay ICs? I had been working on the SFS RT w/ the assumption that the ICs would be from CORe. I only ask because if the Replay ICs are used, the missing value flag in the sfc ICs needs to be changed from 1.e30 to -1.e30 to avoid overflow error in NST.

The reason it is an issue is because we're trying ensure consistency between the RTs and the G-W. I can't pass the debug test in the RTs w/ the Replay ICs unless the sfc ICs are fixed.

@NeilBarton-NOAA
Copy link
Copy Markdown
Contributor Author

@DeniseWorthen These changes have updates to run with replay and CPC ICs. Yes, we need to fix the ICs that we are using for these tests outside of g-w. I'll ask @Yangxing.Zheng when he is back from A/L

Copy link
Copy Markdown

@github-advanced-security github-advanced-security AI left a comment

Choose a reason for hiding this comment

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

ShellCheck found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.

Comment thread ush/forecast_postdet.sh Fixed
Comment thread ush/forecast_postdet.sh Fixed
Comment thread ush/forecast_postdet.sh Fixed
Comment thread ush/forecast_postdet.sh Fixed
Comment thread ush/forecast_postdet.sh Fixed
Comment thread ush/forecast_postdet.sh Fixed
Comment thread ush/forecast_postdet.sh Fixed
Comment thread ush/forecast_postdet.sh Fixed
Comment thread ush/forecast_postdet.sh Fixed
Comment thread ush/forecast_postdet.sh Fixed
Comment thread ush/forecast_postdet.sh Fixed
Comment thread ush/forecast_postdet.sh
# Do Monthly Average ocean output and move to output ocean history directory (valid up to 12 month forecasts only)
if [[ "${RUN}" == sfs ]]; then
local last_fh_output files f_name
last_fh_output=$(ls -f "${COMOUT_OCEAN_HISTORY}/${RUN}.ocean.t${cyc}z.${FHOUT_OCN}hr_avg.f${FHMAX_GFS}.nc" )

Check notice

Code scanning / shellcheck

Possible misspelling: FHMAX_GFS may not be assigned. Did you mean FHMAX_HF? Note

Possible misspelling: FHMAX_GFS may not be assigned. Did you mean FHMAX_HF?
@NeilBarton-NOAA
Copy link
Copy Markdown
Contributor Author

I'm closing this PR as it is now being merged into dev/sfs

#4137

@NeilBarton-NOAA NeilBarton-NOAA deleted the sfs_ICS branch December 8, 2025 21:28
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.

9 participants