Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

WRF V4.1.2 release

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.

Xun_Wang

New member
Hi,

In the WRF Version 4.1.2 release there is a bug fix in temperature and winds computation when the “traditional fields” diagnostics option is turned on.

What is the “traditional fields” diagnostics option? Which namelist option is that?

Thanks for your help!

Best regards,
Xun
 
Xun,
That is a good question, as this doesn't seem to be mentioned in the Users' Guide yet. Here is a description of this option (which can also be found in WRF/run/README.namelist):

Traditional / full fields model output

The ARW WRF model output may be modified at run-time to also include a stream that contains
more traditional fields: temperature, pressure, geopotential height, etc. The flag needs to
be activated in the namelist (diag_nwp2 = 1). In the registry.trad_fields, the output stream
is "h1", so that stream needs to be explicitly requested in the namelist.input file.

&diags
diag_nwp2 = 1
/

&time_control
io_form_auxhist1 = 2
auxhist1_interval = 180, 30, 30,
frames_per_auxhist1 = 1, 1, 1,
auxhist1_outname = "wrf_trad_fields_d<domain>_<date>"
/
 
Hi,

thanks for your reply and explanation!

Does that mean if I didn't turn on the diag_nwp2 option, then the simulated temperature and wind were correct and not affected by this bug fix?

Best regards,
Xun
 
Top