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

(RESOLVED) ERROR: Mismatch between namelist and input file dimensions

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.

Edo_021

New member
Hello everyone I am new to WRF. I have the following error in the REAL simulation.

Domain 1: Current date being processed: 2021-07-30_00:00:00.0000, which is loop # 9 out of 13
configflags%julyr, %julday, %gmt: 2021 211 0.00000000
d01 2021-07-30_00:00:00 Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.2
d01 2021-07-30_00:00:00 Input data is acceptable to use: met_em.d01.2021-07-30_00:00:00.nc
metgrid input_wrf.F first_date_input = 2021-07-30_00:00:00
metgrid input_wrf.F first_date_nml = 2021-07-28_00:00:00
d01 2021-07-30_00:00:00 input_wrf.F: SIZE MISMATCH: namelist num_metgrid_levels = 34
d01 2021-07-30_00:00:00 input_wrf.F: SIZE MISMATCH: input file BOTTOM-TOP_GRID_DIMENSION = 29
d01 2021-07-30_00:00:00 ---- ERROR: Mismatch between namelist and input file dimensions
NOTE: 1 namelist vs input data inconsistencies found.
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 1299
NOTE: Please check and reset these options
-------------------------------------------
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 1299
NOTE: Please check and reset these options

But my met_em* file has exactly 34 vertical levels, which I have specified in the namelist.input file.
Please, Request any help go overcome this problem
Thanks in advance

The namelist.input, namelist.wps are attached.
 

Attachments

  • namelist.input
    5.7 KB · Views: 39
  • namelist.wps
    1.8 KB · Views: 26
Hi,
Make sure to check the number of levels in each of your met_em* files and make sure you don't have any other lingering met_em* files in your running directory that the model is potentially viewing. If neither of those helps, please package your met_em files into a single *.tar file (not *.rar) and send it to me. It will likely be too large to attach here, so take a look at the homepage of this forum for instructions on sending large files. Thanks!
 
Hi kwerner, thanks for your answer.
I send attached the met_em files for your reference.
Thank you very much for your help
 

Attachments

  • archive.tar.gz
    44.3 MB · Views: 16
Thanks for sending those. I issued this command to check the number of levels in each met_em* file you sent.
Code:
ncdump -h met_em.d01.2021-07-28_00:00:00.nc | grep BOTTOM-TOP_GRID_DIMENSION
And they all give a value of 34, EXCEPT for the met_em.d01.2021-07-30_00:00:00.nc, which only has 29 levels.

I'm not sure why this happened, but you will need to go back to the WPS process and make sure your files are all complete.
 
Hi, thanks for your help
I have checked the WPS files and can't find the error.
According to what was found, in June 2019 there was a GFS update, and I don't know if this will be something similar
Please see the following link
https://forum.mmm.ucar.edu/phpBB3/viewtopic.php?f=94&t=5451

Regards
 
Hi,
I don't think that's the case. Are you using GFS data? If so, where are you obtaining it? I got GFS 0.25 degree data from the CISL RDA site and tested it. Every time period contains 34 vertical levels.
 
Hi sorry for the delay in answering you. Yes, I am using GFS Data.
I downloaded the fnl_20210730_00_00.grib2 file again and now it runs correctly.
I don't know why I downloaded the file wrong initially.
I greatly appreciate your help as it was possible to solve the problem :)
 
Top