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

metgrid error in ext_pkg_write_field

xshan2

New member
hello,

I am trying to run WPS. I've completed the geogrid.exe and ungrib.exe. However, when I try to run metgrid.exe, I got this error:
1663773017079.png

My WRF version is 4.4 so I don't understand why I get this error.

is there anyone can help me?

thanks!
 
hello,

I am trying to run WPS. I've completed the geogrid.exe and ungrib.exe. However, when I try to run metgrid.exe, I got this error:
View attachment 7208

My WRF version is 4.4 so I don't understand why I get this error.

is there anyone can help me?

thanks!
Can you provide your namelist.wps file?
 
What are the input data you ungribbed?
If the QC, QR, QI, and QS fields don't have the same number of vertical levels as other 3-d atmospheric fields (e.g., TT, UU, VV), this may lead to the error you're seeing. If this is the case, please try to modify metgrid.tbl as:

name=QC
mpas_name=qc
interp_option=four_pt+average_4pt
fill_missing=0.
fill_lev=200100:const(0.). # Delete this line
fill_lev=all:const(0); level_template=TT # Add this line
flag_in_output=FLAG_QC

Please let me know whether this fix your problem.
 
What are the input data you ungribbed?
If the QC, QR, QI, and QS fields don't have the same number of vertical levels as other 3-d atmospheric fields (e.g., TT, UU, VV), this may lead to the error you're seeing. If this is the case, please try to modify metgrid.tbl as:

name=QC
mpas_name=qc
interp_option=four_pt+average_4pt
fill_missing=0.
fill_lev=200100:const(0.). # Delete this line
fill_lev=all:const(0); level_template=TT # Add this line
flag_in_output=FLAG_QC

Please let me know whether this fix your problem.
Hello Thank you for your answer.

However I tried to open the METGRID.TBL but I can't. Could you tell me the way to modify it please?
 
This is one of the data I used in ungrib. It's in txt format. Hope this can help!
 

Attachments

  • pgrbanlens_1940020100.txt
    8.2 KB · Views: 24
Hi,
I looked at the file you sent that shows the content of the files "pgrbanlens_1940020100".
I am sorry to tell that this is not an appropriate data that can provide forcing for WRF. This is because it only have 2 or 3 pressure levels. It doesn't have all the variables required for running WRF (e.g., T, QV, RH, etc.)
Please look at this document that deescribes all the variables required for WPS/WRF:
 
Hi,
I looked at the file you sent that shows the content of the files "pgrbanlens_1940020100".
I am sorry to tell that this is not an appropriate data that can provide forcing for WRF. This is because it only have 2 or 3 pressure levels. It doesn't have all the variables required for running WRF (e.g., T, QV, RH, etc.)
Please look at this document that deescribes all the variables required for WPS/WRF:
Hi
Thank you for telling me this.
However I still have another dataset which might be worked. Could you check this for me please?
 

Attachments

  • sflxgrbens_fhr03_1940123118.txt
    43 KB · Views: 2
Hi,
This datafile only contains soil and surface information. Also, its meta data to describe the variable are vague and I can only 'guess' what they are. For example, the name of the variable PRES_98_SFC is pressure, and I think it is surface pressure.
Whatsoever, the data you have are not appropriate for running WRF.
Probably you can try to download some GFS data as your first try. NCAR CIS archives GFS data that are free for public download. Please look at this website:
 
Hi, I am using WRF-Version 4.2.2. I am using ERA5 data from ds633.0 as mentioned in WRF - Free Data.
I downloaded all the pressure level and surface level data.

I ran geogrid and ungrib successfully. But while running metgrid I am getting "ERROR: Error in ext_pkg_write_field" on the third day of simulation. Metgrid writes met_em* files for the first two days of simulation without any error. and on the third day after the second time step it throws the error every time.
I tried both Vtable.ECMWF and Vtable.ERA-interim_pl. But for both Vtables the error is same at the same time.
I am attaching metgrid log file and namelist.wps.

Looking forward to any kind of help.

Thank you
 

Attachments

  • metgrid.log
    1.2 MB · Views: 7
  • namelist.wps
    1.3 KB · Views: 9
Please make sure you have enough storage space to save the data.
If space is not an issue, then please look at your data that work and compare with the data that don't work. if metgrid.exe runs successfully for the first 2 days, it implies that both the code and the data of the first 2 days are fine. You just need to make sure that the data of the 3rd day are correct.
I am suspicious this is either a space issue or a data issue.
 
Dear Ming

I checked. Space is not an issue. I compared the data with the one that was working fine. Its exactly the same files for a different date. The file size, variables everything looks fine. I am not able to figure out the problem.
Looking forward to any kind of help.
 

Attachments

  • metgrid.log
    1.3 MB · Views: 11
  • namelist.wps
    1.3 KB · Views: 6
If storage space is not an issue, then something must be wrong with the data.
Can you check your data of the 3rd day, specifically, please pay attention to the levels of all data. They must be on the same vertical levels and have the same number of vertical levels. This includes both soil data and upper air data.
 
