[Met_help] [rt.rap.ucar.edu #63530] History for How to name the forecast field when use netcdf as input in the point_stat step?
John Halley Gotway via RT
met_help at ucar.edu
Wed Oct 23 09:47:16 MDT 2013
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Dear Sir/Madam:
When i use the NETCDF format forecast files (from pcp_combine) as the input in the 'point_stat' step, the program failed to find the variable. I have tried two settings (see below, also the information of netcdf file). I have also followed the setting in the user's guide, but could not figure out how to set other fileds, such as threshold. I'm wondering how the 'point_stat' judge the input file format? Could you provide me a sample? The MET version i used is 4.1.
(1)
fcst = {
wind_thresh = [ NA ];
message_type = ["ADPSFC"];
field = [
{
name = "APCP_03";
level = [ "(*,*)" ];
cat_thresh = [ >=5.0, >=10.0, >=15.0, >=20.0, >=25.0, >=30.0 ];
}
];
};
obs = fcst;
DEBUG 1: User Config File: ./PointStatConfig_META03
ERROR :
ERROR : VarInfoGrib::set_dict() - unrecognized GRIB1 field abbreviation 'APCP_03' for table version 2
ERROR :
(2)
fcst = {
wind_thresh = [ NA ];
message_type = ["ADPSFC"];
field = [
{
name = "APCP";
level = [ "A03" ];
cat_thresh = [ >=5.0, >=10.0, >=15.0, >=20.0, >=25.0, >=30.0 ];
}
];
};
obs = fcst;
WARNING:
WARNING: process_fcst_climo_files() -> no fields matching APCPA03 found in file: /gpfs/home/forecast/china4km//t639/2013060100/rainprd/03h/2013060100f003_03h.nc
WARNING:
Here is the information of forecast files:
netcdf test {
dimensions:
lat = 1083 ;
lon = 1411 ;
variables:
float lat(lat, lon) ;
lat:long_name = "latitude" ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
float lon(lat, lon) ;
lon:long_name = "longitude" ;
lon:units = "degrees_east" ;
lon:standard_name = "longitude" ;
float APCP_03(lat, lon) ;
APCP_03:name = "APCP_03" ;
APCP_03:long_name = "Total precipitation" ;
APCP_03:level = "A3" ;
APCP_03:units = "kg/m^2" ;
APCP_03:_FillValue = -9999.f ;
APCP_03:init_time = "20130601_000000" ;
APCP_03:init_time_ut = 1370044800 ;
APCP_03:valid_time = "20130601_030000" ;
APCP_03:valid_time_ut = 1370055600 ;
APCP_03:accum_time = "030000" ;
APCP_03:accum_time_sec = 10800 ;
// global attributes:
:FileOrigins = "File /gpfs/home/forecast/china4km//t639/2013060100/rainprd/03h/2013060100f003_03h.nc generated 20131017_083627 UTC on host cxue07 by the MET pcp_combine tool" ;
:MET_version = "V4.1" ;
:MET_tool = "pcp_combine" ;
:RunCommand = "Addition: 1 files." ;
:Projection = "Lambert Conformal" ;
:scale_lat_1 = "35.000000" ;
:scale_lat_2 = "40.000000" ;
:lat_pin = "13.019000" ;
:lon_pin = "82.248000" ;
:x_pin = "0.000000" ;
:y_pin = "0.000000" ;
:lon_orient = "110.000000" ;
:d_km = "4.000000" ;
:r_km = "6371.200000" ;
:nx = "1411" ;
:ny = "1083 grid_points" ;
data:
Thanks!
Kefeng
kefeng at nju.edu.cn
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #63530] How to name the forecast field when use netcdf as input in the point_stat step?
From: John Halley Gotway
Time: Tue Oct 22 10:15:45 2013
Kefeng,
Your first setting looks correct to me:
name = "APCP_03";
level = [ "(*,*)" ];
But you're setting this for both for forecast and observation fields.
That won't work for the observation field in Point-Stat. By
convention, you must specify the point observations as if it was a
GRIB file. We've assigned a GRIB code to each point observation
value, and we use the GRIB conventions when specifying the observation
fields in Point-Stat. So your settings should look like this:
fcst = {
wind_thresh = [ NA ];
field = [
{
name = "APCP_03";
level = [ "(*,*)" ];
cat_thresh = [ >=5.0, >=10.0, >=15.0, >=20.0, >=25.0, >=30.0
];
}
];
};
obs = {
wind_thresh = [ NA ];
message_type = ["ADPSFC"];
field = [
{
name = "APCP";
level = [ "A03" ];
cat_thresh = [ >=5.0, >=10.0, >=15.0, >=20.0, >=25.0, >=30.0
];
}
];
};
Looking at the settings, you and I both know that a NetCDF variable
named "APCP_03" will likely contain 3-hour precipitation for GRIB code
61. But it's more difficult for the computer to know that.
So that's why we have users explicitly set the observation field using
the GRIB conventions.
Hope that helps clarify.
Thanks,
John Halley Gotway
met_help at ucar.edu
On 10/21/2013 08:44 PM, kefeng at nju.edu.cn via RT wrote:
>
> Mon Oct 21 20:44:47 2013: Request 63530 was acted upon.
> Transaction: Ticket created by kefeng at nju.edu.cn
> Queue: met_help
> Subject: How to name the forecast field when use netcdf as
input in the point_stat step?
> Owner: Nobody
> Requestors: kefeng at nju.edu.cn
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=63530 >
>
>
> Dear Sir/Madam:
>
> When i use the NETCDF format forecast files (from
pcp_combine) as the input in the 'point_stat' step, the program failed
to find the variable. I have tried two settings (see below, also the
information of netcdf file). I have also followed the setting in the
user's guide, but could not figure out how to set other fileds, such
as threshold. I'm wondering how the 'point_stat' judge the input file
format? Could you provide me a sample? The MET version i used is 4.1.
> (1)
> fcst = {
> wind_thresh = [ NA ];
> message_type = ["ADPSFC"];
>
> field = [
> {
> name = "APCP_03";
> level = [ "(*,*)" ];
> cat_thresh = [ >=5.0, >=10.0, >=15.0, >=20.0, >=25.0,
>=30.0 ];
> }
> ];
>
> };
> obs = fcst;
>
>
> DEBUG 1: User Config File: ./PointStatConfig_META03
> ERROR :
> ERROR : VarInfoGrib::set_dict() - unrecognized GRIB1 field
abbreviation 'APCP_03' for table version 2
> ERROR :
>
> (2)
> fcst = {
> wind_thresh = [ NA ];
> message_type = ["ADPSFC"];
>
> field = [
> {
> name = "APCP";
> level = [ "A03" ];
> cat_thresh = [ >=5.0, >=10.0, >=15.0, >=20.0, >=25.0,
>=30.0 ];
> }
> ];
>
> };
> obs = fcst;
>
> WARNING:
> WARNING: process_fcst_climo_files() -> no fields matching APCPA03
found in file:
/gpfs/home/forecast/china4km//t639/2013060100/rainprd/03h/2013060100f003_03h.nc
> WARNING:
>
>
> Here is the information of forecast files:
>
> netcdf test {
> dimensions:
> lat = 1083 ;
> lon = 1411 ;
> variables:
> float lat(lat, lon) ;
> lat:long_name = "latitude" ;
> lat:units = "degrees_north" ;
> lat:standard_name = "latitude" ;
> float lon(lat, lon) ;
> lon:long_name = "longitude" ;
> lon:units = "degrees_east" ;
> lon:standard_name = "longitude" ;
> float APCP_03(lat, lon) ;
> APCP_03:name = "APCP_03" ;
> APCP_03:long_name = "Total precipitation" ;
> APCP_03:level = "A3" ;
> APCP_03:units = "kg/m^2" ;
> APCP_03:_FillValue = -9999.f ;
> APCP_03:init_time = "20130601_000000" ;
> APCP_03:init_time_ut = 1370044800 ;
> APCP_03:valid_time = "20130601_030000" ;
> APCP_03:valid_time_ut = 1370055600 ;
> APCP_03:accum_time = "030000" ;
> APCP_03:accum_time_sec = 10800 ;
>
> // global attributes:
> :FileOrigins = "File
/gpfs/home/forecast/china4km//t639/2013060100/rainprd/03h/2013060100f003_03h.nc
generated 20131017_083627 UTC on host cxue07 by the MET pcp_combine
tool" ;
> :MET_version = "V4.1" ;
> :MET_tool = "pcp_combine" ;
> :RunCommand = "Addition: 1 files." ;
> :Projection = "Lambert Conformal" ;
> :scale_lat_1 = "35.000000" ;
> :scale_lat_2 = "40.000000" ;
> :lat_pin = "13.019000" ;
> :lon_pin = "82.248000" ;
> :x_pin = "0.000000" ;
> :y_pin = "0.000000" ;
> :lon_orient = "110.000000" ;
> :d_km = "4.000000" ;
> :r_km = "6371.200000" ;
> :nx = "1411" ;
> :ny = "1083 grid_points" ;
> data:
>
>
> Thanks!
>
>
> Kefeng
>
>
>
> kefeng at nju.edu.cn
>
------------------------------------------------
Subject: How to name the forecast field when use netcdf as input in the point_stat step?
From: kefeng at nju.edu.cn
Time: Tue Oct 22 20:25:45 2013
Thanks! John.
It works.
kefeng at nju.edu.cn
From: John Halley Gotway via RT
Date: 2013-10-23 00:15
To: kefeng
Subject: Re: [rt.rap.ucar.edu #63530] How to name the forecast field
when use netcdf as input in the point_stat step?
Kefeng,
Your first setting looks correct to me:
name = "APCP_03";
level = [ "(*,*)" ];
But you're setting this for both for forecast and observation fields.
That won't work for the observation field in Point-Stat. By
convention, you must specify the point observations as if it was a
GRIB file. We've assigned a GRIB code to each point observation
value, and we use the GRIB conventions when specifying the observation
fields in Point-Stat. So your settings should look like this:
fcst = {
wind_thresh = [ NA ];
field = [
{
name = "APCP_03";
level = [ "(*,*)" ];
cat_thresh = [ >=5.0, >=10.0, >=15.0, >=20.0, >=25.0, >=30.0
];
}
];
};
obs = {
wind_thresh = [ NA ];
message_type = ["ADPSFC"];
field = [
{
name = "APCP";
level = [ "A03" ];
cat_thresh = [ >=5.0, >=10.0, >=15.0, >=20.0, >=25.0, >=30.0
];
}
];
};
Looking at the settings, you and I both know that a NetCDF variable
named "APCP_03" will likely contain 3-hour precipitation for GRIB code
61. But it's more difficult for the computer to know that.
So that's why we have users explicitly set the observation field using
the GRIB conventions.
Hope that helps clarify.
Thanks,
John Halley Gotway
met_help at ucar.edu
On 10/21/2013 08:44 PM, kefeng at nju.edu.cn via RT wrote:
>
> Mon Oct 21 20:44:47 2013: Request 63530 was acted upon.
> Transaction: Ticket created by kefeng at nju.edu.cn
> Queue: met_help
> Subject: How to name the forecast field when use netcdf as
input in the point_stat step?
> Owner: Nobody
> Requestors: kefeng at nju.edu.cn
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=63530 >
>
>
> Dear Sir/Madam:
>
> When i use the NETCDF format forecast files (from
pcp_combine) as the input in the 'point_stat' step, the program failed
to find the variable. I have tried two settings (see below, also the
information of netcdf file). I have also followed the setting in the
user's guide, but could not figure out how to set other fileds, such
as threshold. I'm wondering how the 'point_stat' judge the input file
format? Could you provide me a sample? The MET version i used is 4.1.
> (1)
> fcst = {
> wind_thresh = [ NA ];
> message_type = ["ADPSFC"];
>
> field = [
> {
> name = "APCP_03";
> level = [ "(*,*)" ];
> cat_thresh = [ >=5.0, >=10.0, >=15.0, >=20.0, >=25.0,
>=30.0 ];
> }
> ];
>
> };
> obs = fcst;
>
>
> DEBUG 1: User Config File: ./PointStatConfig_META03
> ERROR :
> ERROR : VarInfoGrib::set_dict() - unrecognized GRIB1 field
abbreviation 'APCP_03' for table version 2
> ERROR :
>
> (2)
> fcst = {
> wind_thresh = [ NA ];
> message_type = ["ADPSFC"];
>
> field = [
> {
> name = "APCP";
> level = [ "A03" ];
> cat_thresh = [ >=5.0, >=10.0, >=15.0, >=20.0, >=25.0,
>=30.0 ];
> }
> ];
>
> };
> obs = fcst;
>
> WARNING:
> WARNING: process_fcst_climo_files() -> no fields matching APCPA03
found in file:
/gpfs/home/forecast/china4km//t639/2013060100/rainprd/03h/2013060100f003_03h.nc
> WARNING:
>
>
> Here is the information of forecast files:
>
> netcdf test {
> dimensions:
> lat = 1083 ;
> lon = 1411 ;
> variables:
> float lat(lat, lon) ;
> lat:long_name = "latitude" ;
> lat:units = "degrees_north" ;
> lat:standard_name = "latitude" ;
> float lon(lat, lon) ;
> lon:long_name = "longitude" ;
> lon:units = "degrees_east" ;
> lon:standard_name = "longitude" ;
> float APCP_03(lat, lon) ;
> APCP_03:name = "APCP_03" ;
> APCP_03:long_name = "Total precipitation" ;
> APCP_03:level = "A3" ;
> APCP_03:units = "kg/m^2" ;
> APCP_03:_FillValue = -9999.f ;
> APCP_03:init_time = "20130601_000000" ;
> APCP_03:init_time_ut = 1370044800 ;
> APCP_03:valid_time = "20130601_030000" ;
> APCP_03:valid_time_ut = 1370055600 ;
> APCP_03:accum_time = "030000" ;
> APCP_03:accum_time_sec = 10800 ;
>
> // global attributes:
> :FileOrigins = "File
/gpfs/home/forecast/china4km//t639/2013060100/rainprd/03h/2013060100f003_03h.nc
generated 20131017_083627 UTC on host cxue07 by the MET pcp_combine
tool" ;
> :MET_version = "V4.1" ;
> :MET_tool = "pcp_combine" ;
> :RunCommand = "Addition: 1 files." ;
> :Projection = "Lambert Conformal" ;
> :scale_lat_1 = "35.000000" ;
> :scale_lat_2 = "40.000000" ;
> :lat_pin = "13.019000" ;
> :lon_pin = "82.248000" ;
> :x_pin = "0.000000" ;
> :y_pin = "0.000000" ;
> :lon_orient = "110.000000" ;
> :d_km = "4.000000" ;
> :r_km = "6371.200000" ;
> :nx = "1411" ;
> :ny = "1083 grid_points" ;
> data:
>
>
> Thanks!
>
>
> Kefeng
>
>
>
> kefeng at nju.edu.cn
>
------------------------------------------------
More information about the Met_help
mailing list