[Met_help] [rt.rap.ucar.edu #89691] History for Climo Erro - Bad Type
John Halley Gotway via RT
met_help at ucar.edu
Tue Jul 9 12:06:51 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
John or Julie, I sent relevant data file to you using AMRDEC_Safe. This is a continuation of problem report #85052. When I run grid stat using a total cloud climo file, I get Bad Type error - see below:
INFO - MET command file executing ['/h/WXQC/met-8.1_beta1/bin/grid_stat', '/h/data/global/ENSEMBLE/data/post/GEPS/global/2019031400/grib2.2019031400.0042.EPOSTOUT', '/h/data/global/WXQC/data/met/nc_obs/wwmca/201903151800_p5.nc', '/h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated', '-outdir', '/h/data/global/WXQC/data/met/gdstat/mdlob_pairs/geps/TC', '-v', '4']
DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES file: /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file: /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
DEBUG 1: Default Config File: /h/WXQC/met-8.1_beta1/share/met/config/GridStatConfig_default
DEBUG 1: User Config File: /h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated
DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new Met2dDataFile object of type "FileType_Gb2".
DEBUG 4: Switching the GRIB2 radius of the earth value of 6367.47 km to 6371.2 km for internal consistency.
DEBUG 4:
DEBUG 4: Latitude/Longitude Grid Data:
DEBUG 4: lat_ll: -90
DEBUG 4: lon_ll: -0
DEBUG 4: delta_lat: 0.5
DEBUG 4: delta_lon: 0.5
DEBUG 4: Nlat: 361
DEBUG 4: Nlon: 720
DEBUG 4:
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2 field indexes - disc: 0, master table: 1, center: 57, local table: 1, parm_cat: 1, parm: 221
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2 field indexes - disc: 0, master table: 1, center: 57, local table: 1, parm_cat: 1, parm: 225
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2 field indexes - disc: 0, master table: 1, center: 57, local table: 1, parm_cat: 1, parm: 227
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2 field indexes - disc: 0, master table: 1, center: 57, local table: 1, parm_cat: 17, parm: 192
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2 field indexes - disc: 0, master table: 1, center: 57, local table: 1, parm_cat: 19, parm: 241
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2 field indexes - disc: 0, master table: 1, center: 57, local table: 1, parm_cat: 19, parm: 242
DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new Met2dDataFile object of type "FileType_NcMet".
DEBUG 4:
DEBUG 4: Latitude/Longitude Grid Data:
DEBUG 4: lat_ll: -90
DEBUG 4: lon_ll: -0
DEBUG 4: delta_lat: 0.5
DEBUG 4: delta_lon: 0.5
DEBUG 4: Nlat: 361
DEBUG 4: Nlon: 720
DEBUG 4:
ERROR :
ERROR : DictionaryEntry::dict_value() -> bad type
ERROR :
I edited the climo file per the instructions from John in problem report #85052 plus I added a valid time to the header but still can't get MET to properly read the file. I can plot the file in plot_data_plane but I gives a valid time error. So, what is missing from this netCDF file the MET wants? A more general suggestion is to provide an addendum to the user guide on what MET requires to be in netCDF climo files since these files are available from many different sources.
Thanks
Bob
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Climo Erro - Bad Type
From: John Halley Gotway
Time: Thu Apr 25 15:17:55 2019
Bob,
The config file error is coming from parsing the climo_mean section:
ERROR : DictionaryEntry::dict_value() -> bad type
Specifically, you set:
field = ["fmcf0020","fmcf8100"];
Instead, "field" should be an array of dictionaries, like it is in the
rest
of the config file:
field = [ { name = "fmcf0020"; level = "(*,*)"; },
{ name = "fmcf8100"; level = "(*,*)"; } ];
And the number of climo_mean.field entries must match the number of
fcst.field entries.
At debug level 3 (using met-8.0), I see this status message:
*DEBUG 3: Skipping climatology field since "match_month" is TRUE but
the
forecast (20190316_060000) and climatology (19700101_000000) months do
not
match for file: porclds_03_6z_fmcf8100.nc
<http://porclds_03_6z_fmcf8100.nc>*
The problem is the format of that NetCDF file. It doesn't follow a
known
convention, and MET is unable to parse the timing information from it.
Do you have any control over the format of that file?
Thanks,
John
On Thu, Apr 11, 2019 at 1:17 PM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> Thu Apr 11 13:13:18 2019: Request 89691 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
> Queue: met_help
> Subject: Climo Erro - Bad Type
> Owner: Nobody
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89691 >
>
>
> John or Julie, I sent relevant data file to you using AMRDEC_Safe.
This
> is a continuation of problem report #85052. When I run grid stat
using a
> total cloud climo file, I get Bad Type error - see below:
>
> INFO - MET command file executing ['/h/WXQC/met-
8.1_beta1/bin/grid_stat',
>
'/h/data/global/ENSEMBLE/data/post/GEPS/global/2019031400/grib2.2019031400.0042.EPOSTOUT',
> '/h/data/global/WXQC/data/met/nc_obs/wwmca/201903151800_p5.nc',
> '/h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated', '-
outdir',
> '/h/data/global/WXQC/data/met/gdstat/mdlob_pairs/geps/TC', '-v',
'4']
> DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES file:
> /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
> DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
> /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
> DEBUG 1: Default Config File:
> /h/WXQC/met-8.1_beta1/share/met/config/GridStatConfig_default
> DEBUG 1: User Config File:
> /h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_Gb2".
> DEBUG 4: Switching the GRIB2 radius of the earth value of 6367.47 km
to
> 6371.2 km for internal consistency.
> DEBUG 4:
> DEBUG 4: Latitude/Longitude Grid Data:
> DEBUG 4: lat_ll: -90
> DEBUG 4: lon_ll: -0
> DEBUG 4: delta_lat: 0.5
> DEBUG 4: delta_lon: 0.5
> DEBUG 4: Nlat: 361
> DEBUG 4: Nlon: 720
> DEBUG 4:
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 1, center: 57, local table:
1,
> parm_cat: 1, parm: 221
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 1, center: 57, local table:
1,
> parm_cat: 1, parm: 225
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 1, center: 57, local table:
1,
> parm_cat: 1, parm: 227
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 1, center: 57, local table:
1,
> parm_cat: 17, parm: 192
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 1, center: 57, local table:
1,
> parm_cat: 19, parm: 241
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 1, center: 57, local table:
1,
> parm_cat: 19, parm: 242
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_NcMet".
> DEBUG 4:
> DEBUG 4: Latitude/Longitude Grid Data:
> DEBUG 4: lat_ll: -90
> DEBUG 4: lon_ll: -0
> DEBUG 4: delta_lat: 0.5
> DEBUG 4: delta_lon: 0.5
> DEBUG 4: Nlat: 361
> DEBUG 4: Nlon: 720
> DEBUG 4:
> ERROR :
> ERROR : DictionaryEntry::dict_value() -> bad type
> ERROR :
>
> I edited the climo file per the instructions from John in problem
report
> #85052 plus I added a valid time to the header but still can't get
MET to
> properly read the file. I can plot the file in plot_data_plane but
I gives
> a valid time error. So, what is missing from this netCDF file the
MET
> wants? A more general suggestion is to provide an addendum to the
user
> guide on what MET requires to be in netCDF climo files since these
files
> are available from many different sources.
>
> Thanks
> Bob
>
>
------------------------------------------------
Subject: Climo Erro - Bad Type
From: John Halley Gotway
Time: Fri Apr 26 06:23:33 2019
> Bob,
>
> The config file error is coming from parsing the climo_mean section:
> ERROR : DictionaryEntry::dict_value() -> bad type
>
> Specifically, you set:
> field = ["fmcf0020","fmcf8100"];
>
> Instead, "field" should be an array of dictionaries, like it is in
the
> rest of the config file:
> field = [ { name = "fmcf0020"; level = "(*,*)"; },
> { name = "fmcf8100"; level = "(*,*)"; } ];
>
> And the number of climo_mean.field entries must match the number of
> fcst.field entries.
>
> At debug level 3 (using met-8.0), I see this status message:
> *DEBUG 3: Skipping climatology field since "match_month" is TRUE but
the
> forecast (20190316_060000) and climatology (19700101_000000) months
do not
> match for file: porclds_03_6z_fmcf8100.nc
> <http://porclds_03_6z_fmcf8100.nc>*
>
> The problem is the format of that NetCDF file. It doesn't follow a
known
> convention, and MET is unable to parse the timing information from
it.
>
> Do you have any control over the format of that file?
>
> Thanks,
> John
>
>
>
>
> On Thu, Apr 11, 2019 at 1:17 PM robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
>>
>> Thu Apr 11 13:13:18 2019: Request 89691 was acted upon.
>> Transaction: Ticket created by robert.craig.2 at us.af.mil
>> Queue: met_help
>> Subject: Climo Erro - Bad Type
>> Owner: Nobody
>> Requestors: robert.craig.2 at us.af.mil
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89691 >
>>
>>
>> John or Julie, I sent relevant data file to you using AMRDEC_Safe.
This
>> is a continuation of problem report #85052. When I run grid stat
using a
>> total cloud climo file, I get Bad Type error - see below:
>>
>> INFO - MET command file executing ['/h/WXQC/met-
8.1_beta1/bin/grid_stat',
>>
'/h/data/global/ENSEMBLE/data/post/GEPS/global/2019031400/grib2.2019031400.0042.EPOSTOUT',
>> '/h/data/global/WXQC/data/met/nc_obs/wwmca/201903151800_p5.nc',
>> '/h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated', '-
outdir',
>> '/h/data/global/WXQC/data/met/gdstat/mdlob_pairs/geps/TC', '-v',
'4']
>> DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES file:
>> /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
>> DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
>> /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
>> DEBUG 1: Default Config File:
>> /h/WXQC/met-8.1_beta1/share/met/config/GridStatConfig_default
>> DEBUG 1: User Config File:
>> /h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated
>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
>> Met2dDataFile object of type "FileType_Gb2".
>> DEBUG 4: Switching the GRIB2 radius of the earth value of 6367.47
km to
>> 6371.2 km for internal consistency.
>> DEBUG 4:
>> DEBUG 4: Latitude/Longitude Grid Data:
>> DEBUG 4: lat_ll: -90
>> DEBUG 4: lon_ll: -0
>> DEBUG 4: delta_lat: 0.5
>> DEBUG 4: delta_lon: 0.5
>> DEBUG 4: Nlat: 361
>> DEBUG 4: Nlon: 720
>> DEBUG 4:
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 1, center: 57, local table:
1,
>> parm_cat: 1, parm: 221
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 1, center: 57, local table:
1,
>> parm_cat: 1, parm: 225
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 1, center: 57, local table:
1,
>> parm_cat: 1, parm: 227
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 1, center: 57, local table:
1,
>> parm_cat: 17, parm: 192
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 1, center: 57, local table:
1,
>> parm_cat: 19, parm: 241
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 1, center: 57, local table:
1,
>> parm_cat: 19, parm: 242
>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
>> Met2dDataFile object of type "FileType_NcMet".
>> DEBUG 4:
>> DEBUG 4: Latitude/Longitude Grid Data:
>> DEBUG 4: lat_ll: -90
>> DEBUG 4: lon_ll: -0
>> DEBUG 4: delta_lat: 0.5
>> DEBUG 4: delta_lon: 0.5
>> DEBUG 4: Nlat: 361
>> DEBUG 4: Nlon: 720
>> DEBUG 4:
>> ERROR :
>> ERROR : DictionaryEntry::dict_value() -> bad type
>> ERROR :
>>
>> I edited the climo file per the instructions from John in problem
report
>> #85052 plus I added a valid time to the header but still can't get
MET to
>> properly read the file. I can plot the file in plot_data_plane but
I gives
>> a valid time error. So, what is missing from this netCDF file the
MET
>> wants? A more general suggestion is to provide an addendum to the
user
>> guide on what MET requires to be in netCDF climo files since these
files
>> are available from many different sources.
>>
>> Thanks
>> Bob
>>
>>
------------------------------------------------
Subject: FW: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo Erro - Bad Type
From: robert.craig.2 at us.af.mil
Time: Fri Apr 26 10:13:39 2019
John, per my previous email, what does MET need in the header to
figure out the valid time. I added a valid time value but that was
not enough. I notice in other netcdf files there is a init_time and
init_time_ut as well as valid_time and valid_time_ut. Does MET care
about the ut fields and if so how should they be set?
Thanks
Bob
-----Original Message-----
From: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
Sent: Friday, April 26, 2019 9:22 AM
To: 'met_help at ucar.edu' <met_help at ucar.edu>
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo Erro
- Bad Type
John, I should have got the dictionary issue and the mismatch of
dates. Is the problem with the climo files something lacking or wrong
in the header? I can modify the headers if I know what they need to
be set too. I could also read the climo files into memory and then to
write them back out in the proper netcdf format if I know what MET is
looking for.
-----Original Message-----
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Friday, April 26, 2019 7:24 AM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo Erro -
Bad Type
> Bob,
>
> The config file error is coming from parsing the climo_mean section:
> ERROR : DictionaryEntry::dict_value() -> bad type
>
> Specifically, you set:
> field = ["fmcf0020","fmcf8100"];
>
> Instead, "field" should be an array of dictionaries, like it is in
the
> rest of the config file:
> field = [ { name = "fmcf0020"; level = "(*,*)"; },
> { name = "fmcf8100"; level = "(*,*)"; } ];
>
> And the number of climo_mean.field entries must match the number of
> fcst.field entries.
>
> At debug level 3 (using met-8.0), I see this status message:
> *DEBUG 3: Skipping climatology field since "match_month" is TRUE but
> the forecast (20190316_060000) and climatology (19700101_000000)
> months do not match for file: porclds_03_6z_fmcf8100.nc
> <http://porclds_03_6z_fmcf8100.nc>*
>
> The problem is the format of that NetCDF file. It doesn't follow a
> known convention, and MET is unable to parse the timing information
from it.
>
> Do you have any control over the format of that file?
>
> Thanks,
> John
>
>
>
>
> On Thu, Apr 11, 2019 at 1:17 PM robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
>>
>> Thu Apr 11 13:13:18 2019: Request 89691 was acted upon.
>> Transaction: Ticket created by robert.craig.2 at us.af.mil
>> Queue: met_help
>> Subject: Climo Erro - Bad Type
>> Owner: Nobody
>> Requestors: robert.craig.2 at us.af.mil
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89691
>> >
>>
>>
>> John or Julie, I sent relevant data file to you using AMRDEC_Safe.
>> This is a continuation of problem report #85052. When I run grid
>> stat using a total cloud climo file, I get Bad Type error - see
below:
>>
>> INFO - MET command file executing
>> ['/h/WXQC/met-8.1_beta1/bin/grid_stat',
>>
'/h/data/global/ENSEMBLE/data/post/GEPS/global/2019031400/grib2.20190
>> 31400.0042.EPOSTOUT',
>> '/h/data/global/WXQC/data/met/nc_obs/wwmca/201903151800_p5.nc',
>> '/h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated',
>> '-outdir',
'/h/data/global/WXQC/data/met/gdstat/mdlob_pairs/geps/TC',
>> '-v', '4'] DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES
file:
>> /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
>> DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
>> /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
>> DEBUG 1: Default Config File:
>> /h/WXQC/met-8.1_beta1/share/met/config/GridStatConfig_default
>> DEBUG 1: User Config File:
>> /h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated
>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
>> Met2dDataFile object of type "FileType_Gb2".
>> DEBUG 4: Switching the GRIB2 radius of the earth value of 6367.47
km
>> to
>> 6371.2 km for internal consistency.
>> DEBUG 4:
>> DEBUG 4: Latitude/Longitude Grid Data:
>> DEBUG 4: lat_ll: -90
>> DEBUG 4: lon_ll: -0
>> DEBUG 4: delta_lat: 0.5
>> DEBUG 4: delta_lon: 0.5
>> DEBUG 4: Nlat: 361
>> DEBUG 4: Nlon: 720
>> DEBUG 4:
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
>> table: 1,
>> parm_cat: 1, parm: 221
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
>> table: 1,
>> parm_cat: 1, parm: 225
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
>> table: 1,
>> parm_cat: 1, parm: 227
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
>> table: 1,
>> parm_cat: 17, parm: 192
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
>> table: 1,
>> parm_cat: 19, parm: 241
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
>> table: 1,
>> parm_cat: 19, parm: 242
>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
>> Met2dDataFile object of type "FileType_NcMet".
>> DEBUG 4:
>> DEBUG 4: Latitude/Longitude Grid Data:
>> DEBUG 4: lat_ll: -90
>> DEBUG 4: lon_ll: -0
>> DEBUG 4: delta_lat: 0.5
>> DEBUG 4: delta_lon: 0.5
>> DEBUG 4: Nlat: 361
>> DEBUG 4: Nlon: 720
>> DEBUG 4:
>> ERROR :
>> ERROR : DictionaryEntry::dict_value() -> bad type ERROR :
>>
>> I edited the climo file per the instructions from John in problem
>> report
>> #85052 plus I added a valid time to the header but still can't get
>> MET to properly read the file. I can plot the file in
>> plot_data_plane but I gives a valid time error. So, what is
missing
>> from this netCDF file the MET wants? A more general suggestion is
to
>> provide an addendum to the user guide on what MET requires to be in
>> netCDF climo files since these files are available from many
different sources.
>>
>> Thanks
>> Bob
>>
>>
------------------------------------------------
Subject: Climo Erro - Bad Type
From: David Fillmore
Time: Fri Apr 26 15:05:13 2019
Hi Bob -
John is out-of-office today. He should be back on Monday to follow up
on
this ticket.
It appears looking at the MET netcdf readers that they are expecting
both
"valid_time_ut" and "init_time_ut"
attributes, which refer to unix time, or seconds since 1970/01/01.
thanks,
David
On Fri, Apr 26, 2019 at 10:13 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89691 >
>
> John, per my previous email, what does MET need in the header to
figure
> out the valid time. I added a valid time value but that was not
enough. I
> notice in other netcdf files there is a init_time and init_time_ut
as well
> as valid_time and valid_time_ut. Does MET care about the ut fields
and if
> so how should they be set?
>
> Thanks
> Bob
>
> -----Original Message-----
> From: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> Sent: Friday, April 26, 2019 9:22 AM
> To: 'met_help at ucar.edu' <met_help at ucar.edu>
> Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo
Erro -
> Bad Type
>
> John, I should have got the dictionary issue and the mismatch of
dates.
> Is the problem with the climo files something lacking or wrong in
the
> header? I can modify the headers if I know what they need to be set
too.
> I could also read the climo files into memory and then to write them
back
> out in the proper netcdf format if I know what MET is looking for.
>
> -----Original Message-----
> From: John Halley Gotway via RT <met_help at ucar.edu>
> Sent: Friday, April 26, 2019 7:24 AM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo Erro -
Bad
> Type
>
> > Bob,
> >
> > The config file error is coming from parsing the climo_mean
section:
> > ERROR : DictionaryEntry::dict_value() -> bad type
> >
> > Specifically, you set:
> > field = ["fmcf0020","fmcf8100"];
> >
> > Instead, "field" should be an array of dictionaries, like it is in
the
> > rest of the config file:
> > field = [ { name = "fmcf0020"; level = "(*,*)"; },
> > { name = "fmcf8100"; level = "(*,*)"; } ];
> >
> > And the number of climo_mean.field entries must match the number
of
> > fcst.field entries.
> >
> > At debug level 3 (using met-8.0), I see this status message:
> > *DEBUG 3: Skipping climatology field since "match_month" is TRUE
but
> > the forecast (20190316_060000) and climatology (19700101_000000)
> > months do not match for file: porclds_03_6z_fmcf8100.nc
> > <http://porclds_03_6z_fmcf8100.nc>*
> >
> > The problem is the format of that NetCDF file. It doesn't follow
a
> > known convention, and MET is unable to parse the timing
information from
> it.
> >
> > Do you have any control over the format of that file?
> >
> > Thanks,
> > John
> >
> >
> >
> >
> > On Thu, Apr 11, 2019 at 1:17 PM robert.craig.2 at us.af.mil via RT <
> > met_help at ucar.edu> wrote:
> >
> >>
> >> Thu Apr 11 13:13:18 2019: Request 89691 was acted upon.
> >> Transaction: Ticket created by robert.craig.2 at us.af.mil
> >> Queue: met_help
> >> Subject: Climo Erro - Bad Type
> >> Owner: Nobody
> >> Requestors: robert.craig.2 at us.af.mil
> >> Status: new
> >> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89691
> >> >
> >>
> >>
> >> John or Julie, I sent relevant data file to you using
AMRDEC_Safe.
> >> This is a continuation of problem report #85052. When I run grid
> >> stat using a total cloud climo file, I get Bad Type error - see
below:
> >>
> >> INFO - MET command file executing
> >> ['/h/WXQC/met-8.1_beta1/bin/grid_stat',
> >>
'/h/data/global/ENSEMBLE/data/post/GEPS/global/2019031400/grib2.20190
> >> 31400.0042.EPOSTOUT',
> >> '/h/data/global/WXQC/data/met/nc_obs/wwmca/201903151800_p5.nc',
> >> '/h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated',
> >> '-outdir',
'/h/data/global/WXQC/data/met/gdstat/mdlob_pairs/geps/TC',
> >> '-v', '4'] DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES
file:
> >> /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
> >> DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
> >> /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
> >> DEBUG 1: Default Config File:
> >> /h/WXQC/met-8.1_beta1/share/met/config/GridStatConfig_default
> >> DEBUG 1: User Config File:
> >> /h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated
> >> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> >> Met2dDataFile object of type "FileType_Gb2".
> >> DEBUG 4: Switching the GRIB2 radius of the earth value of 6367.47
km
> >> to
> >> 6371.2 km for internal consistency.
> >> DEBUG 4:
> >> DEBUG 4: Latitude/Longitude Grid Data:
> >> DEBUG 4: lat_ll: -90
> >> DEBUG 4: lon_ll: -0
> >> DEBUG 4: delta_lat: 0.5
> >> DEBUG 4: delta_lon: 0.5
> >> DEBUG 4: Nlat: 361
> >> DEBUG 4: Nlon: 720
> >> DEBUG 4:
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 1, parm: 221
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 1, parm: 225
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 1, parm: 227
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 17, parm: 192
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 19, parm: 241
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 19, parm: 242
> >> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> >> Met2dDataFile object of type "FileType_NcMet".
> >> DEBUG 4:
> >> DEBUG 4: Latitude/Longitude Grid Data:
> >> DEBUG 4: lat_ll: -90
> >> DEBUG 4: lon_ll: -0
> >> DEBUG 4: delta_lat: 0.5
> >> DEBUG 4: delta_lon: 0.5
> >> DEBUG 4: Nlat: 361
> >> DEBUG 4: Nlon: 720
> >> DEBUG 4:
> >> ERROR :
> >> ERROR : DictionaryEntry::dict_value() -> bad type ERROR :
> >>
> >> I edited the climo file per the instructions from John in problem
> >> report
> >> #85052 plus I added a valid time to the header but still can't
get
> >> MET to properly read the file. I can plot the file in
> >> plot_data_plane but I gives a valid time error. So, what is
missing
> >> from this netCDF file the MET wants? A more general suggestion
is to
> >> provide an addendum to the user guide on what MET requires to be
in
> >> netCDF climo files since these files are available from many
different
> sources.
> >>
> >> Thanks
> >> Bob
> >>
> >>
>
>
>
>
------------------------------------------------
Subject: RE: FW: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo Erro - Bad Type
From: robert.craig.2 at us.af.mil
Time: Fri Apr 26 15:15:48 2019
Thanks, Dave I will give that a try.
-----Original Message-----
From: David Fillmore via RT <met_help at ucar.edu>
Sent: Friday, April 26, 2019 4:05 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: Re: FW: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo
Erro - Bad Type
Hi Bob -
John is out-of-office today. He should be back on Monday to follow up
on this ticket.
It appears looking at the MET netcdf readers that they are expecting
both "valid_time_ut" and "init_time_ut"
attributes, which refer to unix time, or seconds since 1970/01/01.
thanks,
David
On Fri, Apr 26, 2019 at 10:13 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89691 >
>
> John, per my previous email, what does MET need in the header to
> figure out the valid time. I added a valid time value but that was
> not enough. I notice in other netcdf files there is a init_time and
> init_time_ut as well as valid_time and valid_time_ut. Does MET care
> about the ut fields and if so how should they be set?
>
> Thanks
> Bob
>
> -----Original Message-----
> From: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> Sent: Friday, April 26, 2019 9:22 AM
> To: 'met_help at ucar.edu' <met_help at ucar.edu>
> Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo
Erro
> - Bad Type
>
> John, I should have got the dictionary issue and the mismatch of
dates.
> Is the problem with the climo files something lacking or wrong in
the
> header? I can modify the headers if I know what they need to be set
too.
> I could also read the climo files into memory and then to write them
> back out in the proper netcdf format if I know what MET is looking
for.
>
> -----Original Message-----
> From: John Halley Gotway via RT <met_help at ucar.edu>
> Sent: Friday, April 26, 2019 7:24 AM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo Erro -
> Bad Type
>
> > Bob,
> >
> > The config file error is coming from parsing the climo_mean
section:
> > ERROR : DictionaryEntry::dict_value() -> bad type
> >
> > Specifically, you set:
> > field = ["fmcf0020","fmcf8100"];
> >
> > Instead, "field" should be an array of dictionaries, like it is in
> > the rest of the config file:
> > field = [ { name = "fmcf0020"; level = "(*,*)"; },
> > { name = "fmcf8100"; level = "(*,*)"; } ];
> >
> > And the number of climo_mean.field entries must match the number
of
> > fcst.field entries.
> >
> > At debug level 3 (using met-8.0), I see this status message:
> > *DEBUG 3: Skipping climatology field since "match_month" is TRUE
but
> > the forecast (20190316_060000) and climatology (19700101_000000)
> > months do not match for file: porclds_03_6z_fmcf8100.nc
> > <http://porclds_03_6z_fmcf8100.nc>*
> >
> > The problem is the format of that NetCDF file. It doesn't follow
a
> > known convention, and MET is unable to parse the timing
information
> > from
> it.
> >
> > Do you have any control over the format of that file?
> >
> > Thanks,
> > John
> >
> >
> >
> >
> > On Thu, Apr 11, 2019 at 1:17 PM robert.craig.2 at us.af.mil via RT <
> > met_help at ucar.edu> wrote:
> >
> >>
> >> Thu Apr 11 13:13:18 2019: Request 89691 was acted upon.
> >> Transaction: Ticket created by robert.craig.2 at us.af.mil
> >> Queue: met_help
> >> Subject: Climo Erro - Bad Type
> >> Owner: Nobody
> >> Requestors: robert.craig.2 at us.af.mil
> >> Status: new
> >> Ticket <URL:
> >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89691
> >> >
> >>
> >>
> >> John or Julie, I sent relevant data file to you using
AMRDEC_Safe.
> >> This is a continuation of problem report #85052. When I run grid
> >> stat using a total cloud climo file, I get Bad Type error - see
below:
> >>
> >> INFO - MET command file executing
> >> ['/h/WXQC/met-8.1_beta1/bin/grid_stat',
> >>
'/h/data/global/ENSEMBLE/data/post/GEPS/global/2019031400/grib2.201
> >> 90
> >> 31400.0042.EPOSTOUT',
> >> '/h/data/global/WXQC/data/met/nc_obs/wwmca/201903151800_p5.nc',
> >> '/h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated',
> >> '-outdir',
> >> '/h/data/global/WXQC/data/met/gdstat/mdlob_pairs/geps/TC',
> >> '-v', '4'] DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES
file:
> >> /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
> >> DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
> >> /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
> >> DEBUG 1: Default Config File:
> >> /h/WXQC/met-8.1_beta1/share/met/config/GridStatConfig_default
> >> DEBUG 1: User Config File:
> >> /h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated
> >> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
> >> new Met2dDataFile object of type "FileType_Gb2".
> >> DEBUG 4: Switching the GRIB2 radius of the earth value of 6367.47
> >> km to
> >> 6371.2 km for internal consistency.
> >> DEBUG 4:
> >> DEBUG 4: Latitude/Longitude Grid Data:
> >> DEBUG 4: lat_ll: -90
> >> DEBUG 4: lon_ll: -0
> >> DEBUG 4: delta_lat: 0.5
> >> DEBUG 4: delta_lon: 0.5
> >> DEBUG 4: Nlat: 361
> >> DEBUG 4: Nlon: 720
> >> DEBUG 4:
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 1, parm: 221
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 1, parm: 225
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 1, parm: 227
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 17, parm: 192
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 19, parm: 241
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 19, parm: 242
> >> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
> >> new Met2dDataFile object of type "FileType_NcMet".
> >> DEBUG 4:
> >> DEBUG 4: Latitude/Longitude Grid Data:
> >> DEBUG 4: lat_ll: -90
> >> DEBUG 4: lon_ll: -0
> >> DEBUG 4: delta_lat: 0.5
> >> DEBUG 4: delta_lon: 0.5
> >> DEBUG 4: Nlat: 361
> >> DEBUG 4: Nlon: 720
> >> DEBUG 4:
> >> ERROR :
> >> ERROR : DictionaryEntry::dict_value() -> bad type ERROR :
> >>
> >> I edited the climo file per the instructions from John in problem
> >> report
> >> #85052 plus I added a valid time to the header but still can't
get
> >> MET to properly read the file. I can plot the file in
> >> plot_data_plane but I gives a valid time error. So, what is
> >> missing from this netCDF file the MET wants? A more general
> >> suggestion is to provide an addendum to the user guide on what
MET
> >> requires to be in netCDF climo files since these files are
> >> available from many different
> sources.
> >>
> >> Thanks
> >> Bob
> >>
> >>
>
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo Erro - Bad Type
From: robert.craig.2 at us.af.mil
Time: Fri Apr 26 16:09:59 2019
John, I should have got the dictionary issue and the mismatch of
dates. Is the problem with the climo files something lacking or wrong
in the header? I can modify the headers if I know what they need to
be set too. I could also read the climo files into memory and then to
write them back out in the proper netcdf format if I know what MET is
looking for.
-----Original Message-----
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Friday, April 26, 2019 7:24 AM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo Erro -
Bad Type
> Bob,
>
> The config file error is coming from parsing the climo_mean section:
> ERROR : DictionaryEntry::dict_value() -> bad type
>
> Specifically, you set:
> field = ["fmcf0020","fmcf8100"];
>
> Instead, "field" should be an array of dictionaries, like it is in
the
> rest of the config file:
> field = [ { name = "fmcf0020"; level = "(*,*)"; },
> { name = "fmcf8100"; level = "(*,*)"; } ];
>
> And the number of climo_mean.field entries must match the number of
> fcst.field entries.
>
> At debug level 3 (using met-8.0), I see this status message:
> *DEBUG 3: Skipping climatology field since "match_month" is TRUE but
> the forecast (20190316_060000) and climatology (19700101_000000)
> months do not match for file: porclds_03_6z_fmcf8100.nc
> <http://porclds_03_6z_fmcf8100.nc>*
>
> The problem is the format of that NetCDF file. It doesn't follow a
> known convention, and MET is unable to parse the timing information
from it.
>
> Do you have any control over the format of that file?
>
> Thanks,
> John
>
>
>
>
> On Thu, Apr 11, 2019 at 1:17 PM robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
>>
>> Thu Apr 11 13:13:18 2019: Request 89691 was acted upon.
>> Transaction: Ticket created by robert.craig.2 at us.af.mil
>> Queue: met_help
>> Subject: Climo Erro - Bad Type
>> Owner: Nobody
>> Requestors: robert.craig.2 at us.af.mil
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89691
>> >
>>
>>
>> John or Julie, I sent relevant data file to you using AMRDEC_Safe.
>> This is a continuation of problem report #85052. When I run grid
>> stat using a total cloud climo file, I get Bad Type error - see
below:
>>
>> INFO - MET command file executing
>> ['/h/WXQC/met-8.1_beta1/bin/grid_stat',
>>
'/h/data/global/ENSEMBLE/data/post/GEPS/global/2019031400/grib2.20190
>> 31400.0042.EPOSTOUT',
>> '/h/data/global/WXQC/data/met/nc_obs/wwmca/201903151800_p5.nc',
>> '/h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated',
>> '-outdir',
'/h/data/global/WXQC/data/met/gdstat/mdlob_pairs/geps/TC',
>> '-v', '4'] DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES
file:
>> /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
>> DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
>> /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
>> DEBUG 1: Default Config File:
>> /h/WXQC/met-8.1_beta1/share/met/config/GridStatConfig_default
>> DEBUG 1: User Config File:
>> /h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated
>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
>> Met2dDataFile object of type "FileType_Gb2".
>> DEBUG 4: Switching the GRIB2 radius of the earth value of 6367.47
km
>> to
>> 6371.2 km for internal consistency.
>> DEBUG 4:
>> DEBUG 4: Latitude/Longitude Grid Data:
>> DEBUG 4: lat_ll: -90
>> DEBUG 4: lon_ll: -0
>> DEBUG 4: delta_lat: 0.5
>> DEBUG 4: delta_lon: 0.5
>> DEBUG 4: Nlat: 361
>> DEBUG 4: Nlon: 720
>> DEBUG 4:
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
>> table: 1,
>> parm_cat: 1, parm: 221
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
>> table: 1,
>> parm_cat: 1, parm: 225
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
>> table: 1,
>> parm_cat: 1, parm: 227
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
>> table: 1,
>> parm_cat: 17, parm: 192
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
>> table: 1,
>> parm_cat: 19, parm: 241
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
>> table: 1,
>> parm_cat: 19, parm: 242
>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
>> Met2dDataFile object of type "FileType_NcMet".
>> DEBUG 4:
>> DEBUG 4: Latitude/Longitude Grid Data:
>> DEBUG 4: lat_ll: -90
>> DEBUG 4: lon_ll: -0
>> DEBUG 4: delta_lat: 0.5
>> DEBUG 4: delta_lon: 0.5
>> DEBUG 4: Nlat: 361
>> DEBUG 4: Nlon: 720
>> DEBUG 4:
>> ERROR :
>> ERROR : DictionaryEntry::dict_value() -> bad type ERROR :
>>
>> I edited the climo file per the instructions from John in problem
>> report
>> #85052 plus I added a valid time to the header but still can't get
>> MET to properly read the file. I can plot the file in
>> plot_data_plane but I gives a valid time error. So, what is
missing
>> from this netCDF file the MET wants? A more general suggestion is
to
>> provide an addendum to the user guide on what MET requires to be in
>> netCDF climo files since these files are available from many
different sources.
>>
>> Thanks
>> Bob
>>
>>
------------------------------------------------
Subject: Climo Erro - Bad Type
From: John Halley Gotway
Time: Mon Apr 29 09:36:03 2019
Bob,
MET can read a few different flavors of NetCDF. I'd suggest either
using
MET's internal NetCDF format (i.e. the output of pcp_combine) or
follow the
CF conventions. I see from the NetCDF header that you were going
trying
the latter:
* :Conventions = "CF-1.7" ;*
But, as you've noted, the timing information is missing. So MET is
able to
read the file in the current form, but isn't able to read extract the
timing info. The trick is that the way you specify timing info for
the CF
convention (i.e. a time dimension and variable) is different from the
way
you do using MET's NetCDF format (i.e. variable attributes defining
the
times). Since you've already started with the CF route, let's do
that.
Here are the steps I followed:
(1) Run ncdump to dump your file to ascii:
*ncdump porclds_03_6z_fmcf8100.nc <http://porclds_03_6z_fmcf8100.nc> >
porclds_03_6z_fmcf8100.ncdump*
(2) Modified the ncdump file by adding a time dimension and variable
(see
below for the final header).
(3) Regenerated the file using:
*ncgen -o porclds_03_6z_fmcf8100.nc <http://porclds_03_6z_fmcf8100.nc>
porclds_03_6z_fmcf8100.ncdump*
When I re-ran Grid-Stat, I got this descriptive log message:
*DEBUG 3: Skipping climatology field since "match_day" is TRUE but the
forecast (20190316_060000) and climatology (19700315_060000) days do
not
match for file: porclds_03_6z_fmcf8100.nc
<http://porclds_03_6z_fmcf8100.nc>*
So just for testing, I reconfigured Grid-Stat to set *match_day =
FALSE;*
And finally, I do now get the BRIER_CL and BSS columns populated in
the
output. Hope this helps get you going. I'll try attaching the final
NetCDF file to this email, but just in case it doesn't come through,
I've
cut-and-pasted the final NetCDF header below.
Thanks,
John
*netcdf porclds_03_6z_fmcf8100 {dimensions: time = 1; lat = 720
;
lon = 1440 ;variables: double time(time) ; time:long_name =
"valid time" ; time:units = "seconds since 1970-01-01" ;
float
lat(lat) ; lat:units = "degrees_north" ; float lon(lon) ;
lon:units = "degrees_east" ; int fmcf8100(time, lon, lat) ;
fmcf8100:units = "percent" ; fmcf8100:long_name = "fmcf8100
Long
Name" ; fmcf8100:_FillValue = -9999.f ;// global attributes:
:Conventions = "CF-1.7" ;data: time = 6328800 ; lat = -89.75, -89.5,
...*
On Fri, Apr 26, 2019 at 4:10 PM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89691 >
>
> John, I should have got the dictionary issue and the mismatch of
dates.
> Is the problem with the climo files something lacking or wrong in
the
> header? I can modify the headers if I know what they need to be set
too.
> I could also read the climo files into memory and then to write them
back
> out in the proper netcdf format if I know what MET is looking for.
>
> -----Original Message-----
> From: John Halley Gotway via RT <met_help at ucar.edu>
> Sent: Friday, April 26, 2019 7:24 AM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo Erro -
Bad
> Type
>
> > Bob,
> >
> > The config file error is coming from parsing the climo_mean
section:
> > ERROR : DictionaryEntry::dict_value() -> bad type
> >
> > Specifically, you set:
> > field = ["fmcf0020","fmcf8100"];
> >
> > Instead, "field" should be an array of dictionaries, like it is in
the
> > rest of the config file:
> > field = [ { name = "fmcf0020"; level = "(*,*)"; },
> > { name = "fmcf8100"; level = "(*,*)"; } ];
> >
> > And the number of climo_mean.field entries must match the number
of
> > fcst.field entries.
> >
> > At debug level 3 (using met-8.0), I see this status message:
> > *DEBUG 3: Skipping climatology field since "match_month" is TRUE
but
> > the forecast (20190316_060000) and climatology (19700101_000000)
> > months do not match for file: porclds_03_6z_fmcf8100.nc
> > <http://porclds_03_6z_fmcf8100.nc>*
> >
> > The problem is the format of that NetCDF file. It doesn't follow
a
> > known convention, and MET is unable to parse the timing
information from
> it.
> >
> > Do you have any control over the format of that file?
> >
> > Thanks,
> > John
> >
> >
> >
> >
> > On Thu, Apr 11, 2019 at 1:17 PM robert.craig.2 at us.af.mil via RT <
> > met_help at ucar.edu> wrote:
> >
> >>
> >> Thu Apr 11 13:13:18 2019: Request 89691 was acted upon.
> >> Transaction: Ticket created by robert.craig.2 at us.af.mil
> >> Queue: met_help
> >> Subject: Climo Erro - Bad Type
> >> Owner: Nobody
> >> Requestors: robert.craig.2 at us.af.mil
> >> Status: new
> >> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89691
> >> >
> >>
> >>
> >> John or Julie, I sent relevant data file to you using
AMRDEC_Safe.
> >> This is a continuation of problem report #85052. When I run grid
> >> stat using a total cloud climo file, I get Bad Type error - see
below:
> >>
> >> INFO - MET command file executing
> >> ['/h/WXQC/met-8.1_beta1/bin/grid_stat',
> >>
'/h/data/global/ENSEMBLE/data/post/GEPS/global/2019031400/grib2.20190
> >> 31400.0042.EPOSTOUT',
> >> '/h/data/global/WXQC/data/met/nc_obs/wwmca/201903151800_p5.nc',
> >> '/h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated',
> >> '-outdir',
'/h/data/global/WXQC/data/met/gdstat/mdlob_pairs/geps/TC',
> >> '-v', '4'] DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES
file:
> >> /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
> >> DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
> >> /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
> >> DEBUG 1: Default Config File:
> >> /h/WXQC/met-8.1_beta1/share/met/config/GridStatConfig_default
> >> DEBUG 1: User Config File:
> >> /h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated
> >> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> >> Met2dDataFile object of type "FileType_Gb2".
> >> DEBUG 4: Switching the GRIB2 radius of the earth value of 6367.47
km
> >> to
> >> 6371.2 km for internal consistency.
> >> DEBUG 4:
> >> DEBUG 4: Latitude/Longitude Grid Data:
> >> DEBUG 4: lat_ll: -90
> >> DEBUG 4: lon_ll: -0
> >> DEBUG 4: delta_lat: 0.5
> >> DEBUG 4: delta_lon: 0.5
> >> DEBUG 4: Nlat: 361
> >> DEBUG 4: Nlon: 720
> >> DEBUG 4:
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 1, parm: 221
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 1, parm: 225
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 1, parm: 227
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 17, parm: 192
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 19, parm: 241
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 19, parm: 242
> >> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> >> Met2dDataFile object of type "FileType_NcMet".
> >> DEBUG 4:
> >> DEBUG 4: Latitude/Longitude Grid Data:
> >> DEBUG 4: lat_ll: -90
> >> DEBUG 4: lon_ll: -0
> >> DEBUG 4: delta_lat: 0.5
> >> DEBUG 4: delta_lon: 0.5
> >> DEBUG 4: Nlat: 361
> >> DEBUG 4: Nlon: 720
> >> DEBUG 4:
> >> ERROR :
> >> ERROR : DictionaryEntry::dict_value() -> bad type ERROR :
> >>
> >> I edited the climo file per the instructions from John in problem
> >> report
> >> #85052 plus I added a valid time to the header but still can't
get
> >> MET to properly read the file. I can plot the file in
> >> plot_data_plane but I gives a valid time error. So, what is
missing
> >> from this netCDF file the MET wants? A more general suggestion
is to
> >> provide an addendum to the user guide on what MET requires to be
in
> >> netCDF climo files since these files are available from many
different
> sources.
> >>
> >> Thanks
> >> Bob
> >>
> >>
>
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo Erro - Bad Type
From: robert.craig.2 at us.af.mil
Time: Tue Apr 30 08:48:14 2019
John, where do you get the time = 6328800? Is it the number of
seconds since 19700101?
Thanks
Bob
-----Original Message-----
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Monday, April 29, 2019 10:36 AM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Cc: craigr3 at cox.net
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo Erro
- Bad Type
Bob,
MET can read a few different flavors of NetCDF. I'd suggest either
using
MET's internal NetCDF format (i.e. the output of pcp_combine) or
follow the CF conventions. I see from the NetCDF header that you were
going trying the latter:
* :Conventions = "CF-1.7" ;*
But, as you've noted, the timing information is missing. So MET is
able to read the file in the current form, but isn't able to read
extract the timing info. The trick is that the way you specify timing
info for the CF convention (i.e. a time dimension and variable) is
different from the way you do using MET's NetCDF format (i.e. variable
attributes defining the times). Since you've already started with the
CF route, let's do that.
Here are the steps I followed:
(1) Run ncdump to dump your file to ascii:
*ncdump porclds_03_6z_fmcf8100.nc <http://porclds_03_6z_fmcf8100.nc> >
porclds_03_6z_fmcf8100.ncdump*
(2) Modified the ncdump file by adding a time dimension and variable
(see below for the final header).
(3) Regenerated the file using:
*ncgen -o porclds_03_6z_fmcf8100.nc <http://porclds_03_6z_fmcf8100.nc>
porclds_03_6z_fmcf8100.ncdump*
When I re-ran Grid-Stat, I got this descriptive log message:
*DEBUG 3: Skipping climatology field since "match_day" is TRUE but the
forecast (20190316_060000) and climatology (19700315_060000) days do
not match for file: porclds_03_6z_fmcf8100.nc
<http://porclds_03_6z_fmcf8100.nc>*
So just for testing, I reconfigured Grid-Stat to set *match_day =
FALSE;*
And finally, I do now get the BRIER_CL and BSS columns populated in
the output. Hope this helps get you going. I'll try attaching the
final NetCDF file to this email, but just in case it doesn't come
through, I've cut-and-pasted the final NetCDF header below.
Thanks,
John
*netcdf porclds_03_6z_fmcf8100 {dimensions: time = 1; lat = 720
;
lon = 1440 ;variables: double time(time) ; time:long_name =
"valid time" ; time:units = "seconds since 1970-01-01" ;
float
lat(lat) ; lat:units = "degrees_north" ; float lon(lon) ;
lon:units = "degrees_east" ; int fmcf8100(time, lon, lat) ;
fmcf8100:units = "percent" ; fmcf8100:long_name = "fmcf8100
Long
Name" ; fmcf8100:_FillValue = -9999.f ;// global attributes:
:Conventions = "CF-1.7" ;data: time = 6328800 ; lat = -89.75, -89.5,
...*
On Fri, Apr 26, 2019 at 4:10 PM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89691 >
>
> John, I should have got the dictionary issue and the mismatch of
dates.
> Is the problem with the climo files something lacking or wrong in
the
> header? I can modify the headers if I know what they need to be set
too.
> I could also read the climo files into memory and then to write them
> back out in the proper netcdf format if I know what MET is looking
for.
>
> -----Original Message-----
> From: John Halley Gotway via RT <met_help at ucar.edu>
> Sent: Friday, April 26, 2019 7:24 AM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo Erro -
> Bad Type
>
> > Bob,
> >
> > The config file error is coming from parsing the climo_mean
section:
> > ERROR : DictionaryEntry::dict_value() -> bad type
> >
> > Specifically, you set:
> > field = ["fmcf0020","fmcf8100"];
> >
> > Instead, "field" should be an array of dictionaries, like it is in
> > the rest of the config file:
> > field = [ { name = "fmcf0020"; level = "(*,*)"; },
> > { name = "fmcf8100"; level = "(*,*)"; } ];
> >
> > And the number of climo_mean.field entries must match the number
of
> > fcst.field entries.
> >
> > At debug level 3 (using met-8.0), I see this status message:
> > *DEBUG 3: Skipping climatology field since "match_month" is TRUE
but
> > the forecast (20190316_060000) and climatology (19700101_000000)
> > months do not match for file: porclds_03_6z_fmcf8100.nc
> > <http://porclds_03_6z_fmcf8100.nc>*
> >
> > The problem is the format of that NetCDF file. It doesn't follow
a
> > known convention, and MET is unable to parse the timing
information
> > from
> it.
> >
> > Do you have any control over the format of that file?
> >
> > Thanks,
> > John
> >
> >
> >
> >
> > On Thu, Apr 11, 2019 at 1:17 PM robert.craig.2 at us.af.mil via RT <
> > met_help at ucar.edu> wrote:
> >
> >>
> >> Thu Apr 11 13:13:18 2019: Request 89691 was acted upon.
> >> Transaction: Ticket created by robert.craig.2 at us.af.mil
> >> Queue: met_help
> >> Subject: Climo Erro - Bad Type
> >> Owner: Nobody
> >> Requestors: robert.craig.2 at us.af.mil
> >> Status: new
> >> Ticket <URL:
> >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89691
> >> >
> >>
> >>
> >> John or Julie, I sent relevant data file to you using
AMRDEC_Safe.
> >> This is a continuation of problem report #85052. When I run grid
> >> stat using a total cloud climo file, I get Bad Type error - see
below:
> >>
> >> INFO - MET command file executing
> >> ['/h/WXQC/met-8.1_beta1/bin/grid_stat',
> >>
'/h/data/global/ENSEMBLE/data/post/GEPS/global/2019031400/grib2.201
> >> 90
> >> 31400.0042.EPOSTOUT',
> >> '/h/data/global/WXQC/data/met/nc_obs/wwmca/201903151800_p5.nc',
> >> '/h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated',
> >> '-outdir',
> >> '/h/data/global/WXQC/data/met/gdstat/mdlob_pairs/geps/TC',
> >> '-v', '4'] DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES
file:
> >> /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
> >> DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
> >> /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
> >> DEBUG 1: Default Config File:
> >> /h/WXQC/met-8.1_beta1/share/met/config/GridStatConfig_default
> >> DEBUG 1: User Config File:
> >> /h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated
> >> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
> >> new Met2dDataFile object of type "FileType_Gb2".
> >> DEBUG 4: Switching the GRIB2 radius of the earth value of 6367.47
> >> km to
> >> 6371.2 km for internal consistency.
> >> DEBUG 4:
> >> DEBUG 4: Latitude/Longitude Grid Data:
> >> DEBUG 4: lat_ll: -90
> >> DEBUG 4: lon_ll: -0
> >> DEBUG 4: delta_lat: 0.5
> >> DEBUG 4: delta_lon: 0.5
> >> DEBUG 4: Nlat: 361
> >> DEBUG 4: Nlon: 720
> >> DEBUG 4:
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 1, parm: 221
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 1, parm: 225
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 1, parm: 227
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 17, parm: 192
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 19, parm: 241
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 1, center: 57, local
> >> table: 1,
> >> parm_cat: 19, parm: 242
> >> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
> >> new Met2dDataFile object of type "FileType_NcMet".
> >> DEBUG 4:
> >> DEBUG 4: Latitude/Longitude Grid Data:
> >> DEBUG 4: lat_ll: -90
> >> DEBUG 4: lon_ll: -0
> >> DEBUG 4: delta_lat: 0.5
> >> DEBUG 4: delta_lon: 0.5
> >> DEBUG 4: Nlat: 361
> >> DEBUG 4: Nlon: 720
> >> DEBUG 4:
> >> ERROR :
> >> ERROR : DictionaryEntry::dict_value() -> bad type ERROR :
> >>
> >> I edited the climo file per the instructions from John in problem
> >> report
> >> #85052 plus I added a valid time to the header but still can't
get
> >> MET to properly read the file. I can plot the file in
> >> plot_data_plane but I gives a valid time error. So, what is
> >> missing from this netCDF file the MET wants? A more general
> >> suggestion is to provide an addendum to the user guide on what
MET
> >> requires to be in netCDF climo files since these files are
> >> available from many different
> sources.
> >>
> >> Thanks
> >> Bob
> >>
> >>
>
>
>
>
------------------------------------------------
Subject: Recall: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo Erro - Bad Type
From: robert.craig.2 at us.af.mil
Time: Tue Apr 30 08:53:12 2019
CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN would like to recall the
message, "[Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo Erro -
Bad Type".
------------------------------------------------
Subject: Climo Erro - Bad Type
From: John Halley Gotway
Time: Tue Apr 30 09:25:38 2019
Yes, that's correct. Here's how you can use the date command to
figure out
the number of seconds since Jan 1, 1970 (also known as unixtime):
*date -ud ''1970-03-15' UTC '06:00:00'' +%s*
And going the other way (converting from unixtime to year, month,
day):
* date -ud '1970-01-01 UTC '6328800' seconds' +"%Y-%m-%d %H:%M:%S"*
FYI, you don't have to specify time in that way. The CF-convention
(and
the MET code) supports any number of variations for the time "units".
The
units should be of the form "something" since "sometime". So it could
be
"hours since 2001-01-01" or "days since 1977-08-07". But since
unixtime is
widely known and used, you'll often see "seconds since 1970-01-01".
John
On Tue, Apr 30, 2019 at 8:48 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89691 >
>
> John, where do you get the time = 6328800? Is it the number of
seconds
> since 19700101?
> Thanks
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT <met_help at ucar.edu>
> Sent: Monday, April 29, 2019 10:36 AM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Cc: craigr3 at cox.net
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo
Erro -
> Bad Type
>
> Bob,
>
> MET can read a few different flavors of NetCDF. I'd suggest either
using
> MET's internal NetCDF format (i.e. the output of pcp_combine) or
follow
> the CF conventions. I see from the NetCDF header that you were
going
> trying the latter:
> * :Conventions = "CF-1.7" ;*
>
> But, as you've noted, the timing information is missing. So MET is
able
> to read the file in the current form, but isn't able to read extract
the
> timing info. The trick is that the way you specify timing info for
the CF
> convention (i.e. a time dimension and variable) is different from
the way
> you do using MET's NetCDF format (i.e. variable attributes defining
the
> times). Since you've already started with the CF route, let's do
that.
> Here are the steps I followed:
>
> (1) Run ncdump to dump your file to ascii:
> *ncdump porclds_03_6z_fmcf8100.nc <http://porclds_03_6z_fmcf8100.nc>
>
> porclds_03_6z_fmcf8100.ncdump*
>
> (2) Modified the ncdump file by adding a time dimension and variable
(see
> below for the final header).
>
> (3) Regenerated the file using:
> *ncgen -o porclds_03_6z_fmcf8100.nc
<http://porclds_03_6z_fmcf8100.nc>
> porclds_03_6z_fmcf8100.ncdump*
>
> When I re-ran Grid-Stat, I got this descriptive log message:
> *DEBUG 3: Skipping climatology field since "match_day" is TRUE but
the
> forecast (20190316_060000) and climatology (19700315_060000) days do
not
> match for file: porclds_03_6z_fmcf8100.nc
> <http://porclds_03_6z_fmcf8100.nc>*
>
> So just for testing, I reconfigured Grid-Stat to set *match_day =
FALSE;*
>
> And finally, I do now get the BRIER_CL and BSS columns populated in
the
> output. Hope this helps get you going. I'll try attaching the
final
> NetCDF file to this email, but just in case it doesn't come through,
I've
> cut-and-pasted the final NetCDF header below.
>
> Thanks,
> John
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *netcdf porclds_03_6z_fmcf8100 {dimensions: time = 1; lat =
720 ;
> lon = 1440 ;variables: double time(time) ; time:long_name
=
> "valid time" ; time:units = "seconds since 1970-01-01" ;
float
> lat(lat) ; lat:units = "degrees_north" ; float lon(lon) ;
> lon:units = "degrees_east" ; int fmcf8100(time, lon, lat) ;
> fmcf8100:units = "percent" ; fmcf8100:long_name = "fmcf8100
Long
> Name" ; fmcf8100:_FillValue = -9999.f ;// global attributes:
> :Conventions = "CF-1.7" ;data: time = 6328800 ; lat = -89.75, -89.5,
...*
>
> On Fri, Apr 26, 2019 at 4:10 PM robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89691 >
> >
> > John, I should have got the dictionary issue and the mismatch of
dates.
> > Is the problem with the climo files something lacking or wrong in
the
> > header? I can modify the headers if I know what they need to be
set too.
> > I could also read the climo files into memory and then to write
them
> > back out in the proper netcdf format if I know what MET is looking
for.
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT <met_help at ucar.edu>
> > Sent: Friday, April 26, 2019 7:24 AM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo Erro
-
> > Bad Type
> >
> > > Bob,
> > >
> > > The config file error is coming from parsing the climo_mean
section:
> > > ERROR : DictionaryEntry::dict_value() -> bad type
> > >
> > > Specifically, you set:
> > > field = ["fmcf0020","fmcf8100"];
> > >
> > > Instead, "field" should be an array of dictionaries, like it is
in
> > > the rest of the config file:
> > > field = [ { name = "fmcf0020"; level = "(*,*)"; },
> > > { name = "fmcf8100"; level = "(*,*)"; } ];
> > >
> > > And the number of climo_mean.field entries must match the number
of
> > > fcst.field entries.
> > >
> > > At debug level 3 (using met-8.0), I see this status message:
> > > *DEBUG 3: Skipping climatology field since "match_month" is TRUE
but
> > > the forecast (20190316_060000) and climatology (19700101_000000)
> > > months do not match for file: porclds_03_6z_fmcf8100.nc
> > > <http://porclds_03_6z_fmcf8100.nc>*
> > >
> > > The problem is the format of that NetCDF file. It doesn't
follow a
> > > known convention, and MET is unable to parse the timing
information
> > > from
> > it.
> > >
> > > Do you have any control over the format of that file?
> > >
> > > Thanks,
> > > John
> > >
> > >
> > >
> > >
> > > On Thu, Apr 11, 2019 at 1:17 PM robert.craig.2 at us.af.mil via RT
<
> > > met_help at ucar.edu> wrote:
> > >
> > >>
> > >> Thu Apr 11 13:13:18 2019: Request 89691 was acted upon.
> > >> Transaction: Ticket created by robert.craig.2 at us.af.mil
> > >> Queue: met_help
> > >> Subject: Climo Erro - Bad Type
> > >> Owner: Nobody
> > >> Requestors: robert.craig.2 at us.af.mil
> > >> Status: new
> > >> Ticket <URL:
> > >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89691
> > >> >
> > >>
> > >>
> > >> John or Julie, I sent relevant data file to you using
AMRDEC_Safe.
> > >> This is a continuation of problem report #85052. When I run
grid
> > >> stat using a total cloud climo file, I get Bad Type error - see
below:
> > >>
> > >> INFO - MET command file executing
> > >> ['/h/WXQC/met-8.1_beta1/bin/grid_stat',
> > >>
'/h/data/global/ENSEMBLE/data/post/GEPS/global/2019031400/grib2.201
> > >> 90
> > >> 31400.0042.EPOSTOUT',
> > >> '/h/data/global/WXQC/data/met/nc_obs/wwmca/201903151800_p5.nc',
> > >> '/h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated',
> > >> '-outdir',
> > >> '/h/data/global/WXQC/data/met/gdstat/mdlob_pairs/geps/TC',
> > >> '-v', '4'] DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES
file:
> > >> /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
> > >> DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
> > >> /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
> > >> DEBUG 1: Default Config File:
> > >> /h/WXQC/met-8.1_beta1/share/met/config/GridStatConfig_default
> > >> DEBUG 1: User Config File:
> > >> /h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated
> > >> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
> > >> new Met2dDataFile object of type "FileType_Gb2".
> > >> DEBUG 4: Switching the GRIB2 radius of the earth value of
6367.47
> > >> km to
> > >> 6371.2 km for internal consistency.
> > >> DEBUG 4:
> > >> DEBUG 4: Latitude/Longitude Grid Data:
> > >> DEBUG 4: lat_ll: -90
> > >> DEBUG 4: lon_ll: -0
> > >> DEBUG 4: delta_lat: 0.5
> > >> DEBUG 4: delta_lon: 0.5
> > >> DEBUG 4: Nlat: 361
> > >> DEBUG 4: Nlon: 720
> > >> DEBUG 4:
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 1, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 1, parm: 221
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 1, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 1, parm: 225
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 1, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 1, parm: 227
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 1, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 17, parm: 192
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 1, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 19, parm: 241
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 1, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 19, parm: 242
> > >> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
> > >> new Met2dDataFile object of type "FileType_NcMet".
> > >> DEBUG 4:
> > >> DEBUG 4: Latitude/Longitude Grid Data:
> > >> DEBUG 4: lat_ll: -90
> > >> DEBUG 4: lon_ll: -0
> > >> DEBUG 4: delta_lat: 0.5
> > >> DEBUG 4: delta_lon: 0.5
> > >> DEBUG 4: Nlat: 361
> > >> DEBUG 4: Nlon: 720
> > >> DEBUG 4:
> > >> ERROR :
> > >> ERROR : DictionaryEntry::dict_value() -> bad type ERROR :
> > >>
> > >> I edited the climo file per the instructions from John in
problem
> > >> report
> > >> #85052 plus I added a valid time to the header but still can't
get
> > >> MET to properly read the file. I can plot the file in
> > >> plot_data_plane but I gives a valid time error. So, what is
> > >> missing from this netCDF file the MET wants? A more general
> > >> suggestion is to provide an addendum to the user guide on what
MET
> > >> requires to be in netCDF climo files since these files are
> > >> available from many different
> > sources.
> > >>
> > >> Thanks
> > >> Bob
> > >>
> > >>
> >
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo Erro - Bad Type
From: robert.craig.2 at us.af.mil
Time: Tue Apr 30 09:29:36 2019
Okay,
Thanks
-----Original Message-----
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Tuesday, April 30, 2019 10:26 AM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Cc: craigr3 at cox.net
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo Erro
- Bad Type
Yes, that's correct. Here's how you can use the date command to
figure out the number of seconds since Jan 1, 1970 (also known as
unixtime):
*date -ud ''1970-03-15' UTC '06:00:00'' +%s*
And going the other way (converting from unixtime to year, month,
day):
* date -ud '1970-01-01 UTC '6328800' seconds' +"%Y-%m-%d %H:%M:%S"*
FYI, you don't have to specify time in that way. The CF-convention
(and the MET code) supports any number of variations for the time
"units". The units should be of the form "something" since
"sometime". So it could be "hours since 2001-01-01" or "days since
1977-08-07". But since unixtime is widely known and used, you'll
often see "seconds since 1970-01-01".
John
On Tue, Apr 30, 2019 at 8:48 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89691 >
>
> John, where do you get the time = 6328800? Is it the number of
> seconds since 19700101?
> Thanks
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT <met_help at ucar.edu>
> Sent: Monday, April 29, 2019 10:36 AM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Cc: craigr3 at cox.net
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo
Erro
> - Bad Type
>
> Bob,
>
> MET can read a few different flavors of NetCDF. I'd suggest either
using
> MET's internal NetCDF format (i.e. the output of pcp_combine) or
> follow the CF conventions. I see from the NetCDF header that you
were
> going trying the latter:
> * :Conventions = "CF-1.7" ;*
>
> But, as you've noted, the timing information is missing. So MET is
> able to read the file in the current form, but isn't able to read
> extract the timing info. The trick is that the way you specify
timing
> info for the CF convention (i.e. a time dimension and variable) is
> different from the way you do using MET's NetCDF format (i.e.
variable
> attributes defining the times). Since you've already started with
the CF route, let's do that.
> Here are the steps I followed:
>
> (1) Run ncdump to dump your file to ascii:
> *ncdump porclds_03_6z_fmcf8100.nc <http://porclds_03_6z_fmcf8100.nc>
>
> porclds_03_6z_fmcf8100.ncdump*
>
> (2) Modified the ncdump file by adding a time dimension and variable
> (see below for the final header).
>
> (3) Regenerated the file using:
> *ncgen -o porclds_03_6z_fmcf8100.nc
<http://porclds_03_6z_fmcf8100.nc>
> porclds_03_6z_fmcf8100.ncdump*
>
> When I re-ran Grid-Stat, I got this descriptive log message:
> *DEBUG 3: Skipping climatology field since "match_day" is TRUE but
the
> forecast (20190316_060000) and climatology (19700315_060000) days do
> not match for file: porclds_03_6z_fmcf8100.nc
> <http://porclds_03_6z_fmcf8100.nc>*
>
> So just for testing, I reconfigured Grid-Stat to set *match_day =
> FALSE;*
>
> And finally, I do now get the BRIER_CL and BSS columns populated in
> the output. Hope this helps get you going. I'll try attaching the
> final NetCDF file to this email, but just in case it doesn't come
> through, I've cut-and-pasted the final NetCDF header below.
>
> Thanks,
> John
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *netcdf porclds_03_6z_fmcf8100 {dimensions: time = 1; lat =
720 ;
> lon = 1440 ;variables: double time(time) ; time:long_name
=
> "valid time" ; time:units = "seconds since 1970-01-01" ;
float
> lat(lat) ; lat:units = "degrees_north" ; float lon(lon) ;
> lon:units = "degrees_east" ; int fmcf8100(time, lon, lat) ;
> fmcf8100:units = "percent" ; fmcf8100:long_name = "fmcf8100
Long
> Name" ; fmcf8100:_FillValue = -9999.f ;// global attributes:
> :Conventions = "CF-1.7" ;data: time = 6328800 ; lat = -89.75, -89.5,
> ...*
>
> On Fri, Apr 26, 2019 at 4:10 PM robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89691 >
> >
> > John, I should have got the dictionary issue and the mismatch of
dates.
> > Is the problem with the climo files something lacking or wrong in
> > the header? I can modify the headers if I know what they need to
be set too.
> > I could also read the climo files into memory and then to write
them
> > back out in the proper netcdf format if I know what MET is looking
for.
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT <met_help at ucar.edu>
> > Sent: Friday, April 26, 2019 7:24 AM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #89691] Climo Erro
-
> > Bad Type
> >
> > > Bob,
> > >
> > > The config file error is coming from parsing the climo_mean
section:
> > > ERROR : DictionaryEntry::dict_value() -> bad type
> > >
> > > Specifically, you set:
> > > field = ["fmcf0020","fmcf8100"];
> > >
> > > Instead, "field" should be an array of dictionaries, like it is
in
> > > the rest of the config file:
> > > field = [ { name = "fmcf0020"; level = "(*,*)"; },
> > > { name = "fmcf8100"; level = "(*,*)"; } ];
> > >
> > > And the number of climo_mean.field entries must match the number
> > > of fcst.field entries.
> > >
> > > At debug level 3 (using met-8.0), I see this status message:
> > > *DEBUG 3: Skipping climatology field since "match_month" is TRUE
> > > but the forecast (20190316_060000) and climatology
> > > (19700101_000000) months do not match for file:
> > > porclds_03_6z_fmcf8100.nc
> > > <http://porclds_03_6z_fmcf8100.nc>*
> > >
> > > The problem is the format of that NetCDF file. It doesn't
follow
> > > a known convention, and MET is unable to parse the timing
> > > information from
> > it.
> > >
> > > Do you have any control over the format of that file?
> > >
> > > Thanks,
> > > John
> > >
> > >
> > >
> > >
> > > On Thu, Apr 11, 2019 at 1:17 PM robert.craig.2 at us.af.mil via RT
<
> > > met_help at ucar.edu> wrote:
> > >
> > >>
> > >> Thu Apr 11 13:13:18 2019: Request 89691 was acted upon.
> > >> Transaction: Ticket created by robert.craig.2 at us.af.mil
> > >> Queue: met_help
> > >> Subject: Climo Erro - Bad Type
> > >> Owner: Nobody
> > >> Requestors: robert.craig.2 at us.af.mil
> > >> Status: new
> > >> Ticket <URL:
> > >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89691
> > >> >
> > >>
> > >>
> > >> John or Julie, I sent relevant data file to you using
AMRDEC_Safe.
> > >> This is a continuation of problem report #85052. When I run
grid
> > >> stat using a total cloud climo file, I get Bad Type error - see
below:
> > >>
> > >> INFO - MET command file executing
> > >> ['/h/WXQC/met-8.1_beta1/bin/grid_stat',
> > >>
'/h/data/global/ENSEMBLE/data/post/GEPS/global/2019031400/grib2.2
> > >> 01
> > >> 90
> > >> 31400.0042.EPOSTOUT',
> > >> '/h/data/global/WXQC/data/met/nc_obs/wwmca/201903151800_p5.nc',
> > >> '/h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated',
> > >> '-outdir',
> > >> '/h/data/global/WXQC/data/met/gdstat/mdlob_pairs/geps/TC',
> > >> '-v', '4'] DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES
file:
> > >> /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
> > >> DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
> > >> /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
> > >> DEBUG 1: Default Config File:
> > >> /h/WXQC/met-8.1_beta1/share/met/config/GridStatConfig_default
> > >> DEBUG 1: User Config File:
> > >> /h/WXQC/met-6.1/data/config/GridStatConfig_geps_tc_updated
> > >> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
> > >> new Met2dDataFile object of type "FileType_Gb2".
> > >> DEBUG 4: Switching the GRIB2 radius of the earth value of
6367.47
> > >> km to
> > >> 6371.2 km for internal consistency.
> > >> DEBUG 4:
> > >> DEBUG 4: Latitude/Longitude Grid Data:
> > >> DEBUG 4: lat_ll: -90
> > >> DEBUG 4: lon_ll: -0
> > >> DEBUG 4: delta_lat: 0.5
> > >> DEBUG 4: delta_lon: 0.5
> > >> DEBUG 4: Nlat: 361
> > >> DEBUG 4: Nlon: 720
> > >> DEBUG 4:
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 1, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 1, parm: 221
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 1, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 1, parm: 225
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 1, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 1, parm: 227
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 1, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 17, parm: 192
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 1, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 19, parm: 241
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 1, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 19, parm: 242
> > >> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
> > >> new Met2dDataFile object of type "FileType_NcMet".
> > >> DEBUG 4:
> > >> DEBUG 4: Latitude/Longitude Grid Data:
> > >> DEBUG 4: lat_ll: -90
> > >> DEBUG 4: lon_ll: -0
> > >> DEBUG 4: delta_lat: 0.5
> > >> DEBUG 4: delta_lon: 0.5
> > >> DEBUG 4: Nlat: 361
> > >> DEBUG 4: Nlon: 720
> > >> DEBUG 4:
> > >> ERROR :
> > >> ERROR : DictionaryEntry::dict_value() -> bad type ERROR :
> > >>
> > >> I edited the climo file per the instructions from John in
problem
> > >> report
> > >> #85052 plus I added a valid time to the header but still can't
> > >> get MET to properly read the file. I can plot the file in
> > >> plot_data_plane but I gives a valid time error. So, what is
> > >> missing from this netCDF file the MET wants? A more general
> > >> suggestion is to provide an addendum to the user guide on what
> > >> MET requires to be in netCDF climo files since these files are
> > >> available from many different
> > sources.
> > >>
> > >> Thanks
> > >> Bob
> > >>
> > >>
> >
> >
> >
> >
>
>
>
>
------------------------------------------------
More information about the Met_help
mailing list