Mismatch between namelist and input file dimensions

[wenli]

I am running WRF Elec V4.5 using FNL input data.
While running real.exe I am getting the error: "
d01 2020-07-08_00:00:00 input_wrf.F: SIZE MISMATCH: namelist num_metgrid_levels = 34
d01 2020-07-08_00:00:00 input_wrf.F: SIZE MISMATCH: input file BOTTOM-TOP_GRID_DIMENSION = 1
d01 2020-07-08_00:00:00 ---- ERROR: Mismatch between namelist and input file dimensions
"
I tried to rerun geogrid.exe, ungrid.exe and metgrid.exe, but also get the same error.
The namelist, rsl files are attached.
Thank you for your help!

 

[Ming Chen]

The error message "SIZE MISMATCH: input file BOTTOM-TOP_GRID_DIMENSION = 1" implies that your input data (i.e. met_em files) don't have upper level data. Please clarify where you downlaod FNL data and how you run WPS to process this data. I am suspicious that something went wrong when you run ungrib.

 

[wenli]

The error message "SIZE MISMATCH: input file BOTTOM-TOP_GRID_DIMENSION = 1" implies that your input data (i.e. met_em files) don't have upper level data. Please clarify where you downlaod FNL data and how you run WPS to process this data. I am suspicious that something went wrong when you run ungrib.

Thank you for your reply. FNL data was downloaded at this link: NCAR RDA Dataset d083002.
I run WPS using the commands in the attachment. It is strange to show this error because I successfully ran the same settings last time.
Looking forward to your reply.

 

[Ming Chen]

The site NCAR RDA Dataset d083002 is temporarily unavailable. I will take a look once it comes back.

Your WPS process looks fine. Would you please take a look at a single intermediate file, and figure out whether it includes upper level data?

 

[wenli]

The site NCAR RDA Dataset d083002 is temporarily unavailable. I will take a look once it comes back.

Your WPS process looks fine. Would you please take a look at a single intermediate file, and figure out whether it includes upper level data?

Did you refer to the met_em* files? I checked all the met_em* files, and found except the first met_em file, the other files all include upper level data.

 

[Ming Chen]

In this case, please rerun metgrid.exe to process only the first intermediate file, and reproduce the first met-em file. Please let me know whether the newly created met_em file for the initial time contains all upper-level data.

I expect that rerun metgrid.exe to process only the first-time intermediate file would give you a correct met-em data for the initial time. However, if this doesn't work, we need to check the intermediate file.

Please keep me updated about the result. Thanks.

 

[wenli]

In this case, please rerun metgrid.exe to process only the first intermediate file, and reproduce the first met-em file. Please let me know whether the newly created met_em file for the initial time contains all upper-level data.

I expect that rerun metgrid.exe to process only the first-time intermediate file would give you a correct met-em data for the initial time. However, if this doesn't work, we need to check the intermediate file.

Please keep me updated about the result. Thanks.

Thank you for your reply!
I rerun metgrid.exe to and get a new met_em file and it contains all 34 upper-level data.
But when I rerun metgrid.exe to get all met_em files, I got the mismatch error in "met_em.d01.2020-07-08_06_00_00.nc" and in it BOTTOM-TOP_GRID_DIMENSION = 13

 

[Ming Chen]

Please take a look at your intermediate files and let me know whether they have the same/similar size. You may simply issue the command:

ls -lrt FILE:* > log

If the intermediate files are correct (which I expect), then we need to check metgrid.exe.

By the way, did you run metgrid.exe in interactive mode, i.e., in your terminal with the command ./metgrid.exe?

 

[wenli]

请查看您的中间文件，并让我知道它们是否具有相同/相似的大小。您可以简单地发出以下命令：

ls -lrt 文件：* > log

如果中间文件是正确的（我所期望的），那么我们需要检查 metgrid.exe。

顺便说一句，您是否以交互模式运行metgrid.exe，即在终端中使用命令 ./metgrid.exe？

The 06 met_em file is smaller than others. I rerun it by sbatch the commands file to background. I will try to run it in interactive mode and update about the result. Will it cause different results? Why?

 

[Ming Chen]

This is a weird issue, which we have never seen before. I have no immediate answer to the question why metgrid.exe behaves this way ...

By re-running metgrid.exe over a specifc time period, I would expect that you can get the correct met_em file.