AstroCrush
New member
I'm trying to run an ERA5 forecast on a one-hour global scale. All the steps in the WPS work correctly, but when I run the real.exe it returns an error.
I'm attaching the met_em file and the two namelist's. If anyone can help me, I will be eternally grateful.
Edit: I'm using the last version of both WPS and WRF, which comes with the code for the version 4.6.1
Domain # 1: dx = ********* m
REAL_EM V4.6.1 PREPROCESSOR
git commit d66e442fccc04111067e29274c9f9eaccc3cef28
DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 608648052 bytes allocated
Time period # 1 to process = 2020-01-01_00:00:00.
Time period # 2 to process = 2020-01-01_01:00:00.
Total analysis times to input = 2.
-----------------------------------------------------------------------------
Domain 1: Current date being processed: 2020-01-01_00:00:00.0000, which is loop # 1 out of 2
configflags%julyr, %julday, %gmt: 2020 1 0.00000000
Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.6.0
Input data is acceptable to use: met_em.d01.2020-01-01_00:00:00.nc
metgrid input_wrf.F first_date_input = 2020-01-01_00:00:00
metgrid input_wrf.F first_date_nml = 2020-01-01_00:00:00
Timing for input 0 s.
flag_soil_layers read from met_em file is 1
*** Error in boundary condition specification
boundary conditions at xs 1
boundary conditions at xe 1
boundary conditions at ys 2
boundary conditions at ye 2
boundary conditions logicals are
periodic_x F
periodic_y F
symmetric_xs F
symmetric_xe F
symmetric_ys F
symmetric_ye F
open_xs F
open_xe F
open_ys F
open_ye F
polar T
nested F
specified T
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 165
*** Error in boundary condition specification
-------------------------------------------
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 165
*** Error in boundary condition specification
-------------------------------------------
STOP wrf_abort
I'm attaching the met_em file and the two namelist's. If anyone can help me, I will be eternally grateful.
Edit: I'm using the last version of both WPS and WRF, which comes with the code for the version 4.6.1
Domain # 1: dx = ********* m
REAL_EM V4.6.1 PREPROCESSOR
git commit d66e442fccc04111067e29274c9f9eaccc3cef28
DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 608648052 bytes allocated
Time period # 1 to process = 2020-01-01_00:00:00.
Time period # 2 to process = 2020-01-01_01:00:00.
Total analysis times to input = 2.
-----------------------------------------------------------------------------
Domain 1: Current date being processed: 2020-01-01_00:00:00.0000, which is loop # 1 out of 2
configflags%julyr, %julday, %gmt: 2020 1 0.00000000
Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.6.0
Input data is acceptable to use: met_em.d01.2020-01-01_00:00:00.nc
metgrid input_wrf.F first_date_input = 2020-01-01_00:00:00
metgrid input_wrf.F first_date_nml = 2020-01-01_00:00:00
Timing for input 0 s.
flag_soil_layers read from met_em file is 1
*** Error in boundary condition specification
boundary conditions at xs 1
boundary conditions at xe 1
boundary conditions at ys 2
boundary conditions at ye 2
boundary conditions logicals are
periodic_x F
periodic_y F
symmetric_xs F
symmetric_xe F
symmetric_ys F
symmetric_ye F
open_xs F
open_xe F
open_ys F
open_ye F
polar T
nested F
specified T
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 165
*** Error in boundary condition specification
-------------------------------------------
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 165
*** Error in boundary condition specification
-------------------------------------------
STOP wrf_abort
Attachments
Last edited: