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

Ran out of valid boundary conditions in file wrfbdy_d01, at end time. [running wrf.exe]

natalia_c

New member
Dear Forum,
I've been trying to run wrf.exe for a couple of days, but I haven't been able to fix the following error. This message comes from the bottom of the rsl.error.0000 file, created after running wrf.exe.

***********************************************************************************************************************************
Timing for main: time 2021-10-07_22:59:42 on domain 1: 0.36524 elapsed seconds
Timing for main: time 2021-10-07_23:00:36 on domain 1: 0.35921 elapsed seconds
Timing for Writing wrfout_d01_2021-10-07_23:00:36 for domain 1: 4.92698 elapsed seconds
d01 2021-10-07_23:00:36 Input data is acceptable to use: wrfbdy_d01
2 input_wrf: wrf_get_next_time current_date: 2021-10-07_23:00:36 Status = -4
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 1149
---- ERROR: Ran out of valid boundary conditions in file wrfbdy_d01
-------------------------------------------
Abort(1) on node 0 (rank 0 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0
***********************************************************************************************************************************

To simplify the simulation, I used only one domain. Input data corresponds to ERA5 hourly data (0.25°x0.25°). I attached the namelist files. Also, the simulation is of 5 days, starting at 2021/10/03 at 00:00:00 and ends at 2021/10/07 at 23:00:00.
If anyone knows how to solve this, I would appreciate the help. I also don't understand why the current date (in the error) is 23:00:36. Why the 36 seconds?? I would have expected it to be at exactly 23:00:00.

Thanks in advance for the help!
 

Attachments

  • namelist.input
    3.9 KB · Views: 18
  • namelist.wps
    840 bytes · Views: 8
This is because your integration time is beyond the time period your wrfbdy files covers.
Please change run_days = 0, then try again.
 
Top