Yes it was a downloading error. Some data were missing even though the number of files were same. I freshly downloaded the data. Now its running fine.
Thank you for pointing out the error possibilities.

Regards
Anie
 
Dear @Ming Chen,
I am also having the same error after running metgrid.exe. In my case too, geogrid.exe and ungrib.exe ran successfully. Earlier, I did the simulations for other works, and every time metgrid.exe ran successfully. But I don't know why this time I am getting this error. I want to mention the following points, which I didn't see before, but this time I am facing them:. They are:
(1) During ungrib.exe, I saw the following lines, which were printed before showing " ! Successful completion of ungrib. !"
-------------------------------------------------------------------------------
Name of source model =>NCEP GFS Analysis GRID 3
Interpolating to fill in UU at level 40.00 hPa using levels 50.00 hPa and 30.00 hPa
Interpolating to fill in UU at level 15.00 hPa using levels 20.00 hPa and 10.00 hPa
Interpolating to fill in VV at level 40.00 hPa using levels 50.00 hPa and 30.00 hPa
Interpolating to fill in VV at level 15.00 hPa using levels 20.00 hPa and 10.00 hPa
Interpolating to fill in RH at level 40.00 hPa using levels 50.00 hPa and 30.00 hPa
Interpolating to fill in RH at level 15.00 hPa using levels 20.00 hPa and 10.00 hPa


###############################################################################
(2) In the metgrid.log file, the following lines are printed at the end:

2024-03-05 00:56:15.231 --- INFORM: Couldn't find SW100200 at level 200100.000000 to fill level 4.000000 of SW.
2024-03-05 00:56:15.231 --- INFORM: Couldn't find SW000010 at level 200100.000000 to fill level 1.000000 of SW.
2024-03-05 00:56:15.231 --- INFORM: Couldn't find SW010200 at level 200100.000000 to fill level 2.000000 of SW.
2024-03-05 00:56:15.231 --- INFORM: Going to create the field SOIL_LAYERS
2024-03-05 00:56:15.232 --- INFORM: Going to create the field SOILM
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILM000 at level 200100.000000 to fill level 0.000000 of SOILM.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILM005 at level 200100.000000 to fill level 5.000000 of SOILM.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILM020 at level 200100.000000 to fill level 20.000000 of SOILM.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILM040 at level 200100.000000 to fill level 40.000000 of SOILM.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILM160 at level 200100.000000 to fill level 160.000000 of SOILM.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILM300 at level 200100.000000 to fill level 300.000000 of SOILM.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILM001 at level 200100.000000 to fill level 1.000000 of SOILM.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILM004 at level 200100.000000 to fill level 4.000000 of SOILM.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILM010 at level 200100.000000 to fill level 10.000000 of SOILM.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILM030 at level 200100.000000 to fill level 30.000000 of SOILM.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILM060 at level 200100.000000 to fill level 60.000000 of SOILM.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILM100 at level 200100.000000 to fill level 100.000000 of SOILM.
2024-03-05 00:56:15.232 --- INFORM: Going to create the field SOILT
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILT000 at level 200100.000000 to fill level 0.000000 of SOILT.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILT005 at level 200100.000000 to fill level 5.000000 of SOILT.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILT020 at level 200100.000000 to fill level 20.000000 of SOILT.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILT040 at level 200100.000000 to fill level 40.000000 of SOILT.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILT160 at level 200100.000000 to fill level 160.000000 of SOILT.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILT300 at level 200100.000000 to fill level 300.000000 of SOILT.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILT050 at level 200100.000000 to fill level 49.000000 of SOILT.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILT050 at level 200100.000000 to fill level 51.000000 of SOILT.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILT001 at level 200100.000000 to fill level 1.000000 of SOILT.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILT004 at level 200100.000000 to fill level 4.000000 of SOILT.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILT010 at level 200100.000000 to fill level 10.000000 of SOILT.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILT030 at level 200100.000000 to fill level 30.000000 of SOILT.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILT060 at level 200100.000000 to fill level 60.000000 of SOILT.
2024-03-05 00:56:15.232 --- INFORM: Couldn't find SOILT100 at level 200100.000000 to fill level 100.000000 of SOILT.
2024-03-05 00:56:15.232 --- INFORM: Going to create the field SOIL_LEVELS
2024-03-05 00:56:15.232 --- INFORM: Going to create the field PRES
2024-03-05 00:56:15.241 --- INFORM: PRES at level 200100.000000 already exists; leaving it alone.
2024-03-05 00:56:15.282 --- INFORM: Field LANDSEA.mask does not have a valid mask and will not be checked for missing values
2024-03-05 00:56:15.327 --- Initializing output module.
2024-03-05 00:56:15.330 --- ERROR: Error in ext_pkg_write_field

For your convenience, I am also attaching the metgrid.log file. Can you please help me to solve this issue? Do I have to change the 'METGRID.TBL' file? Any help will be greatly appreciated. I am really looking forward to hearing from you. Thank you for your time and consideration.
With regards,
Ankan
 

Attachments

  • metgrid.log
    26.3 KB · Views: 1
Top