flexible history file output time and consistent control variables

[junwang-noaa]

Description

Currently the ufs weather model fv3atm component can not output history files at flexible forecast time. Also there are two sets of variables controlling when to output the history files. One in the fv3 forecast component, namelist variables fdiag, fhout,fhmax, fhouthf, fhmaxhf are used, the other set is used by the write grid component with variables nfhout, nfhmax, nfhout_hf, nfhmax_hf, nsout in model_configure. This causes some issues when inconsistent setting are used at run time.

Solution

In this issue, the control variables are cleaned up. Only one set of control variables will be used in the fv3 cap to control when to update data buffer on forecast side and when to pick up those data and write out to history files on write grid component side. Also a configuration variable output_fh is introduced to output history files at forecast times users choose, because of that the ESMF alarm is removed as it can't support irregular alarm frequency. So code updates include:

1. fdiag, fhout,fhmax, fhouthf, and fhmaxhf are removed from fv3 namelist atmos_model_nml. With the code updates, those variables should be deleted from namelist.
2. in model_configure, there are two ways to control output forecast time

• Use nfhout, nfhmax, nfhout_hf, nfhmax_hf, nsout, the meanings of those variables do not change.
• Use output_fh to control output time:
  a) An array of output_fh means to output history files at those forecast time, e.g.:
  "output_fh: 0 1 2 3 12 24 48"
  If the first elelment is zero, it means the first time step output.
  b) If there are two elements in output_fh and the second one has value -1, it means the first element is output frequency. e.g.
  " output_fh: 6 -1"
  fv3atm will output the history file every 6 hours.

Related to

• It will resolve issue #339
  FV3 and ufs-weather-model PRs will be created.

[SMoorthi-emc]

How do you handle when you want to output hourly up to 120 hours and 3 hourly beyond that?

…

On Tue, Jun 29, 2021 at 2:57 PM Jun Wang ***@***.***> wrote: Description Currently the ufs weather model fv3atm component can not output history files at flexible forecast time. Also there are two sets of variables controlling when to output the history files. One in the fv3 forecast component, namelist variables fdiag, fhout,fhmax, fhouthf, fhmaxhf are used, the other set is used by the write grid component with variables nfhout, nfhmax, nfhout_hf, nfhmax_hf, nsout in model_configure. This causes some issues when inconsistent setting are used at run time. Solution In this issue, the control variables are cleaned up. Only one set of control variables will be used in the fv3 cap to control when to update data buffer on forecast side and when to pick up those data and write out to history files on write grid component side. Also a configuration variable output_fh is introduced to output history files at forecast times users choose, because of that the ESMF alarm is removed as it can't support irregular alarm frequency. So code updates include: 1. fdiag, fhout,fhmax, fhouthf, and fhmaxhf are removed from fv3 namelist atmos_model_nml. With the code updates, those variables should be deleted from namelist. 2. in model_configure, there are two ways to control output forecast time - Use nfhout, nfhmax, nfhout_hf, nfhmax_hf, nsout, the meanings of those variables do not change. - Use output_fh to control output time: a) An array of output_fh means to output history files at those forecast time, e.g.: "output_fh: 0 1 2 3 12 24 48" If the first elelment is zero, it means the first time step output. b) If there are two elements in output_fh and the second one has value -1, it means the first element is output frequency. e.g. " output_fh: 6 -1" fv3atm will output the history file every 6 hours. Related to FV3 and ufs-weather-model PRs will be created. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#674>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALLVRYVAT5QAUEHQU2FCYMTTVIJRTANCNFSM47Q2LQQA> .

-- Dr. Shrinivas Moorthi Research Meteorologist Modeling and Data Assimilation Branch Environmental Modeling Center / National Centers for Environmental Prediction 5830 University Research Court - (W/NP23), College Park MD 20740 USA Tel: (301)683-3718 e-mail: ***@***.*** Phone: (301) 683-3718 Fax: (301) 683-3718

[junwang-noaa]

If you do not want to specify the long list of the forecast time, you can still use the fhout/fhout_hf in model_configure. On Tue, Jun 29, 2021 at 3:14 PM SMoorthi-emc ***@***.***> wrote:

…

How do you handle when you want to output hourly up to 120 hours and 3 hourly beyond that? On Tue, Jun 29, 2021 at 2:57 PM Jun Wang ***@***.***> wrote: > Description > > Currently the ufs weather model fv3atm component can not output history > files at flexible forecast time. Also there are two sets of variables > controlling when to output the history files. One in the fv3 forecast > component, namelist variables fdiag, fhout,fhmax, fhouthf, fhmaxhf are > used, the other set is used by the write grid component with variables > nfhout, nfhmax, nfhout_hf, nfhmax_hf, nsout in model_configure. This causes > some issues when inconsistent setting are used at run time. > Solution > > In this issue, the control variables are cleaned up. Only one set of > control variables will be used in the fv3 cap to control when to update > data buffer on forecast side and when to pick up those data and write out > to history files on write grid component side. Also a configuration > variable output_fh is introduced to output history files at forecast times > users choose, because of that the ESMF alarm is removed as it can't support > irregular alarm frequency. So code updates include: > > 1. fdiag, fhout,fhmax, fhouthf, and fhmaxhf are removed from fv3 > namelist atmos_model_nml. With the code updates, those variables should be > deleted from namelist. > 2. in model_configure, there are two ways to control output forecast > time > > > - Use nfhout, nfhmax, nfhout_hf, nfhmax_hf, nsout, the meanings of > those variables do not change. > - Use output_fh to control output time: > a) An array of output_fh means to output history files at those > forecast time, e.g.: > "output_fh: 0 1 2 3 12 24 48" > If the first elelment is zero, it means the first time step output. > b) If there are two elements in output_fh and the second one has value > -1, it means the first element is output frequency. e.g. > " output_fh: 6 -1" > fv3atm will output the history file every 6 hours. > > Related to > > FV3 and ufs-weather-model PRs will be created. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#674>, or > unsubscribe > < https://github.com/notifications/unsubscribe-auth/ALLVRYVAT5QAUEHQU2FCYMTTVIJRTANCNFSM47Q2LQQA > > . > -- Dr. Shrinivas Moorthi Research Meteorologist Modeling and Data Assimilation Branch Environmental Modeling Center / National Centers for Environmental Prediction 5830 University Research Court - (W/NP23), College Park MD 20740 USA Tel: (301)683-3718 e-mail: ***@***.*** Phone: (301) 683-3718 Fax: (301) 683-3718 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#674 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AI7D6TJQVYYF3HF6HE5TQDTTVILPTANCNFSM47Q2LQQA> .