Incorrect Size of wrfrst File for Inner Domain

[ehsantaghizadeh]

I attempted to run WRF using the attached namelist.wps and namelist.input files. I set restart_interval = 7200 for a simulation period of 156 hours. There are three wrfinput and wrfout files, which appear to be correct as I was able to open them with ncview. However, there are only two wrfrst files, and the one for d02 is only 48 bytes. Opening wrfrst_d01_2019-02-06_12:00:00 resulted in some warnings, but it displayed a plot in ncview:

Warning: did not correctly match mapped dims specified in the coordinates attribute to dims in the variable
Problem encountered on variable "SPFORCC5" which has shape (1,138,214)
and has coordinates attribute "XLONG XLAT XTIME"
The problem is that coordinate var "XLONG" has shape (1,137,213), which does not match dimensions in the variable being mapped!
Abandoning coordinate mapping for this variable
-------------
Warning: did not correctly match mapped dims specified in the coordinates attribute to dims in the variable
Problem encountered on variable "SPFORCC5" which has shape (1,138,214)
and has coordinates attribute "XLONG XLAT XTIME"
The problem is that coordinate var "XLAT" has shape (1,137,213), which does not match dimensions in the variable being mapped!
Abandoning coordinate mapping for this variable
-------------
Warning: did not correctly match mapped dims specified in the coordinates attribute to dims in the variable
Problem encountered on variable "SPFORCS5" which has shape (1,138,214)
and has coordinates attribute "XLONG XLAT XTIME"
The problem is that coordinate var "XLONG" has shape (1,137,213), which does not match dimensions in the variable being mapped!
Abandoning coordinate mapping for this variable
-------------
Warning: did not correctly match mapped dims specified in the coordinates attribute to dims in the variable
Problem encountered on variable "SPFORCS5" which has shape (1,138,214)
and has coordinates attribute "XLONG XLAT XTIME"
The problem is that coordinate var "XLAT" has shape (1,137,213), which does not match dimensions in the variable being mapped!
Abandoning coordinate mapping for this variable

However, opening wrfrst_d02_2019-02-06_12:00:00 failed with the message: "ncview: can't recognize format of input file."

Additionally, wrf.exe has frozen while running with a SLURM script, and no progress is being made. Should I terminate this wrf.exe process?

I also attempted to run WRF with the restart file by making the following change in namelist.input:

start_day = 06, 06, 06,
restart = .true.,

However, upon checking rsl.error.0000, the last line reads: "RESTART: nest, opening wrfrst_d02_2019-02-06_12:00:00 for reading." Clearly, the new wrf.exe process has stopped. I should mention that I have not yet terminated the previous wrf.exe process from the initial simulation.

I followed the thread WRF stuck when generating the first restart file (WRF stuck when generating the first restart file), but there have been no updates.

My specific questions are:

1. Why did wrf.exe freeze?
2. Does this issue occur for every run with a restart_interval shorter than the simulation period?
3. For a simulation with three domains, how many restart files should be created?
4. Do you have any idea why the wrfrst file for d02 was not created correctly?

Any help would be appreciated.

Sincerely,
Ehsan

 

[William.Hatheway]

Just to confirm this is your domain correct?

WRF restart setting

Dear Office, I ran WRF without the settings below: restart = .true., restart_interval = 1440, If I modify this as restart = .false., restart_interval = 1440, during the running period (the wrfout file has not been output for 24 hours), is that ok? I saw your guide at ARW Online Tutorial and...

forum.mmm.ucar.edu

This post above might help you

 

[kwerner]

Why did wrf.exe freeze?

It's really hard to say. We would need to start by looking at all of the rsl* files for the initial simulation. If that simulation didn't complete, then the restart simulation won't be able to run. Can you package those into a single *.tar file and attach that?

Does this issue occur for every run with a restart_interval shorter than the simulation period?

No, it shouldn't - that would defeat the purpose of the restart program. We expect wrf.exe to run to completion during the initial simulation, and to produce wrfrst* files at the interval specified for restart_interval.

For a simulation with three domains, how many restart files should be created?

There should be a restart file created at the end of every restart_interval. You have it set to 7200, meaning if wrf.exe for the initial simulation completed, you should have a restart file every 5 days of simulation time for each of the three domains.

Do you have any idea why the wrfrst file for d02 was not created correctly?

Again, we will need to investigate the rsl* files for the initial wrf simulation.