[Met_help] [rt.rap.ucar.edu #95673] History for Set GRIB2_ipdtmpl_index and GRIB2_ipdtmpl_val for each file in a pcp_combine usage?
John Halley Gotway via RT
met_help at ucar.edu
Fri Jun 19 10:46:11 MDT 2020
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi all,
Ran in to a bit a funny problem, and I wanted to check with you to see if there's a concrete fix.
I'm currently creating custom precipitation accumulations in pcp_combine. In this case, I'm using the parameter SPRATE, which holds a custom snowfall product. The problem is, the parent grib2 file holds both a total and 3 hour SPRATE variable. I'll include the basic command below to show you the base output.
In the past, I've been able to skip around these kind of problems with the other GRIB2 fields, including designating GRIB2_ipdtmpl_index and GRIB2_ipdtmpl_val. However, my question in this: can I set separate 'field' values for each of the files in a 'subtract' or 'add' function? Do I simply enter two 'field' entries?
In the example below, I can simply sort these out by the 9th pdt value, which is 0 in the parameter I want, and non-zero in the field I don't. But for time periods that start at 0....say if I was creating a temperature difference of a 0-3 forecast hour period, this wouldn't be case...and I would need to use the 27th value to pick the correct parameter in each file-the problem being these values differ in the two files I'd be subtracting. So, in the example below, if I was simply to enter something like GRIB2_ipdtmpl_index[26]; GRIB2_ipdtmpl_val[48], this will fail with the second file needed for the subtraction (since its value will be 24 and not 48), and the entire process fails. I'll include that as a second set of output below.
I hope this makes sense, and I didn't totally confuse you!
Any insight? Or is at simple as adding a second set of 'field' parameters?
Thanks!
-Tom
/usr/local/bin/pcp_combine -subtract /fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2 /fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2 /fewxops/verification/data/model/met_output/conusarw/pcp_combine/feens1_snow_24_2020061000f48.nc -field 'name="SPRATE";level="Z0";'
DEBUG 2: Since the "-field" command line option was used, parsing the command line arguments as a list of files.
DEBUG 1: Reading input file: /fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
DEBUG 1: Reading data (name="SPRATE";level="Z0";) from input file: /fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
WARNING:
WARNING: MetGrib2DataFile::data_plane() -> Using the first of 2 matching records for "SPRATE/Z0":
WARNING: record 25 field 1: ipdtmpl[29] = 1, 66, 2, 0, 116, 0, 0, 1, 0, 1, 0, 0, 255, 0, 0, 2020, 6, 12, 0, 0, 0, 1, 0, 1, 2, 1, 48, 255, 0
WARNING: record 29 field 1: ipdtmpl[29] = 1, 66, 2, 0, 116, 0, 0, 1, 45, 1, 0, 0, 255, 0, 0, 2020, 6, 12, 0, 0, 0, 1, 0, 2, 2, 1, 3, 255, 0
WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and "GRIB2_ipdtmpl_val" config file options to select one.
WARNING:
DEBUG 1: Reading input file: /fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
DEBUG 1: Reading data (name="SPRATE";level="Z0";) from input file: /fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
WARNING:
WARNING: MetGrib2DataFile::data_plane() -> Using the first of 2 matching records for "SPRATE/Z0":
WARNING: record 25 field 1: ipdtmpl[29] = 1, 66, 2, 0, 116, 0, 0, 1, 0, 1, 0, 0, 255, 0, 0, 2020, 6, 11, 0, 0, 0, 1, 0, 1, 2, 1, 24, 255, 0
WARNING: record 29 field 1: ipdtmpl[29] = 1, 66, 2, 0, 116, 0, 0, 1, 21, 1, 0, 0, 255, 0, 0, 2020, 6, 11, 0, 0, 0, 1, 0, 2, 2, 1, 3, 255, 0
WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and "GRIB2_ipdtmpl_val" config file options to select one.
WARNING:
DEBUG 2: Performing subtraction command.
DEBUG 1: Creating output file: /fewxops/verification/data/model/met_output/conusarw/pcp_combine/feens1_snow_24_2020061000f48.nc
DEBUG 2: Writing output variable "SPRATE_24" for the "diff" of "SPRATE/Z0".
DEBUG 1: Closing output file: /fewxops/verification/data/model/met_output/conusarw/pcp_combine/feens1_snow_24_2020061000f48.nc
/usr/local/bin/pcp_combine -subtract /fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2 /fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2 /fewxops/verification/data/model/met_output/conusarw/pcp_combine/feens1_snow_24_2020061000f48.nc -field 'name="SPRATE";level="Z0";GRIB2_ipdtmpl_index=[26];GRIB2_ipdtmpl_val=[48];'
DEBUG 2: Since the "-field" command line option was used, parsing the command line arguments as a list of files.
DEBUG 1: Reading input file: /fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
DEBUG 1: Reading data (name="SPRATE";level="Z0";GRIB2_ipdtmpl_index=[26];GRIB2_ipdtmpl_val=[48];) from input file: /fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
DEBUG 1: Reading input file: /fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
DEBUG 1: Reading data (name="SPRATE";level="Z0";GRIB2_ipdtmpl_index=[26];GRIB2_ipdtmpl_val=[48];) from input file: /fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
WARNING:
WARNING: MetGrib2DataFile::data_plane() -> No matching record found for 'SPRATE/Z0'
WARNING:
ERROR :
ERROR : get_field() -> can't get data plane from file "/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2"
ERROR :
------------------------------------------------------------------------------
The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Set GRIB2_ipdtmpl_index and GRIB2_ipdtmpl_val for each file in a pcp_combine usage?
From: Minna Win
Time: Fri Jun 19 09:08:11 2020
Hi Tom,
It looks like you have some questions pertaining to pcp_combine. I'm
assigning this ticket to John Halley Gotway, please allow a few
business
days for a full response.
Regards,
Minna
---------------
Minna Win
National Center for Atmospheric Research
Developmental Testbed Center
Phone: 303-497-8423
Fax: 303-497-8401
On Fri, Jun 19, 2020 at 7:40 AM Workoff, Thomas E via RT
<met_help at ucar.edu>
wrote:
>
> Fri Jun 19 07:40:16 2020: Request 95673 was acted upon.
> Transaction: Ticket created by tworkoff at firstenergycorp.com
> Queue: met_help
> Subject: Set GRIB2_ipdtmpl_index and GRIB2_ipdtmpl_val for each
file
> in a pcp_combine usage?
> Owner: Nobody
> Requestors: tworkoff at firstenergycorp.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95673 >
>
>
> Hi all,
>
> Ran in to a bit a funny problem, and I wanted to check with you to
see if
> there's a concrete fix.
>
> I'm currently creating custom precipitation accumulations in
pcp_combine.
> In this case, I'm using the parameter SPRATE, which holds a custom
snowfall
> product. The problem is, the parent grib2 file holds both a total
and 3
> hour SPRATE variable. I'll include the basic command below to show
you the
> base output.
>
> In the past, I've been able to skip around these kind of problems
with the
> other GRIB2 fields, including designating GRIB2_ipdtmpl_index and
> GRIB2_ipdtmpl_val. However, my question in this: can I set
separate
> 'field' values for each of the files in a 'subtract' or 'add'
function? Do
> I simply enter two 'field' entries?
>
> In the example below, I can simply sort these out by the 9th pdt
value,
> which is 0 in the parameter I want, and non-zero in the field I
don't. But
> for time periods that start at 0....say if I was creating a
temperature
> difference of a 0-3 forecast hour period, this wouldn't be
case...and I
> would need to use the 27th value to pick the correct parameter in
each
> file-the problem being these values differ in the two files I'd be
> subtracting. So, in the example below, if I was simply to enter
something
> like GRIB2_ipdtmpl_index[26]; GRIB2_ipdtmpl_val[48], this will fail
with
> the second file needed for the subtraction (since its value will be
24 and
> not 48), and the entire process fails. I'll include that as a second
set of
> output below.
>
> I hope this makes sense, and I didn't totally confuse you!
>
> Any insight? Or is at simple as adding a second set of 'field'
parameters?
>
> Thanks!
> -Tom
>
> /usr/local/bin/pcp_combine -subtract
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> /fewxops/verification/data/model/met_output/conusarw/pcp_combine/
> feens1_snow_24_2020061000f48.nc -field 'name="SPRATE";level="Z0";'
> DEBUG 2: Since the "-field" command line option was used, parsing
the
> command line arguments as a list of files.
> DEBUG 1: Reading input file:
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> DEBUG 1: Reading data (name="SPRATE";level="Z0";) from input file:
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> WARNING:
> WARNING: MetGrib2DataFile::data_plane() -> Using the first of 2
matching
> records for "SPRATE/Z0":
> WARNING: record 25 field 1: ipdtmpl[29] = 1, 66, 2, 0, 116, 0, 0, 1,
0, 1,
> 0, 0, 255, 0, 0, 2020, 6, 12, 0, 0, 0, 1, 0, 1, 2, 1, 48, 255, 0
> WARNING: record 29 field 1: ipdtmpl[29] = 1, 66, 2, 0, 116, 0, 0, 1,
45,
> 1, 0, 0, 255, 0, 0, 2020, 6, 12, 0, 0, 0, 1, 0, 2, 2, 1, 3, 255, 0
> WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and
> "GRIB2_ipdtmpl_val" config file options to select one.
> WARNING:
> DEBUG 1: Reading input file:
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> DEBUG 1: Reading data (name="SPRATE";level="Z0";) from input file:
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> WARNING:
> WARNING: MetGrib2DataFile::data_plane() -> Using the first of 2
matching
> records for "SPRATE/Z0":
> WARNING: record 25 field 1: ipdtmpl[29] = 1, 66, 2, 0, 116, 0, 0, 1,
0, 1,
> 0, 0, 255, 0, 0, 2020, 6, 11, 0, 0, 0, 1, 0, 1, 2, 1, 24, 255, 0
> WARNING: record 29 field 1: ipdtmpl[29] = 1, 66, 2, 0, 116, 0, 0, 1,
21,
> 1, 0, 0, 255, 0, 0, 2020, 6, 11, 0, 0, 0, 1, 0, 2, 2, 1, 3, 255, 0
> WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and
> "GRIB2_ipdtmpl_val" config file options to select one.
> WARNING:
> DEBUG 2: Performing subtraction command.
> DEBUG 1: Creating output file:
> /fewxops/verification/data/model/met_output/conusarw/pcp_combine/
> feens1_snow_24_2020061000f48.nc
> DEBUG 2: Writing output variable "SPRATE_24" for the "diff" of
"SPRATE/Z0".
> DEBUG 1: Closing output file:
> /fewxops/verification/data/model/met_output/conusarw/pcp_combine/
> feens1_snow_24_2020061000f48.nc
>
>
> /usr/local/bin/pcp_combine -subtract
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> /fewxops/verification/data/model/met_output/conusarw/pcp_combine/
> feens1_snow_24_2020061000f48.nc -field
>
'name="SPRATE";level="Z0";GRIB2_ipdtmpl_index=[26];GRIB2_ipdtmpl_val=[48];'
> DEBUG 2: Since the "-field" command line option was used, parsing
the
> command line arguments as a list of files.
> DEBUG 1: Reading input file:
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> DEBUG 1: Reading data
>
(name="SPRATE";level="Z0";GRIB2_ipdtmpl_index=[26];GRIB2_ipdtmpl_val=[48];)
> from input file:
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> DEBUG 1: Reading input file:
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> DEBUG 1: Reading data
>
(name="SPRATE";level="Z0";GRIB2_ipdtmpl_index=[26];GRIB2_ipdtmpl_val=[48];)
> from input file:
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> WARNING:
> WARNING: MetGrib2DataFile::data_plane() -> No matching record found
for
> 'SPRATE/Z0'
> WARNING:
> ERROR :
> ERROR : get_field() -> can't get data plane from file
>
"/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2"
> ERROR :
>
>
>
------------------------------------------------------------------------------
>
> The information contained in this message is intended only for the
> personal and confidential use of the recipient(s) named above. If
the
> reader of this message is not the intended recipient or an agent
> responsible for delivering it to the intended recipient, you are
hereby
> notified that you have received this document in error and that any
review,
> dissemination, distribution, or copying of this message is strictly
> prohibited. If you have received this communication in error, please
notify
> us immediately, and delete the original message.
>
>
------------------------------------------------
Subject: Set GRIB2_ipdtmpl_index and GRIB2_ipdtmpl_val for each file in a pcp_combine usage?
From: John Halley Gotway
Time: Fri Jun 19 10:32:05 2020
Tom,
I see you have a question about the command line options for
pcp_combine.
Good news, yes, you can configure exactly the fields you need.
Looking at the lengthy pcp_combine usage statement, you'll see the
subtract
option listed like this:
*Usage: pcp_combine*
* -subtract input_files*
* out_file*
And "*input_files*" is further described as:
I*NPUT_FILES:*
* file_1 config_str_1 ... file_n config_str_n | *
* file_1 ... file_n |*
* input_file_list*
You're currently using the 2nd option listed there (file_1 ... file_n)
to
just specify 2 input file names.
But you can switch to the first option instead where each file name is
followed by a configuration string.
With your data, you'd setup the pcp_combine command something like
this:
*/usr/local/bin/pcp_combine -subtract \*
*feens1_verify_2020061000f48.grib2 'name="SPRATE";
level="Z0"; GRIB2_ipdtmpl_index=[8]; GRIB2_ipdtmpl_index=[45];' \*
*feens1_verify_2020061000f24.grib2 'name="SPRATE";
level="Z0"; GRIB2_ipdtmpl_index=[8]; GRIB2_ipdtmpl_index=[21];' \*
*feens1_snow_24_2020061000f48.nc
<http://feens1_snow_24_2020061000f48.nc> \*
*-name SPRATE_A24*
Let me know if that doesn't fix it. Note that I also used the "-name"
command line argument to tell pcp_combine how to name the output
variable.
Thanks,
John
On Fri, Jun 19, 2020 at 9:08 AM Minna Win via RT <met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95673 >
>
> Hi Tom,
>
> It looks like you have some questions pertaining to pcp_combine.
I'm
> assigning this ticket to John Halley Gotway, please allow a few
business
> days for a full response.
>
> Regards,
> Minna
> ---------------
> Minna Win
> National Center for Atmospheric Research
> Developmental Testbed Center
> Phone: 303-497-8423
> Fax: 303-497-8401
>
>
>
> On Fri, Jun 19, 2020 at 7:40 AM Workoff, Thomas E via RT <
> met_help at ucar.edu>
> wrote:
>
> >
> > Fri Jun 19 07:40:16 2020: Request 95673 was acted upon.
> > Transaction: Ticket created by tworkoff at firstenergycorp.com
> > Queue: met_help
> > Subject: Set GRIB2_ipdtmpl_index and GRIB2_ipdtmpl_val for
each file
> > in a pcp_combine usage?
> > Owner: Nobody
> > Requestors: tworkoff at firstenergycorp.com
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95673 >
> >
> >
> > Hi all,
> >
> > Ran in to a bit a funny problem, and I wanted to check with you to
see if
> > there's a concrete fix.
> >
> > I'm currently creating custom precipitation accumulations in
pcp_combine.
> > In this case, I'm using the parameter SPRATE, which holds a custom
> snowfall
> > product. The problem is, the parent grib2 file holds both a total
and 3
> > hour SPRATE variable. I'll include the basic command below to
show you
> the
> > base output.
> >
> > In the past, I've been able to skip around these kind of problems
with
> the
> > other GRIB2 fields, including designating GRIB2_ipdtmpl_index and
> > GRIB2_ipdtmpl_val. However, my question in this: can I set
separate
> > 'field' values for each of the files in a 'subtract' or 'add'
function?
> Do
> > I simply enter two 'field' entries?
> >
> > In the example below, I can simply sort these out by the 9th pdt
value,
> > which is 0 in the parameter I want, and non-zero in the field I
don't.
> But
> > for time periods that start at 0....say if I was creating a
temperature
> > difference of a 0-3 forecast hour period, this wouldn't be
case...and I
> > would need to use the 27th value to pick the correct parameter in
each
> > file-the problem being these values differ in the two files I'd be
> > subtracting. So, in the example below, if I was simply to enter
> something
> > like GRIB2_ipdtmpl_index[26]; GRIB2_ipdtmpl_val[48], this will
fail with
> > the second file needed for the subtraction (since its value will
be 24
> and
> > not 48), and the entire process fails. I'll include that as a
second set
> of
> > output below.
> >
> > I hope this makes sense, and I didn't totally confuse you!
> >
> > Any insight? Or is at simple as adding a second set of 'field'
> parameters?
> >
> > Thanks!
> > -Tom
> >
> > /usr/local/bin/pcp_combine -subtract
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> > /fewxops/verification/data/model/met_output/conusarw/pcp_combine/
> > feens1_snow_24_2020061000f48.nc -field 'name="SPRATE";level="Z0";'
> > DEBUG 2: Since the "-field" command line option was used, parsing
the
> > command line arguments as a list of files.
> > DEBUG 1: Reading input file:
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> > DEBUG 1: Reading data (name="SPRATE";level="Z0";) from input file:
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> > WARNING:
> > WARNING: MetGrib2DataFile::data_plane() -> Using the first of 2
matching
> > records for "SPRATE/Z0":
> > WARNING: record 25 field 1: ipdtmpl[29] = 1, 66, 2, 0, 116, 0, 0,
1, 0,
> 1,
> > 0, 0, 255, 0, 0, 2020, 6, 12, 0, 0, 0, 1, 0, 1, 2, 1, 48, 255, 0
> > WARNING: record 29 field 1: ipdtmpl[29] = 1, 66, 2, 0, 116, 0, 0,
1, 45,
> > 1, 0, 0, 255, 0, 0, 2020, 6, 12, 0, 0, 0, 1, 0, 2, 2, 1, 3, 255, 0
> > WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and
> > "GRIB2_ipdtmpl_val" config file options to select one.
> > WARNING:
> > DEBUG 1: Reading input file:
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> > DEBUG 1: Reading data (name="SPRATE";level="Z0";) from input file:
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> > WARNING:
> > WARNING: MetGrib2DataFile::data_plane() -> Using the first of 2
matching
> > records for "SPRATE/Z0":
> > WARNING: record 25 field 1: ipdtmpl[29] = 1, 66, 2, 0, 116, 0, 0,
1, 0,
> 1,
> > 0, 0, 255, 0, 0, 2020, 6, 11, 0, 0, 0, 1, 0, 1, 2, 1, 24, 255, 0
> > WARNING: record 29 field 1: ipdtmpl[29] = 1, 66, 2, 0, 116, 0, 0,
1, 21,
> > 1, 0, 0, 255, 0, 0, 2020, 6, 11, 0, 0, 0, 1, 0, 2, 2, 1, 3, 255, 0
> > WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and
> > "GRIB2_ipdtmpl_val" config file options to select one.
> > WARNING:
> > DEBUG 2: Performing subtraction command.
> > DEBUG 1: Creating output file:
> > /fewxops/verification/data/model/met_output/conusarw/pcp_combine/
> > feens1_snow_24_2020061000f48.nc
> > DEBUG 2: Writing output variable "SPRATE_24" for the "diff" of
> "SPRATE/Z0".
> > DEBUG 1: Closing output file:
> > /fewxops/verification/data/model/met_output/conusarw/pcp_combine/
> > feens1_snow_24_2020061000f48.nc
> >
> >
> > /usr/local/bin/pcp_combine -subtract
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> > /fewxops/verification/data/model/met_output/conusarw/pcp_combine/
> > feens1_snow_24_2020061000f48.nc -field
> >
>
'name="SPRATE";level="Z0";GRIB2_ipdtmpl_index=[26];GRIB2_ipdtmpl_val=[48];'
> > DEBUG 2: Since the "-field" command line option was used, parsing
the
> > command line arguments as a list of files.
> > DEBUG 1: Reading input file:
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> > DEBUG 1: Reading data
> >
>
(name="SPRATE";level="Z0";GRIB2_ipdtmpl_index=[26];GRIB2_ipdtmpl_val=[48];)
> > from input file:
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> > DEBUG 1: Reading input file:
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> > DEBUG 1: Reading data
> >
>
(name="SPRATE";level="Z0";GRIB2_ipdtmpl_index=[26];GRIB2_ipdtmpl_val=[48];)
> > from input file:
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> > WARNING:
> > WARNING: MetGrib2DataFile::data_plane() -> No matching record
found for
> > 'SPRATE/Z0'
> > WARNING:
> > ERROR :
> > ERROR : get_field() -> can't get data plane from file
> >
>
"/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2"
> > ERROR :
> >
> >
> >
>
------------------------------------------------------------------------------
> >
> > The information contained in this message is intended only for the
> > personal and confidential use of the recipient(s) named above. If
the
> > reader of this message is not the intended recipient or an agent
> > responsible for delivering it to the intended recipient, you are
hereby
> > notified that you have received this document in error and that
any
> review,
> > dissemination, distribution, or copying of this message is
strictly
> > prohibited. If you have received this communication in error,
please
> notify
> > us immediately, and delete the original message.
> >
> >
>
>
------------------------------------------------
Subject: RE: [EXTERNAL] Re: [rt.rap.ucar.edu #95673] Set GRIB2_ipdtmpl_index and GRIB2_ipdtmpl_val for each file in a pcp_combine usage?
From: Workoff, Thomas E
Time: Fri Jun 19 10:40:17 2020
John,
Thanks for the quick reply! This is perfect. I'm not sure how I
missed the first option in the documentation. It's been a while--
perhaps I need to refresh myself on the basic command line options
available.
Regardless, this solves my issue. I realize needing this
functionality is way 'down in the weeds', but it's super helpful with
using specialized or user-created grib values and parameters--
especially because users can really get painted in a corner when
attempting to make new, user-created grib parameters in post-
processing.
Thanks again!
-Tom
-----Original Message-----
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Friday, June 19, 2020 12:32 PM
To: Workoff, Thomas E <tworkoff at firstenergycorp.com>
Subject: [EXTERNAL] Re: [rt.rap.ucar.edu #95673] Set
GRIB2_ipdtmpl_index and GRIB2_ipdtmpl_val for each file in a
pcp_combine usage?
Tom,
I see you have a question about the command line options for
pcp_combine.
Good news, yes, you can configure exactly the fields you need.
Looking at the lengthy pcp_combine usage statement, you'll see the
subtract option listed like this:
*Usage: pcp_combine*
* -subtract input_files*
* out_file*
And "*input_files*" is further described as:
I*NPUT_FILES:*
* file_1 config_str_1 ... file_n config_str_n | *
* file_1 ... file_n |*
* input_file_list*
You're currently using the 2nd option listed there (file_1 ... file_n)
to just specify 2 input file names.
But you can switch to the first option instead where each file name is
followed by a configuration string.
With your data, you'd setup the pcp_combine command something like
this:
*/usr/local/bin/pcp_combine -subtract \*
*feens1_verify_2020061000f48.grib2 'name="SPRATE"; level="Z0";
GRIB2_ipdtmpl_index=[8]; GRIB2_ipdtmpl_index=[45];' \*
*feens1_verify_2020061000f24.grib2 'name="SPRATE"; level="Z0";
GRIB2_ipdtmpl_index=[8]; GRIB2_ipdtmpl_index=[21];' \*
*feens1_snow_24_2020061000f48.nc <http://secure-
web.cisco.com/13Y8TwQNExAToJZ5lfuY-QO1cJx09el95PH64AhHXIb-
rn11YNMqd8UTAHb60C4Qg49btXB5EOoFlV-
GRO5cXpdPgkf8f5pWY0HEmLELMKsNPUffraasATf6hgekzveWEaWTz5Qqsl4M1e0GPzalSfgT4cCtBGjzmW970UgYx5HQBnb0TP8nUUtZ1qRUYlDdRc5ujxtaMJtjJ12gvmwFMdnIRrI9Oq58yKBkEo-
HC6tqFgATPoZX-
KlCs47tBZwAfjqhIDvCv_B5KkptwRPiIiBT4P9MkRsRfz20iOb672eQo0Ghm1ptCg-
b81b4lXpD_KgAcxYVWwttMhx6ZbkpeWxLnEM6btJ6_yuXBwuxNT9ZmYHQhbXdkhDAGQLQVB3I_/http%3A%2F%2Ffeens1_snow_24_2020061000f48.nc>
\*
*-name SPRATE_A24*
Let me know if that doesn't fix it. Note that I also used the "-name"
command line argument to tell pcp_combine how to name the output
variable.
Thanks,
John
On Fri, Jun 19, 2020 at 9:08 AM Minna Win via RT <met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95673 >
>
> Hi Tom,
>
> It looks like you have some questions pertaining to pcp_combine.
I'm
> assigning this ticket to John Halley Gotway, please allow a few
> business days for a full response.
>
> Regards,
> Minna
> ---------------
> Minna Win
> National Center for Atmospheric Research Developmental Testbed
Center
> Phone: 303-497-8423
> Fax: 303-497-8401
>
>
>
> On Fri, Jun 19, 2020 at 7:40 AM Workoff, Thomas E via RT <
> met_help at ucar.edu>
> wrote:
>
> >
> > Fri Jun 19 07:40:16 2020: Request 95673 was acted upon.
> > Transaction: Ticket created by tworkoff at firstenergycorp.com
> > Queue: met_help
> > Subject: Set GRIB2_ipdtmpl_index and GRIB2_ipdtmpl_val for
each file
> > in a pcp_combine usage?
> > Owner: Nobody
> > Requestors: tworkoff at firstenergycorp.com
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95673 >
> >
> >
> > Hi all,
> >
> > Ran in to a bit a funny problem, and I wanted to check with you to
see if
> > there's a concrete fix.
> >
> > I'm currently creating custom precipitation accumulations in
pcp_combine.
> > In this case, I'm using the parameter SPRATE, which holds a custom
> snowfall
> > product. The problem is, the parent grib2 file holds both a total
and 3
> > hour SPRATE variable. I'll include the basic command below to
show you
> the
> > base output.
> >
> > In the past, I've been able to skip around these kind of problems
with
> the
> > other GRIB2 fields, including designating GRIB2_ipdtmpl_index and
> > GRIB2_ipdtmpl_val. However, my question in this: can I set
separate
> > 'field' values for each of the files in a 'subtract' or 'add'
function?
> Do
> > I simply enter two 'field' entries?
> >
> > In the example below, I can simply sort these out by the 9th pdt
value,
> > which is 0 in the parameter I want, and non-zero in the field I
don't.
> But
> > for time periods that start at 0....say if I was creating a
temperature
> > difference of a 0-3 forecast hour period, this wouldn't be
case...and I
> > would need to use the 27th value to pick the correct parameter in
each
> > file-the problem being these values differ in the two files I'd be
> > subtracting. So, in the example below, if I was simply to enter
> something
> > like GRIB2_ipdtmpl_index[26]; GRIB2_ipdtmpl_val[48], this will
fail with
> > the second file needed for the subtraction (since its value will
be 24
> and
> > not 48), and the entire process fails. I'll include that as a
second set
> of
> > output below.
> >
> > I hope this makes sense, and I didn't totally confuse you!
> >
> > Any insight? Or is at simple as adding a second set of 'field'
> parameters?
> >
> > Thanks!
> > -Tom
> >
> > /usr/local/bin/pcp_combine -subtract
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> > /fewxops/verification/data/model/met_output/conusarw/pcp_combine/
> > feens1_snow_24_2020061000f48.nc -field 'name="SPRATE";level="Z0";'
> > DEBUG 2: Since the "-field" command line option was used, parsing
the
> > command line arguments as a list of files.
> > DEBUG 1: Reading input file:
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> > DEBUG 1: Reading data (name="SPRATE";level="Z0";) from input file:
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> > WARNING:
> > WARNING: MetGrib2DataFile::data_plane() -> Using the first of 2
matching
> > records for "SPRATE/Z0":
> > WARNING: record 25 field 1: ipdtmpl[29] = 1, 66, 2, 0, 116, 0, 0,
1, 0,
> 1,
> > 0, 0, 255, 0, 0, 2020, 6, 12, 0, 0, 0, 1, 0, 1, 2, 1, 48, 255, 0
> > WARNING: record 29 field 1: ipdtmpl[29] = 1, 66, 2, 0, 116, 0, 0,
1, 45,
> > 1, 0, 0, 255, 0, 0, 2020, 6, 12, 0, 0, 0, 1, 0, 2, 2, 1, 3, 255, 0
> > WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and
> > "GRIB2_ipdtmpl_val" config file options to select one.
> > WARNING:
> > DEBUG 1: Reading input file:
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> > DEBUG 1: Reading data (name="SPRATE";level="Z0";) from input file:
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> > WARNING:
> > WARNING: MetGrib2DataFile::data_plane() -> Using the first of 2
matching
> > records for "SPRATE/Z0":
> > WARNING: record 25 field 1: ipdtmpl[29] = 1, 66, 2, 0, 116, 0, 0,
1, 0,
> 1,
> > 0, 0, 255, 0, 0, 2020, 6, 11, 0, 0, 0, 1, 0, 1, 2, 1, 24, 255, 0
> > WARNING: record 29 field 1: ipdtmpl[29] = 1, 66, 2, 0, 116, 0, 0,
1, 21,
> > 1, 0, 0, 255, 0, 0, 2020, 6, 11, 0, 0, 0, 1, 0, 2, 2, 1, 3, 255, 0
> > WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and
> > "GRIB2_ipdtmpl_val" config file options to select one.
> > WARNING:
> > DEBUG 2: Performing subtraction command.
> > DEBUG 1: Creating output file:
> > /fewxops/verification/data/model/met_output/conusarw/pcp_combine/
> > feens1_snow_24_2020061000f48.nc
> > DEBUG 2: Writing output variable "SPRATE_24" for the "diff" of
> "SPRATE/Z0".
> > DEBUG 1: Closing output file:
> > /fewxops/verification/data/model/met_output/conusarw/pcp_combine/
> > feens1_snow_24_2020061000f48.nc
> >
> >
> > /usr/local/bin/pcp_combine -subtract
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> > /fewxops/verification/data/model/met_output/conusarw/pcp_combine/
> > feens1_snow_24_2020061000f48.nc -field
> >
>
'name="SPRATE";level="Z0";GRIB2_ipdtmpl_index=[26];GRIB2_ipdtmpl_val=[48];'
> > DEBUG 2: Since the "-field" command line option was used, parsing
the
> > command line arguments as a list of files.
> > DEBUG 1: Reading input file:
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> > DEBUG 1: Reading data
> >
>
(name="SPRATE";level="Z0";GRIB2_ipdtmpl_index=[26];GRIB2_ipdtmpl_val=[48];)
> > from input file:
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> > DEBUG 1: Reading input file:
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> > DEBUG 1: Reading data
> >
>
(name="SPRATE";level="Z0";GRIB2_ipdtmpl_index=[26];GRIB2_ipdtmpl_val=[48];)
> > from input file:
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> > WARNING:
> > WARNING: MetGrib2DataFile::data_plane() -> No matching record
found for
> > 'SPRATE/Z0'
> > WARNING:
> > ERROR :
> > ERROR : get_field() -> can't get data plane from file
> >
>
"/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2"
> > ERROR :
> >
> >
> >
>
------------------------------------------------------------------------------
> >
> > The information contained in this message is intended only for the
> > personal and confidential use of the recipient(s) named above. If
the
> > reader of this message is not the intended recipient or an agent
> > responsible for delivering it to the intended recipient, you are
hereby
> > notified that you have received this document in error and that
any
> review,
> > dissemination, distribution, or copying of this message is
strictly
> > prohibited. If you have received this communication in error,
please
> notify
> > us immediately, and delete the original message.
> >
> >
>
>
------------------------------------------------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If the
reader of this message is not the intended recipient or an agent
responsible for delivering it to the intended recipient, you are
hereby notified that you have received this document in error and that
any review, dissemination, distribution, or copying of this message is
strictly prohibited. If you have received this communication in error,
please notify us immediately, and delete the original message.
------------------------------------------------
Subject: Set GRIB2_ipdtmpl_index and GRIB2_ipdtmpl_val for each file in a pcp_combine usage?
From: John Halley Gotway
Time: Fri Jun 19 10:45:56 2020
Great, thanks for confirming that did the trick.
John
On Fri, Jun 19, 2020 at 10:40 AM Workoff, Thomas E via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95673 >
>
> John,
>
> Thanks for the quick reply! This is perfect. I'm not sure how I
missed
> the first option in the documentation. It's been a while--perhaps I
need
> to refresh myself on the basic command line options available.
>
> Regardless, this solves my issue. I realize needing this
functionality is
> way 'down in the weeds', but it's super helpful with using
specialized or
> user-created grib values and parameters--especially because users
can
> really get painted in a corner when attempting to make new, user-
created
> grib parameters in post-processing.
>
> Thanks again!
> -Tom
>
> -----Original Message-----
> From: John Halley Gotway via RT <met_help at ucar.edu>
> Sent: Friday, June 19, 2020 12:32 PM
> To: Workoff, Thomas E <tworkoff at firstenergycorp.com>
> Subject: [EXTERNAL] Re: [rt.rap.ucar.edu #95673] Set
GRIB2_ipdtmpl_index
> and GRIB2_ipdtmpl_val for each file in a pcp_combine usage?
>
> Tom,
>
> I see you have a question about the command line options for
pcp_combine.
> Good news, yes, you can configure exactly the fields you need.
>
> Looking at the lengthy pcp_combine usage statement, you'll see the
> subtract option listed like this:
>
> *Usage: pcp_combine*
>
> * -subtract input_files*
>
> * out_file*
>
>
> And "*input_files*" is further described as:
>
>
> I*NPUT_FILES:*
>
> * file_1 config_str_1 ... file_n config_str_n | *
>
> * file_1 ... file_n |*
>
> * input_file_list*
>
>
> You're currently using the 2nd option listed there (file_1 ...
file_n) to
> just specify 2 input file names.
>
> But you can switch to the first option instead where each file name
is
> followed by a configuration string.
>
>
> With your data, you'd setup the pcp_combine command something like
this:
>
>
> */usr/local/bin/pcp_combine -subtract \*
>
> *feens1_verify_2020061000f48.grib2 'name="SPRATE"; level="Z0";
> GRIB2_ipdtmpl_index=[8]; GRIB2_ipdtmpl_index=[45];' \*
>
> *feens1_verify_2020061000f24.grib2 'name="SPRATE"; level="Z0";
> GRIB2_ipdtmpl_index=[8]; GRIB2_ipdtmpl_index=[21];' \*
>
> *feens1_snow_24_2020061000f48.nc <
> http://secure-web.cisco.com/13Y8TwQNExAToJZ5lfuY-
QO1cJx09el95PH64AhHXIb-rn11YNMqd8UTAHb60C4Qg49btXB5EOoFlV-
GRO5cXpdPgkf8f5pWY0HEmLELMKsNPUffraasATf6hgekzveWEaWTz5Qqsl4M1e0GPzalSfgT4cCtBGjzmW970UgYx5HQBnb0TP8nUUtZ1qRUYlDdRc5ujxtaMJtjJ12gvmwFMdnIRrI9Oq58yKBkEo-
HC6tqFgATPoZX-
KlCs47tBZwAfjqhIDvCv_B5KkptwRPiIiBT4P9MkRsRfz20iOb672eQo0Ghm1ptCg-
b81b4lXpD_KgAcxYVWwttMhx6ZbkpeWxLnEM6btJ6_yuXBwuxNT9ZmYHQhbXdkhDAGQLQVB3I_/http%3A%2F%2Ffeens1_snow_24_2020061000f48.nc>
> \*
>
> *-name SPRATE_A24*
>
>
> Let me know if that doesn't fix it. Note that I also used the "-
name"
> command line argument to tell pcp_combine how to name the output
variable.
>
>
> Thanks,
> John
>
> On Fri, Jun 19, 2020 at 9:08 AM Minna Win via RT <met_help at ucar.edu>
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95673 >
> >
> > Hi Tom,
> >
> > It looks like you have some questions pertaining to pcp_combine.
I'm
> > assigning this ticket to John Halley Gotway, please allow a few
> > business days for a full response.
> >
> > Regards,
> > Minna
> > ---------------
> > Minna Win
> > National Center for Atmospheric Research Developmental Testbed
Center
> > Phone: 303-497-8423
> > Fax: 303-497-8401
> >
> >
> >
> > On Fri, Jun 19, 2020 at 7:40 AM Workoff, Thomas E via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > >
> > > Fri Jun 19 07:40:16 2020: Request 95673 was acted upon.
> > > Transaction: Ticket created by tworkoff at firstenergycorp.com
> > > Queue: met_help
> > > Subject: Set GRIB2_ipdtmpl_index and GRIB2_ipdtmpl_val for
each
> file
> > > in a pcp_combine usage?
> > > Owner: Nobody
> > > Requestors: tworkoff at firstenergycorp.com
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95673
> >
> > >
> > >
> > > Hi all,
> > >
> > > Ran in to a bit a funny problem, and I wanted to check with you
to see
> if
> > > there's a concrete fix.
> > >
> > > I'm currently creating custom precipitation accumulations in
> pcp_combine.
> > > In this case, I'm using the parameter SPRATE, which holds a
custom
> > snowfall
> > > product. The problem is, the parent grib2 file holds both a
total and
> 3
> > > hour SPRATE variable. I'll include the basic command below to
show you
> > the
> > > base output.
> > >
> > > In the past, I've been able to skip around these kind of
problems with
> > the
> > > other GRIB2 fields, including designating GRIB2_ipdtmpl_index
and
> > > GRIB2_ipdtmpl_val. However, my question in this: can I set
separate
> > > 'field' values for each of the files in a 'subtract' or 'add'
function?
> > Do
> > > I simply enter two 'field' entries?
> > >
> > > In the example below, I can simply sort these out by the 9th
pdt
> value,
> > > which is 0 in the parameter I want, and non-zero in the field I
don't.
> > But
> > > for time periods that start at 0....say if I was creating a
temperature
> > > difference of a 0-3 forecast hour period, this wouldn't be
case...and
> I
> > > would need to use the 27th value to pick the correct parameter
in each
> > > file-the problem being these values differ in the two files I'd
be
> > > subtracting. So, in the example below, if I was simply to enter
> > something
> > > like GRIB2_ipdtmpl_index[26]; GRIB2_ipdtmpl_val[48], this will
fail
> with
> > > the second file needed for the subtraction (since its value will
be 24
> > and
> > > not 48), and the entire process fails. I'll include that as a
second
> set
> > of
> > > output below.
> > >
> > > I hope this makes sense, and I didn't totally confuse you!
> > >
> > > Any insight? Or is at simple as adding a second set of 'field'
> > parameters?
> > >
> > > Thanks!
> > > -Tom
> > >
> > > /usr/local/bin/pcp_combine -subtract
> > >
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> > >
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> > >
/fewxops/verification/data/model/met_output/conusarw/pcp_combine/
> > > feens1_snow_24_2020061000f48.nc -field
'name="SPRATE";level="Z0";'
> > > DEBUG 2: Since the "-field" command line option was used,
parsing the
> > > command line arguments as a list of files.
> > > DEBUG 1: Reading input file:
> > >
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> > > DEBUG 1: Reading data (name="SPRATE";level="Z0";) from input
file:
> > >
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> > > WARNING:
> > > WARNING: MetGrib2DataFile::data_plane() -> Using the first of 2
> matching
> > > records for "SPRATE/Z0":
> > > WARNING: record 25 field 1: ipdtmpl[29] = 1, 66, 2, 0, 116, 0,
0, 1, 0,
> > 1,
> > > 0, 0, 255, 0, 0, 2020, 6, 12, 0, 0, 0, 1, 0, 1, 2, 1, 48, 255, 0
> > > WARNING: record 29 field 1: ipdtmpl[29] = 1, 66, 2, 0, 116, 0,
0, 1,
> 45,
> > > 1, 0, 0, 255, 0, 0, 2020, 6, 12, 0, 0, 0, 1, 0, 2, 2, 1, 3, 255,
0
> > > WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and
> > > "GRIB2_ipdtmpl_val" config file options to select one.
> > > WARNING:
> > > DEBUG 1: Reading input file:
> > >
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> > > DEBUG 1: Reading data (name="SPRATE";level="Z0";) from input
file:
> > >
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> > > WARNING:
> > > WARNING: MetGrib2DataFile::data_plane() -> Using the first of 2
> matching
> > > records for "SPRATE/Z0":
> > > WARNING: record 25 field 1: ipdtmpl[29] = 1, 66, 2, 0, 116, 0,
0, 1, 0,
> > 1,
> > > 0, 0, 255, 0, 0, 2020, 6, 11, 0, 0, 0, 1, 0, 1, 2, 1, 24, 255, 0
> > > WARNING: record 29 field 1: ipdtmpl[29] = 1, 66, 2, 0, 116, 0,
0, 1,
> 21,
> > > 1, 0, 0, 255, 0, 0, 2020, 6, 11, 0, 0, 0, 1, 0, 2, 2, 1, 3, 255,
0
> > > WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and
> > > "GRIB2_ipdtmpl_val" config file options to select one.
> > > WARNING:
> > > DEBUG 2: Performing subtraction command.
> > > DEBUG 1: Creating output file:
> > >
/fewxops/verification/data/model/met_output/conusarw/pcp_combine/
> > > feens1_snow_24_2020061000f48.nc
> > > DEBUG 2: Writing output variable "SPRATE_24" for the "diff" of
> > "SPRATE/Z0".
> > > DEBUG 1: Closing output file:
> > >
/fewxops/verification/data/model/met_output/conusarw/pcp_combine/
> > > feens1_snow_24_2020061000f48.nc
> > >
> > >
> > > /usr/local/bin/pcp_combine -subtract
> > >
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> > >
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> > >
/fewxops/verification/data/model/met_output/conusarw/pcp_combine/
> > > feens1_snow_24_2020061000f48.nc -field
> > >
> >
>
'name="SPRATE";level="Z0";GRIB2_ipdtmpl_index=[26];GRIB2_ipdtmpl_val=[48];'
> > > DEBUG 2: Since the "-field" command line option was used,
parsing the
> > > command line arguments as a list of files.
> > > DEBUG 1: Reading input file:
> > >
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> > > DEBUG 1: Reading data
> > >
> >
>
(name="SPRATE";level="Z0";GRIB2_ipdtmpl_index=[26];GRIB2_ipdtmpl_val=[48];)
> > > from input file:
> > >
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f48.grib2
> > > DEBUG 1: Reading input file:
> > >
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> > > DEBUG 1: Reading data
> > >
> >
>
(name="SPRATE";level="Z0";GRIB2_ipdtmpl_index=[26];GRIB2_ipdtmpl_val=[48];)
> > > from input file:
> > >
> >
>
/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2
> > > WARNING:
> > > WARNING: MetGrib2DataFile::data_plane() -> No matching record
found for
> > > 'SPRATE/Z0'
> > > WARNING:
> > > ERROR :
> > > ERROR : get_field() -> can't get data plane from file
> > >
> >
>
"/fewxops/verification/data/model/grib2/feens1/2020/feens1_verify_2020061000f24.grib2"
> > > ERROR :
> > >
> > >
> > >
> >
>
------------------------------------------------------------------------------
> > >
> > > The information contained in this message is intended only for
the
> > > personal and confidential use of the recipient(s) named above.
If the
> > > reader of this message is not the intended recipient or an agent
> > > responsible for delivering it to the intended recipient, you are
hereby
> > > notified that you have received this document in error and that
any
> > review,
> > > dissemination, distribution, or copying of this message is
strictly
> > > prohibited. If you have received this communication in error,
please
> > notify
> > > us immediately, and delete the original message.
> > >
> > >
> >
> >
>
>
>
>
------------------------------------------------------------------------------
>
> The information contained in this message is intended only for the
> personal and confidential use of the recipient(s) named above. If
the
> reader of this message is not the intended recipient or an agent
> responsible for delivering it to the intended recipient, you are
hereby
> notified that you have received this document in error and that any
review,
> dissemination, distribution, or copying of this message is strictly
> prohibited. If you have received this communication in error, please
notify
> us immediately, and delete the original message.
>
>
>
------------------------------------------------
More information about the Met_help
mailing list