I am new to WRF and I am trying to run the model for a nested domain (D1 and D2, I attach the namelist). I have metgrid files for all the times in Domain 1, and just for the initial time (met_em.d02.2018-11-01_00:00:00.nc) in Domain 2 (as further times should not be needed). However, when running real.exe, after it runs for D1, it processes the initial time for D2 but then stops when trying to find the second met_em.d02 file (see the rsl.out.0000 output below). The met_em.d02.2018-11-01_01:00:00.nc does not exist because I thought it was not needed. Am I wrong? Is that warning "normal"? I do not see any "real.exe run successfully" at the end because it stops running after the FATAL CALLED, however, wrfinput_d01, wrfinput_d02 and wrfbdy_d01 are generated.
Thank you for your help.
From rsl.out.0000:
-----------------------------------------------------------------------------
Domain 2: Current date being processed: 2018-11-01_00:00:00.0000, which is loop # 1 out of 13
configflags%julyr, %julday, %gmt: 2018 305 0.0000000E+00
Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.4
Input data is acceptable to use: met_em.d02.2018-11-01_00:00:00.nc
metgrid input_wrf.F first_date_input = 2018-11-01_00:00:00
metgrid input_wrf.F first_date_nml = 2018-11-01_00:00:00
Timing for input 15 s.
flag_soil_layers read from met_em file is 1
Using sfcprs3 to compute psfc
No average surface temperature for use with inland lakes
Assume Noah LSM input
forcing artificial silty clay loam at 69 points, out of 16740
Timing for processing 1 s.
Timing for output 50 s.
Timing for loop # 1 = 66 s.
-----------------------------------------------------------------------------
Domain 2: Current date being processed: 2018-11-01_01:00:00.0000, which is loop # 2 out of 13
configflags%julyr, %julday, %gmt: 2018 305 1.000000
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 409
error opening met_em.d02.2018-11-01_01:00:00.nc for input; bad date in namelist or file not in directory
-------------------------------------------
taskid: 0 hostname: gadi-cpu-clx-1875.gadi.nci.org.au
Thank you for your help.
From rsl.out.0000:
-----------------------------------------------------------------------------
Domain 2: Current date being processed: 2018-11-01_00:00:00.0000, which is loop # 1 out of 13
configflags%julyr, %julday, %gmt: 2018 305 0.0000000E+00
Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.4
Input data is acceptable to use: met_em.d02.2018-11-01_00:00:00.nc
metgrid input_wrf.F first_date_input = 2018-11-01_00:00:00
metgrid input_wrf.F first_date_nml = 2018-11-01_00:00:00
Timing for input 15 s.
flag_soil_layers read from met_em file is 1
Using sfcprs3 to compute psfc
No average surface temperature for use with inland lakes
Assume Noah LSM input
forcing artificial silty clay loam at 69 points, out of 16740
Timing for processing 1 s.
Timing for output 50 s.
Timing for loop # 1 = 66 s.
-----------------------------------------------------------------------------
Domain 2: Current date being processed: 2018-11-01_01:00:00.0000, which is loop # 2 out of 13
configflags%julyr, %julday, %gmt: 2018 305 1.000000
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 409
error opening met_em.d02.2018-11-01_01:00:00.nc for input; bad date in namelist or file not in directory
-------------------------------------------
taskid: 0 hostname: gadi-cpu-clx-1875.gadi.nci.org.au