Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

real.exe-trouble when I use ERA-ECMWF

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.


New member
Dear all
I want to use ERA-20C but I am tryng use ERA now.
My WPS/WRF compute well whcn I use FNL or gdas.
However, when I made run real.exe with ERA, the followin messages are shown.
metgrid input_wrf.F first_date_input = 2000-09-10_18:00:00
metgrid input_wrf.F first_date_nml = 2000-09-10_18:00:00
d01 2000-09-10_18:00:00 input_wrf.F: SIZE MISMATCH: namelist num_metgrid_levels = 61
d01 2000-09-10_18:00:00 input_wrf.F: SIZE MISMATCH: input file BOTTOM-TOP_GRID_DIMENSION = 1
d01 2000-09-10_18:00:00 ---- ERROR: Mismatch between namelist and input file dimensions
NOTE: 1 namelist vs input data inconsistencies found.

I think "making num_metgrid_levels = 1" is strange, if it is number of z-layers.
I heard that num_metgrid_levels = 61 for ERA".

WPS/ungrib.exe and WPS/geogrid.exe ran well. Next I made run calc_ecmwf.exe and metgrid.exe.
met_em* were successfully made. Then real.exe showed the messages above.

I attach some logs. I will appreciate it if you give me any advices.


  • calc_ecmwf.log
    3.7 KB · Views: 51
  • geogrid.log
    38.7 KB · Views: 44
  • metgrid.log
    407 KB · Views: 48
  • namelist.input
    4.3 KB · Views: 46
  • ungrib.log
    57.5 KB · Views: 69
  • Vtable.log
    770 bytes · Views: 51
  • rsl.error.0000.log
    1.4 KB · Views: 48
  • rsl.out.0000.log
    2.2 KB · Views: 50
  • namelist.wps
    1,019 bytes · Views: 48
If the model is saying that you only have 1 level in the met_em file, then that likely is the case. You can check this with the following command:
ncdump -h met_em.d01.2000-09-10_18:00:00 | grep BOTTOM-TOP_GRID_DIMENSION
Additionally, when I look at your ungrib.log, it is only processing 1 level for every time period, so it seems that perhaps you are only grabbing a single level of data. You will need to ensure that you get all the levels when obtaining your input data.