[Met_help] [rt.rap.ucar.edu #92340] History for GRIB1_code question
John Halley Gotway via RT
met_help at ucar.edu
Fri Oct 11 16:22:47 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi,
I noticed that when I use GRIB1_code to choose a record (e.g., for 'fcst' in grid_stat) that FCST_VAR ends up in the .stat output as "NA". Is there any way to populate that field with an identifier?
If I run grid_stat and have multiple variables identified in 'fcst', there's no way to distinguish between the records, unless I use something like the "DESC" field. The only problem there is I can't set multiple values of "DESC" in the config file for grid_stat.
It would be nice if there was a way to allow users to set DESC for each fcst variable. I suppose output_prefix could be leveraged instead to force separate output files for each single variable, which would be an alternate way of avoiding the "NA" ambiguity when multiple fcst fields are identified solely through GRIB1_code.
Maybe MET already has this capability, and I just don't know. But Bob Craig and I thought it was worth asking.
Thanks,
Matt
Matthew C. Sittel, Meteorologist
University Corporation for Atmospheric Research
Matthew.Sittel.ctr at us.af.mil
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: GRIB1_code question
From: Minna Win
Time: Thu Sep 26 08:21:02 2019
Hello,
It looks like you have a question about setting the DESC for each
variable
in your grib data (while using MET grid stat). I'm assigning this
ticket
to John Halley Gotway. Please allow a few business days for a
response.
Thank you for your question.
Regards,
Minna
---------------
Minna Win
National Center for Atmospheric Research
Developmental Testbed Center
Phone: 303-497-8423
Fax: 303-497-8401
On Thu, Sep 26, 2019 at 8:03 AM SITTEL, MATTHEW C CTR USAF AFWA 16
WS/WXN
via RT <met_help at ucar.edu> wrote:
>
> Thu Sep 26 08:02:39 2019: Request 92340 was acted upon.
> Transaction: Ticket created by matthew.sittel.ctr at us.af.mil
> Queue: met_help
> Subject: GRIB1_code question
> Owner: Nobody
> Requestors: matthew.sittel.ctr at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92340 >
>
>
> Hi,
>
> I noticed that when I use GRIB1_code to choose a record (e.g., for
'fcst'
> in grid_stat) that FCST_VAR ends up in the .stat output as "NA". Is
there
> any way to populate that field with an identifier?
>
> If I run grid_stat and have multiple variables identified in 'fcst',
> there's no way to distinguish between the records, unless I use
something
> like the "DESC" field. The only problem there is I can't set
multiple
> values of "DESC" in the config file for grid_stat.
>
> It would be nice if there was a way to allow users to set DESC for
each
> fcst variable. I suppose output_prefix could be leveraged instead
to force
> separate output files for each single variable, which would be an
alternate
> way of avoiding the "NA" ambiguity when multiple fcst fields are
identified
> solely through GRIB1_code.
>
> Maybe MET already has this capability, and I just don't know. But
Bob
> Craig and I thought it was worth asking.
>
> Thanks,
> Matt
>
> Matthew C. Sittel, Meteorologist
> University Corporation for Atmospheric Research
> Matthew.Sittel.ctr at us.af.mil
>
>
>
------------------------------------------------
Subject: GRIB1_code question
From: Minna Win
Time: Thu Sep 26 08:24:31 2019
Hello,
In the meantime, I have an old MET grid stat config file I used for
another
project where I used the 'desc' to identify the level:
fcst = {
field = [
{
name = "TMP";
level = [ "Z2" ];
desc = two_agl;
},
{
name = "TMP";
level = TMP_pres_levels;
desc = pres;
},
Is this what you were looking for?
Thanks,
Minna
---------------
Minna Win
National Center for Atmospheric Research
Developmental Testbed Center
Phone: 303-497-8423
Fax: 303-497-8401
On Thu, Sep 26, 2019 at 8:03 AM SITTEL, MATTHEW C CTR USAF AFWA 16
WS/WXN
via RT <met_help at ucar.edu> wrote:
>
> Thu Sep 26 08:02:39 2019: Request 92340 was acted upon.
> Transaction: Ticket created by matthew.sittel.ctr at us.af.mil
> Queue: met_help
> Subject: GRIB1_code question
> Owner: Nobody
> Requestors: matthew.sittel.ctr at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92340 >
>
>
> Hi,
>
> I noticed that when I use GRIB1_code to choose a record (e.g., for
'fcst'
> in grid_stat) that FCST_VAR ends up in the .stat output as "NA". Is
there
> any way to populate that field with an identifier?
>
> If I run grid_stat and have multiple variables identified in 'fcst',
> there's no way to distinguish between the records, unless I use
something
> like the "DESC" field. The only problem there is I can't set
multiple
> values of "DESC" in the config file for grid_stat.
>
> It would be nice if there was a way to allow users to set DESC for
each
> fcst variable. I suppose output_prefix could be leveraged instead
to force
> separate output files for each single variable, which would be an
alternate
> way of avoiding the "NA" ambiguity when multiple fcst fields are
identified
> solely through GRIB1_code.
>
> Maybe MET already has this capability, and I just don't know. But
Bob
> Craig and I thought it was worth asking.
>
> Thanks,
> Matt
>
> Matthew C. Sittel, Meteorologist
> University Corporation for Atmospheric Research
> Matthew.Sittel.ctr at us.af.mil
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #92340] GRIB1_code question
From: SITTEL, MATTHEW C CTR USAF AFWA 16 WS/WXN
Time: Thu Sep 26 08:36:44 2019
Hi Minna,
I just tested putting "desc" in both fcst and obs definitions. MET
only writes it out when it's used in the obs variable definition.
When set only in fcst it is ignored and set to "NA".
I can certainly work with desc being limited only to obs definitions.
I should have noticed the comment in the config file template that
says desc can be set in each obs.field entry.
The last part about setting the suffix separately still applies.
Matt
-----Original Message-----
From: Minna Win via RT <met_help at ucar.edu>
Sent: Thursday, September 26, 2019 9:25 AM
To: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL
<matthew.sittel.ctr at us.af.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #92340] GRIB1_code
question
Hello,
In the meantime, I have an old MET grid stat config file I used for
another project where I used the 'desc' to identify the level:
fcst = {
field = [
{
name = "TMP";
level = [ "Z2" ];
desc = two_agl;
},
{
name = "TMP";
level = TMP_pres_levels;
desc = pres;
},
Is this what you were looking for?
Thanks,
Minna
---------------
Minna Win
National Center for Atmospheric Research Developmental Testbed Center
Phone: 303-497-8423
Fax: 303-497-8401
On Thu, Sep 26, 2019 at 8:03 AM SITTEL, MATTHEW C CTR USAF AFWA 16
WS/WXN via RT <met_help at ucar.edu> wrote:
>
> Thu Sep 26 08:02:39 2019: Request 92340 was acted upon.
> Transaction: Ticket created by matthew.sittel.ctr at us.af.mil
> Queue: met_help
> Subject: GRIB1_code question
> Owner: Nobody
> Requestors: matthew.sittel.ctr at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92340
> >
>
>
> Hi,
>
> I noticed that when I use GRIB1_code to choose a record (e.g., for
'fcst'
> in grid_stat) that FCST_VAR ends up in the .stat output as "NA". Is
> there any way to populate that field with an identifier?
>
> If I run grid_stat and have multiple variables identified in 'fcst',
> there's no way to distinguish between the records, unless I use
> something like the "DESC" field. The only problem there is I can't
> set multiple values of "DESC" in the config file for grid_stat.
>
> It would be nice if there was a way to allow users to set DESC for
> each fcst variable. I suppose output_prefix could be leveraged
> instead to force separate output files for each single variable,
which
> would be an alternate way of avoiding the "NA" ambiguity when
multiple
> fcst fields are identified solely through GRIB1_code.
>
> Maybe MET already has this capability, and I just don't know. But
Bob
> Craig and I thought it was worth asking.
>
> Thanks,
> Matt
>
> Matthew C. Sittel, Meteorologist
> University Corporation for Atmospheric Research
> Matthew.Sittel.ctr at us.af.mil
>
>
>
------------------------------------------------
Subject: GRIB1_code question
From: John Halley Gotway
Time: Thu Sep 26 10:00:55 2019
Hi Matt,
You and Minna are correct that you can specify DESC separately for
each
entry in the "obs.field" array. But I understand that that doesn't
give
the exact control over the output that you'd like.
Let me point out a development issue that we have listed for met-9.0
that
would directly address this issue:
https://github.com/NCAR/MET/issues/1020
We'd like to add a "set_hdr" option that could be added to each of the
"obs.field" array entries. This would enable you to explicitly
override
any of the output columns written for that verification task. In your
case, you'd set "FCST_VAR = {REAL_VARIABLE_NAME}" and/or "OBS_VAR =
{REAL_VARIABLE_NAME}". But it could also be used to update the level
columns, units, timing info, or any of the other first 21 header
columns.
But that doesn't exist in met-8.1.
With met-8.1 I think the best solution would be to avoid using
"GRIB1_code"
in the first place. Instead, define your custom GRIB table usage in a
custom GRIB table. Set the MET_GRIB_TABLES environment variable to
point
to it. Rather than using GRIB1_code in the config file, just request
the
actual name that you put in that custom GRIB table.
Hope that helps clarify. Let me know if you need any help getting up
and
running creating a custom GRIB table.
Thanks,
John
On Thu, Sep 26, 2019 at 8:37 AM SITTEL, MATTHEW C CTR USAF AFWA 16
WS/WXN
via RT <met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92340 >
>
> Hi Minna,
>
> I just tested putting "desc" in both fcst and obs definitions. MET
only
> writes it out when it's used in the obs variable definition. When
set only
> in fcst it is ignored and set to "NA".
>
> I can certainly work with desc being limited only to obs
definitions. I
> should have noticed the comment in the config file template that
says desc
> can be set in each obs.field entry.
>
> The last part about setting the suffix separately still applies.
>
> Matt
>
> -----Original Message-----
> From: Minna Win via RT <met_help at ucar.edu>
> Sent: Thursday, September 26, 2019 9:25 AM
> To: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> matthew.sittel.ctr at us.af.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #92340] GRIB1_code
question
>
> Hello,
>
> In the meantime, I have an old MET grid stat config file I used for
> another project where I used the 'desc' to identify the level:
>
> fcst = {
>
>
> field = [
>
> {
>
> name = "TMP";
>
> level = [ "Z2" ];
>
> desc = two_agl;
>
> },
>
> {
>
> name = "TMP";
>
> level = TMP_pres_levels;
>
> desc = pres;
>
> },
>
>
> Is this what you were looking for?
>
> Thanks,
> Minna
> ---------------
> Minna Win
> National Center for Atmospheric Research Developmental Testbed
Center
> Phone: 303-497-8423
> Fax: 303-497-8401
>
>
>
> On Thu, Sep 26, 2019 at 8:03 AM SITTEL, MATTHEW C CTR USAF AFWA 16
WS/WXN
> via RT <met_help at ucar.edu> wrote:
>
> >
> > Thu Sep 26 08:02:39 2019: Request 92340 was acted upon.
> > Transaction: Ticket created by matthew.sittel.ctr at us.af.mil
> > Queue: met_help
> > Subject: GRIB1_code question
> > Owner: Nobody
> > Requestors: matthew.sittel.ctr at us.af.mil
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92340
> > >
> >
> >
> > Hi,
> >
> > I noticed that when I use GRIB1_code to choose a record (e.g., for
'fcst'
> > in grid_stat) that FCST_VAR ends up in the .stat output as "NA".
Is
> > there any way to populate that field with an identifier?
> >
> > If I run grid_stat and have multiple variables identified in
'fcst',
> > there's no way to distinguish between the records, unless I use
> > something like the "DESC" field. The only problem there is I
can't
> > set multiple values of "DESC" in the config file for grid_stat.
> >
> > It would be nice if there was a way to allow users to set DESC for
> > each fcst variable. I suppose output_prefix could be leveraged
> > instead to force separate output files for each single variable,
which
> > would be an alternate way of avoiding the "NA" ambiguity when
multiple
> > fcst fields are identified solely through GRIB1_code.
> >
> > Maybe MET already has this capability, and I just don't know. But
Bob
> > Craig and I thought it was worth asking.
> >
> > Thanks,
> > Matt
> >
> > Matthew C. Sittel, Meteorologist
> > University Corporation for Atmospheric Research
> > Matthew.Sittel.ctr at us.af.mil
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #92340] GRIB1_code question
From: SITTEL, MATTHEW C CTR USAF AFWA 16 WS/WXN
Time: Thu Sep 26 12:37:12 2019
Hi John,
I did switch away from using the GRIB1_code setting. My problem was
the GRIB1 table didn't have all the correct numbers for the record I
was reading. Once I had them correct the variable name now works as
it should.
We have some weirdness in the ensemble data; they used certain kpds
values for cloud ceiling data but the variable names listed in the
GRIB data are those from the standard GRIB1 table (e.g., MLI, UICE).
My workaround will be to use DESC to put their correct ceiling
variable names and ignoring the variable field.
Thanks for your help, and for the information about MET 9. That
should be useful to Bob and me both.
Matt
-----Original Message-----
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Thursday, September 26, 2019 11:01 AM
To: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL
<matthew.sittel.ctr at us.af.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #92340] GRIB1_code
question
Hi Matt,
You and Minna are correct that you can specify DESC separately for
each entry in the "obs.field" array. But I understand that that
doesn't give the exact control over the output that you'd like.
Let me point out a development issue that we have listed for met-9.0
that would directly address this issue:
https://github.com/NCAR/MET/issues/1020
We'd like to add a "set_hdr" option that could be added to each of the
"obs.field" array entries. This would enable you to explicitly
override any of the output columns written for that verification task.
In your case, you'd set "FCST_VAR = {REAL_VARIABLE_NAME}" and/or
"OBS_VAR = {REAL_VARIABLE_NAME}". But it could also be used to update
the level columns, units, timing info, or any of the other first 21
header columns.
But that doesn't exist in met-8.1.
With met-8.1 I think the best solution would be to avoid using
"GRIB1_code"
in the first place. Instead, define your custom GRIB table usage in a
custom GRIB table. Set the MET_GRIB_TABLES environment variable to
point to it. Rather than using GRIB1_code in the config file, just
request the actual name that you put in that custom GRIB table.
Hope that helps clarify. Let me know if you need any help getting up
and running creating a custom GRIB table.
Thanks,
John
On Thu, Sep 26, 2019 at 8:37 AM SITTEL, MATTHEW C CTR USAF AFWA 16
WS/WXN via RT <met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92340 >
>
> Hi Minna,
>
> I just tested putting "desc" in both fcst and obs definitions. MET
> only writes it out when it's used in the obs variable definition.
> When set only in fcst it is ignored and set to "NA".
>
> I can certainly work with desc being limited only to obs
definitions.
> I should have noticed the comment in the config file template that
> says desc can be set in each obs.field entry.
>
> The last part about setting the suffix separately still applies.
>
> Matt
>
> -----Original Message-----
> From: Minna Win via RT <met_help at ucar.edu>
> Sent: Thursday, September 26, 2019 9:25 AM
> To: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> matthew.sittel.ctr at us.af.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #92340] GRIB1_code
> question
>
> Hello,
>
> In the meantime, I have an old MET grid stat config file I used for
> another project where I used the 'desc' to identify the level:
>
> fcst = {
>
>
> field = [
>
> {
>
> name = "TMP";
>
> level = [ "Z2" ];
>
> desc = two_agl;
>
> },
>
> {
>
> name = "TMP";
>
> level = TMP_pres_levels;
>
> desc = pres;
>
> },
>
>
> Is this what you were looking for?
>
> Thanks,
> Minna
> ---------------
> Minna Win
> National Center for Atmospheric Research Developmental Testbed
Center
> Phone: 303-497-8423
> Fax: 303-497-8401
>
>
>
> On Thu, Sep 26, 2019 at 8:03 AM SITTEL, MATTHEW C CTR USAF AFWA 16
> WS/WXN via RT <met_help at ucar.edu> wrote:
>
> >
> > Thu Sep 26 08:02:39 2019: Request 92340 was acted upon.
> > Transaction: Ticket created by matthew.sittel.ctr at us.af.mil
> > Queue: met_help
> > Subject: GRIB1_code question
> > Owner: Nobody
> > Requestors: matthew.sittel.ctr at us.af.mil
> > Status: new
> > Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92340
> > >
> >
> >
> > Hi,
> >
> > I noticed that when I use GRIB1_code to choose a record (e.g., for
'fcst'
> > in grid_stat) that FCST_VAR ends up in the .stat output as "NA".
Is
> > there any way to populate that field with an identifier?
> >
> > If I run grid_stat and have multiple variables identified in
'fcst',
> > there's no way to distinguish between the records, unless I use
> > something like the "DESC" field. The only problem there is I
can't
> > set multiple values of "DESC" in the config file for grid_stat.
> >
> > It would be nice if there was a way to allow users to set DESC for
> > each fcst variable. I suppose output_prefix could be leveraged
> > instead to force separate output files for each single variable,
> > which would be an alternate way of avoiding the "NA" ambiguity
when
> > multiple fcst fields are identified solely through GRIB1_code.
> >
> > Maybe MET already has this capability, and I just don't know. But
> > Bob Craig and I thought it was worth asking.
> >
> > Thanks,
> > Matt
> >
> > Matthew C. Sittel, Meteorologist
> > University Corporation for Atmospheric Research
> > Matthew.Sittel.ctr at us.af.mil
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: GRIB1_code question
From: John Halley Gotway
Time: Thu Sep 26 16:47:36 2019
Matt,
I see that some creative construction of the AF GRIB files has led to
the
contents of the output FCST_VAR and/or OBS_VAR columns not actually
matching the data that you're processing. And this is exactly the
motivation for that enhancement in met-9.0 to easily override the
contents
of the output header columns.
BUT, you can still fix this now. Your custom GRIB table does not need
to
be complete. Let's say there's just 2 variables for which the output
name
doesn't accurately describe the real data. You can create a custom
GRIB table that only includes those 2 lines. MET reads in your custom
GRIB table FIRST and then reads in the defaults second. Your custom
settings will override the default ones. It may make your life easier
in
the long run to get this set up and working well now so that you
really can
trust the output FCST_VAR and OBS_VAR columns.
If you'd like to pursue that and have questions, just let me know. I
vaguely recall Bob doing this in the past?
Thanks,
John
On Thu, Sep 26, 2019 at 12:37 PM SITTEL, MATTHEW C CTR USAF AFWA 16
WS/WXN
via RT <met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92340 >
>
> Hi John,
>
> I did switch away from using the GRIB1_code setting. My problem was
the
> GRIB1 table didn't have all the correct numbers for the record I was
> reading. Once I had them correct the variable name now works as it
should.
>
> We have some weirdness in the ensemble data; they used certain kpds
values
> for cloud ceiling data but the variable names listed in the GRIB
data are
> those from the standard GRIB1 table (e.g., MLI, UICE). My
workaround will
> be to use DESC to put their correct ceiling variable names and
ignoring the
> variable field.
>
> Thanks for your help, and for the information about MET 9. That
should be
> useful to Bob and me both.
>
> Matt
>
> -----Original Message-----
> From: John Halley Gotway via RT <met_help at ucar.edu>
> Sent: Thursday, September 26, 2019 11:01 AM
> To: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> matthew.sittel.ctr at us.af.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #92340]
GRIB1_code
> question
>
> Hi Matt,
>
> You and Minna are correct that you can specify DESC separately for
each
> entry in the "obs.field" array. But I understand that that doesn't
give
> the exact control over the output that you'd like.
>
> Let me point out a development issue that we have listed for met-9.0
that
> would directly address this issue:
> https://github.com/NCAR/MET/issues/1020
>
> We'd like to add a "set_hdr" option that could be added to each of
the
> "obs.field" array entries. This would enable you to explicitly
override
> any of the output columns written for that verification task. In
your
> case, you'd set "FCST_VAR = {REAL_VARIABLE_NAME}" and/or "OBS_VAR =
> {REAL_VARIABLE_NAME}". But it could also be used to update the
level
> columns, units, timing info, or any of the other first 21 header
columns.
> But that doesn't exist in met-8.1.
>
> With met-8.1 I think the best solution would be to avoid using
"GRIB1_code"
> in the first place. Instead, define your custom GRIB table usage in
a
> custom GRIB table. Set the MET_GRIB_TABLES environment variable to
point
> to it. Rather than using GRIB1_code in the config file, just
request the
> actual name that you put in that custom GRIB table.
>
> Hope that helps clarify. Let me know if you need any help getting
up and
> running creating a custom GRIB table.
>
> Thanks,
> John
>
> On Thu, Sep 26, 2019 at 8:37 AM SITTEL, MATTHEW C CTR USAF AFWA 16
WS/WXN
> via RT <met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92340 >
> >
> > Hi Minna,
> >
> > I just tested putting "desc" in both fcst and obs definitions.
MET
> > only writes it out when it's used in the obs variable definition.
> > When set only in fcst it is ignored and set to "NA".
> >
> > I can certainly work with desc being limited only to obs
definitions.
> > I should have noticed the comment in the config file template that
> > says desc can be set in each obs.field entry.
> >
> > The last part about setting the suffix separately still applies.
> >
> > Matt
> >
> > -----Original Message-----
> > From: Minna Win via RT <met_help at ucar.edu>
> > Sent: Thursday, September 26, 2019 9:25 AM
> > To: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> > matthew.sittel.ctr at us.af.mil>
> > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #92340] GRIB1_code
> > question
> >
> > Hello,
> >
> > In the meantime, I have an old MET grid stat config file I used
for
> > another project where I used the 'desc' to identify the level:
> >
> > fcst = {
> >
> >
> > field = [
> >
> > {
> >
> > name = "TMP";
> >
> > level = [ "Z2" ];
> >
> > desc = two_agl;
> >
> > },
> >
> > {
> >
> > name = "TMP";
> >
> > level = TMP_pres_levels;
> >
> > desc = pres;
> >
> > },
> >
> >
> > Is this what you were looking for?
> >
> > Thanks,
> > Minna
> > ---------------
> > Minna Win
> > National Center for Atmospheric Research Developmental Testbed
Center
> > Phone: 303-497-8423
> > Fax: 303-497-8401
> >
> >
> >
> > On Thu, Sep 26, 2019 at 8:03 AM SITTEL, MATTHEW C CTR USAF AFWA 16
> > WS/WXN via RT <met_help at ucar.edu> wrote:
> >
> > >
> > > Thu Sep 26 08:02:39 2019: Request 92340 was acted upon.
> > > Transaction: Ticket created by matthew.sittel.ctr at us.af.mil
> > > Queue: met_help
> > > Subject: GRIB1_code question
> > > Owner: Nobody
> > > Requestors: matthew.sittel.ctr at us.af.mil
> > > Status: new
> > > Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92340
> > > >
> > >
> > >
> > > Hi,
> > >
> > > I noticed that when I use GRIB1_code to choose a record (e.g.,
for
> 'fcst'
> > > in grid_stat) that FCST_VAR ends up in the .stat output as "NA".
Is
> > > there any way to populate that field with an identifier?
> > >
> > > If I run grid_stat and have multiple variables identified in
'fcst',
> > > there's no way to distinguish between the records, unless I use
> > > something like the "DESC" field. The only problem there is I
can't
> > > set multiple values of "DESC" in the config file for grid_stat.
> > >
> > > It would be nice if there was a way to allow users to set DESC
for
> > > each fcst variable. I suppose output_prefix could be leveraged
> > > instead to force separate output files for each single variable,
> > > which would be an alternate way of avoiding the "NA" ambiguity
when
> > > multiple fcst fields are identified solely through GRIB1_code.
> > >
> > > Maybe MET already has this capability, and I just don't know.
But
> > > Bob Craig and I thought it was worth asking.
> > >
> > > Thanks,
> > > Matt
> > >
> > > Matthew C. Sittel, Meteorologist
> > > University Corporation for Atmospheric Research
> > > Matthew.Sittel.ctr at us.af.mil
> > >
> > >
> > >
> >
> >
> >
> >
>
>
>
>
------------------------------------------------
More information about the Met_help
mailing list