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

not writing wrfout_d0* files in WRF 4.0 after completion of run

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.

nitinpatil85

New member
I am running WRF.exe for one day starting from 26 and ending at 27 (3 domains).

seems run is completing successfully but not writing the Writing wrfout_d01/2/3_2017-07-27_00:00:00 at the end instead of this it is just keeping
wrfout_d01/2/3_2017-07-26_00:00:00

I am expecting to write wrfout_d01/2/3_2017-07-27_00:00:00 not by the starting date, any help!

======================
Timing for main: time 2017-07-26_23:59:20 on domain 3: 0.23375 elapsed seconds
Timing for main: time 2017-07-26_23:59:20 on domain 2: 1.04414 elapsed seconds
Timing for main: time 2017-07-26_23:59:33 on domain 3: 0.24239 elapsed seconds
Timing for main: time 2017-07-26_23:59:46 on domain 3: 0.23367 elapsed seconds
Timing for main: time 2017-07-27_00:00:00 on domain 3: 0.23290 elapsed seconds
Timing for Writing wrfout_d03_2017-07-27_00:00:00 for domain 3: 2.61794 elapsed seconds
Timing for main: time 2017-07-27_00:00:00 on domain 2: 3.67430 elapsed seconds
Timing for Writing wrfout_d02_2017-07-27_00:00:00 for domain 2: 1.37804 elapsed seconds
Timing for main: time 2017-07-27_00:00:00 on domain 1: 7.37689 elapsed seconds
Timing for Writing wrfout_d01_2017-07-27_00:00:00 for domain 1: 0.43139 elapsed seconds
wrf: SUCCESS COMPLETE WRF
===================================
 
Can you issue the command: ncdump -v Times wrfout_d01_2017-07-27_00:00:00?

I suppose you can find that all times of output are saved in the same single file.

If you want them to be in separate wrfout files, please modify your namelist.input and set the option:

frames_per_outfile = 1, 1, 1,

Then rerun the case.
 
Hi Ming,
Thanks,

It includes all the steps which I needed, I don't need separate files. so kept frames_per_file 1000

Why I am getting file name by start date 26 not by 27 as a final wrfout.
I am getting this filename wrfout_d01_2017-07-26_00:00:00
 
If you set frames_per_outfile = 1000, 1000, 1000, then each wrfout file will consist of 1000 times of output. The first output file is wrfout_d01/2/3_2017-07-26_00:00:00. Although the time in its name is 2017-07-26_00:00:00, it actually includes wrfout files at all other times. This is why I suggest you issue the command: ncdump -v Times wrfout_d01/2/3_2017-07-26_00:00:00, which will yield all the times when wrfout files are written.
 
Hi Ming,

Thanks for your reply. I have checked earlier with ncdump and it includes all the timesteps.
I was only wondering about the name of wrfout was not the end_date but in earlier version it was, so thought better to clarify.

Thanks again for your support!
 
Top