Problem with radiation driver

Any issues with the actual running of the WRF.

Problem with radiation driver

Postby dingwell » Wed Apr 15, 2015 11:58 am

WRF is crashing in the radiation driver. I'm running a version compiled with debugging options and get the following in one of the rsl.error.* files:
Code: Select all
...
forrtl: warning (402): fort: (1): In call to PRE_RADIATION_DRIVER, an array temporary was created for argument #51

forrtl: warning (402): fort: (1): In call to RADIATION_DRIVER, an array temporary was created for argument #94

forrtl: warning (402): fort: (1): In call to RADIATION_DRIVER, an array temporary was created for argument #96

forrtl: severe (408): fort: (3): Subscript #1 of the array TOTPLNK has value -5 which is less than the lower bound of 1

Image              PC                Routine            Line        Source             
libintlc.so.5      00002B97C7D73A7A  Unknown               Unknown  Unknown
libintlc.so.5      00002B97C7D72576  Unknown               Unknown  Unknown
libifcore.so.5     00002B97C6E1F8EC  Unknown               Unknown  Unknown
libifcore.so.5     00002B97C6D91E92  Unknown               Unknown  Unknown
libifcore.so.5     00002B97C6D92413  Unknown               Unknown  Unknown
wrf.exe            0000000006212AA1  module_ra_rrtm_mp        6375  module_ra_rrtm.f90
wrf.exe            0000000006100CB3  module_ra_rrtm_mp        2258  module_ra_rrtm.f90
wrf.exe            00000000060FB088  module_ra_rrtm_mp        1992  module_ra_rrtm.f90
wrf.exe            0000000003B83EE8  module_radiation_        1106  module_radiation_driver.f90
wrf.exe            0000000004204E1D  module_first_rk_s         267  module_first_rk_step_part1.f90
wrf.exe            0000000003128313  solve_em_                 824  solve_em.f90
wrf.exe            0000000002CB10A9  solve_interface_          117  solve_interface.f90
wrf.exe            00000000004F0B78  module_integrate_         313  module_integrate.f90
wrf.exe            0000000000406B3E  module_wrf_top_mp         333  module_wrf_top.f90
wrf.exe            000000000040612E  MAIN__                     31  wrf.f90
wrf.exe            00000000004060CC  Unknown               Unknown  Unknown
libc.so.6          00002B97C7ED5D5D  Unknown               Unknown  Unknown
wrf.exe            0000000000405FC9  Unknown               Unknown  Unknown

There are plenty of warnings similar to the first three lines listed above. I find no hints of problem in the rsl.out.* files.

When I run with a fixed time step, the model crashes at 6 minutes after initialization, which, I guess, is the first time that the radiation module is called (radt=6). When I run with a variable time step the model crashes at 00:12:22 after initialization.

Has anyone seen this before?
dingwell
 
Posts: 10
Joined: Mon Jan 30, 2012 6:10 am

Re: Problem with radiation driver

Postby tristan » Mon Feb 20, 2017 8:07 pm

Hello, have you found a solution to this issue? I am noting the same problem with v3.8.1.

My understanding is that this part of the code in subroutine RTRN is failing:
DBDTLEV= TOTPLNK(INDLEV(LEV)+1, IBAND) - TOTPLNK (INDLEV(LEV), IBAND)

It seems that it could be a memory issue, as before I ran this with debugging options, a segmentation fault occurred. STACK options etc do not solve it.

d01 2008-01-01_00:00:00 CALL rrtm
d01 2008-01-01_00:00:00 CAM-CLWRF interpolated values______ year: 2008 julian day: 0.0000000E+00
d01 2008-01-01_00:00:00 CAM-CLWRF co2vmr: 3.790000046137720E-004 n2ovmr: 3.190000086306100E-007 ch4vmr: 1.773999997567444E-006
forrtl: severe (408): fort: (2): Subscript #1 of the array TOTPLNK has value 191 which is greater than the upper bound of 181

