GDAS data was used to run WRF v3, but the real.exe report this error:
metgrid input_wrf.F first_date_input = 2016-12-21_12:00:00
metgrid input_wrf.F first_date_nml = 2016-12-21_12:00:00
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 827
input_wrf.F: SIZE MISMATCH: namelist ide,jde,num_metgrid_levels= 191
131 32 ; input data ide,jde,num_metgrid_levels= 191
131 34
-------------------------------------------
In some cases, this would mean that the num_metgrid_levels in the namelist.input and the met_em file are not the same, but, when I use
ncdump -h met_em.d01.2016-12-21_12:00:00| grep BOTTOM-TOP_GRID_DIMENSION, I got
BOTTOM-TOP_GRID_DIMENSION = 32
and ncdump -h met_em.d01.2016-12-21_12:00:00| grep num_metgrid_levels, it was 34. In the namelist.input, num_metgrid_levels was set to 32.
In short, real.exe read a 32 level met_em input file and report it has 34 levels as the BOTTOM-TOP_GRID_DIMENSION in the met_file are not the same as num_metgrid_levels.
how to solve this problem?
metgrid input_wrf.F first_date_input = 2016-12-21_12:00:00
metgrid input_wrf.F first_date_nml = 2016-12-21_12:00:00
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 827
input_wrf.F: SIZE MISMATCH: namelist ide,jde,num_metgrid_levels= 191
131 32 ; input data ide,jde,num_metgrid_levels= 191
131 34
-------------------------------------------
In some cases, this would mean that the num_metgrid_levels in the namelist.input and the met_em file are not the same, but, when I use
ncdump -h met_em.d01.2016-12-21_12:00:00| grep BOTTOM-TOP_GRID_DIMENSION, I got
BOTTOM-TOP_GRID_DIMENSION = 32
and ncdump -h met_em.d01.2016-12-21_12:00:00| grep num_metgrid_levels, it was 34. In the namelist.input, num_metgrid_levels was set to 32.
In short, real.exe read a 32 level met_em input file and report it has 34 levels as the BOTTOM-TOP_GRID_DIMENSION in the met_file are not the same as num_metgrid_levels.
how to solve this problem?