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

updates from RTs for wave restart name and nml files #1457

Closed
DeniseWorthen opened this issue Apr 12, 2023 · 1 comment · Fixed by #3190
Closed

updates from RTs for wave restart name and nml files #1457

DeniseWorthen opened this issue Apr 12, 2023 · 1 comment · Fixed by #3190
Assignees
Labels
feature New feature or request

Comments

@DeniseWorthen
Copy link

DeniseWorthen commented Apr 12, 2023

Description

Two PRs have been merged and the corresponding changes need to be made in the workflow.

  1. update CMEPS to allow bilinear ATM<->WAV mapping for global coupled application; utilize custom restart names for WW3 (was #1684)  ufs-community/ufs-weather-model#1692. This changes the name of the WW3 restart file and fixes For a "continue" run, WW3 should not start unless a restart is present ufs-community/ufs-weather-model#1590.

This change required in the nems.configure file is to add user_sets_restname = true in the WAV_attributes:: section. The restart file will then be consistent with the restart names produced by ICE and CMEPS. It will also contain an application specific name, eg. ufs.hafs.ww3.r.YYYY-MM-DD-SSSSS or ufs.cpld.ww3.r.YYYY-MM-DD-SSSSS

  1. add cmeps capable atm-wav test ufs-community/ufs-weather-model#1407. This added use of nml files for the wave model. The template for the file are ww3_shel.nml.IN. Also, the list of point output is now in a separate file ww3_points.list. Both are located in the UFS tests/parm directory. The structure of the nml that needs to be parsed is
&input_nml
  input%forcing%winds      = 'C'
  input%forcing%currents   = '@[WAV_CUR]'
  input%forcing%ice_conc   = '@[WAV_ICE]'
  input%forcing%ice_param1 = '@[WAV_IC1]'
  input%forcing%ice_param5 = '@[WAV_IC5]'
/

&output_type_nml
  type%field%list = '@[OUTPARS_WAV]'
  type%point%file = 'ww3_points.list'
/

&output_date_nml
  date%field%outffile  = '1'
  date%field%stride    = '@[DTFLD]'
  date%point%outffile  = '1'
  date%point%stride    = '@[DTPNT]'
  date%restart2%stride = '@[DT_2_RST]'
/

The variables are consistent w/ the variables in the current inp file with the exception of the forcing fields. These are now either C for coupled or F for not. The values for WAV_ICE1 and WAV_ICE5 should be F unless WW3-CICE6 coupling is used (currently not implemented in UFS).

For the HAFS application, the use of outfile=1 will now create time-stamped files, for example 20190829.060000.out_grd.ww3 in place of out_grd.ww3.

Requirements

Acceptance Criteria (Definition of Done)

Dependencies
Related: #1277

@DeniseWorthen
Copy link
Author

@aerorahul

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants