Recently, while running a large-eddy simulation, I wanted to run it for a while first to check the results and then restart it. However, I found an issue with the restart file (wrfrst) output — the output times are not at integer intervals; there’s always a few extra seconds.Does it matter？How can this be avoided?
Does it matter if the file output name is non-hourly? such as wrfrst_d03_2018_07-09_08:30:18
- Thread starter zr_826
- Start date
William.Hatheway
Well-known member
I think I know what the issue is, upload your namelist.input and that will confirm my suspicion
Oh thank you so much!! I known the reason, which was because my time step was 27second ,and my output time(1800s) can't be divisible by 27
Thank you so much ! While I have already tried this method, it didn't work. The adjust_output_times = .true could help me to adjust wrfout.
Of course, here is the namelist.input. Recently, I have a new problem that is the cfl error after encrypting the number of near-earth layers（the averaged Above Ground Level below 100 meters are : 7m, 16m, 28m, 42m, 55m, 72m, 97m). The simulation I am conducting is a typhoon nearshore large eddy simulation. And the cfl errors I also add to the attach files, could you please help have a look?Thank you so much !
Attachments
In your namelist.input, you set
restart_interval = 30,
time_step = 24
Is there any special reasons that you need to have wrfrst files every 30-minute? The wrfrst output time is not coincident with the time of forward model integration. This is the reason you get the weird wrfrst filenames.
restart_interval = 30,
time_step = 24
Is there any special reasons that you need to have wrfrst files every 30-minute? The wrfrst output time is not coincident with the time of forward model integration. This is the reason you get the weird wrfrst filenames.
Yeah, I would like to run WRF-LES (my innermost domain, the d05, start from 4:00)for 1hour and a half to have a look at the simulated effect ,the half is used for spin-up and if I need more data in the future, I could restart at 5:30 in d05 domain. And if I'd like to restart at 5:30 in d05 domain, I should restart at the same time in all of my domains(d01 to d05), so I chose the smallest common divisor of my simulation time from d01 to d05 to make all domains can output the restart file at the same time and which is what I need. In this way, I can save computing resources.