Cannot support split netcdf option for real.exe

[jianglizhi]

Hello,
I had created the met_em.nc_nnnn files successfully, with the option io_form_geogrid=102 and io_form_metgrid=102
Then, I tried to running the real.exe with the namelist.wps option "io_form_input =102".
However, the program stop with the error:
"FATAL CALLED FROM FILE: <stdin> LINE: 409 error opening met_em.d01.2023-07-27_12:00:00.nc for input; bad date in namelist or file not in director"

It seems that the "io_form_input" did not make sense. The real.exe program seems still try to find the met_em.d01.*.nc
can anyone help how to solve it? Thanks in advance.

Version: WRF 4.6.0

namelist.input

namelist.output

rsl.out.0000

Update: after searching in the wrfforum. I find the problems may similar as this expcet for a newer verson of WRFV4.6.0 :

error running real.exe​

error running real.exe

 

[jianglizhi]

Update:
I just read a related posts. I think my problems are the same.
It need to add io_form_auxinput1 for reading split met_em files.
Using Split met_em Files With real.exe

I will try it again and update later.

 

[Ming Chen]

Please try the option io_form_auxinput1 = 102, and let me know whether it works for your case. Thanks in advance.

 

[jianglizhi]

Thank you for the reply. I had set the option io_form_auxinput1 = 102. The real.exe can read the file, however, another problem occurs:
it saids "Mismatch between namelist and wrf input files for dimension NUM_LAND_CAT"

Domain 1: Current date being processed: 2023-07-27_12:00:00.0000, which is loop # 1 out of 43
configflags%julyr, %julday, %gmt: 2023 208 12.00000
d01 2023-07-27_12:00:00 Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.5
d01 2023-07-27_12:00:00 Input data is acceptable to use:
metgrid input_wrf.F first_date_input = 2023-07-27_12:00:00
metgrid input_wrf.F first_date_nml = 2023-07-27_12:00:00
----------------- ERROR -------------------
namelist : NUM_LAND_CAT = 21
input files : NUM_LAND_CAT = 20 (from geogrid selections).
d01 2023-07-27_12:00:00 ---- ERROR: Mismatch between namelist and wrf input files for dimension NUM_LAND_CAT
NOTE: 1 namelist vs input data inconsistencies found.
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 1307
NOTE: Please check and reset these options
-------------------------------------------

Then, I referred the posts below:

Mismatch between namelist and wrf input files for dimension NUM_LAND_CAT

Hi! I am a student starting to learn wrf, and I'm running an example to learn the whole process of WRF. However I met some problems that I do not know how to deal with. Could you please give me some help? I have successfully preprocessed the data through WPS, and added chem、bio and anthro...

forum.mmm.ucar.edu

considering the kwerner's reply, I had checked the met_em.d01.nc_nxxx files. so I entered these commands:

[lzjiang@schooner3 wrf_test3]$ ls wps/met_em.d01.2023-07-2* |awk '{print "ncdump -h "$0"|grep -i num_land_cat"}' >filelist.txt
[lzjiang@schooner3 wrf_test3]$ ls wps/met_em.d01.2023-07-2* |awk '{print "ncdump -h "$0"|grep -i num_land_cat"}'|bash > filelist_result.txt

The first line is to list the filenames of all splited met_em files by the program of metgrid.exe. Both files are uploaded below.
The second lines is to get the "num_land_cat" in each splited met_em files.
The results shows that only the first part of file for each timestep (ie. file with ".nc_0000" suffix) held the value num_land_cat=21, the value of num_land_cat for the rest part of splited met_em files each timestep are 0.
I don't know whether there is OK for the splited netcdf files. But I thought the error may not cause from the splited netcdf files.


Additional Information:
the dirven data: GFS-0.25degreex0.25degree hourly, downloaded from AWS cloud.

https://noaa-gfs-bdp-pds.s3.amazonaws.com/index.html#gfs.20230727/00/atmos/

 

[jianglizhi]

Please try the option io_form_auxinput1 = 102, and let me know whether it works for your case. Thanks in advance.

Update: after searching again, I had find the same problem pratially fixed by segfault.

pnetCDF capability for WPS

Hi all, I have a very large domain with 5000x5000 grid points and want to create met_em files using ECMWF IFS input data with a large number of vertical levels making things even more difficult... Creating met_em files works but takes a lot of I/O time with io_form_metgrid = 2 writing out...

forum.mmm.ucar.edu

I think this bug occurs not alone for me, actually It occurs so many times.

Mismatch between namelist and wrf input files for dimension NUM_LAND_CAT

Hi I am trying to incorporate the CORINE land use map into my WRF runs and I encountered a problem. I am getting an error ----------------- ERROR ------------------- namelist : NUM_LAND_CAT = 44 input files : NUM_LAND_CAT = 45 (from geogrid selections). d01...

forum.mmm.ucar.edu

It should be the WPS program bug.

 

[Ming Chen]

The error message 'mismatch between namelist and wrf inpout ...' is caused by different number of landuse type in met-em and that specified in your namelist.input.

Can you find the value of NUM_LAND_CAT in your met-em file, and set the same value in namelist.input, then try again?

 

[jianglizhi]

The error message 'mismatch between namelist and wrf inpout ...' is caused by different number of landuse type in met-em and that specified in your namelist.input.

Can you find the value of NUM_LAND_CAT in your met-em file, and set the same value in namelist.input, then try again?

Hello Dr Chen,
I had already checked the NUM_LAND_CAT value for the met-em file in the previous reply Cannot support split netcdf option for real.exe
The results shows that, for the met-em files of each time step, only the first splitted met_em file (eg. met_em.d01.2023-07-27_12:00:00.nc_0000) had the correct value of NUM_LAND_CAT, while for other splited met_em files (eg. met_em.d01.2023-07-27_12:00:00.nc_0001, met_em.d01.2023-07-27_12:00:00.nc_0002,..., met_em.d01.2023-07-27_12:00:00.nc_0047) the values of NUM_LAND_CAT are all ZERO.
You can check this two files (filelist.txt, filelist_result.txt) in my previous reply, Thank you!

Thank you for the reply. I had set the option io_form_auxinput1 = 102. The real.exe can read the file, however, another problem occurs:
it saids "Mismatch between namelist and wrf input files for dimension NUM_LAND_CAT"

Then, I referred the posts below:

Mismatch between namelist and wrf input files for dimension NUM_LAND_CAT

Hi! I am a student starting to learn wrf, and I'm running an example to learn the whole process of WRF. However I met some problems that I do not know how to deal with. Could you please give me some help? I have successfully preprocessed the data through WPS, and added chem、bio and anthro...

forum.mmm.ucar.edu

considering the kwerner's reply, I had checked the met_em.d01.nc_nxxx files. so I entered these commands:

The first line is to list the filenames of all splited met_em files by the program of metgrid.exe. Both files are uploaded below.
The second lines is to get the "num_land_cat" in each splited met_em files.
The results shows that only the first part of file for each timestep (ie. file with ".nc_0000" suffix) held the value num_land_cat=21, the value of num_land_cat for the rest part of splited met_em files each timestep are 0.
I don't know whether there is OK for the splited netcdf files. But I thought the error may not cause from the splited netcdf files.


Additional Information:
the dirven data: GFS-0.25degreex0.25degree hourly, downloaded from AWS cloud.

https://noaa-gfs-bdp-pds.s3.amazonaws.com/index.html#gfs.20230727/00/atmos/

 

[Ming Chen]

This issue could possibly be attributed to bugs in WPS when running with the option io_form_metgrid = 102

Please avoid using this option at present.