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 real completes successfully but did not create boundary/nudging for all times specified in &time_control

koszutam

New member
I am trying to model an AR event on the west coast in Oct. 1962 using ERA5 data downloaded from the UCAR RDA. This is one of about 20 storms that I am simulating for a project, with the rest completing successful using our original configuration with WRFv4.3.1. This storm was routinely failing with a Segmentation Fault I could not track down so I switched to a newer version of WRF (v4.6.0).

Using WRFv4.6.0, the event simulated fine until the last 6 hours when it abruptly stopped. Looking at wrfbdy_d01 and wrffdda_d01, I realized that it did not contain data for the last two time steps of the forcing data, which is passed every 3 hours. I then extended the start and end times for WRF event slightly to hopefully circumvent the issue, but real.exe continues to show the SUCCESS COMPLETE message even though it did not include the last 15 hours of data in the WRF files.

I have attached the namelist, rsl files, a few of the last met_em.d01.* files, and the wrfbdy_d01 file for you to reference here: https://nextcloud.mmm.ucar.edu/index.php/s/n8in8C8PAAaYqAy/download?path=/&files=1962_issues_mk.tar. Thanks for any insight you can pass along!
 
Hi,
I believe the problem is due to the fact that you have end_hour set twice in the namelist.

Code:
 end_hour                            = 12, 12,
 end_hour                            = 00, 00,

The namelist is read from top to bottom, meaning the value of 00 is overwriting the value of 12. The wrfbdy and wrffdda files will only show the times for the beginning of each interval, so it would make sense that you would be seeing it go through the time of 1962-10-16_21:00:00. Just remove that second entry, set to 00, and see if that fixes the problem.
 
Top