Image PC Routine Line Source
wrf.exe 000000000B8ECD76 Unknown Unknown Unknown
wrf.exe 00000000059F2DF9 module_ra_rrtm_mp 6397 module_ra_rrtm.f90
wrf.exe 00000000059368CC module_ra_rrtm_mp 2280 module_ra_rrtm.f90
wrf.exe 00000000059319D7 module_ra_rrtm_mp 2014 module_ra_rrtm.f90
wrf.exe 0000000003C6C60E module_radiation_ 1349 module_radiation_driver.f90
wrf.exe 00000000041A8283 module_first_rk_s 286 module_first_rk_step_part1.f90
wrf.exe 000000000325C9F9 solve_em_ 917 solve_em.f90
wrf.exe 0000000002E5990D solve_interface_ 130 solve_interface.f90
wrf.exe 000000000051149F module_integrate_ 339 module_integrate.f90
wrf.exe 000000000040B52E module_wrf_top_mp 347 module_wrf_top.f90
wrf.exe 000000000040A9C5 MAIN__ 54 wrf.f90
wrf.exe 000000000040A97E Unknown Unknown Unknown
wrf.exe 000000000B9CB080 Unknown Unknown Unknown
wrf.exe 000000000040A857 Unknown Unknown Unknown
tristan
 
Posts: 8
Joined: Tue Nov 29, 2011 11:31 pm

Re: Problem with radiation driver

Postby tristan » Tue Mar 07, 2017 8:01 pm

I have solved this particular problem.

In my case, the issue related directly to the input dataset. I am using ERA-Interim model level data, and I was missing a crucial step in the WPS process that generates data vertically interpolated from model level to pressure level. This was causing all sorts of issues with WRF, as one can imagine. It is essential when working with ERA-Interim model level data that the following step is done after running ungrib.exe:

Create coefficient table (e.g. called 'ecmwf_coeffs') ; edit ‘namelist.wps’ prefix under &ungrib from ‘FILE’ to ‘PRES’; run ./calc_ecmwf_p.exe (PRES* intermediate files created).
Note: before running metgrid.exe you will need to add the 'PRES' prefix to 'fg_name' under &metgrid.

While I can't be sure what dataset the previous user was working with, I know that I solved this issue by undertaking the steps outlined above.



Example coefficient table
0 0.000000 0.00000000
1 20.000000 0.00000000
2 38.425343 0.00000000
3 63.647804 0.00000000
4 95.636963 0.00000000
5 134.483307 0.00000000
6 180.584351 0.00000000
7 234.779053 0.00000000
8 298.495789 0.00000000
9 373.971924 0.00000000
10 464.618134 0.00000000
11 575.651001 0.00000000
12 713.218079 0.00000000
13 883.660522 0.00000000
14 1094.834717 0.00000000
15 1356.474609 0.00000000
16 1680.640259 0.00000000
17 2082.273926 0.00000000
18 2579.888672 0.00000000
19 3196.421631 0.00000000
20 3960.291504 0.00000000
21 4906.708496 0.00000000
22 6018.019531 0.00000000
23 7306.631348 0.00000000
24 8765.053711 0.00007582
25 10376.126953 0.00046139
26 12077.446289 0.00181516
27 13775.325195 0.00508112
28 15379.805664 0.01114291
29 16819.474609 0.02067788
30 18045.183594 0.03412116
31 19027.695313 0.05169041
32 19755.109375 0.07353383
33 20222.205078 0.09967469
34 20429.863281 0.13002251
35 20384.480469 0.16438432
36 20097.402344 0.20247594
37 19584.330078 0.24393314
38 18864.750000 0.28832296
39 17961.357422 0.33515489
40 16899.468750 0.38389215
41 15706.447266 0.43396294
42 14411.124023 0.48477158
43 13043.218750 0.53570992
44 11632.758789 0.58616841
45 10209.500977 0.63554746
46 8802.356445 0.68326861
47 7438.803223 0.72878581
48 6144.314941 0.77159661
49 4941.778320 0.81125343
50 3850.913330 0.84737492
51 2887.696533 0.87965691
52 2063.779785 0.90788388
53 1385.912598 0.93194032
54 855.361755 0.95182151
55 467.333588 0.96764523
56 210.393890 0.97966272
57 65.889244 0.98827010
58 7.367743 0.99401945
59 0.000000 0.99763012
60 0.000000 1.00000000
tristan
 
Posts: 8
Joined: Tue Nov 29, 2011 11:31 pm

Re: Problem with radiation driver

Postby wxtom » Tue Oct 15, 2019 9:56 am

I believe I'm having this same issue, but am using the 20th Century Reanalysis. Has anyone figured out a solution when using that dataset rather than the ERA?
wxtom
 
Posts: 18
Joined: Wed Feb 24, 2010 10:23 am


Return to Runtime Problems

Who is online

Users browsing this forum: No registered users and 12 guests