[Met_help] [rt.rap.ucar.edu #86388] History for HIRA Setting Climo Data
Julie Prestopnik via RT
met_help at ucar.edu
Thu Sep 20 15:48:53 MDT 2018
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
John, I have another HIRA question for you. When I run the command line (
/h/WXQC/met-6.1/bin/point_stat
/h/data/global/FSMT/data/GALWEM/RD/output/global_17km/PS.557WW_SC.U_DI.C_GP.
GALWEM-GD_GR.C17KM_AR.GLOBAL_DD.20180501_CY.00_FH.012_DF.GR2
/h/data/global/WXQC/data/met/nc_obs/cdcb/2018050112.nc
/h/WXQC/met-6.1/data/config/PointStatConfig_hira_updated -outdir
/h/data/global/WXQC/data/met/ptstat/mdlob_pairs/global_17km/CB -v 4 ), I get
the following output.
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 14, center: 57, local table: 1,
parm_cat: 13, parm: 192
DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo object of
type "FileType_Gb2".
DEBUG 3:
DEBUG 3: Multiple GRIB2 table entries match lookup criteria (parm_name =
CEIL):
DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 1, grib2_cntr = 57,
grib2_ltab = 1, index_b = 6, index_c = 13
DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 1, grib2_cntr = 0,
grib2_ltab = 0, index_b = 6, index_c = 13
DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 14, grib2_cntr = 57,
grib2_ltab = 0, index_b = 6, index_c = 13
DEBUG 3: Using the first match found: parm_name: CEIL, index_a = 0,
grib2_mtab = 1, grib2_cntr = 57, grib2_ltab = 1, index_b = 6, index_c = 13
DEBUG 3:
DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact match for
"CEIL/L0" in GRIB2 record 1 field 1 of GRIB2 file
"/h/data/global/FSMT/data/GALWEM/RD/output/global_17km/PS.557WW_SC.U_DI.C_GP
.GALWEM-GD_GR.C17KM_AR.GLOBAL_DD.20180430_CY.12_FH.000_DF.GR2"
DEBUG 4:
DEBUG 4: Data plane information:
DEBUG 4: plane min: -82
DEBUG 4: plane max: 15258
DEBUG 4: scan mode: 64
DEBUG 4: valid time: 20180430_120000
DEBUG 4: lead time: 000000
DEBUG 4: init time: 20180430_120000
DEBUG 4: bitmap flag: 0
DEBUG 4:
DEBUG 3: Found 0 climatology fields.
DEBUG 2: For CEIL/L0 found 1 forecast levels, 0 climatology mean levels, and
0 climatology standard deviation levels.
DEBUG 2:
DEBUG 2:
----------------------------------------------------------------------------
----
DEBUG 2:
DEBUG 2: Searching 13708 observations from 13708 messages.
DEBUG 2:
DEBUG 2:
----------------------------------------------------------------------------
----
DEBUG 2:
WARNING:
WARNING: check_hdr_str() -> null string!
WARNING:
DEBUG 2: Processing CEIL/L0 versus (null)/L0, for observation type ADPSFC,
over region FULL, for interpolation method NEAREST(1), using 2599 pairs.
DEBUG 3: Number of matched pairs = 2599
DEBUG 3: Observations processed = 13708
DEBUG 3: Rejected: SID exclusion = 0
DEBUG 3: Rejected: GRIB code = 0
DEBUG 3: Rejected: valid time = 0
DEBUG 3: Rejected: bad obs value = 10469
DEBUG 3: Rejected: off the grid = 2
DEBUG 3: Rejected: level mismatch = 0
DEBUG 3: Rejected: quality marker = 0
DEBUG 3: Rejected: message type = 0
DEBUG 3: Rejected: masking region = 0
DEBUG 3: Rejected: bad fcst value = 638
DEBUG 3: Rejected: duplicates = 0
DEBUG 2: Computing Categorical Statistics.
DEBUG 2: Computing Continuous Statistics.
DEBUG 2: Processing CEIL/L0==0.01 versus (null)/L0>=304, for observation
type ADPSFC, over region FULL, for interpolation method HiRA NBRHD(121),
using 1052 pairs.
MET says it finds the climo data but doesn't seem to use it and the messages
don't tell me why. In this case the climo file is just a persistence file
(model forecast from previous day valid at same diurnal cycle). I attached
the configuration file I am using. Do I have the climo fields set properly
for the HIRA setting?
When I look in the PSTD file the BSS values are all NA. When I look I the
mpr file, all the climo fields are NA.
Another question, does MET use a neighborhood for the climo field as it does
for the forecast field? I ask because the BSS simple is a large negative
number. I would expect it to be closer to 0.
The model files are available on AMRDEC - still up loading.
Thanks for your help.
Bob Craig
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: HIRA Setting Climo Data
From: Julie Prestopnik
Time: Mon Jul 30 10:32:12 2018
Hi Bob.
Unfortunately, John is out of the office this week. I'll respond to
what I
can, but this ticket will likely need some follow up from John when he
is
back.
I am not very familiar with the climatology aspects of MET, however, I
see
in our User's Guide for met-6.1:
// The "climo_cdf_bins" entry should be set either to an integer or an
> array of
> // floats between 0 and 1. When climatological mean and standard
> deviation data
>
I see in your config file that you have:
climo_cdf_bins = [ 1 ];
> //climo_cdf_bins = [ 0, .1, .2, .3, .4, .5, .6, .7, .8, .9, 1 ];
>
You could try setting the following instead:
> climo_cdf_bins = 1;
>
since the User's Guide indicates it should be either an integer or an
array
of floats (as opposed to an array with one integer in it, as it is set
now), and see if that changes anything. Other than that, I believe
that
your climo fields are set properly.
Also, I don't know if you are intending to use the climo_stdev
functionality, but I do see that there is no file_name specified for
that
functionality:
climo_stdev = climo_mean;
> climo_stdev = {
> file_name = [];
> }
>
Regarding your question:
Another question, does MET use a neighborhood for the climo field as
it does
> for the forecast field?
>
I do not know the answer, but I will see what I can do to find out.
Also, I am not familiar with AMRDEC and do not know how to obtain
files
from it.
Please try the above modification to climo_cdf_bins and let me know
how it
goes. Thanks!
Julie
On Mon, Jul 30, 2018 at 9:55 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> Mon Jul 30 09:54:41 2018: Request 86388 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
> Queue: met_help
> Subject: HIRA Setting Climo Data
> Owner: Nobody
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86388 >
>
>
> John, I have another HIRA question for you. When I run the command
line (
> /h/WXQC/met-6.1/bin/point_stat
>
>
/h/data/global/FSMT/data/GALWEM/RD/output/global_17km/PS.557WW_SC.U_DI.C_GP.
> GALWEM-GD_GR.C17KM_AR.GLOBAL_DD.20180501_CY.00_FH.012_DF.GR2
> /h/data/global/WXQC/data/met/nc_obs/cdcb/2018050112.nc
> /h/WXQC/met-6.1/data/config/PointStatConfig_hira_updated -outdir
> /h/data/global/WXQC/data/met/ptstat/mdlob_pairs/global_17km/CB -v 4
), I
> get
> the following output.
>
>
>
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 14, center: 57, local table:
1,
> parm_cat: 13, parm: 192
>
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
> type "FileType_Gb2".
>
> DEBUG 3:
>
> DEBUG 3: Multiple GRIB2 table entries match lookup criteria
(parm_name =
> CEIL):
>
> DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 1, grib2_cntr
= 57,
> grib2_ltab = 1, index_b = 6, index_c = 13
>
> DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 1, grib2_cntr
= 0,
> grib2_ltab = 0, index_b = 6, index_c = 13
>
> DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 14, grib2_cntr
= 57,
> grib2_ltab = 0, index_b = 6, index_c = 13
>
> DEBUG 3: Using the first match found: parm_name: CEIL, index_a =
0,
> grib2_mtab = 1, grib2_cntr = 57, grib2_ltab = 1, index_b = 6,
index_c = 13
>
> DEBUG 3:
>
> DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact match
for
> "CEIL/L0" in GRIB2 record 1 field 1 of GRIB2 file
>
>
"/h/data/global/FSMT/data/GALWEM/RD/output/global_17km/PS.557WW_SC.U_DI.C_GP
> .GALWEM-GD_GR.C17KM_AR.GLOBAL_DD.20180430_CY.12_FH.000_DF.GR2"
>
> DEBUG 4:
>
> DEBUG 4: Data plane information:
>
> DEBUG 4: plane min: -82
>
> DEBUG 4: plane max: 15258
>
> DEBUG 4: scan mode: 64
>
> DEBUG 4: valid time: 20180430_120000
>
> DEBUG 4: lead time: 000000
>
> DEBUG 4: init time: 20180430_120000
>
> DEBUG 4: bitmap flag: 0
>
> DEBUG 4:
>
> DEBUG 3: Found 0 climatology fields.
>
> DEBUG 2: For CEIL/L0 found 1 forecast levels, 0 climatology mean
levels,
> and
> 0 climatology standard deviation levels.
>
> DEBUG 2:
>
> DEBUG 2:
>
>
----------------------------------------------------------------------------
> ----
>
> DEBUG 2:
>
> DEBUG 2: Searching 13708 observations from 13708 messages.
>
> DEBUG 2:
>
> DEBUG 2:
>
>
----------------------------------------------------------------------------
> ----
>
> DEBUG 2:
>
> WARNING:
>
> WARNING: check_hdr_str() -> null string!
>
> WARNING:
>
> DEBUG 2: Processing CEIL/L0 versus (null)/L0, for observation type
ADPSFC,
> over region FULL, for interpolation method NEAREST(1), using 2599
pairs.
>
> DEBUG 3: Number of matched pairs = 2599
>
> DEBUG 3: Observations processed = 13708
>
> DEBUG 3: Rejected: SID exclusion = 0
>
> DEBUG 3: Rejected: GRIB code = 0
>
> DEBUG 3: Rejected: valid time = 0
>
> DEBUG 3: Rejected: bad obs value = 10469
>
> DEBUG 3: Rejected: off the grid = 2
>
> DEBUG 3: Rejected: level mismatch = 0
>
> DEBUG 3: Rejected: quality marker = 0
>
> DEBUG 3: Rejected: message type = 0
>
> DEBUG 3: Rejected: masking region = 0
>
> DEBUG 3: Rejected: bad fcst value = 638
>
> DEBUG 3: Rejected: duplicates = 0
>
> DEBUG 2: Computing Categorical Statistics.
>
> DEBUG 2: Computing Continuous Statistics.
>
> DEBUG 2: Processing CEIL/L0==0.01 versus (null)/L0>=304, for
observation
> type ADPSFC, over region FULL, for interpolation method HiRA
NBRHD(121),
> using 1052 pairs.
>
>
>
> MET says it finds the climo data but doesn't seem to use it and the
> messages
> don't tell me why. In this case the climo file is just a
persistence file
> (model forecast from previous day valid at same diurnal cycle). I
attached
> the configuration file I am using. Do I have the climo fields set
> properly
> for the HIRA setting?
>
>
>
> When I look in the PSTD file the BSS values are all NA. When I look
I the
> mpr file, all the climo fields are NA.
>
>
>
> Another question, does MET use a neighborhood for the climo field as
it
> does
> for the forecast field? I ask because the BSS simple is a large
negative
> number. I would expect it to be closer to 0.
>
>
>
> The model files are available on AMRDEC - still up loading.
>
>
>
> Thanks for your help.
>
>
>
> Bob Craig
>
>
>
>
>
>
>
>
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #86388] HIRA Setting Climo Data
From: robert.craig.2 at us.af.mil
Time: Mon Jul 30 11:16:43 2018
Thanks Julie. The forecast files I was uploading to AMRDEC are bigger
than normal so they are still uploading - probably be there next week
:)
I tried setting the climo_cdf_bins to 1 instead of [1] but that didn't
change anything. In this scenario, I don't have a climo standard
deviation file. I will experiment some more and let you know when
the forecast files are uploaded.
Thanks
Bob
-----Original Message-----
From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
Sent: Monday, July 30, 2018 11:32 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 #86388] HIRA Setting
Climo Data
Hi Bob.
Unfortunately, John is out of the office this week. I'll respond to
what I can, but this ticket will likely need some follow up from John
when he is back.
I am not very familiar with the climatology aspects of MET, however, I
see in our User's Guide for met-6.1:
// The "climo_cdf_bins" entry should be set either to an integer or an
> array of
> // floats between 0 and 1. When climatological mean and standard
> deviation data
>
I see in your config file that you have:
climo_cdf_bins = [ 1 ];
> //climo_cdf_bins = [ 0, .1, .2, .3, .4, .5, .6, .7, .8, .9, 1 ];
>
You could try setting the following instead:
> climo_cdf_bins = 1;
>
since the User's Guide indicates it should be either an integer or an
array of floats (as opposed to an array with one integer in it, as it
is set now), and see if that changes anything. Other than that, I
believe that your climo fields are set properly.
Also, I don't know if you are intending to use the climo_stdev
functionality, but I do see that there is no file_name specified for
that
functionality:
climo_stdev = climo_mean;
> climo_stdev = {
> file_name = [];
> }
>
Regarding your question:
Another question, does MET use a neighborhood for the climo field as
it does
> for the forecast field?
>
I do not know the answer, but I will see what I can do to find out.
Also, I am not familiar with AMRDEC and do not know how to obtain
files from it.
Please try the above modification to climo_cdf_bins and let me know
how it goes. Thanks!
Julie
On Mon, Jul 30, 2018 at 9:55 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> Mon Jul 30 09:54:41 2018: Request 86388 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
> Queue: met_help
> Subject: HIRA Setting Climo Data
> Owner: Nobody
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86388
> >
>
>
> John, I have another HIRA question for you. When I run the command
> line ( /h/WXQC/met-6.1/bin/point_stat
>
>
/h/data/global/FSMT/data/GALWEM/RD/output/global_17km/PS.557WW_SC.U_DI.C_GP.
> GALWEM-GD_GR.C17KM_AR.GLOBAL_DD.20180501_CY.00_FH.012_DF.GR2
> /h/data/global/WXQC/data/met/nc_obs/cdcb/2018050112.nc
> /h/WXQC/met-6.1/data/config/PointStatConfig_hira_updated -outdir
> /h/data/global/WXQC/data/met/ptstat/mdlob_pairs/global_17km/CB -v 4
),
> I get the following output.
>
>
>
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 14, center: 57, local
> table: 1,
> parm_cat: 13, parm: 192
>
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> of type "FileType_Gb2".
>
> DEBUG 3:
>
> DEBUG 3: Multiple GRIB2 table entries match lookup criteria
(parm_name
> =
> CEIL):
>
> DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 1, grib2_cntr
= 57,
> grib2_ltab = 1, index_b = 6, index_c = 13
>
> DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 1, grib2_cntr
= 0,
> grib2_ltab = 0, index_b = 6, index_c = 13
>
> DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 14, grib2_cntr
= 57,
> grib2_ltab = 0, index_b = 6, index_c = 13
>
> DEBUG 3: Using the first match found: parm_name: CEIL, index_a =
0,
> grib2_mtab = 1, grib2_cntr = 57, grib2_ltab = 1, index_b = 6,
index_c
> = 13
>
> DEBUG 3:
>
> DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact match
for
> "CEIL/L0" in GRIB2 record 1 field 1 of GRIB2 file
>
>
"/h/data/global/FSMT/data/GALWEM/RD/output/global_17km/PS.557WW_SC.U_D
> I.C_GP .GALWEM-
GD_GR.C17KM_AR.GLOBAL_DD.20180430_CY.12_FH.000_DF.GR2"
>
> DEBUG 4:
>
> DEBUG 4: Data plane information:
>
> DEBUG 4: plane min: -82
>
> DEBUG 4: plane max: 15258
>
> DEBUG 4: scan mode: 64
>
> DEBUG 4: valid time: 20180430_120000
>
> DEBUG 4: lead time: 000000
>
> DEBUG 4: init time: 20180430_120000
>
> DEBUG 4: bitmap flag: 0
>
> DEBUG 4:
>
> DEBUG 3: Found 0 climatology fields.
>
> DEBUG 2: For CEIL/L0 found 1 forecast levels, 0 climatology mean
> levels, and
> 0 climatology standard deviation levels.
>
> DEBUG 2:
>
> DEBUG 2:
>
>
----------------------------------------------------------------------
> ------
> ----
>
> DEBUG 2:
>
> DEBUG 2: Searching 13708 observations from 13708 messages.
>
> DEBUG 2:
>
> DEBUG 2:
>
>
----------------------------------------------------------------------
> ------
> ----
>
> DEBUG 2:
>
> WARNING:
>
> WARNING: check_hdr_str() -> null string!
>
> WARNING:
>
> DEBUG 2: Processing CEIL/L0 versus (null)/L0, for observation type
> ADPSFC, over region FULL, for interpolation method NEAREST(1), using
2599 pairs.
>
> DEBUG 3: Number of matched pairs = 2599
>
> DEBUG 3: Observations processed = 13708
>
> DEBUG 3: Rejected: SID exclusion = 0
>
> DEBUG 3: Rejected: GRIB code = 0
>
> DEBUG 3: Rejected: valid time = 0
>
> DEBUG 3: Rejected: bad obs value = 10469
>
> DEBUG 3: Rejected: off the grid = 2
>
> DEBUG 3: Rejected: level mismatch = 0
>
> DEBUG 3: Rejected: quality marker = 0
>
> DEBUG 3: Rejected: message type = 0
>
> DEBUG 3: Rejected: masking region = 0
>
> DEBUG 3: Rejected: bad fcst value = 638
>
> DEBUG 3: Rejected: duplicates = 0
>
> DEBUG 2: Computing Categorical Statistics.
>
> DEBUG 2: Computing Continuous Statistics.
>
> DEBUG 2: Processing CEIL/L0==0.01 versus (null)/L0>=304, for
> observation type ADPSFC, over region FULL, for interpolation method
> HiRA NBRHD(121), using 1052 pairs.
>
>
>
> MET says it finds the climo data but doesn't seem to use it and the
> messages
> don't tell me why. In this case the climo file is just a
persistence file
> (model forecast from previous day valid at same diurnal cycle). I
attached
> the configuration file I am using. Do I have the climo fields set
> properly
> for the HIRA setting?
>
>
>
> When I look in the PSTD file the BSS values are all NA. When I look
I
> the mpr file, all the climo fields are NA.
>
>
>
> Another question, does MET use a neighborhood for the climo field as
> it does for the forecast field? I ask because the BSS simple is a
> large negative number. I would expect it to be closer to 0.
>
>
>
> The model files are available on AMRDEC - still up loading.
>
>
>
> Thanks for your help.
>
>
>
> Bob Craig
>
>
>
>
>
>
>
>
>
>
>
------------------------------------------------
Subject: HIRA Setting Climo Data
From: Julie Prestopnik
Time: Mon Jul 30 11:35:14 2018
Thanks, Bob.
Our statistician agrees that the BSS simple being a large negative
number
is a certainly a tip off that something isn't working, but we are not
clear
on if MET uses a neighborhood for the climo field as it does for the
forecast field, although we suspect it would.
John should be able to provide further clarification next week.
Julie
On Mon, Jul 30, 2018 at 11:16 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=86388 >
>
> Thanks Julie. The forecast files I was uploading to AMRDEC are
bigger
> than normal so they are still uploading - probably be there next
week :)
>
> I tried setting the climo_cdf_bins to 1 instead of [1] but that
didn't
> change anything. In this scenario, I don't have a climo standard
deviation
> file. I will experiment some more and let you know when the
forecast
> files are uploaded.
>
> Thanks
> Bob
>
> -----Original Message-----
> From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
> Sent: Monday, July 30, 2018 11:32 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 #86388] HIRA Setting
Climo
> Data
>
> Hi Bob.
>
> Unfortunately, John is out of the office this week. I'll respond to
what
> I can, but this ticket will likely need some follow up from John
when he is
> back.
>
> I am not very familiar with the climatology aspects of MET, however,
I see
> in our User's Guide for met-6.1:
>
> // The "climo_cdf_bins" entry should be set either to an integer or
an
> > array of
> > // floats between 0 and 1. When climatological mean and standard
> > deviation data
> >
>
> I see in your config file that you have:
>
> climo_cdf_bins = [ 1 ];
> > //climo_cdf_bins = [ 0, .1, .2, .3, .4, .5, .6, .7, .8, .9, 1 ];
> >
>
> You could try setting the following instead:
>
>
> > climo_cdf_bins = 1;
> >
>
> since the User's Guide indicates it should be either an integer or
an
> array of floats (as opposed to an array with one integer in it, as
it is
> set now), and see if that changes anything. Other than that, I
believe
> that your climo fields are set properly.
>
> Also, I don't know if you are intending to use the climo_stdev
> functionality, but I do see that there is no file_name specified for
that
> functionality:
>
> climo_stdev = climo_mean;
> > climo_stdev = {
> > file_name = [];
> > }
> >
>
> Regarding your question:
>
> Another question, does MET use a neighborhood for the climo field as
it
> does
> > for the forecast field?
> >
>
> I do not know the answer, but I will see what I can do to find out.
>
> Also, I am not familiar with AMRDEC and do not know how to obtain
files
> from it.
>
> Please try the above modification to climo_cdf_bins and let me know
how it
> goes. Thanks!
>
> Julie
>
>
>
> On Mon, Jul 30, 2018 at 9:55 AM robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Mon Jul 30 09:54:41 2018: Request 86388 was acted upon.
> > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > Queue: met_help
> > Subject: HIRA Setting Climo Data
> > Owner: Nobody
> > Requestors: robert.craig.2 at us.af.mil
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86388
> > >
> >
> >
> > John, I have another HIRA question for you. When I run the
command
> > line ( /h/WXQC/met-6.1/bin/point_stat
> >
> >
>
/h/data/global/FSMT/data/GALWEM/RD/output/global_17km/PS.557WW_SC.U_DI.C_GP.
> > GALWEM-GD_GR.C17KM_AR.GLOBAL_DD.20180501_CY.00_FH.012_DF.GR2
> > /h/data/global/WXQC/data/met/nc_obs/cdcb/2018050112.nc
> > /h/WXQC/met-6.1/data/config/PointStatConfig_hira_updated -outdir
> > /h/data/global/WXQC/data/met/ptstat/mdlob_pairs/global_17km/CB -v
4 ),
> > I get the following output.
> >
> >
> >
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 14, center: 57, local
> > table: 1,
> > parm_cat: 13, parm: 192
> >
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> > of type "FileType_Gb2".
> >
> > DEBUG 3:
> >
> > DEBUG 3: Multiple GRIB2 table entries match lookup criteria
(parm_name
> > =
> > CEIL):
> >
> > DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 1,
grib2_cntr = 57,
> > grib2_ltab = 1, index_b = 6, index_c = 13
> >
> > DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 1,
grib2_cntr = 0,
> > grib2_ltab = 0, index_b = 6, index_c = 13
> >
> > DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 14,
grib2_cntr =
> 57,
> > grib2_ltab = 0, index_b = 6, index_c = 13
> >
> > DEBUG 3: Using the first match found: parm_name: CEIL, index_a =
0,
> > grib2_mtab = 1, grib2_cntr = 57, grib2_ltab = 1, index_b = 6,
index_c
> > = 13
> >
> > DEBUG 3:
> >
> > DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact match
for
> > "CEIL/L0" in GRIB2 record 1 field 1 of GRIB2 file
> >
> >
"/h/data/global/FSMT/data/GALWEM/RD/output/global_17km/PS.557WW_SC.U_D
> > I.C_GP .GALWEM-
GD_GR.C17KM_AR.GLOBAL_DD.20180430_CY.12_FH.000_DF.GR2"
> >
> > DEBUG 4:
> >
> > DEBUG 4: Data plane information:
> >
> > DEBUG 4: plane min: -82
> >
> > DEBUG 4: plane max: 15258
> >
> > DEBUG 4: scan mode: 64
> >
> > DEBUG 4: valid time: 20180430_120000
> >
> > DEBUG 4: lead time: 000000
> >
> > DEBUG 4: init time: 20180430_120000
> >
> > DEBUG 4: bitmap flag: 0
> >
> > DEBUG 4:
> >
> > DEBUG 3: Found 0 climatology fields.
> >
> > DEBUG 2: For CEIL/L0 found 1 forecast levels, 0 climatology mean
> > levels, and
> > 0 climatology standard deviation levels.
> >
> > DEBUG 2:
> >
> > DEBUG 2:
> >
> >
----------------------------------------------------------------------
> > ------
> > ----
> >
> > DEBUG 2:
> >
> > DEBUG 2: Searching 13708 observations from 13708 messages.
> >
> > DEBUG 2:
> >
> > DEBUG 2:
> >
> >
----------------------------------------------------------------------
> > ------
> > ----
> >
> > DEBUG 2:
> >
> > WARNING:
> >
> > WARNING: check_hdr_str() -> null string!
> >
> > WARNING:
> >
> > DEBUG 2: Processing CEIL/L0 versus (null)/L0, for observation type
> > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using
> 2599 pairs.
> >
> > DEBUG 3: Number of matched pairs = 2599
> >
> > DEBUG 3: Observations processed = 13708
> >
> > DEBUG 3: Rejected: SID exclusion = 0
> >
> > DEBUG 3: Rejected: GRIB code = 0
> >
> > DEBUG 3: Rejected: valid time = 0
> >
> > DEBUG 3: Rejected: bad obs value = 10469
> >
> > DEBUG 3: Rejected: off the grid = 2
> >
> > DEBUG 3: Rejected: level mismatch = 0
> >
> > DEBUG 3: Rejected: quality marker = 0
> >
> > DEBUG 3: Rejected: message type = 0
> >
> > DEBUG 3: Rejected: masking region = 0
> >
> > DEBUG 3: Rejected: bad fcst value = 638
> >
> > DEBUG 3: Rejected: duplicates = 0
> >
> > DEBUG 2: Computing Categorical Statistics.
> >
> > DEBUG 2: Computing Continuous Statistics.
> >
> > DEBUG 2: Processing CEIL/L0==0.01 versus (null)/L0>=304, for
> > observation type ADPSFC, over region FULL, for interpolation
method
> > HiRA NBRHD(121), using 1052 pairs.
> >
> >
> >
> > MET says it finds the climo data but doesn't seem to use it and
the
> > messages
> > don't tell me why. In this case the climo file is just a
persistence
> file
> > (model forecast from previous day valid at same diurnal cycle). I
> attached
> > the configuration file I am using. Do I have the climo fields
set
> > properly
> > for the HIRA setting?
> >
> >
> >
> > When I look in the PSTD file the BSS values are all NA. When I
look I
> > the mpr file, all the climo fields are NA.
> >
> >
> >
> > Another question, does MET use a neighborhood for the climo field
as
> > it does for the forecast field? I ask because the BSS simple is a
> > large negative number. I would expect it to be closer to 0.
> >
> >
> >
> > The model files are available on AMRDEC - still up loading.
> >
> >
> >
> > Thanks for your help.
> >
> >
> >
> > Bob Craig
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #86388] HIRA Setting Climo Data
From: robert.craig.2 at us.af.mil
Time: Mon Jul 30 11:38:15 2018
Thanks Julie.
-----Original Message-----
From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
Sent: Monday, July 30, 2018 12:35 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #86388] HIRA
Setting Climo Data
Thanks, Bob.
Our statistician agrees that the BSS simple being a large negative
number is a certainly a tip off that something isn't working, but we
are not clear on if MET uses a neighborhood for the climo field as it
does for the forecast field, although we suspect it would.
John should be able to provide further clarification next week.
Julie
On Mon, Jul 30, 2018 at 11:16 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=86388 >
>
> Thanks Julie. The forecast files I was uploading to AMRDEC are
bigger
> than normal so they are still uploading - probably be there next
week
> :)
>
> I tried setting the climo_cdf_bins to 1 instead of [1] but that
didn't
> change anything. In this scenario, I don't have a climo standard
deviation
> file. I will experiment some more and let you know when the
forecast
> files are uploaded.
>
> Thanks
> Bob
>
> -----Original Message-----
> From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
> Sent: Monday, July 30, 2018 11:32 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 #86388] HIRA Setting
> Climo Data
>
> Hi Bob.
>
> Unfortunately, John is out of the office this week. I'll respond to
> what I can, but this ticket will likely need some follow up from
John
> when he is back.
>
> I am not very familiar with the climatology aspects of MET, however,
I
> see in our User's Guide for met-6.1:
>
> // The "climo_cdf_bins" entry should be set either to an integer or
an
> > array of
> > // floats between 0 and 1. When climatological mean and standard
> > deviation data
> >
>
> I see in your config file that you have:
>
> climo_cdf_bins = [ 1 ];
> > //climo_cdf_bins = [ 0, .1, .2, .3, .4, .5, .6, .7, .8, .9, 1 ];
> >
>
> You could try setting the following instead:
>
>
> > climo_cdf_bins = 1;
> >
>
> since the User's Guide indicates it should be either an integer or
an
> array of floats (as opposed to an array with one integer in it, as
it
> is set now), and see if that changes anything. Other than that, I
> believe that your climo fields are set properly.
>
> Also, I don't know if you are intending to use the climo_stdev
> functionality, but I do see that there is no file_name specified for
> that
> functionality:
>
> climo_stdev = climo_mean;
> > climo_stdev = {
> > file_name = [];
> > }
> >
>
> Regarding your question:
>
> Another question, does MET use a neighborhood for the climo field as
> it does
> > for the forecast field?
> >
>
> I do not know the answer, but I will see what I can do to find out.
>
> Also, I am not familiar with AMRDEC and do not know how to obtain
> files from it.
>
> Please try the above modification to climo_cdf_bins and let me know
> how it goes. Thanks!
>
> Julie
>
>
>
> On Mon, Jul 30, 2018 at 9:55 AM robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Mon Jul 30 09:54:41 2018: Request 86388 was acted upon.
> > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > Queue: met_help
> > Subject: HIRA Setting Climo Data
> > Owner: Nobody
> > Requestors: robert.craig.2 at us.af.mil
> > Status: new
> > Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86388
> > >
> >
> >
> > John, I have another HIRA question for you. When I run the
command
> > line ( /h/WXQC/met-6.1/bin/point_stat
> >
> >
>
/h/data/global/FSMT/data/GALWEM/RD/output/global_17km/PS.557WW_SC.U_DI.C_GP.
> > GALWEM-GD_GR.C17KM_AR.GLOBAL_DD.20180501_CY.00_FH.012_DF.GR2
> > /h/data/global/WXQC/data/met/nc_obs/cdcb/2018050112.nc
> > /h/WXQC/met-6.1/data/config/PointStatConfig_hira_updated -outdir
> > /h/data/global/WXQC/data/met/ptstat/mdlob_pairs/global_17km/CB -v
4
> > ), I get the following output.
> >
> >
> >
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 14, center: 57, local
> > table: 1,
> > parm_cat: 13, parm: 192
> >
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > object of type "FileType_Gb2".
> >
> > DEBUG 3:
> >
> > DEBUG 3: Multiple GRIB2 table entries match lookup criteria
> > (parm_name =
> > CEIL):
> >
> > DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 1,
grib2_cntr = 57,
> > grib2_ltab = 1, index_b = 6, index_c = 13
> >
> > DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 1,
grib2_cntr = 0,
> > grib2_ltab = 0, index_b = 6, index_c = 13
> >
> > DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 14,
grib2_cntr =
> 57,
> > grib2_ltab = 0, index_b = 6, index_c = 13
> >
> > DEBUG 3: Using the first match found: parm_name: CEIL, index_a =
0,
> > grib2_mtab = 1, grib2_cntr = 57, grib2_ltab = 1, index_b = 6,
> > index_c = 13
> >
> > DEBUG 3:
> >
> > DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact match
> > for "CEIL/L0" in GRIB2 record 1 field 1 of GRIB2 file
> >
> >
"/h/data/global/FSMT/data/GALWEM/RD/output/global_17km/PS.557WW_SC.U
> > _D I.C_GP
> > .GALWEM-GD_GR.C17KM_AR.GLOBAL_DD.20180430_CY.12_FH.000_DF.GR2"
> >
> > DEBUG 4:
> >
> > DEBUG 4: Data plane information:
> >
> > DEBUG 4: plane min: -82
> >
> > DEBUG 4: plane max: 15258
> >
> > DEBUG 4: scan mode: 64
> >
> > DEBUG 4: valid time: 20180430_120000
> >
> > DEBUG 4: lead time: 000000
> >
> > DEBUG 4: init time: 20180430_120000
> >
> > DEBUG 4: bitmap flag: 0
> >
> > DEBUG 4:
> >
> > DEBUG 3: Found 0 climatology fields.
> >
> > DEBUG 2: For CEIL/L0 found 1 forecast levels, 0 climatology mean
> > levels, and
> > 0 climatology standard deviation levels.
> >
> > DEBUG 2:
> >
> > DEBUG 2:
> >
> >
--------------------------------------------------------------------
> > --
> > ------
> > ----
> >
> > DEBUG 2:
> >
> > DEBUG 2: Searching 13708 observations from 13708 messages.
> >
> > DEBUG 2:
> >
> > DEBUG 2:
> >
> >
--------------------------------------------------------------------
> > --
> > ------
> > ----
> >
> > DEBUG 2:
> >
> > WARNING:
> >
> > WARNING: check_hdr_str() -> null string!
> >
> > WARNING:
> >
> > DEBUG 2: Processing CEIL/L0 versus (null)/L0, for observation type
> > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using
> 2599 pairs.
> >
> > DEBUG 3: Number of matched pairs = 2599
> >
> > DEBUG 3: Observations processed = 13708
> >
> > DEBUG 3: Rejected: SID exclusion = 0
> >
> > DEBUG 3: Rejected: GRIB code = 0
> >
> > DEBUG 3: Rejected: valid time = 0
> >
> > DEBUG 3: Rejected: bad obs value = 10469
> >
> > DEBUG 3: Rejected: off the grid = 2
> >
> > DEBUG 3: Rejected: level mismatch = 0
> >
> > DEBUG 3: Rejected: quality marker = 0
> >
> > DEBUG 3: Rejected: message type = 0
> >
> > DEBUG 3: Rejected: masking region = 0
> >
> > DEBUG 3: Rejected: bad fcst value = 638
> >
> > DEBUG 3: Rejected: duplicates = 0
> >
> > DEBUG 2: Computing Categorical Statistics.
> >
> > DEBUG 2: Computing Continuous Statistics.
> >
> > DEBUG 2: Processing CEIL/L0==0.01 versus (null)/L0>=304, for
> > observation type ADPSFC, over region FULL, for interpolation
method
> > HiRA NBRHD(121), using 1052 pairs.
> >
> >
> >
> > MET says it finds the climo data but doesn't seem to use it and
the
> > messages
> > don't tell me why. In this case the climo file is just a
persistence
> file
> > (model forecast from previous day valid at same diurnal cycle). I
> attached
> > the configuration file I am using. Do I have the climo fields
set
> > properly
> > for the HIRA setting?
> >
> >
> >
> > When I look in the PSTD file the BSS values are all NA. When I
look
> > I the mpr file, all the climo fields are NA.
> >
> >
> >
> > Another question, does MET use a neighborhood for the climo field
as
> > it does for the forecast field? I ask because the BSS simple is a
> > large negative number. I would expect it to be closer to 0.
> >
> >
> >
> > The model files are available on AMRDEC - still up loading.
> >
> >
> >
> > Thanks for your help.
> >
> >
> >
> > Bob Craig
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #86388] HIRA Setting Climo Data
From: robert.craig.2 at us.af.mil
Time: Mon Jul 30 13:08:12 2018
Julie, I changed the thresholds for the forecast field, obs field, and
climo field to be <= 304 meters (cloud base height), leaving the
threshold for HIRA as ==0.01 and I got a more reasonable BSS_simple
(.05). The question to pass on to John is when I run HIRA, besides
the issue I mention of all the climo fields being NA, in the MPR files
I get model values for the cloud heights for the fcst and obs columns
instead of a HIRA generated probabiliies. If that is to be expected
then it looks like I would have to save off the daily PSTD files to
get a monthly BSS using HIRA instead of using stat analyisis to
accumulate the data in the mpr/stat files. Am I understanding this
right?
Thanks
Bob
-----Original Message-----
From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
Sent: Monday, July 30, 2018 12:35 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #86388] HIRA
Setting Climo Data
Thanks, Bob.
Our statistician agrees that the BSS simple being a large negative
number is a certainly a tip off that something isn't working, but we
are not clear on if MET uses a neighborhood for the climo field as it
does for the forecast field, although we suspect it would.
John should be able to provide further clarification next week.
Julie
On Mon, Jul 30, 2018 at 11:16 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=86388 >
>
> Thanks Julie. The forecast files I was uploading to AMRDEC are
bigger
> than normal so they are still uploading - probably be there next
week
> :)
>
> I tried setting the climo_cdf_bins to 1 instead of [1] but that
didn't
> change anything. In this scenario, I don't have a climo standard
deviation
> file. I will experiment some more and let you know when the
forecast
> files are uploaded.
>
> Thanks
> Bob
>
> -----Original Message-----
> From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
> Sent: Monday, July 30, 2018 11:32 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 #86388] HIRA Setting
> Climo Data
>
> Hi Bob.
>
> Unfortunately, John is out of the office this week. I'll respond to
> what I can, but this ticket will likely need some follow up from
John
> when he is back.
>
> I am not very familiar with the climatology aspects of MET, however,
I
> see in our User's Guide for met-6.1:
>
> // The "climo_cdf_bins" entry should be set either to an integer or
an
> > array of
> > // floats between 0 and 1. When climatological mean and standard
> > deviation data
> >
>
> I see in your config file that you have:
>
> climo_cdf_bins = [ 1 ];
> > //climo_cdf_bins = [ 0, .1, .2, .3, .4, .5, .6, .7, .8, .9, 1 ];
> >
>
> You could try setting the following instead:
>
>
> > climo_cdf_bins = 1;
> >
>
> since the User's Guide indicates it should be either an integer or
an
> array of floats (as opposed to an array with one integer in it, as
it
> is set now), and see if that changes anything. Other than that, I
> believe that your climo fields are set properly.
>
> Also, I don't know if you are intending to use the climo_stdev
> functionality, but I do see that there is no file_name specified for
> that
> functionality:
>
> climo_stdev = climo_mean;
> > climo_stdev = {
> > file_name = [];
> > }
> >
>
> Regarding your question:
>
> Another question, does MET use a neighborhood for the climo field as
> it does
> > for the forecast field?
> >
>
> I do not know the answer, but I will see what I can do to find out.
>
> Also, I am not familiar with AMRDEC and do not know how to obtain
> files from it.
>
> Please try the above modification to climo_cdf_bins and let me know
> how it goes. Thanks!
>
> Julie
>
>
>
> On Mon, Jul 30, 2018 at 9:55 AM robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Mon Jul 30 09:54:41 2018: Request 86388 was acted upon.
> > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > Queue: met_help
> > Subject: HIRA Setting Climo Data
> > Owner: Nobody
> > Requestors: robert.craig.2 at us.af.mil
> > Status: new
> > Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86388
> > >
> >
> >
> > John, I have another HIRA question for you. When I run the
command
> > line ( /h/WXQC/met-6.1/bin/point_stat
> >
> >
>
/h/data/global/FSMT/data/GALWEM/RD/output/global_17km/PS.557WW_SC.U_DI.C_GP.
> > GALWEM-GD_GR.C17KM_AR.GLOBAL_DD.20180501_CY.00_FH.012_DF.GR2
> > /h/data/global/WXQC/data/met/nc_obs/cdcb/2018050112.nc
> > /h/WXQC/met-6.1/data/config/PointStatConfig_hira_updated -outdir
> > /h/data/global/WXQC/data/met/ptstat/mdlob_pairs/global_17km/CB -v
4
> > ), I get the following output.
> >
> >
> >
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 14, center: 57, local
> > table: 1,
> > parm_cat: 13, parm: 192
> >
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > object of type "FileType_Gb2".
> >
> > DEBUG 3:
> >
> > DEBUG 3: Multiple GRIB2 table entries match lookup criteria
> > (parm_name =
> > CEIL):
> >
> > DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 1,
grib2_cntr = 57,
> > grib2_ltab = 1, index_b = 6, index_c = 13
> >
> > DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 1,
grib2_cntr = 0,
> > grib2_ltab = 0, index_b = 6, index_c = 13
> >
> > DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 14,
grib2_cntr =
> 57,
> > grib2_ltab = 0, index_b = 6, index_c = 13
> >
> > DEBUG 3: Using the first match found: parm_name: CEIL, index_a =
0,
> > grib2_mtab = 1, grib2_cntr = 57, grib2_ltab = 1, index_b = 6,
> > index_c = 13
> >
> > DEBUG 3:
> >
> > DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact match
> > for "CEIL/L0" in GRIB2 record 1 field 1 of GRIB2 file
> >
> >
"/h/data/global/FSMT/data/GALWEM/RD/output/global_17km/PS.557WW_SC.U
> > _D I.C_GP
> > .GALWEM-GD_GR.C17KM_AR.GLOBAL_DD.20180430_CY.12_FH.000_DF.GR2"
> >
> > DEBUG 4:
> >
> > DEBUG 4: Data plane information:
> >
> > DEBUG 4: plane min: -82
> >
> > DEBUG 4: plane max: 15258
> >
> > DEBUG 4: scan mode: 64
> >
> > DEBUG 4: valid time: 20180430_120000
> >
> > DEBUG 4: lead time: 000000
> >
> > DEBUG 4: init time: 20180430_120000
> >
> > DEBUG 4: bitmap flag: 0
> >
> > DEBUG 4:
> >
> > DEBUG 3: Found 0 climatology fields.
> >
> > DEBUG 2: For CEIL/L0 found 1 forecast levels, 0 climatology mean
> > levels, and
> > 0 climatology standard deviation levels.
> >
> > DEBUG 2:
> >
> > DEBUG 2:
> >
> >
--------------------------------------------------------------------
> > --
> > ------
> > ----
> >
> > DEBUG 2:
> >
> > DEBUG 2: Searching 13708 observations from 13708 messages.
> >
> > DEBUG 2:
> >
> > DEBUG 2:
> >
> >
--------------------------------------------------------------------
> > --
> > ------
> > ----
> >
> > DEBUG 2:
> >
> > WARNING:
> >
> > WARNING: check_hdr_str() -> null string!
> >
> > WARNING:
> >
> > DEBUG 2: Processing CEIL/L0 versus (null)/L0, for observation type
> > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using
> 2599 pairs.
> >
> > DEBUG 3: Number of matched pairs = 2599
> >
> > DEBUG 3: Observations processed = 13708
> >
> > DEBUG 3: Rejected: SID exclusion = 0
> >
> > DEBUG 3: Rejected: GRIB code = 0
> >
> > DEBUG 3: Rejected: valid time = 0
> >
> > DEBUG 3: Rejected: bad obs value = 10469
> >
> > DEBUG 3: Rejected: off the grid = 2
> >
> > DEBUG 3: Rejected: level mismatch = 0
> >
> > DEBUG 3: Rejected: quality marker = 0
> >
> > DEBUG 3: Rejected: message type = 0
> >
> > DEBUG 3: Rejected: masking region = 0
> >
> > DEBUG 3: Rejected: bad fcst value = 638
> >
> > DEBUG 3: Rejected: duplicates = 0
> >
> > DEBUG 2: Computing Categorical Statistics.
> >
> > DEBUG 2: Computing Continuous Statistics.
> >
> > DEBUG 2: Processing CEIL/L0==0.01 versus (null)/L0>=304, for
> > observation type ADPSFC, over region FULL, for interpolation
method
> > HiRA NBRHD(121), using 1052 pairs.
> >
> >
> >
> > MET says it finds the climo data but doesn't seem to use it and
the
> > messages
> > don't tell me why. In this case the climo file is just a
persistence
> file
> > (model forecast from previous day valid at same diurnal cycle). I
> attached
> > the configuration file I am using. Do I have the climo fields
set
> > properly
> > for the HIRA setting?
> >
> >
> >
> > When I look in the PSTD file the BSS values are all NA. When I
look
> > I the mpr file, all the climo fields are NA.
> >
> >
> >
> > Another question, does MET use a neighborhood for the climo field
as
> > it does for the forecast field? I ask because the BSS simple is a
> > large negative number. I would expect it to be closer to 0.
> >
> >
> >
> > The model files are available on AMRDEC - still up loading.
> >
> >
> >
> > Thanks for your help.
> >
> >
> >
> > Bob Craig
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: HIRA Setting Climo Data
From: Julie Prestopnik
Time: Mon Jul 30 13:52:47 2018
Hi Bob.
I do believe it is correct that you need to save off the daily PSTD
files
to get a monthly BSS using HIRA instead of using stat analysis to
accumulate the data in the mpr/stat files, however I will have John
follow
up when he gets back to be sure.
Thanks,
Julie
On Mon, Jul 30, 2018 at 1:08 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=86388 >
>
> Julie, I changed the thresholds for the forecast field, obs field,
and
> climo field to be <= 304 meters (cloud base height), leaving the
threshold
> for HIRA as ==0.01 and I got a more reasonable BSS_simple (.05).
The
> question to pass on to John is when I run HIRA, besides the issue I
mention
> of all the climo fields being NA, in the MPR files I get model
values for
> the cloud heights for the fcst and obs columns instead of a HIRA
generated
> probabiliies. If that is to be expected then it looks like I would
have to
> save off the daily PSTD files to get a monthly BSS using HIRA
instead of
> using stat analyisis to accumulate the data in the mpr/stat files.
Am I
> understanding this right?
>
> Thanks
> Bob
>
> -----Original Message-----
> From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
> Sent: Monday, July 30, 2018 12:35 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #86388] HIRA
Setting
> Climo Data
>
> Thanks, Bob.
>
> Our statistician agrees that the BSS simple being a large negative
number
> is a certainly a tip off that something isn't working, but we are
not clear
> on if MET uses a neighborhood for the climo field as it does for the
> forecast field, although we suspect it would.
>
> John should be able to provide further clarification next week.
>
> Julie
>
>
> On Mon, Jul 30, 2018 at 11:16 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=86388 >
> >
> > Thanks Julie. The forecast files I was uploading to AMRDEC are
bigger
> > than normal so they are still uploading - probably be there next
week
> > :)
> >
> > I tried setting the climo_cdf_bins to 1 instead of [1] but that
didn't
> > change anything. In this scenario, I don't have a climo standard
> deviation
> > file. I will experiment some more and let you know when the
forecast
> > files are uploaded.
> >
> > Thanks
> > Bob
> >
> > -----Original Message-----
> > From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
> > Sent: Monday, July 30, 2018 11:32 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 #86388] HIRA
Setting
> > Climo Data
> >
> > Hi Bob.
> >
> > Unfortunately, John is out of the office this week. I'll respond
to
> > what I can, but this ticket will likely need some follow up from
John
> > when he is back.
> >
> > I am not very familiar with the climatology aspects of MET,
however, I
> > see in our User's Guide for met-6.1:
> >
> > // The "climo_cdf_bins" entry should be set either to an integer
or an
> > > array of
> > > // floats between 0 and 1. When climatological mean and
standard
> > > deviation data
> > >
> >
> > I see in your config file that you have:
> >
> > climo_cdf_bins = [ 1 ];
> > > //climo_cdf_bins = [ 0, .1, .2, .3, .4, .5, .6, .7, .8, .9, 1
];
> > >
> >
> > You could try setting the following instead:
> >
> >
> > > climo_cdf_bins = 1;
> > >
> >
> > since the User's Guide indicates it should be either an integer or
an
> > array of floats (as opposed to an array with one integer in it, as
it
> > is set now), and see if that changes anything. Other than that, I
> > believe that your climo fields are set properly.
> >
> > Also, I don't know if you are intending to use the climo_stdev
> > functionality, but I do see that there is no file_name specified
for
> > that
> > functionality:
> >
> > climo_stdev = climo_mean;
> > > climo_stdev = {
> > > file_name = [];
> > > }
> > >
> >
> > Regarding your question:
> >
> > Another question, does MET use a neighborhood for the climo field
as
> > it does
> > > for the forecast field?
> > >
> >
> > I do not know the answer, but I will see what I can do to find
out.
> >
> > Also, I am not familiar with AMRDEC and do not know how to obtain
> > files from it.
> >
> > Please try the above modification to climo_cdf_bins and let me
know
> > how it goes. Thanks!
> >
> > Julie
> >
> >
> >
> > On Mon, Jul 30, 2018 at 9:55 AM robert.craig.2 at us.af.mil via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Mon Jul 30 09:54:41 2018: Request 86388 was acted upon.
> > > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > > Queue: met_help
> > > Subject: HIRA Setting Climo Data
> > > Owner: Nobody
> > > Requestors: robert.craig.2 at us.af.mil
> > > Status: new
> > > Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86388
> > > >
> > >
> > >
> > > John, I have another HIRA question for you. When I run the
command
> > > line ( /h/WXQC/met-6.1/bin/point_stat
> > >
> > >
> >
>
/h/data/global/FSMT/data/GALWEM/RD/output/global_17km/PS.557WW_SC.U_DI.C_GP.
> > > GALWEM-GD_GR.C17KM_AR.GLOBAL_DD.20180501_CY.00_FH.012_DF.GR2
> > > /h/data/global/WXQC/data/met/nc_obs/cdcb/2018050112.nc
> > > /h/WXQC/met-6.1/data/config/PointStatConfig_hira_updated -outdir
> > > /h/data/global/WXQC/data/met/ptstat/mdlob_pairs/global_17km/CB
-v 4
> > > ), I get the following output.
> > >
> > >
> > >
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 14, center: 57,
local
> > > table: 1,
> > > parm_cat: 13, parm: 192
> > >
> > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > > object of type "FileType_Gb2".
> > >
> > > DEBUG 3:
> > >
> > > DEBUG 3: Multiple GRIB2 table entries match lookup criteria
> > > (parm_name =
> > > CEIL):
> > >
> > > DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 1,
grib2_cntr =
> 57,
> > > grib2_ltab = 1, index_b = 6, index_c = 13
> > >
> > > DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 1,
grib2_cntr =
> 0,
> > > grib2_ltab = 0, index_b = 6, index_c = 13
> > >
> > > DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 14,
grib2_cntr =
> > 57,
> > > grib2_ltab = 0, index_b = 6, index_c = 13
> > >
> > > DEBUG 3: Using the first match found: parm_name: CEIL, index_a
= 0,
> > > grib2_mtab = 1, grib2_cntr = 57, grib2_ltab = 1, index_b = 6,
> > > index_c = 13
> > >
> > > DEBUG 3:
> > >
> > > DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact
match
> > > for "CEIL/L0" in GRIB2 record 1 field 1 of GRIB2 file
> > >
> > >
"/h/data/global/FSMT/data/GALWEM/RD/output/global_17km/PS.557WW_SC.U
> > > _D I.C_GP
> > > .GALWEM-GD_GR.C17KM_AR.GLOBAL_DD.20180430_CY.12_FH.000_DF.GR2"
> > >
> > > DEBUG 4:
> > >
> > > DEBUG 4: Data plane information:
> > >
> > > DEBUG 4: plane min: -82
> > >
> > > DEBUG 4: plane max: 15258
> > >
> > > DEBUG 4: scan mode: 64
> > >
> > > DEBUG 4: valid time: 20180430_120000
> > >
> > > DEBUG 4: lead time: 000000
> > >
> > > DEBUG 4: init time: 20180430_120000
> > >
> > > DEBUG 4: bitmap flag: 0
> > >
> > > DEBUG 4:
> > >
> > > DEBUG 3: Found 0 climatology fields.
> > >
> > > DEBUG 2: For CEIL/L0 found 1 forecast levels, 0 climatology mean
> > > levels, and
> > > 0 climatology standard deviation levels.
> > >
> > > DEBUG 2:
> > >
> > > DEBUG 2:
> > >
> > >
--------------------------------------------------------------------
> > > --
> > > ------
> > > ----
> > >
> > > DEBUG 2:
> > >
> > > DEBUG 2: Searching 13708 observations from 13708 messages.
> > >
> > > DEBUG 2:
> > >
> > > DEBUG 2:
> > >
> > >
--------------------------------------------------------------------
> > > --
> > > ------
> > > ----
> > >
> > > DEBUG 2:
> > >
> > > WARNING:
> > >
> > > WARNING: check_hdr_str() -> null string!
> > >
> > > WARNING:
> > >
> > > DEBUG 2: Processing CEIL/L0 versus (null)/L0, for observation
type
> > > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using
> > 2599 pairs.
> > >
> > > DEBUG 3: Number of matched pairs = 2599
> > >
> > > DEBUG 3: Observations processed = 13708
> > >
> > > DEBUG 3: Rejected: SID exclusion = 0
> > >
> > > DEBUG 3: Rejected: GRIB code = 0
> > >
> > > DEBUG 3: Rejected: valid time = 0
> > >
> > > DEBUG 3: Rejected: bad obs value = 10469
> > >
> > > DEBUG 3: Rejected: off the grid = 2
> > >
> > > DEBUG 3: Rejected: level mismatch = 0
> > >
> > > DEBUG 3: Rejected: quality marker = 0
> > >
> > > DEBUG 3: Rejected: message type = 0
> > >
> > > DEBUG 3: Rejected: masking region = 0
> > >
> > > DEBUG 3: Rejected: bad fcst value = 638
> > >
> > > DEBUG 3: Rejected: duplicates = 0
> > >
> > > DEBUG 2: Computing Categorical Statistics.
> > >
> > > DEBUG 2: Computing Continuous Statistics.
> > >
> > > DEBUG 2: Processing CEIL/L0==0.01 versus (null)/L0>=304, for
> > > observation type ADPSFC, over region FULL, for interpolation
method
> > > HiRA NBRHD(121), using 1052 pairs.
> > >
> > >
> > >
> > > MET says it finds the climo data but doesn't seem to use it and
the
> > > messages
> > > don't tell me why. In this case the climo file is just a
persistence
> > file
> > > (model forecast from previous day valid at same diurnal cycle).
I
> > attached
> > > the configuration file I am using. Do I have the climo fields
set
> > > properly
> > > for the HIRA setting?
> > >
> > >
> > >
> > > When I look in the PSTD file the BSS values are all NA. When I
look
> > > I the mpr file, all the climo fields are NA.
> > >
> > >
> > >
> > > Another question, does MET use a neighborhood for the climo
field as
> > > it does for the forecast field? I ask because the BSS simple is
a
> > > large negative number. I would expect it to be closer to 0.
> > >
> > >
> > >
> > > The model files are available on AMRDEC - still up loading.
> > >
> > >
> > >
> > > Thanks for your help.
> > >
> > >
> > >
> > > Bob Craig
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: FW: [Non-DoD Source] Re: [rt.rap.ucar.edu #86388] HIRA Setting Climo Data
From: robert.craig.2 at us.af.mil
Time: Mon Jul 30 15:31:59 2018
Julie, again for John, I finally looked further down through the MPR
file and now see where the HIRA neighborhood probabilities show up in
the fcst field. The obs field still has the ob value instead of a 0
or 1 indicating the ob reached the threshold or not (ceiling < 304
meters). Is it supposed to be doing this? And the climo fields are
still NA. I calculated out the data in the MPR file assuming the
threshold was applied to the obs value and I got the same result the
MET calculated. If stat_analysis handles these mpr files correctly
then all is well. So the only remaining issue is the NA for the climo
fields.
Bob
-----Original Message-----
From: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
Sent: Monday, July 30, 2018 2:08 PM
To: 'met_help at ucar.edu' <met_help at ucar.edu>
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #86388] HIRA
Setting Climo Data
Julie, I changed the thresholds for the forecast field, obs field, and
climo field to be <= 304 meters (cloud base height), leaving the
threshold for HIRA as ==0.01 and I got a more reasonable BSS_simple
(.05). The question to pass on to John is when I run HIRA, besides
the issue I mention of all the climo fields being NA, in the MPR files
I get model values for the cloud heights for the fcst and obs columns
instead of a HIRA generated probabiliies. If that is to be expected
then it looks like I would have to save off the daily PSTD files to
get a monthly BSS using HIRA instead of using stat analyisis to
accumulate the data in the mpr/stat files. Am I understanding this
right?
Thanks
Bob
-----Original Message-----
From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
Sent: Monday, July 30, 2018 12:35 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #86388] HIRA
Setting Climo Data
Thanks, Bob.
Our statistician agrees that the BSS simple being a large negative
number is a certainly a tip off that something isn't working, but we
are not clear on if MET uses a neighborhood for the climo field as it
does for the forecast field, although we suspect it would.
John should be able to provide further clarification next week.
Julie
On Mon, Jul 30, 2018 at 11:16 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=86388 >
>
> Thanks Julie. The forecast files I was uploading to AMRDEC are
bigger
> than normal so they are still uploading - probably be there next
week
> :)
>
> I tried setting the climo_cdf_bins to 1 instead of [1] but that
didn't
> change anything. In this scenario, I don't have a climo standard
deviation
> file. I will experiment some more and let you know when the
forecast
> files are uploaded.
>
> Thanks
> Bob
>
> -----Original Message-----
> From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
> Sent: Monday, July 30, 2018 11:32 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 #86388] HIRA Setting
> Climo Data
>
> Hi Bob.
>
> Unfortunately, John is out of the office this week. I'll respond to
> what I can, but this ticket will likely need some follow up from
John
> when he is back.
>
> I am not very familiar with the climatology aspects of MET, however,
I
> see in our User's Guide for met-6.1:
>
> // The "climo_cdf_bins" entry should be set either to an integer or
an
> > array of
> > // floats between 0 and 1. When climatological mean and standard
> > deviation data
> >
>
> I see in your config file that you have:
>
> climo_cdf_bins = [ 1 ];
> > //climo_cdf_bins = [ 0, .1, .2, .3, .4, .5, .6, .7, .8, .9, 1 ];
> >
>
> You could try setting the following instead:
>
>
> > climo_cdf_bins = 1;
> >
>
> since the User's Guide indicates it should be either an integer or
an
> array of floats (as opposed to an array with one integer in it, as
it
> is set now), and see if that changes anything. Other than that, I
> believe that your climo fields are set properly.
>
> Also, I don't know if you are intending to use the climo_stdev
> functionality, but I do see that there is no file_name specified for
> that
> functionality:
>
> climo_stdev = climo_mean;
> > climo_stdev = {
> > file_name = [];
> > }
> >
>
> Regarding your question:
>
> Another question, does MET use a neighborhood for the climo field as
> it does
> > for the forecast field?
> >
>
> I do not know the answer, but I will see what I can do to find out.
>
> Also, I am not familiar with AMRDEC and do not know how to obtain
> files from it.
>
> Please try the above modification to climo_cdf_bins and let me know
> how it goes. Thanks!
>
> Julie
>
>
>
> On Mon, Jul 30, 2018 at 9:55 AM robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Mon Jul 30 09:54:41 2018: Request 86388 was acted upon.
> > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > Queue: met_help
> > Subject: HIRA Setting Climo Data
> > Owner: Nobody
> > Requestors: robert.craig.2 at us.af.mil
> > Status: new
> > Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86388
> > >
> >
> >
> > John, I have another HIRA question for you. When I run the
command
> > line ( /h/WXQC/met-6.1/bin/point_stat
> >
> >
>
/h/data/global/FSMT/data/GALWEM/RD/output/global_17km/PS.557WW_SC.U_DI.C_GP.
> > GALWEM-GD_GR.C17KM_AR.GLOBAL_DD.20180501_CY.00_FH.012_DF.GR2
> > /h/data/global/WXQC/data/met/nc_obs/cdcb/2018050112.nc
> > /h/WXQC/met-6.1/data/config/PointStatConfig_hira_updated -outdir
> > /h/data/global/WXQC/data/met/ptstat/mdlob_pairs/global_17km/CB -v
4
> > ), I get the following output.
> >
> >
> >
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 14, center: 57, local
> > table: 1,
> > parm_cat: 13, parm: 192
> >
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > object of type "FileType_Gb2".
> >
> > DEBUG 3:
> >
> > DEBUG 3: Multiple GRIB2 table entries match lookup criteria
> > (parm_name =
> > CEIL):
> >
> > DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 1,
grib2_cntr = 57,
> > grib2_ltab = 1, index_b = 6, index_c = 13
> >
> > DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 1,
grib2_cntr = 0,
> > grib2_ltab = 0, index_b = 6, index_c = 13
> >
> > DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 14,
grib2_cntr =
> 57,
> > grib2_ltab = 0, index_b = 6, index_c = 13
> >
> > DEBUG 3: Using the first match found: parm_name: CEIL, index_a =
0,
> > grib2_mtab = 1, grib2_cntr = 57, grib2_ltab = 1, index_b = 6,
> > index_c = 13
> >
> > DEBUG 3:
> >
> > DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact match
> > for "CEIL/L0" in GRIB2 record 1 field 1 of GRIB2 file
> >
> >
"/h/data/global/FSMT/data/GALWEM/RD/output/global_17km/PS.557WW_SC.U
> > _D I.C_GP
> > .GALWEM-GD_GR.C17KM_AR.GLOBAL_DD.20180430_CY.12_FH.000_DF.GR2"
> >
> > DEBUG 4:
> >
> > DEBUG 4: Data plane information:
> >
> > DEBUG 4: plane min: -82
> >
> > DEBUG 4: plane max: 15258
> >
> > DEBUG 4: scan mode: 64
> >
> > DEBUG 4: valid time: 20180430_120000
> >
> > DEBUG 4: lead time: 000000
> >
> > DEBUG 4: init time: 20180430_120000
> >
> > DEBUG 4: bitmap flag: 0
> >
> > DEBUG 4:
> >
> > DEBUG 3: Found 0 climatology fields.
> >
> > DEBUG 2: For CEIL/L0 found 1 forecast levels, 0 climatology mean
> > levels, and
> > 0 climatology standard deviation levels.
> >
> > DEBUG 2:
> >
> > DEBUG 2:
> >
> >
--------------------------------------------------------------------
> > --
> > ------
> > ----
> >
> > DEBUG 2:
> >
> > DEBUG 2: Searching 13708 observations from 13708 messages.
> >
> > DEBUG 2:
> >
> > DEBUG 2:
> >
> >
--------------------------------------------------------------------
> > --
> > ------
> > ----
> >
> > DEBUG 2:
> >
> > WARNING:
> >
> > WARNING: check_hdr_str() -> null string!
> >
> > WARNING:
> >
> > DEBUG 2: Processing CEIL/L0 versus (null)/L0, for observation type
> > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using
> 2599 pairs.
> >
> > DEBUG 3: Number of matched pairs = 2599
> >
> > DEBUG 3: Observations processed = 13708
> >
> > DEBUG 3: Rejected: SID exclusion = 0
> >
> > DEBUG 3: Rejected: GRIB code = 0
> >
> > DEBUG 3: Rejected: valid time = 0
> >
> > DEBUG 3: Rejected: bad obs value = 10469
> >
> > DEBUG 3: Rejected: off the grid = 2
> >
> > DEBUG 3: Rejected: level mismatch = 0
> >
> > DEBUG 3: Rejected: quality marker = 0
> >
> > DEBUG 3: Rejected: message type = 0
> >
> > DEBUG 3: Rejected: masking region = 0
> >
> > DEBUG 3: Rejected: bad fcst value = 638
> >
> > DEBUG 3: Rejected: duplicates = 0
> >
> > DEBUG 2: Computing Categorical Statistics.
> >
> > DEBUG 2: Computing Continuous Statistics.
> >
> > DEBUG 2: Processing CEIL/L0==0.01 versus (null)/L0>=304, for
> > observation type ADPSFC, over region FULL, for interpolation
method
> > HiRA NBRHD(121), using 1052 pairs.
> >
> >
> >
> > MET says it finds the climo data but doesn't seem to use it and
the
> > messages
> > don't tell me why. In this case the climo file is just a
persistence
> file
> > (model forecast from previous day valid at same diurnal cycle). I
> attached
> > the configuration file I am using. Do I have the climo fields
set
> > properly
> > for the HIRA setting?
> >
> >
> >
> > When I look in the PSTD file the BSS values are all NA. When I
look
> > I the mpr file, all the climo fields are NA.
> >
> >
> >
> > Another question, does MET use a neighborhood for the climo field
as
> > it does for the forecast field? I ask because the BSS simple is a
> > large negative number. I would expect it to be closer to 0.
> >
> >
> >
> > The model files are available on AMRDEC - still up loading.
> >
> >
> >
> > Thanks for your help.
> >
> >
> >
> > Bob Craig
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: HIRA Setting Climo Data
From: John Halley Gotway
Time: Wed Aug 08 16:57:52 2018
Hi Bob,
Sorry for the long delay in getting back to you on this. I grabbed
the
sample data you posted to the ARMDEC site and was able to reproduce
exactly
the same log messages you're getting from Point-Stat. Perhaps all the
log
messages are confusing, but they do indicate that no matching
climatology
data was found:
DEBUG 3: Found 0 climatology fields.
DEBUG 2: For CEIL/L0 found 1 forecast levels, 0 climatology mean
levels,
and 0 climatology standard deviation levels.
So I would fully expect that the CLIMO_MEAN column of the MPR output
lines
would contain NA, meaning that no climatology data was used.
I suspect the real question is *why not*?
You're evaluating a GALWEM model output data that's valid at this
timestamp: 20180501_120000
And you're providing "climatology" data that's valid at this
timestamp:
20180430_120000
Notice that the forecast is valid in May and the climo data is valid
in
April.
This "climo_mean" logic was set up with NCEP data in mind. They have
2
specific climatology data sources. One is valid monthly... and the
other
is valid daily. When MET goes hunting for a climatology data use, it
only
considers climo data whose month matches the month of the forecast
valid
time. Additionally, if "match_day = TRUE", it only considers data
when the
days match.
In your example, the months do not match, so grid_stat will never find
a
match! By way of testing, I passed the same file in for the forecast
and
the climo_mean and reran. And yes, that does produce a climo match
and
populate the CLIMO_MEAN output column of MPR.
Clearly, the existing logic doesn't handle well the way the AF defines
climatologies. We need to update the search parameter logic to allow
for
this type of climo definition.
Does that all make sense to you?
Thanks,
John
On Mon, Jul 30, 2018 at 3:32 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=86388 >
>
> Julie, again for John, I finally looked further down through the MPR
file
> and now see where the HIRA neighborhood probabilities show up in the
fcst
> field. The obs field still has the ob value instead of a 0 or 1
indicating
> the ob reached the threshold or not (ceiling < 304 meters). Is it
> supposed to be doing this? And the climo fields are still NA. I
> calculated out the data in the MPR file assuming the threshold was
applied
> to the obs value and I got the same result the MET calculated. If
> stat_analysis handles these mpr files correctly then all is well.
So the
> only remaining issue is the NA for the climo fields.
>
> Bob
>
> -----Original Message-----
> From: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> Sent: Monday, July 30, 2018 2:08 PM
> To: 'met_help at ucar.edu' <met_help at ucar.edu>
> Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #86388] HIRA
Setting
> Climo Data
>
> Julie, I changed the thresholds for the forecast field, obs field,
and
> climo field to be <= 304 meters (cloud base height), leaving the
threshold
> for HIRA as ==0.01 and I got a more reasonable BSS_simple (.05).
The
> question to pass on to John is when I run HIRA, besides the issue I
mention
> of all the climo fields being NA, in the MPR files I get model
values for
> the cloud heights for the fcst and obs columns instead of a HIRA
generated
> probabiliies. If that is to be expected then it looks like I would
have to
> save off the daily PSTD files to get a monthly BSS using HIRA
instead of
> using stat analyisis to accumulate the data in the mpr/stat files.
Am I
> understanding this right?
>
> Thanks
> Bob
>
> -----Original Message-----
> From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
> Sent: Monday, July 30, 2018 12:35 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #86388] HIRA
Setting
> Climo Data
>
> Thanks, Bob.
>
> Our statistician agrees that the BSS simple being a large negative
number
> is a certainly a tip off that something isn't working, but we are
not clear
> on if MET uses a neighborhood for the climo field as it does for the
> forecast field, although we suspect it would.
>
> John should be able to provide further clarification next week.
>
> Julie
>
>
> On Mon, Jul 30, 2018 at 11:16 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=86388 >
> >
> > Thanks Julie. The forecast files I was uploading to AMRDEC are
bigger
> > than normal so they are still uploading - probably be there next
week
> > :)
> >
> > I tried setting the climo_cdf_bins to 1 instead of [1] but that
didn't
> > change anything. In this scenario, I don't have a climo standard
> deviation
> > file. I will experiment some more and let you know when the
forecast
> > files are uploaded.
> >
> > Thanks
> > Bob
> >
> > -----Original Message-----
> > From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
> > Sent: Monday, July 30, 2018 11:32 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 #86388] HIRA
Setting
> > Climo Data
> >
> > Hi Bob.
> >
> > Unfortunately, John is out of the office this week. I'll respond
to
> > what I can, but this ticket will likely need some follow up from
John
> > when he is back.
> >
> > I am not very familiar with the climatology aspects of MET,
however, I
> > see in our User's Guide for met-6.1:
> >
> > // The "climo_cdf_bins" entry should be set either to an integer
or an
> > > array of
> > > // floats between 0 and 1. When climatological mean and
standard
> > > deviation data
> > >
> >
> > I see in your config file that you have:
> >
> > climo_cdf_bins = [ 1 ];
> > > //climo_cdf_bins = [ 0, .1, .2, .3, .4, .5, .6, .7, .8, .9, 1
];
> > >
> >
> > You could try setting the following instead:
> >
> >
> > > climo_cdf_bins = 1;
> > >
> >
> > since the User's Guide indicates it should be either an integer or
an
> > array of floats (as opposed to an array with one integer in it, as
it
> > is set now), and see if that changes anything. Other than that, I
> > believe that your climo fields are set properly.
> >
> > Also, I don't know if you are intending to use the climo_stdev
> > functionality, but I do see that there is no file_name specified
for
> > that
> > functionality:
> >
> > climo_stdev = climo_mean;
> > > climo_stdev = {
> > > file_name = [];
> > > }
> > >
> >
> > Regarding your question:
> >
> > Another question, does MET use a neighborhood for the climo field
as
> > it does
> > > for the forecast field?
> > >
> >
> > I do not know the answer, but I will see what I can do to find
out.
> >
> > Also, I am not familiar with AMRDEC and do not know how to obtain
> > files from it.
> >
> > Please try the above modification to climo_cdf_bins and let me
know
> > how it goes. Thanks!
> >
> > Julie
> >
> >
> >
> > On Mon, Jul 30, 2018 at 9:55 AM robert.craig.2 at us.af.mil via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Mon Jul 30 09:54:41 2018: Request 86388 was acted upon.
> > > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > > Queue: met_help
> > > Subject: HIRA Setting Climo Data
> > > Owner: Nobody
> > > Requestors: robert.craig.2 at us.af.mil
> > > Status: new
> > > Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86388
> > > >
> > >
> > >
> > > John, I have another HIRA question for you. When I run the
command
> > > line ( /h/WXQC/met-6.1/bin/point_stat
> > >
> > >
> >
>
/h/data/global/FSMT/data/GALWEM/RD/output/global_17km/PS.557WW_SC.U_DI.C_GP.
> > > GALWEM-GD_GR.C17KM_AR.GLOBAL_DD.20180501_CY.00_FH.012_DF.GR2
> > > /h/data/global/WXQC/data/met/nc_obs/cdcb/2018050112.nc
> > > /h/WXQC/met-6.1/data/config/PointStatConfig_hira_updated -outdir
> > > /h/data/global/WXQC/data/met/ptstat/mdlob_pairs/global_17km/CB
-v 4
> > > ), I get the following output.
> > >
> > >
> > >
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 14, center: 57,
local
> > > table: 1,
> > > parm_cat: 13, parm: 192
> > >
> > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > > object of type "FileType_Gb2".
> > >
> > > DEBUG 3:
> > >
> > > DEBUG 3: Multiple GRIB2 table entries match lookup criteria
> > > (parm_name =
> > > CEIL):
> > >
> > > DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 1,
grib2_cntr =
> 57,
> > > grib2_ltab = 1, index_b = 6, index_c = 13
> > >
> > > DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 1,
grib2_cntr =
> 0,
> > > grib2_ltab = 0, index_b = 6, index_c = 13
> > >
> > > DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 14,
grib2_cntr =
> > 57,
> > > grib2_ltab = 0, index_b = 6, index_c = 13
> > >
> > > DEBUG 3: Using the first match found: parm_name: CEIL, index_a
= 0,
> > > grib2_mtab = 1, grib2_cntr = 57, grib2_ltab = 1, index_b = 6,
> > > index_c = 13
> > >
> > > DEBUG 3:
> > >
> > > DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact
match
> > > for "CEIL/L0" in GRIB2 record 1 field 1 of GRIB2 file
> > >
> > >
"/h/data/global/FSMT/data/GALWEM/RD/output/global_17km/PS.557WW_SC.U
> > > _D I.C_GP
> > > .GALWEM-GD_GR.C17KM_AR.GLOBAL_DD.20180430_CY.12_FH.000_DF.GR2"
> > >
> > > DEBUG 4:
> > >
> > > DEBUG 4: Data plane information:
> > >
> > > DEBUG 4: plane min: -82
> > >
> > > DEBUG 4: plane max: 15258
> > >
> > > DEBUG 4: scan mode: 64
> > >
> > > DEBUG 4: valid time: 20180430_120000
> > >
> > > DEBUG 4: lead time: 000000
> > >
> > > DEBUG 4: init time: 20180430_120000
> > >
> > > DEBUG 4: bitmap flag: 0
> > >
> > > DEBUG 4:
> > >
> > > DEBUG 3: Found 0 climatology fields.
> > >
> > > DEBUG 2: For CEIL/L0 found 1 forecast levels, 0 climatology mean
> > > levels, and
> > > 0 climatology standard deviation levels.
> > >
> > > DEBUG 2:
> > >
> > > DEBUG 2:
> > >
> > >
--------------------------------------------------------------------
> > > --
> > > ------
> > > ----
> > >
> > > DEBUG 2:
> > >
> > > DEBUG 2: Searching 13708 observations from 13708 messages.
> > >
> > > DEBUG 2:
> > >
> > > DEBUG 2:
> > >
> > >
--------------------------------------------------------------------
> > > --
> > > ------
> > > ----
> > >
> > > DEBUG 2:
> > >
> > > WARNING:
> > >
> > > WARNING: check_hdr_str() -> null string!
> > >
> > > WARNING:
> > >
> > > DEBUG 2: Processing CEIL/L0 versus (null)/L0, for observation
type
> > > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using
> > 2599 pairs.
> > >
> > > DEBUG 3: Number of matched pairs = 2599
> > >
> > > DEBUG 3: Observations processed = 13708
> > >
> > > DEBUG 3: Rejected: SID exclusion = 0
> > >
> > > DEBUG 3: Rejected: GRIB code = 0
> > >
> > > DEBUG 3: Rejected: valid time = 0
> > >
> > > DEBUG 3: Rejected: bad obs value = 10469
> > >
> > > DEBUG 3: Rejected: off the grid = 2
> > >
> > > DEBUG 3: Rejected: level mismatch = 0
> > >
> > > DEBUG 3: Rejected: quality marker = 0
> > >
> > > DEBUG 3: Rejected: message type = 0
> > >
> > > DEBUG 3: Rejected: masking region = 0
> > >
> > > DEBUG 3: Rejected: bad fcst value = 638
> > >
> > > DEBUG 3: Rejected: duplicates = 0
> > >
> > > DEBUG 2: Computing Categorical Statistics.
> > >
> > > DEBUG 2: Computing Continuous Statistics.
> > >
> > > DEBUG 2: Processing CEIL/L0==0.01 versus (null)/L0>=304, for
> > > observation type ADPSFC, over region FULL, for interpolation
method
> > > HiRA NBRHD(121), using 1052 pairs.
> > >
> > >
> > >
> > > MET says it finds the climo data but doesn't seem to use it and
the
> > > messages
> > > don't tell me why. In this case the climo file is just a
persistence
> > file
> > > (model forecast from previous day valid at same diurnal cycle).
I
> > attached
> > > the configuration file I am using. Do I have the climo fields
set
> > > properly
> > > for the HIRA setting?
> > >
> > >
> > >
> > > When I look in the PSTD file the BSS values are all NA. When I
look
> > > I the mpr file, all the climo fields are NA.
> > >
> > >
> > >
> > > Another question, does MET use a neighborhood for the climo
field as
> > > it does for the forecast field? I ask because the BSS simple is
a
> > > large negative number. I would expect it to be closer to 0.
> > >
> > >
> > >
> > > The model files are available on AMRDEC - still up loading.
> > >
> > >
> > >
> > > Thanks for your help.
> > >
> > >
> > >
> > > Bob Craig
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: HIRA Setting Climo Data
From: John Halley Gotway
Time: Wed Aug 08 17:08:25 2018
Bob,
I just wrote up a development ticket to update MET to handle this
case.
Please see attached PDF.
Just in case the attachment doesn't come through the AF network,
here's the
main point of it. Please read through and let me know if you like the
idea
of adding a "match_month = TRUE/FALSE"... or do you prefer the idea of
having the user define the time format which defines the match using
"match_date_format"?
Thanks,
John
TITLE: Update climo_mean and climo_stdev config sections for Air Force
climatology definitions.This issue arose via a MET-Help ticket from
Bob
Craig:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86388
The logic for searching for a climatology match assumes that the valid
month of the climo data should always match the valid month of the
forecast. If match_day = TRUE, it also requires that the days match.
The Air Forces defines their climatology using an earlier forecast.
Basically, the climatology is a persistence forecast. When the valid
time
of the climo and forecast data fall in different months, Grid-Stat
finds no
match.
We should update the climo_mean and climo_stdev to handle this case.
We currently have "match_day = TRUE/FALSE"... so we could add
"match_month
= TRUE/FALSE" as well.
Or we could replace "match_day = TRUE/FALSE" with something like:
match_date_format = "%m%d";
That would require that the month and day both match. Whereas "%m"
would
only require that the months match. And "" would require that no time
elements match.
On Wed, Aug 8, 2018 at 4:57 PM John Halley Gotway <johnhg at ucar.edu>
wrote:
> Hi Bob,
>
> Sorry for the long delay in getting back to you on this. I grabbed
the
> sample data you posted to the ARMDEC site and was able to reproduce
exactly
> the same log messages you're getting from Point-Stat. Perhaps all
the log
> messages are confusing, but they do indicate that no matching
climatology
> data was found:
>
> DEBUG 3: Found 0 climatology fields.
> DEBUG 2: For CEIL/L0 found 1 forecast levels, 0 climatology mean
levels,
> and 0 climatology standard deviation levels.
>
> So I would fully expect that the CLIMO_MEAN column of the MPR output
lines
> would contain NA, meaning that no climatology data was used.
>
> I suspect the real question is *why not*?
>
> You're evaluating a GALWEM model output data that's valid at this
> timestamp: 20180501_120000
> And you're providing "climatology" data that's valid at this
timestamp:
> 20180430_120000
> Notice that the forecast is valid in May and the climo data is valid
in
> April.
>
> This "climo_mean" logic was set up with NCEP data in mind. They
have 2
> specific climatology data sources. One is valid monthly... and the
other
> is valid daily. When MET goes hunting for a climatology data use,
it only
> considers climo data whose month matches the month of the forecast
valid
> time. Additionally, if "match_day = TRUE", it only considers data
when the
> days match.
>
> In your example, the months do not match, so grid_stat will never
find a
> match! By way of testing, I passed the same file in for the
forecast and
> the climo_mean and reran. And yes, that does produce a climo match
and
> populate the CLIMO_MEAN output column of MPR.
>
> Clearly, the existing logic doesn't handle well the way the AF
defines
> climatologies. We need to update the search parameter logic to
allow for
> this type of climo definition.
>
> Does that all make sense to you?
>
> Thanks,
> John
>
>
>
>
>
>
>
> On Mon, Jul 30, 2018 at 3:32 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=86388 >
>>
>> Julie, again for John, I finally looked further down through the
MPR file
>> and now see where the HIRA neighborhood probabilities show up in
the fcst
>> field. The obs field still has the ob value instead of a 0 or 1
indicating
>> the ob reached the threshold or not (ceiling < 304 meters). Is it
>> supposed to be doing this? And the climo fields are still NA. I
>> calculated out the data in the MPR file assuming the threshold was
applied
>> to the obs value and I got the same result the MET calculated. If
>> stat_analysis handles these mpr files correctly then all is well.
So the
>> only remaining issue is the NA for the climo fields.
>>
>> Bob
>>
>> -----Original Message-----
>> From: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
>> Sent: Monday, July 30, 2018 2:08 PM
>> To: 'met_help at ucar.edu' <met_help at ucar.edu>
>> Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #86388] HIRA
Setting
>> Climo Data
>>
>> Julie, I changed the thresholds for the forecast field, obs field,
and
>> climo field to be <= 304 meters (cloud base height), leaving the
threshold
>> for HIRA as ==0.01 and I got a more reasonable BSS_simple (.05).
The
>> question to pass on to John is when I run HIRA, besides the issue I
mention
>> of all the climo fields being NA, in the MPR files I get model
values for
>> the cloud heights for the fcst and obs columns instead of a HIRA
generated
>> probabiliies. If that is to be expected then it looks like I would
have to
>> save off the daily PSTD files to get a monthly BSS using HIRA
instead of
>> using stat analyisis to accumulate the data in the mpr/stat files.
Am I
>> understanding this right?
>>
>> Thanks
>> Bob
>>
>> -----Original Message-----
>> From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
>> Sent: Monday, July 30, 2018 12:35 PM
>> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
>> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #86388] HIRA
Setting
>> Climo Data
>>
>> Thanks, Bob.
>>
>> Our statistician agrees that the BSS simple being a large negative
number
>> is a certainly a tip off that something isn't working, but we are
not clear
>> on if MET uses a neighborhood for the climo field as it does for
the
>> forecast field, although we suspect it would.
>>
>> John should be able to provide further clarification next week.
>>
>> Julie
>>
>>
>> On Mon, Jul 30, 2018 at 11:16 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=86388 >
>> >
>> > Thanks Julie. The forecast files I was uploading to AMRDEC are
bigger
>> > than normal so they are still uploading - probably be there next
week
>> > :)
>> >
>> > I tried setting the climo_cdf_bins to 1 instead of [1] but that
didn't
>> > change anything. In this scenario, I don't have a climo standard
>> deviation
>> > file. I will experiment some more and let you know when the
forecast
>> > files are uploaded.
>> >
>> > Thanks
>> > Bob
>> >
>> > -----Original Message-----
>> > From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
>> > Sent: Monday, July 30, 2018 11:32 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 #86388] HIRA
Setting
>> > Climo Data
>> >
>> > Hi Bob.
>> >
>> > Unfortunately, John is out of the office this week. I'll respond
to
>> > what I can, but this ticket will likely need some follow up from
John
>> > when he is back.
>> >
>> > I am not very familiar with the climatology aspects of MET,
however, I
>> > see in our User's Guide for met-6.1:
>> >
>> > // The "climo_cdf_bins" entry should be set either to an integer
or an
>> > > array of
>> > > // floats between 0 and 1. When climatological mean and
standard
>> > > deviation data
>> > >
>> >
>> > I see in your config file that you have:
>> >
>> > climo_cdf_bins = [ 1 ];
>> > > //climo_cdf_bins = [ 0, .1, .2, .3, .4, .5, .6, .7, .8, .9, 1
];
>> > >
>> >
>> > You could try setting the following instead:
>> >
>> >
>> > > climo_cdf_bins = 1;
>> > >
>> >
>> > since the User's Guide indicates it should be either an integer
or an
>> > array of floats (as opposed to an array with one integer in it,
as it
>> > is set now), and see if that changes anything. Other than that,
I
>> > believe that your climo fields are set properly.
>> >
>> > Also, I don't know if you are intending to use the climo_stdev
>> > functionality, but I do see that there is no file_name specified
for
>> > that
>> > functionality:
>> >
>> > climo_stdev = climo_mean;
>> > > climo_stdev = {
>> > > file_name = [];
>> > > }
>> > >
>> >
>> > Regarding your question:
>> >
>> > Another question, does MET use a neighborhood for the climo field
as
>> > it does
>> > > for the forecast field?
>> > >
>> >
>> > I do not know the answer, but I will see what I can do to find
out.
>> >
>> > Also, I am not familiar with AMRDEC and do not know how to obtain
>> > files from it.
>> >
>> > Please try the above modification to climo_cdf_bins and let me
know
>> > how it goes. Thanks!
>> >
>> > Julie
>> >
>> >
>> >
>> > On Mon, Jul 30, 2018 at 9:55 AM robert.craig.2 at us.af.mil via RT <
>> > met_help at ucar.edu> wrote:
>> >
>> > >
>> > > Mon Jul 30 09:54:41 2018: Request 86388 was acted upon.
>> > > Transaction: Ticket created by robert.craig.2 at us.af.mil
>> > > Queue: met_help
>> > > Subject: HIRA Setting Climo Data
>> > > Owner: Nobody
>> > > Requestors: robert.craig.2 at us.af.mil
>> > > Status: new
>> > > Ticket <URL:
>> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86388
>> > > >
>> > >
>> > >
>> > > John, I have another HIRA question for you. When I run the
command
>> > > line ( /h/WXQC/met-6.1/bin/point_stat
>> > >
>> > >
>> >
>>
/h/data/global/FSMT/data/GALWEM/RD/output/global_17km/PS.557WW_SC.U_DI.C_GP.
>> > > GALWEM-GD_GR.C17KM_AR.GLOBAL_DD.20180501_CY.00_FH.012_DF.GR2
>> > > /h/data/global/WXQC/data/met/nc_obs/cdcb/2018050112.nc
>> > > /h/WXQC/met-6.1/data/config/PointStatConfig_hira_updated
-outdir
>> > > /h/data/global/WXQC/data/met/ptstat/mdlob_pairs/global_17km/CB
-v 4
>> > > ), I get the following output.
>> > >
>> > >
>> > >
>> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
>> > > GRIB2 field indexes - disc: 0, master table: 14, center: 57,
local
>> > > table: 1,
>> > > parm_cat: 13, parm: 192
>> > >
>> > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
>> > > object of type "FileType_Gb2".
>> > >
>> > > DEBUG 3:
>> > >
>> > > DEBUG 3: Multiple GRIB2 table entries match lookup criteria
>> > > (parm_name =
>> > > CEIL):
>> > >
>> > > DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 1,
grib2_cntr =
>> 57,
>> > > grib2_ltab = 1, index_b = 6, index_c = 13
>> > >
>> > > DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 1,
grib2_cntr =
>> 0,
>> > > grib2_ltab = 0, index_b = 6, index_c = 13
>> > >
>> > > DEBUG 3: parm_name: CEIL, index_a = 0, grib2_mtab = 14,
grib2_cntr =
>> > 57,
>> > > grib2_ltab = 0, index_b = 6, index_c = 13
>> > >
>> > > DEBUG 3: Using the first match found: parm_name: CEIL,
index_a = 0,
>> > > grib2_mtab = 1, grib2_cntr = 57, grib2_ltab = 1, index_b = 6,
>> > > index_c = 13
>> > >
>> > > DEBUG 3:
>> > >
>> > > DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact
match
>> > > for "CEIL/L0" in GRIB2 record 1 field 1 of GRIB2 file
>> > >
>> > >
"/h/data/global/FSMT/data/GALWEM/RD/output/global_17km/PS.557WW_SC.U
>> > > _D I.C_GP
>> > > .GALWEM-GD_GR.C17KM_AR.GLOBAL_DD.20180430_CY.12_FH.000_DF.GR2"
>> > >
>> > > DEBUG 4:
>> > >
>> > > DEBUG 4: Data plane information:
>> > >
>> > > DEBUG 4: plane min: -82
>> > >
>> > > DEBUG 4: plane max: 15258
>> > >
>> > > DEBUG 4: scan mode: 64
>> > >
>> > > DEBUG 4: valid time: 20180430_120000
>> > >
>> > > DEBUG 4: lead time: 000000
>> > >
>> > > DEBUG 4: init time: 20180430_120000
>> > >
>> > > DEBUG 4: bitmap flag: 0
>> > >
>> > > DEBUG 4:
>> > >
>> > > DEBUG 3: Found 0 climatology fields.
>> > >
>> > > DEBUG 2: For CEIL/L0 found 1 forecast levels, 0 climatology
mean
>> > > levels, and
>> > > 0 climatology standard deviation levels.
>> > >
>> > > DEBUG 2:
>> > >
>> > > DEBUG 2:
>> > >
>> > >
--------------------------------------------------------------------
>> > > --
>> > > ------
>> > > ----
>> > >
>> > > DEBUG 2:
>> > >
>> > > DEBUG 2: Searching 13708 observations from 13708 messages.
>> > >
>> > > DEBUG 2:
>> > >
>> > > DEBUG 2:
>> > >
>> > >
--------------------------------------------------------------------
>> > > --
>> > > ------
>> > > ----
>> > >
>> > > DEBUG 2:
>> > >
>> > > WARNING:
>> > >
>> > > WARNING: check_hdr_str() -> null string!
>> > >
>> > > WARNING:
>> > >
>> > > DEBUG 2: Processing CEIL/L0 versus (null)/L0, for observation
type
>> > > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using
>> > 2599 pairs.
>> > >
>> > > DEBUG 3: Number of matched pairs = 2599
>> > >
>> > > DEBUG 3: Observations processed = 13708
>> > >
>> > > DEBUG 3: Rejected: SID exclusion = 0
>> > >
>> > > DEBUG 3: Rejected: GRIB code = 0
>> > >
>> > > DEBUG 3: Rejected: valid time = 0
>> > >
>> > > DEBUG 3: Rejected: bad obs value = 10469
>> > >
>> > > DEBUG 3: Rejected: off the grid = 2
>> > >
>> > > DEBUG 3: Rejected: level mismatch = 0
>> > >
>> > > DEBUG 3: Rejected: quality marker = 0
>> > >
>> > > DEBUG 3: Rejected: message type = 0
>> > >
>> > > DEBUG 3: Rejected: masking region = 0
>> > >
>> > > DEBUG 3: Rejected: bad fcst value = 638
>> > >
>> > > DEBUG 3: Rejected: duplicates = 0
>> > >
>> > > DEBUG 2: Computing Categorical Statistics.
>> > >
>> > > DEBUG 2: Computing Continuous Statistics.
>> > >
>> > > DEBUG 2: Processing CEIL/L0==0.01 versus (null)/L0>=304, for
>> > > observation type ADPSFC, over region FULL, for interpolation
method
>> > > HiRA NBRHD(121), using 1052 pairs.
>> > >
>> > >
>> > >
>> > > MET says it finds the climo data but doesn't seem to use it and
the
>> > > messages
>> > > don't tell me why. In this case the climo file is just a
persistence
>> > file
>> > > (model forecast from previous day valid at same diurnal cycle).
I
>> > attached
>> > > the configuration file I am using. Do I have the climo fields
set
>> > > properly
>> > > for the HIRA setting?
>> > >
>> > >
>> > >
>> > > When I look in the PSTD file the BSS values are all NA. When I
look
>> > > I the mpr file, all the climo fields are NA.
>> > >
>> > >
>> > >
>> > > Another question, does MET use a neighborhood for the climo
field as
>> > > it does for the forecast field? I ask because the BSS simple
is a
>> > > large negative number. I would expect it to be closer to 0.
>> > >
>> > >
>> > >
>> > > The model files are available on AMRDEC - still up loading.
>> > >
>> > >
>> > >
>> > > Thanks for your help.
>> > >
>> > >
>> > >
>> > > Bob Craig
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> >
>> >
>> >
>> >
>>
>>
>>
>>
------------------------------------------------
More information about the Met_help
mailing list