You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the vertical coordinate configuration is hard-coded for the UFS SRW App. We should introduce the capability for users to specify their own vertical coordinate configuration.
Solution
Add an option to set npz_type in the namelist to 'input', which then allows a user to place a text file with the vertical level ak/bks in the run directory to be read in by the model. Also, from @BenjaminBlake-NOAA: "There is a small block of code changes to fv_eta.F90 in the ufs-weather-model code that allows you to use npz_type = 'input'".
Need to confirm whether defining 'npz' or 'levp' values in the namelist are still required when using this method.
Requirements**
Acceptance Criteria (Definition of Done)
The text was updated successfully, but these errors were encountered:
Original issue opened by @JeffBeck-NOAA migrated from regional_workflow repository: ufs-community/regional_workflow#524
Description
Currently the vertical coordinate configuration is hard-coded for the UFS SRW App. We should introduce the capability for users to specify their own vertical coordinate configuration.
Solution
Add an option to set npz_type in the namelist to 'input', which then allows a user to place a text file with the vertical level ak/bks in the run directory to be read in by the model. Also, from @BenjaminBlake-NOAA: "There is a small block of code changes to fv_eta.F90 in the ufs-weather-model code that allows you to use npz_type = 'input'".
Need to confirm whether defining 'npz' or 'levp' values in the namelist are still required when using this method.
Requirements**
Acceptance Criteria (Definition of Done)
The text was updated successfully, but these errors were encountered: