Hello,
After I successfully ran a "Base" physics configuration (see table below) multiple times, doing high-res. topgraphy and vertical-levels-number experiments, I needed to try other physics parameterizations. According to an extensive literature review and my case's characteristics (tropical, oceanic, mountainous island), I selected two physics schemes configurations, Test1 and Test2, as shown in table below :
I did not find any contraindication between the physical schemes selected for each of both new configurations.
However, both runs crash. I checked that it's not a CFL condition breach.
Nevertheless I tried decreasing the timestep from 40 seconds to 36 seconds. Still both runs crash at respectively the 7th and 8th step (equivalent to approx. 4-5 mins). See below :
I then tried decreasing to 30 seconds, the simulations go on for 2 more steps each, to 9th and 10th (again, around 4-5 mins). When reducing the timestep to 10 seconds for Test1, I get further in the steps (until 29th), but still : the run crashes around 5 minutes in.
I also did investigate the wrfinput files (despite the script doesn't handle very well powered number, it's OK for a quick tour I guess) :
Using ncview and looking at some variables didn't help either : I can't find anything wrong in wrfinput files. About other inputs : wrflowinp files are unchaged since previous "Base" runs (contain only VEGFRA and SST). As for wrfbdy files obtained via NDOWN, it can't unfortunately be visualized by ncview. However, I respected the whole previously successful process without any sign of an error and am pretty confident the problem doesn't originate in this file.
Lastly : the first wrfout* files (approx 15 Mb size) contains no time mark nor are being readable by ncview.
Attached hereunder are the tar files containing all rsl.error* files as well as the namelist.input, for each of both configurations.
Thank you for your time.
EDIT : it seems, once again, the problem originates from NDOWN's wrfinput* files. The config. works fine when initialized by REAL's ouputs (even though the config. used in the REAL namelist is not exactly the same as the one run in WRF).
After I successfully ran a "Base" physics configuration (see table below) multiple times, doing high-res. topgraphy and vertical-levels-number experiments, I needed to try other physics parameterizations. According to an extensive literature review and my case's characteristics (tropical, oceanic, mountainous island), I selected two physics schemes configurations, Test1 and Test2, as shown in table below :
&Physics | Base | Test1 (WD_KF_CAM) | Test2 (WS_TK_RRTMG) |
mp_physics | 6. WSM6 | 16. WDM6 | 6. WSM6 |
cu_physics | 2. BMJ | 1. KF | 6. TDK |
ra_lw_physics | 1. RRTM | 3. CAM | 4. RRTMG |
ra_sw_physics | 1. Dudia | 3. CAM | 4. RRTMG |
sf_surface_physics | 1. Thermal Diffusion | 2. Noah LSM | 2. Noah LSM |
sf_sfclay_physics | 1. Revised MM5 | 1. Revised MM5 | 1. Revised MM5 |
pbl_physics | 1. YSU | 1. YSU | 1. YSU |
I did not find any contraindication between the physical schemes selected for each of both new configurations.
However, both runs crash. I checked that it's not a CFL condition breach.
Nevertheless I tried decreasing the timestep from 40 seconds to 36 seconds. Still both runs crash at respectively the 7th and 8th step (equivalent to approx. 4-5 mins). See below :
Code:
cat rsl.error.0007 | tail -n 20 | head -n 10
d01 2013-09-01_00:04:12 calling inc/HALO_EM_PHYS_A_inline.inc
d01 2013-09-01_00:04:12 Top of Radiation Driver
d01 2013-09-01_00:04:12 calling inc/HALO_PWP_inline.inc
d01 2013-09-01_00:04:12 calling inc/HALO_CUP_G3_IN_inline.inc
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
wrfexe 000000000288329D for__signal_handl Unknown Unknown
libpthread-2.19.s 00002AAAADE23870 Unknown Unknown Unknown
wrfexe 000000000229590C Unknown Unknown Unknown
wrfexe 000000000228C156 Unknown Unknown Unknown
Code:
cat rsl.error.0012 | tail -n 20 | head -n 10
d01 2013-09-01_00:04:48 Top of Radiation Driver
d01 2013-09-01_00:04:48 CALL cldfra1
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
wrfexe 000000000288329D for__signal_handl Unknown Unknown
libpthread-2.19.s 00002AAAADE23870 Unknown Unknown Unknown
wrfexe 0000000001C6FD44 Unknown Unknown Unknown
wrfexe 0000000001C0B286 Unknown Unknown Unknown
wrfexe 0000000001C05C28 Unknown Unknown Unknown
wrfexe 0000000001BFBACC Unknown Unknown Unknown
I then tried decreasing to 30 seconds, the simulations go on for 2 more steps each, to 9th and 10th (again, around 4-5 mins). When reducing the timestep to 10 seconds for Test1, I get further in the steps (until 29th), but still : the run crashes around 5 minutes in.
I also did investigate the wrfinput files (despite the script doesn't handle very well powered number, it's OK for a quick tour I guess) :
Code:
./minmax.sh wrfinput_d01_2013_09
Variable Minimum Maximum
---------------------------------------------
T2: 296.2937, 301.6903,
T: -6.958842e-05, 201.2966,
PSFC: 91929.33, 101260.6,
P: 0.6750414, 1259.358,
U10: -8.037662, -1.940215,
V10: -2.003774, 4.477623,
U: -10.00002, 27.52425,
V: -9.141862e-05, 17.43193,
W: -9.000254e-05, 9.999888e-05,
SST: 296.163, 303.1039,
TSK: 296.163, 303.1039,
TH2: 295.2446, 301.8733,
Q2: 0.01450976, 0.01995717,
QCLOUD: 0 9.9431e-06,
QVAPOR: 0.0001000018, 9.999984e-07,
./minmax.sh wrfinput_d02_2013_09
Variable Minimum Maximum
---------------------------------------------
T2: 297.4885, 301.6901,
T: -8.41996e-05, 194.4953,
PSFC: 91930.78, 101171.6,
P: 0.8658642, 1170.362,
U10: -8.000412, -1.995662,
V10: -2.003796, 4.477623,
U: -9.000722, 22.21929,
V: -9.379655e-05, 12.23109,
W: -9.000978e-06, 9.999872e-05,
SST: 296.1638, 302.3132
TSK: 296.1638, 302.3132
TH2: 297.0318, 301.8732,
Q2: 0.01605123, 0.01889061,
QCLOUD: 0 9.998767e-08,
QVAPOR: 0.0001000005, 9.999933e-07,
Using ncview and looking at some variables didn't help either : I can't find anything wrong in wrfinput files. About other inputs : wrflowinp files are unchaged since previous "Base" runs (contain only VEGFRA and SST). As for wrfbdy files obtained via NDOWN, it can't unfortunately be visualized by ncview. However, I respected the whole previously successful process without any sign of an error and am pretty confident the problem doesn't originate in this file.
Lastly : the first wrfout* files (approx 15 Mb size) contains no time mark nor are being readable by ncview.
Attached hereunder are the tar files containing all rsl.error* files as well as the namelist.input, for each of both configurations.
Thank you for your time.
EDIT : it seems, once again, the problem originates from NDOWN's wrfinput* files. The config. works fine when initialized by REAL's ouputs (even though the config. used in the REAL namelist is not exactly the same as the one run in WRF).
Attachments
Last edited: