ZhangHanyang
New member
When i ran real.exe, i recived a report in file 'rsl.error.0000'.
taskid: 0 hostname: zhy-virtual-machine
module_io_quilt_old.F 2931 T
Ntasks in X 1 , ntasks in Y 1
*************************************
Configuring physics suite 'conus'
mp_physics: 8
cu_physics: 6
ra_lw_physics: 4
ra_sw_physics: 4
bl_pbl_physics: 2
sf_sfclay_physics: 2
sf_surface_physics: 2
*************************************
Domain # 1: dx = 20000.000 m
REAL_EM V4.5.1 PREPROCESSOR
No git found or not a git repository, git commit version not available.
*************************************
Parent domain
ids,ide,jds,jde 1 74 1 61
ims,ime,jms,jme -4 79 -4 66
ips,ipe,jps,jpe 1 74 1 61
*************************************
DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 222168244 bytes allocated
d01 2024-01-12_00:00:00 Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.5
d01 2024-01-12_00:00:00 Input data is acceptable to use: met_em.d01.2024-01-12_00:00:00.nc
metgrid input_wrf.F first_date_input = 2024-01-12_00:00:00
metgrid input_wrf.F first_date_nml = 2024-01-12_00:00:00
d01 2024-01-12_00:00:00 Timing for input 0 s.
d01 2024-01-12_00:00:00 flag_soil_layers read from met_em file is 1
d01 2024-01-12_00:00:00 Turning off use of MAX WIND level data in vertical interpolation
d01 2024-01-12_00:00:00 Turning off use of TROPOPAUSE level data in vertical interpolation
Max map factor in domain 1 = 1.02. Scale the dt in the model accordingly.
Using sfcprs3 to compute psfc
d01 2024-01-12_00:00:00 No average surface temperature for use with inland lakes
Assume Noah LSM input
d01 2024-01-12_00:00:00 forcing artificial silty clay loam at 70 points, out of 4380
d01 2024-01-12_00:00:00 Timing for processing 0 s.
d01 2024-01-12_00:00:00 Timing for output 0 s.
d01 2024-01-12_00:00:00 Timing for loop # 1 = 0 s.
d01 2024-01-12_03:00:00 Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.5
d01 2024-01-12_03:00:00 Input data is acceptable to use: met_em.d01.2024-01-12_03:00:00.nc
metgrid input_wrf.F first_date_input = 2024-01-12_03:00:00
metgrid input_wrf.F first_date_nml = 2024-01-12_00:00:00
d01 2024-01-12_03:00:00 Timing for input 0 s.
d01 2024-01-12_03:00:00 flag_soil_layers read from met_em file is 1
d01 2024-01-12_03:00:00 Turning off use of MAX WIND level data in vertical interpolation
d01 2024-01-12_03:00:00 Turning off use of TROPOPAUSE level data in vertical interpolation
Using sfcprs3 to compute psfc
d01 2024-01-12_03:00:00 No average surface temperature for use with inland lakes
Assume Noah LSM input
d01 2024-01-12_03:00:00 forcing artificial silty clay loam at 20 points, out of 4380
d01 2024-01-12_03:00:00 Timing for processing 0 s.
d01 2024-01-12_03:00:00 Timing for output 0 s.
d01 2024-01-12_03:00:00 Timing for loop # 2 = 0 s.
d01 2024-01-12_06:00:00 Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.5
d01 2024-01-12_06:00:00 Input data is acceptable to use: met_em.d01.2024-01-12_06:00:00.nc
metgrid input_wrf.F first_date_input = 2024-01-12_06:00:00
metgrid input_wrf.F first_date_nml = 2024-01-12_00:00:00
d01 2024-01-12_06:00:00 Timing for input 0 s.
d01 2024-01-12_06:00:00 flag_soil_layers read from met_em file is 1
d01 2024-01-12_06:00:00 Turning off use of MAX WIND level data in vertical interpolation
d01 2024-01-12_06:00:00 Turning off use of TROPOPAUSE level data in vertical interpolation
Using sfcprs3 to compute psfc
d01 2024-01-12_06:00:00 No average surface temperature for use with inland lakes
Assume Noah LSM input
d01 2024-01-12_06:00:00 forcing artificial silty clay loam at 20 points, out of 4380
d01 2024-01-12_06:00:00 Timing for processing 0 s.
d01 2024-01-12_06:00:00 Timing for output 0 s.
d01 2024-01-12_06:00:00 Timing for loop # 3 = 0 s.
d01 2024-01-12_06:00:00 real_em: SUCCESS COMPLETE REAL_EM INIT
This report seems like normal i think.
But after i ran wrf.exe, the report changed like this:
Configuring physics suite 'conus'
mp_physics: 8
cu_physics: 6
ra_lw_physics: 4
ra_sw_physics: 4
bl_pbl_physics: 2
sf_sfclay_physics: 2
sf_surface_physics: 2
*************************************
Domain # 1: dx = 20000.000 m
WRF V4.5.1 MODEL
No git found or not a git repository, git commit version not available.
*************************************
Parent domain
ids,ide,jds,jde 1 74 1 61
ims,ime,jms,jme -4 79 -4 66
ips,ipe,jps,jpe 1 74 1 61
*************************************
DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 195377956 bytes allocated
med_initialdata_input: calling input_input
Input data is acceptable to use: wrfinput_d01
CURRENT DATE = 2024-01-12_00:00:00
SIMULATION START DATE = 2024-01-12_00:00:00
Timing for processing wrfinput file (stream 0) for domain 1: 0.01425 elapsed seconds
Max map factor in domain 1 = 1.02. Scale the dt in the model accordingly.
D01: Time step = NaN (s)
D01: Grid Distance = 20.0000000 (km)
D01: Grid Distance Ratio dt/dx = NaN (s/km)
D01: Ratio Including Maximum Map Factor = NaN (s/km)
D01: NML defined reasonable_time_step_ratio = 6.00000000
Climate GHG input from file from year 1765 to 2499
CO2 range = 277.91300000000001 579.26400000000001 ppm
N2O range = 274.37200000000001 359.79800000000000 ppb
CH4 range = 738.98599999999999 997.31100000000004 ppb
CFC11 range = 0.0000000000000000 1.4000000000000000E-002 ppt
CFC12 range = 0.0000000000000000 2.8809999999999998 ppt
Normal ending of CAMtr_volume_mixing_ratio file
GHG annual values from CAM trace gas file
Year = 2024 , Julian day = 12
CO2 = 4.2483025403275318E-004 volume mixing ratio
N2O = 3.3485441771049668E-007 volume mixing ratio
CH4 = 1.9474552038451087E-006 volume mixing ratio
CFC11 = 2.0837477437176578E-010 volume mixing ratio
CFC12 = 4.7829795650137353E-010 volume mixing ratio
INPUT LandUse = "MODIFIED_IGBP_MODIS_NOAH"
LANDUSE TYPE = "MODIFIED_IGBP_MODIS_NOAH" FOUND 61 CATEGORIES 2 SEASONS WATER CATEGORY = 17 SNOW CATEGORY = 15
INITIALIZE THREE Noah LSM RELATED TABLES
Skipping over LUTYPE = USGS
LANDUSE TYPE = MODIFIED_IGBP_MODIS_NOAH FOUND 20 CATEGORIES
INPUT SOIL TEXTURE CLASSIFICATION = STAS
SOIL TEXTURE CLASSIFICATION = STAS FOUND 19 CATEGORIES
ThompMP: read qr_acr_qg_V4.dat instead of computing
ThompMP: read qr_acr_qsV2.dat instead of computing
ThompMP: read freezeH2O.dat instead of computing
mediation_integrate.G 1242 DATASET=HISTORY
mediation_integrate.G 1243 grid%id 1 grid%oid 1
Timing for Writing wrfout_d01_2024-01-12_00:00:00 for domain 1: 0.11246 elapsed seconds
d01 2024-01-12_00:00:00 Input data is acceptable to use: wrfbdy_d01
Timing for processing lateral boundary for domain 1: 0.00444 elapsed seconds
Tile Strategy is not specified. Assuming 1D-Y
WRF TILE 1 IS 1 IE 74 JS 1 JE 61
WRF NUMBER OF TILES = 1
d01 2024-01-12_00:00:00 ----------------------------------------
d01 2024-01-12_00:00:00 W-DAMPING BEGINS AT W-COURANT NUMBER = 1.00000000
d01 2024-01-12_00:00:00 ----------------------------------------
Timing for main: time 2024-01-12_00:00:20 on domain 1: 3.07665 elapsed seconds
Program received signal SIGFPE: Floating-point exception - erroneous arithmetic operation.
Backtrace for this error:
#0 0x1498e6a23960 in ???
#1 0x1498e6a22ac5 in ???
#2 0x1498e3c4251f in ???
at ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
#3 0x565356820923 in ???
#4 0x5653569682d2 in ???
#5 0x5653561c1fde in ???
#6 0x565355fb11aa in ???
#7 0x565354fe2529 in ???
#8 0x565354f63b37 in ???
#9 0x565354f62fbe in ???
#10 0x1498e3c29d8f in __libc_start_call_main
at ../sysdeps/nptl/libc_start_call_main.h:58
#11 0x1498e3c29e3f in __libc_start_main_impl
taskid: 0 hostname: zhy-virtual-machine
module_io_quilt_old.F 2931 T
Ntasks in X 1 , ntasks in Y 1
*************************************
Configuring physics suite 'conus'
mp_physics: 8
cu_physics: 6
ra_lw_physics: 4
ra_sw_physics: 4
bl_pbl_physics: 2
sf_sfclay_physics: 2
sf_surface_physics: 2
*************************************
Domain # 1: dx = 20000.000 m
REAL_EM V4.5.1 PREPROCESSOR
No git found or not a git repository, git commit version not available.
*************************************
Parent domain
ids,ide,jds,jde 1 74 1 61
ims,ime,jms,jme -4 79 -4 66
ips,ipe,jps,jpe 1 74 1 61
*************************************
DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 222168244 bytes allocated
d01 2024-01-12_00:00:00 Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.5
d01 2024-01-12_00:00:00 Input data is acceptable to use: met_em.d01.2024-01-12_00:00:00.nc
metgrid input_wrf.F first_date_input = 2024-01-12_00:00:00
metgrid input_wrf.F first_date_nml = 2024-01-12_00:00:00
d01 2024-01-12_00:00:00 Timing for input 0 s.
d01 2024-01-12_00:00:00 flag_soil_layers read from met_em file is 1
d01 2024-01-12_00:00:00 Turning off use of MAX WIND level data in vertical interpolation
d01 2024-01-12_00:00:00 Turning off use of TROPOPAUSE level data in vertical interpolation
Max map factor in domain 1 = 1.02. Scale the dt in the model accordingly.
Using sfcprs3 to compute psfc
d01 2024-01-12_00:00:00 No average surface temperature for use with inland lakes
Assume Noah LSM input
d01 2024-01-12_00:00:00 forcing artificial silty clay loam at 70 points, out of 4380
d01 2024-01-12_00:00:00 Timing for processing 0 s.
d01 2024-01-12_00:00:00 Timing for output 0 s.
d01 2024-01-12_00:00:00 Timing for loop # 1 = 0 s.
d01 2024-01-12_03:00:00 Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.5
d01 2024-01-12_03:00:00 Input data is acceptable to use: met_em.d01.2024-01-12_03:00:00.nc
metgrid input_wrf.F first_date_input = 2024-01-12_03:00:00
metgrid input_wrf.F first_date_nml = 2024-01-12_00:00:00
d01 2024-01-12_03:00:00 Timing for input 0 s.
d01 2024-01-12_03:00:00 flag_soil_layers read from met_em file is 1
d01 2024-01-12_03:00:00 Turning off use of MAX WIND level data in vertical interpolation
d01 2024-01-12_03:00:00 Turning off use of TROPOPAUSE level data in vertical interpolation
Using sfcprs3 to compute psfc
d01 2024-01-12_03:00:00 No average surface temperature for use with inland lakes
Assume Noah LSM input
d01 2024-01-12_03:00:00 forcing artificial silty clay loam at 20 points, out of 4380
d01 2024-01-12_03:00:00 Timing for processing 0 s.
d01 2024-01-12_03:00:00 Timing for output 0 s.
d01 2024-01-12_03:00:00 Timing for loop # 2 = 0 s.
d01 2024-01-12_06:00:00 Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.5
d01 2024-01-12_06:00:00 Input data is acceptable to use: met_em.d01.2024-01-12_06:00:00.nc
metgrid input_wrf.F first_date_input = 2024-01-12_06:00:00
metgrid input_wrf.F first_date_nml = 2024-01-12_00:00:00
d01 2024-01-12_06:00:00 Timing for input 0 s.
d01 2024-01-12_06:00:00 flag_soil_layers read from met_em file is 1
d01 2024-01-12_06:00:00 Turning off use of MAX WIND level data in vertical interpolation
d01 2024-01-12_06:00:00 Turning off use of TROPOPAUSE level data in vertical interpolation
Using sfcprs3 to compute psfc
d01 2024-01-12_06:00:00 No average surface temperature for use with inland lakes
Assume Noah LSM input
d01 2024-01-12_06:00:00 forcing artificial silty clay loam at 20 points, out of 4380
d01 2024-01-12_06:00:00 Timing for processing 0 s.
d01 2024-01-12_06:00:00 Timing for output 0 s.
d01 2024-01-12_06:00:00 Timing for loop # 3 = 0 s.
d01 2024-01-12_06:00:00 real_em: SUCCESS COMPLETE REAL_EM INIT
This report seems like normal i think.
But after i ran wrf.exe, the report changed like this:
Configuring physics suite 'conus'
mp_physics: 8
cu_physics: 6
ra_lw_physics: 4
ra_sw_physics: 4
bl_pbl_physics: 2
sf_sfclay_physics: 2
sf_surface_physics: 2
*************************************
Domain # 1: dx = 20000.000 m
WRF V4.5.1 MODEL
No git found or not a git repository, git commit version not available.
*************************************
Parent domain
ids,ide,jds,jde 1 74 1 61
ims,ime,jms,jme -4 79 -4 66
ips,ipe,jps,jpe 1 74 1 61
*************************************
DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 195377956 bytes allocated
med_initialdata_input: calling input_input
Input data is acceptable to use: wrfinput_d01
CURRENT DATE = 2024-01-12_00:00:00
SIMULATION START DATE = 2024-01-12_00:00:00
Timing for processing wrfinput file (stream 0) for domain 1: 0.01425 elapsed seconds
Max map factor in domain 1 = 1.02. Scale the dt in the model accordingly.
D01: Time step = NaN (s)
D01: Grid Distance = 20.0000000 (km)
D01: Grid Distance Ratio dt/dx = NaN (s/km)
D01: Ratio Including Maximum Map Factor = NaN (s/km)
D01: NML defined reasonable_time_step_ratio = 6.00000000
Climate GHG input from file from year 1765 to 2499
CO2 range = 277.91300000000001 579.26400000000001 ppm
N2O range = 274.37200000000001 359.79800000000000 ppb
CH4 range = 738.98599999999999 997.31100000000004 ppb
CFC11 range = 0.0000000000000000 1.4000000000000000E-002 ppt
CFC12 range = 0.0000000000000000 2.8809999999999998 ppt
Normal ending of CAMtr_volume_mixing_ratio file
GHG annual values from CAM trace gas file
Year = 2024 , Julian day = 12
CO2 = 4.2483025403275318E-004 volume mixing ratio
N2O = 3.3485441771049668E-007 volume mixing ratio
CH4 = 1.9474552038451087E-006 volume mixing ratio
CFC11 = 2.0837477437176578E-010 volume mixing ratio
CFC12 = 4.7829795650137353E-010 volume mixing ratio
INPUT LandUse = "MODIFIED_IGBP_MODIS_NOAH"
LANDUSE TYPE = "MODIFIED_IGBP_MODIS_NOAH" FOUND 61 CATEGORIES 2 SEASONS WATER CATEGORY = 17 SNOW CATEGORY = 15
INITIALIZE THREE Noah LSM RELATED TABLES
Skipping over LUTYPE = USGS
LANDUSE TYPE = MODIFIED_IGBP_MODIS_NOAH FOUND 20 CATEGORIES
INPUT SOIL TEXTURE CLASSIFICATION = STAS
SOIL TEXTURE CLASSIFICATION = STAS FOUND 19 CATEGORIES
ThompMP: read qr_acr_qg_V4.dat instead of computing
ThompMP: read qr_acr_qsV2.dat instead of computing
ThompMP: read freezeH2O.dat instead of computing
mediation_integrate.G 1242 DATASET=HISTORY
mediation_integrate.G 1243 grid%id 1 grid%oid 1
Timing for Writing wrfout_d01_2024-01-12_00:00:00 for domain 1: 0.11246 elapsed seconds
d01 2024-01-12_00:00:00 Input data is acceptable to use: wrfbdy_d01
Timing for processing lateral boundary for domain 1: 0.00444 elapsed seconds
Tile Strategy is not specified. Assuming 1D-Y
WRF TILE 1 IS 1 IE 74 JS 1 JE 61
WRF NUMBER OF TILES = 1
d01 2024-01-12_00:00:00 ----------------------------------------
d01 2024-01-12_00:00:00 W-DAMPING BEGINS AT W-COURANT NUMBER = 1.00000000
d01 2024-01-12_00:00:00 ----------------------------------------
Timing for main: time 2024-01-12_00:00:20 on domain 1: 3.07665 elapsed seconds
Program received signal SIGFPE: Floating-point exception - erroneous arithmetic operation.
Backtrace for this error:
#0 0x1498e6a23960 in ???
#1 0x1498e6a22ac5 in ???
#2 0x1498e3c4251f in ???
at ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
#3 0x565356820923 in ???
#4 0x5653569682d2 in ???
#5 0x5653561c1fde in ???
#6 0x565355fb11aa in ???
#7 0x565354fe2529 in ???
#8 0x565354f63b37 in ???
#9 0x565354f62fbe in ???
#10 0x1498e3c29d8f in __libc_start_call_main
at ../sysdeps/nptl/libc_start_call_main.h:58
#11 0x1498e3c29e3f in __libc_start_main_impl