Differents values for num_metgrid_levels in met_em* files

Having problems running the WRF Preprocessing Sysmte (WPS)?

Differents values for num_metgrid_levels in met_em* files

Postby azepeda » Fri Nov 27, 2015 2:24 pm

Hello,

After getting this error for real.exe:

-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 862
input_wrf.F: SIZE MISMATCH: namelist ide,jde,num_metgrid_levels= 76 76 27 ; input data ide,jde,num_metgrid_levels= 76 76 22
-------------------------------------------

I checked the levels in the input data (inside a directory just created for the run):

Code: Select all
for f in met_em*; do ncdump -h $f | grep "num_metgrid_levels =" ; done | sort -u


And I found that severals levels existed:

Code: Select all
met_em.d01.2015-11-26_18:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-26_21:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-27_00:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-27_03:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-27_06:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-27_09:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-27_12:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-27_15:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-27_18:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-27_21:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-28_00:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-28_03:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-28_06:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-28_09:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-28_12:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-28_15:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-28_18:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-28_21:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-29_00:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-29_03:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-29_06:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-29_09:00:00.nc
        num_metgrid_levels = 22 ;
met_em.d01.2015-11-29_12:00:00.nc
        num_metgrid_levels = 27 ;
[b]met_em.d01.2015-11-29_15:00:00.nc
        num_metgrid_levels = 12 ;[/b]
met_em.d01.2015-11-29_18:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-29_21:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d01.2015-11-30_00:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-26_18:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-26_21:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-27_00:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-27_03:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-27_06:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-27_09:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-27_12:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-27_15:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-27_18:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-27_21:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-28_00:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-28_03:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-28_06:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-28_09:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-28_12:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-28_15:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-28_18:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-28_21:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-29_00:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-29_03:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-29_06:00:00.nc
        num_metgrid_levels = 27 ;
[b]met_em.d02.2015-11-29_09:00:00.nc
        num_metgrid_levels = 22 ;[/b]
met_em.d02.2015-11-29_12:00:00.nc
        num_metgrid_levels = 27 ;
[b]met_em.d02.2015-11-29_15:00:00.nc
        num_metgrid_levels = 12 ;[/b]
met_em.d02.2015-11-29_18:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-29_21:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d02.2015-11-30_00:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-26_18:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-26_21:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-27_00:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-27_03:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-27_06:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-27_09:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-27_12:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-27_15:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-27_18:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-27_21:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-28_00:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-28_03:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-28_06:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-28_09:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-28_12:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-28_15:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-28_18:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-28_21:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-29_00:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-29_03:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-29_06:00:00.nc
        num_metgrid_levels = 27 ;
[b]met_em.d03.2015-11-29_09:00:00.nc
        num_metgrid_levels = 22 ;[/b]
met_em.d03.2015-11-29_12:00:00.nc
        num_metgrid_levels = 27 ;
[b]met_em.d03.2015-11-29_15:00:00.nc
        num_metgrid_levels = 12 ;[/b]
met_em.d03.2015-11-29_18:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-29_21:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d03.2015-11-30_00:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-26_18:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-26_21:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-27_00:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-27_03:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-27_06:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-27_09:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-27_12:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-27_15:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-27_18:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-27_21:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-28_00:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-28_03:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-28_06:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-28_09:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-28_12:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-28_15:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-28_18:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-28_21:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-29_00:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-29_03:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-29_06:00:00.nc
        num_metgrid_levels = 27 ;
[b]met_em.d04.2015-11-29_09:00:00.nc
        num_metgrid_levels = 22 ;[/b]
met_em.d04.2015-11-29_12:00:00.nc
        num_metgrid_levels = 27 ;
[b]met_em.d04.2015-11-29_15:00:00.nc
        num_metgrid_levels = 12 ;[/b]
met_em.d04.2015-11-29_18:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-29_21:00:00.nc
        num_metgrid_levels = 27 ;
met_em.d04.2015-11-30_00:00:00.nc
        num_metgrid_levels = 27 ;


Why is it possible to have several values for num_metgrid_levels?
azepeda
 
Posts: 9
Joined: Thu Apr 18, 2013 2:36 pm

Re: Differents values for num_metgrid_levels in met_em* file

Postby kwthomas » Mon Nov 30, 2015 2:22 pm

Look at the 11/29 09Z file. It is reporting 22 levels. That's probably the problem.
Kevin W. Thomas
Center for Analysis and Prediction of Storms
University of Oklahoma
kwthomas
 
Posts: 168
Joined: Thu Aug 07, 2008 6:53 pm

Re: Differents values for num_metgrid_levels in met_em* file

Postby azepeda » Tue Dec 01, 2015 8:13 am

Thank you kwthomas,

What could the cause be for this? Why has real.exe found this value in the input data?

Metgrid has read it from ungrib and ungrib from GFS... I am using GFS data from NCEP:

Code: Select all
2015-11-26 19:44:34: [http://ftpprd.ncep.noaa.gov/data/nccf/com/gfs/prod/gfs.2015112618]

=========== Data GFS ==========

-rw------- 1 azepeda users  59324886 Nov 26 18:24 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f000
-rw------- 1 azepeda users  66577520 Nov 26 18:27 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f003
-rw------- 1 azepeda users  67587503 Nov 26 18:29 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f006
-rw------- 1 azepeda users  67647285 Nov 26 18:31 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f009
-rw------- 1 azepeda users  68871261 Nov 26 18:33 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f012
-rw------- 1 azepeda users  68999413 Nov 26 18:34 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f015
-rw------- 1 azepeda users  69070604 Nov 26 18:35 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f018
-rw------- 1 azepeda users  69035053 Nov 26 18:36 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f021
-rw------- 1 azepeda users  69645691 Nov 26 18:37 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f024
-rw------- 1 azepeda users  69471725 Nov 26 18:38 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f027
-rw------- 1 azepeda users  69675221 Nov 26 18:39 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f030
-rw------- 1 azepeda users  69053975 Nov 26 18:40 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f033
-rw------- 1 azepeda users  69893028 Nov 26 18:41 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f036
-rw------- 1 azepeda users  69852094 Nov 26 18:42 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f039
-rw------- 1 azepeda users  70415874 Nov 26 18:43 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f042
-rw------- 1 azepeda users  70139482 Nov 26 18:44 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f045
-rw------- 1 azepeda users  70398492 Nov 26 18:44 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f048
-rw------- 1 azepeda users  71487681 Nov 26 18:46 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f051
-rw------- 1 azepeda users  70867066 Nov 26 18:46 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f054
-rw------- 1 azepeda users  70678167 Nov 26 18:47 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f057
-rw------- 1 azepeda users  80045890 Nov 26 18:49 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f060
-rw------- 1 azepeda users 106576970 Nov 26 18:49 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f063
-rw------- 1 azepeda users  70551361 Nov 26 18:50 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f066
-rw------- 1 azepeda users 122555043 Nov 26 18:51 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f069
-rw------- 1 azepeda users  72653615 Nov 26 18:52 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f072
-rw------- 1 azepeda users  75723772 Nov 26 18:53 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f075
-rw-r--r-- 1 azepeda users       675 Nov 26 19:44 /home/azepeda/tmp/swrf.gfs/2015112618/list.txt
-rw------- 1 azepeda users       132 Nov 26 19:44 /home/azepeda/tmp/swrf.gfs/2015112618/source.url
-rw------- 1 azepeda users  71043212 Nov 26 20:28 /home/azepeda/tmp/swrf.gfs/2015112618/gfs.t18z.pgrb2.0p50.f078

===============================


The whole process is automatized and the workspace is every time a clean and fresh directory just created for the run. Furthermore, this is not a frequent event but when it happens it obviously blows up the run.

So, can this rare event be detected before the preprocessing? Should I scan the GFS files searching for these levels? If I detect the anomaly, the run is lost irremediably lost or may somehow skip this file?

What would you suggest?

By the way, We are using WPS+WRF 3.7.
azepeda
 
Posts: 9
Joined: Thu Apr 18, 2013 2:36 pm

Re: Differents values for num_metgrid_levels in met_em* file

Postby kwthomas » Wed Dec 02, 2015 5:22 pm

Unfortunately, I can't answer why. I don't even use the WPS software. I use the CAPS software that creates the met* files, then let "real.exe" and "wrf.exe" take over.

One possibility might be a problem with the input data to WPS. Maybe it doesn't have all the levels it is supposed to have.

You might try upgrading to WRF 3.7.1 and see if that helps.
Kevin W. Thomas
Center for Analysis and Prediction of Storms
University of Oklahoma
kwthomas
 
Posts: 168
Joined: Thu Aug 07, 2008 6:53 pm

Re: Differents values for num_metgrid_levels in met_em* file

Postby azepeda » Sat Apr 16, 2016 9:12 am

It is still happening :-(

From time to time, this strange error repeats itself blowing up our runs...

Here some timestamps from our logs related to these issue:

2015-06-05 20:15:52.721189
2015-06-05 20:15:45.549276
2015-10-09 08:23:25.840488
2015-10-09 08:23:41.352535
2015-11-18 20:07:42.906449
2015-11-18 20:08:32.497188
2015-11-19 20:13:19.171674
2015-11-19 20:13:20.940825
2015-11-20 14:13:53.498349
2015-11-20 20:12:12.175672
2015-11-21 08:10:29.765376
2015-11-21 20:12:12.325116
2015-11-22 08:12:29.276123
2015-11-22 20:28:31.823589
2015-11-23 08:14:49.64984
2015-11-23 10:29:36.830229
2015-11-23 11:30:48.345947
2015-11-23 14:19:32.072538
2015-11-25 20:38:32.546526
2015-11-25 20:38:37.019811
2015-11-26 20:35:40.565821
2015-11-27 10:09:01.353084
2015-11-27 10:09:26.896522
2015-11-27 10:29:14.519454
2015-11-27 10:30:12.517143
2015-11-27 20:40:13.29772
2016-02-27 09:21:22.259974
2016-02-27 09:21:36.141391
2016-02-27 09:22:09.70735
2016-04-16 08:31:06.835586
2016-04-16 08:31:11.046058
2016-04-16 08:52:47.589905

Does somebody have found something like this issue?
azepeda
 
Posts: 9
Joined: Thu Apr 18, 2013 2:36 pm

Re: Differents values for num_metgrid_levels in met_em* file

Postby azepeda » Wed Nov 16, 2016 11:09 am

Rephrasing this issue again...

From time to time real.exe blows up when is reading the met_em.*.nc files because it finds that there is a different value than expected for num_metgrid_levels.

A rsl.out.0000 file shows this:

Domain 1: Current date being processed: 2016-11-11_15:00:00.0000, which is loop # 12 out of 22
configflags%julyr, %julday, %gmt: 2016 316 15.0000000
metgrid input_wrf.F first_date_input = 2016-11-11_15:00:00
metgrid input_wrf.F first_date_nml = 2016-11-10_06:00:00
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 862
input_wrf.F: SIZE MISMATCH: namelist ide,jde,num_metgrid_levels= 115 115 32 ; input data ide,jde,num_metgrid_levels= 115 115 19
-------------------------------------------

So, now we have a previous update for this field in the namelist.input file according to the value found in the met_em*.nc files.

However, what could we do when we find several values for num_metgrid_levels?

Imagine that most of the met_em*nc files contain "num_metgrid_levels = 32 ;" but two or three have "num_metgrid_levels = 19 ;" too. How is this even possible?

Thanks,
azepeda
 
Posts: 9
Joined: Thu Apr 18, 2013 2:36 pm


Return to Runtime Problems

Who is online

Users browsing this forum: No registered users and 1 guest

cron