Basic nesting in WRFV3

Discuss the nesting capability within the model itself and any problems you might have run into.

Basic nesting in WRFV3

Postby mtnez » Mon Oct 13, 2008 6:00 pm

Hi all WRF users,
I am a new WRF user. I have just installed WRF/WPS V3 in a linux box (gcc/gfortran compiler and basic nesting option 1). I have been able to run successfully most of the test cases. However, I have got into trouble when running the nesting case for the hurricane Katrina. The pre-processing WPS steps runs Ok and the intermediate and geo*.nc files for the two domains are generated correctly. The problem is that real.exe stops after processing domain 1 (check the FATAL ERROR message at the end).
Any advice..??
thanks a lot in advance
mtnez


[mtnez@yz em_real]$ ./real.exe

Namelist dfi_control not found in namelist.input. Using registry defaults for variables in dfi_control
REAL_EM V3.0 PREPROCESSOR
*************************************
Parent domain
ids,ide,jds,jde 1 98 1 70
ims,ime,jms,jme -4 103 -4 75
ips,ipe,jps,jpe 1 98 1 70
*************************************
DYNAMICS OPTION: Eulerian Mass Coordinate
Time period # 1 to process = 2005-08-28_00:00:00.
Time period # 2 to process = 2005-08-28_06:00:00.
Time period # 3 to process = 2005-08-28_12:00:00.
Time period # 4 to process = 2005-08-28_18:00:00.
Time period # 5 to process = 2005-08-29_00:00:00.
Total analysis times to input = 5.

-----------------------------------------------------------------------------

Domain 1: Current date being processed: 2005-08-28_00:00:00.0000, which is loop # 1 out of 5
configflags%julyr, %julday, %gmt: 2005 240 0.000000
d01 2005-08-28_00:00:00 Timing for input 0 s.
Converged znw(kte) should be about 0.0 = 2.7107822E-08
LAND CHANGE = 0
WATER CHANGE = 0
d01 2005-08-28_00:00:00 Timing for processing 1 s.
d01 2005-08-28_00:00:00 Timing for output 0 s.
d01 2005-08-28_00:00:00 Timing for loop # 1 = 1 s.

-----------------------------------------------------------------------------

Domain 1: Current date being processed: 2005-08-28_06:00:00.0000, which is loop # 2 out of 5
configflags%julyr, %julday, %gmt: 2005 240 6.000000
d01 2005-08-28_06:00:00 Timing for input 0 s.
LAND CHANGE = 0
WATER CHANGE = 0
d01 2005-08-28_06:00:00 Timing for processing 1 s.
LBC valid between these times 2005-08-28_00:00:00.0000 2005-08-28_06:00:00
d01 2005-08-28_06:00:00 Timing for output 0 s.
d01 2005-08-28_06:00:00 Timing for loop # 2 = 1 s.

-----------------------------------------------------------------------------

Domain 1: Current date being processed: 2005-08-28_12:00:00.0000, which is loop # 3 out of 5
configflags%julyr, %julday, %gmt: 2005 240 12.00000
d01 2005-08-28_12:00:00 Timing for input 0 s.
LAND CHANGE = 0
WATER CHANGE = 0
d01 2005-08-28_12:00:00 Timing for processing 1 s.
LBC valid between these times 2005-08-28_06:00:00.0000 2005-08-28_12:00:00
d01 2005-08-28_12:00:00 Timing for output 0 s.
d01 2005-08-28_12:00:00 Timing for loop # 3 = 1 s.

-----------------------------------------------------------------------------

Domain 1: Current date being processed: 2005-08-28_18:00:00.0000, which is loop # 4 out of 5
configflags%julyr, %julday, %gmt: 2005 240 18.00000
d01 2005-08-28_18:00:00 Timing for input 0 s.
LAND CHANGE = 0
WATER CHANGE = 0
d01 2005-08-28_18:00:00 Timing for processing 1 s.
LBC valid between these times 2005-08-28_12:00:00.0000 2005-08-28_18:00:00
d01 2005-08-28_18:00:00 Timing for output 0 s.
d01 2005-08-28_18:00:00 Timing for loop # 4 = 1 s.

-----------------------------------------------------------------------------

Domain 1: Current date being processed: 2005-08-29_00:00:00.0000, which is loop # 5 out of 5
configflags%julyr, %julday, %gmt: 2005 241 0.000000
d01 2005-08-29_00:00:00 Timing for input 0 s.
LAND CHANGE = 0
WATER CHANGE = 0
d01 2005-08-29_00:00:00 Timing for processing 1 s.
LBC valid between these times 2005-08-28_18:00:00.0000 2005-08-29_00:00:00
d01 2005-08-29_00:00:00 Timing for output 0 s.
d01 2005-08-29_00:00:00 Timing for loop # 5 = 1 s.
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: real_em.b LINE: 199
real_em.F: Could not find the parent domain
-------------------------------------------
mtnez
 
Posts: 2
Joined: Thu Oct 09, 2008 10:48 am

Re: Basic nesting in WRFV3

Postby mtnez » Fri Oct 17, 2008 2:33 pm

Hi all WRF users ,

Ifound the answer to my previous problem. It was very easy.
Just add a second column (because I am using 2 domains) to the parameter parent_id in the namelist.input.

parent_id = 0, 1,

thanks

mtnez
mtnez
 
Posts: 2
Joined: Thu Oct 09, 2008 10:48 am

Re: Basic nesting in WRFV3

Postby alainaketh » Mon Apr 04, 2016 11:07 am

Hi everyone,

In my case, I was using tree domains, telescopic nesting, so in my namelist.input I had

parent_id = 1, 1, 2,

But it crashed with the error stated here. I solved the problem by adding the following line

grid_id = 1, 2, 3,

In the &domains section of the namelist.input file. Check this page for references: http://mailman.ucar.edu/pipermail/wrf-u ... 03259.html
alainaketh
 
Posts: 28
Joined: Fri Jun 26, 2015 12:30 pm


Return to Nesting

Who is online

Users browsing this forum: No registered users and 2 guests