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 writing unexpectedly many wrfout_d01* files

pegwan

New member
I am currently completing an intensive simulation that (due to the specifications of the HPC network I'm using) requires a restart for every 12 hours of simulation time. The simulation is doubly nested, with three concentric domains (d01–d03).

My first two restarts went without hitch, however I have noticed an abnormality with the most recent run. Instead of writing output every hour and saving these into six-hour batches (as specified in namelist.input), the data for d01 — and only d01 — has been written every 54 seconds, and saved into 5:24 minute batches:

1716246491022.jpeg

It seems to me that the system has somehow attempted to write output at the maximal frequency, despite this not at all being my desire. I have checked this run's namelist.input file for typos that might be causing this behaviour, but I have not been able to find any. I have attached said namelist.input file for reference.

If anyone could tell me what mistake I have made, or alternatively, which process(es) might be causing this unwanted behaviour, I would be incredibly grateful.
 

Attachments

  • namelist.input.txt
    5.8 KB · Views: 1
Hi,
Can you try adding "override_restart_timers = .true." to the &time_control namelist record and see if that helps?
 
Top