unrecognized GRIB1 field abbreviation 'APCP_24' #2640
-
[Update: I tried to change the variable name of the netCDF file from APCP_24 to APCP and I get the following error: The netCDF file I'm using is an output of the PCP Combine tool Now, I used the CF Compliance Checker and here are the details: CHECKING NetCDF FILE: /tmp/tmpz0ixo91o.ncUsing CF Checker Version 4.1.0 WARN: (2.6.1): No 'Conventions' attribute present Checking variable: latChecking variable: lonChecking variable: APCPERRORS detected: 0 ] Hello I am currently working on verifying the WRF output using point synoptic data using the Point Stat of the METplus. When I am trying to use Point Stat, I get the following error: (ai4rp) erdanx@erdanx:~/ai4rp$ point_stat ${METPLUS_DATA}/fcst/WRFrr24h.nc ${METPLUS_DATA}/obs/synoprr24hFmtd/nc/2021/synoprr24h202112010000.nc /home/erdanx/ai4rp/user_config/PointStatConfig -outdir /home/erdanx/ai4rp/output/pointStat -v 2 I have used the PCP Combine for my WRF data and I have used the ASCII2NC tool for my point observation data. Here are some information for my WRF data: And here are some information for my point observation data: Here are some information about my Point Stat config: // // //////////////////////////////////////////////////////////////////////////////// // //////////////////////////////////////////////////////////////////////////////// // // } //////////////////////////////////////////////////////////////////////////////// // // //////////////////////////////////////////////////////////////////////////////// // file_name = []; regrid = { time_interp_method = DW_MEAN; climo_stdev = climo_mean; // //////////////////////////////////////////////////////////////////////////////// // // //////////////////////////////////////////////////////////////////////////////// // //////////////////////////////////////////////////////////////////////////////// // //////////////////////////////////////////////////////////////////////////////// // boot = { //////////////////////////////////////////////////////////////////////////////// // type = [ //////////////////////////////////////////////////////////////////////////////// // //////////////////////////////////////////////////////////////////////////////// // //////////////////////////////////////////////////////////////////////////////// // //////////////////////////////////////////////////////////////////////////////// tmp_dir = "/tmp"; //////////////////////////////////////////////////////////////////////////////// |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Hello, And thank you for your question. I think the fix for this problem may be in how you are calling the forecast field level. As you stated, you've already successfully used the PCP-Combine tool on your WRF file; this means that the input file is a netCDF. But in your forecast dictionary's level setting you're using
When using a netCDF file, you must use the proper level notation for the file type. For netCDFs, this is parentheses, along with the indicies for each array of data. Since APCP_24 is defined by
Note that the asterisks are used to convey to MET that you would like all values associated with each array of data (as opposed to an individual row, column, or value). You can read more about the netCDF settings available from the forecast or observation dictionaries in the MET User's Guide (scroll down from this link to the "NetCDF (from MET tools, CF-compliant, p_interp, and wrf_interp):" bullet). I'd also caution that as you currently have your configuration file set, your observation dictionary values (variable name, levels, thresholding, etc.) will be a copy of your forecast dictionary values, but you are passing in a different observation file from your forecast file:
You will need to create a observation dictionary that has its own field information, including the appropriate variable name and level information, that matches the contents of your ASCII2NC output file. |
Beta Was this translation helpful? Give feedback.
-
Hello, I wanted to reach out again to see if the suggestion helped you through your issue. If it has, please select the comment as an answer and I'll go ahead and lock the Discussion. |
Beta Was this translation helpful? Give feedback.
Hello,
And thank you for your question. I think the fix for this problem may be in how you are calling the forecast field level.
As you stated, you've already successfully used the PCP-Combine tool on your WRF file; this means that the input file is a netCDF. But in your forecast dictionary's level setting you're using
When using a netCDF file, you must use the proper level notation for the file type. For netCDFs, this is parentheses, along with the indicies for each array of data. Since APCP_24 is defined by
(lat,lon)
, the correct notation would beNote that the asteris…