[Met_help] [rt.rap.ucar.edu #96930] History for changing names of variables in METplus
John Halley Gotway via RT
met_help at ucar.edu
Tue Oct 13 12:47:45 MDT 2020
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi, there,
Got a question. Is there a way to change the name of the variable written
out to the .stat file in point_stat than what the FCST_VAR1_NAME is?
The reason why I ask is that PMTF is the variable for the hourly PM, but
it's also the name of the variable (in the grib2 file) for the daily
average PM. But for the .stat files, we need to be able to differentiate
between the hourly PM and the daily average PM. Can we change the name of
the forecast variable so that it is different than the grib search term?
Thanks!
Perry
--
Perry C. Shafran
Verification/MEG Group Leader for IMSG
VPPPG Branch of EMC/NCEP/NOAA/NWS
Office: 301-683-3765
Cell: 301-717-6454
perry.shafran at noaa.gov
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: changing names of variables in METplus
From: John Halley Gotway
Time: Fri Oct 02 09:30:15 2020
Perry,
Indeed there is! New as of met-9.1. And your question makes me glad we
added it.
Listed below are several config file options we added that begin with
“set_attr”. This is taken from the user's guide on this page:
https://dtcenter.github.io/MET/Users_Guide/data_io.html
// // Data attributes
// set_attr_name = "string";
// set_attr_level = "string";
// set_attr_units = "string";
// set_attr_long_name = "string";
//
// // Time attributes
// set_attr_init = "YYYYMMDD[_HH[MMSS]]";
// set_attr_valid = "YYYYMMDD[_HH[MMSS]]";
// set_attr_lead = "HH[MMSS]";
// set_attr_accum = "HH[MMSS]";
//
// // Grid definition (must match the actual data dimensions)
// set_attr_grid = "named grid or grid specification string";
Since you want to update the variable name, you'd use:
set_attr_name = "AVGPMTF"; // or whatever string you'd like to use
And since you're running this through METplus, you'd put this into the
METplus config file like this:
FCST_VAR1_OPTIONS = set_attr_name = "AVGPMTF";
Now I haven't actually tested this myself through METplus to confirm
that
it works as expected, but that's how it *should* work. Similarly, you
can
define the output level string, units, long name (only written to
NetCDF
output files), timing information, and even grid definition. In fact,
the
original reason for adding these options was a GRIB file with an
incorrect
grid definition. It was supposed to be over the north pole but the
grid
spec defined it's location as Australia.
Please let me know if this does the trick.
Thanks,
John
On Fri, Oct 2, 2020 at 6:51 AM perry.shafran at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
>
> Fri Oct 02 06:51:57 2020: Request 96930 was acted upon.
>
> Transaction: Ticket created by perry.shafran at noaa.gov
>
> Queue: met_help
>
> Subject: changing names of variables in METplus
>
> Owner: Nobody
>
> Requestors: perry.shafran at noaa.gov
>
> Status: new
>
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=96930 >
>
>
>
>
>
> Hi, there,
>
>
>
> Got a question. Is there a way to change the name of the variable
written
>
> out to the .stat file in point_stat than what the FCST_VAR1_NAME is?
>
>
>
> The reason why I ask is that PMTF is the variable for the hourly PM,
but
>
> it's also the name of the variable (in the grib2 file) for the daily
>
> average PM. But for the .stat files, we need to be able to
differentiate
>
> between the hourly PM and the daily average PM. Can we change the
name of
>
> the forecast variable so that it is different than the grib search
term?
>
>
>
> Thanks!
>
>
>
> Perry
>
>
>
> --
>
> Perry C. Shafran
>
> Verification/MEG Group Leader for IMSG
>
> VPPPG Branch of EMC/NCEP/NOAA/NWS
>
> Office: 301-683-3765
>
> Cell: 301-717-6454
>
> perry.shafran at noaa.gov
>
>
>
>
------------------------------------------------
Subject: changing names of variables in METplus
From: perry.shafran at noaa.gov
Time: Fri Oct 02 09:34:34 2020
Thanks! I am sending this to Ed Strobach, who is having trouble with
this
issue. It seems to easily be done for precip, as I see the
accumulating
length appended to the end of the variable, while all instances of
precip
are identified as APCP in the grib2 files. This must be a bit
different.
We do want to make sure that this setting will still find the variable
name
PMTF in the grib file but then write something else out like PMAVE or
something like that.
Ed - take a look at this and let us know if it works.
Thanks!
Perry
On Fri, Oct 2, 2020 at 11:30 AM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
> Perry,
>
> Indeed there is! New as of met-9.1. And your question makes me glad
we
> added it.
>
> Listed below are several config file options we added that begin
with
> “set_attr”. This is taken from the user's guide on this page:
> https://dtcenter.github.io/MET/Users_Guide/data_io.html
>
> // // Data attributes
> // set_attr_name = "string";
> // set_attr_level = "string";
> // set_attr_units = "string";
> // set_attr_long_name = "string";
> //
> // // Time attributes
> // set_attr_init = "YYYYMMDD[_HH[MMSS]]";
> // set_attr_valid = "YYYYMMDD[_HH[MMSS]]";
> // set_attr_lead = "HH[MMSS]";
> // set_attr_accum = "HH[MMSS]";
> //
> // // Grid definition (must match the actual data dimensions)
> // set_attr_grid = "named grid or grid specification
string";
>
>
> Since you want to update the variable name, you'd use:
> set_attr_name = "AVGPMTF"; // or whatever string you'd like to
use
>
> And since you're running this through METplus, you'd put this into
the
> METplus config file like this:
>
> FCST_VAR1_OPTIONS = set_attr_name = "AVGPMTF";
>
> Now I haven't actually tested this myself through METplus to confirm
that
> it works as expected, but that's how it *should* work. Similarly,
you can
> define the output level string, units, long name (only written to
NetCDF
> output files), timing information, and even grid definition. In
fact, the
> original reason for adding these options was a GRIB file with an
incorrect
> grid definition. It was supposed to be over the north pole but the
grid
> spec defined it's location as Australia.
>
> Please let me know if this does the trick.
>
> Thanks,
> John
>
> On Fri, Oct 2, 2020 at 6:51 AM perry.shafran at noaa.gov via RT <
> met_help at ucar.edu> wrote:
>
> >
> >
> > Fri Oct 02 06:51:57 2020: Request 96930 was acted upon.
> >
> > Transaction: Ticket created by perry.shafran at noaa.gov
> >
> > Queue: met_help
> >
> > Subject: changing names of variables in METplus
> >
> > Owner: Nobody
> >
> > Requestors: perry.shafran at noaa.gov
> >
> > Status: new
> >
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=96930 >
> >
> >
> >
> >
> >
> > Hi, there,
> >
> >
> >
> > Got a question. Is there a way to change the name of the variable
> written
> >
> > out to the .stat file in point_stat than what the FCST_VAR1_NAME
is?
> >
> >
> >
> > The reason why I ask is that PMTF is the variable for the hourly
PM, but
> >
> > it's also the name of the variable (in the grib2 file) for the
daily
> >
> > average PM. But for the .stat files, we need to be able to
differentiate
> >
> > between the hourly PM and the daily average PM. Can we change the
name
> of
> >
> > the forecast variable so that it is different than the grib search
term?
> >
> >
> >
> > Thanks!
> >
> >
> >
> > Perry
> >
> >
> >
> > --
> >
> > Perry C. Shafran
> >
> > Verification/MEG Group Leader for IMSG
> >
> > VPPPG Branch of EMC/NCEP/NOAA/NWS
> >
> > Office: 301-683-3765
> >
> > Cell: 301-717-6454
> >
> > perry.shafran at noaa.gov
> >
> >
> >
> >
>
>
--
Perry C. Shafran
Verification/MEG Group Leader for IMSG
VPPPG Branch of EMC/NCEP/NOAA/NWS
Office: 301-683-3765
Cell: 301-717-6454
perry.shafran at noaa.gov
------------------------------------------------
Subject: changing names of variables in METplus
From: Edward Strobach - NOAA Affiliate
Time: Fri Oct 02 09:42:56 2020
Thanks. So I simply add this into my point_stat_pmave.conf file?
On Fri, Oct 2, 2020 at 11:34 AM Perry Shafran - NOAA Affiliate <
perry.shafran at noaa.gov> wrote:
> Thanks! I am sending this to Ed Strobach, who is having trouble
with this
> issue. It seems to easily be done for precip, as I see the
accumulating
> length appended to the end of the variable, while all instances of
precip
> are identified as APCP in the grib2 files. This must be a bit
different.
>
> We do want to make sure that this setting will still find the
variable
> name PMTF in the grib file but then write something else out like
PMAVE or
> something like that.
>
> Ed - take a look at this and let us know if it works.
>
> Thanks!
>
> Perry
>
> On Fri, Oct 2, 2020 at 11:30 AM John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
>> Perry,
>>
>> Indeed there is! New as of met-9.1. And your question makes me glad
we
>> added it.
>>
>> Listed below are several config file options we added that begin
with
>> “set_attr”. This is taken from the user's guide on this page:
>> https://dtcenter.github.io/MET/Users_Guide/data_io.html
>>
>> // // Data attributes
>> // set_attr_name = "string";
>> // set_attr_level = "string";
>> // set_attr_units = "string";
>> // set_attr_long_name = "string";
>> //
>> // // Time attributes
>> // set_attr_init = "YYYYMMDD[_HH[MMSS]]";
>> // set_attr_valid = "YYYYMMDD[_HH[MMSS]]";
>> // set_attr_lead = "HH[MMSS]";
>> // set_attr_accum = "HH[MMSS]";
>> //
>> // // Grid definition (must match the actual data
dimensions)
>> // set_attr_grid = "named grid or grid specification
string";
>>
>>
>> Since you want to update the variable name, you'd use:
>> set_attr_name = "AVGPMTF"; // or whatever string you'd like to
use
>>
>> And since you're running this through METplus, you'd put this into
the
>> METplus config file like this:
>>
>> FCST_VAR1_OPTIONS = set_attr_name = "AVGPMTF";
>>
>> Now I haven't actually tested this myself through METplus to
confirm that
>> it works as expected, but that's how it *should* work. Similarly,
you can
>> define the output level string, units, long name (only written to
NetCDF
>> output files), timing information, and even grid definition. In
fact, the
>> original reason for adding these options was a GRIB file with an
incorrect
>> grid definition. It was supposed to be over the north pole but the
grid
>> spec defined it's location as Australia.
>>
>> Please let me know if this does the trick.
>>
>> Thanks,
>> John
>>
>> On Fri, Oct 2, 2020 at 6:51 AM perry.shafran at noaa.gov via RT <
>> met_help at ucar.edu> wrote:
>>
>> >
>> >
>> > Fri Oct 02 06:51:57 2020: Request 96930 was acted upon.
>> >
>> > Transaction: Ticket created by perry.shafran at noaa.gov
>> >
>> > Queue: met_help
>> >
>> > Subject: changing names of variables in METplus
>> >
>> > Owner: Nobody
>> >
>> > Requestors: perry.shafran at noaa.gov
>> >
>> > Status: new
>> >
>> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=96930 >
>> >
>> >
>> >
>> >
>> >
>> > Hi, there,
>> >
>> >
>> >
>> > Got a question. Is there a way to change the name of the
variable
>> written
>> >
>> > out to the .stat file in point_stat than what the FCST_VAR1_NAME
is?
>> >
>> >
>> >
>> > The reason why I ask is that PMTF is the variable for the hourly
PM, but
>> >
>> > it's also the name of the variable (in the grib2 file) for the
daily
>> >
>> > average PM. But for the .stat files, we need to be able to
>> differentiate
>> >
>> > between the hourly PM and the daily average PM. Can we change
the name
>> of
>> >
>> > the forecast variable so that it is different than the grib
search term?
>> >
>> >
>> >
>> > Thanks!
>> >
>> >
>> >
>> > Perry
>> >
>> >
>> >
>> > --
>> >
>> > Perry C. Shafran
>> >
>> > Verification/MEG Group Leader for IMSG
>> >
>> > VPPPG Branch of EMC/NCEP/NOAA/NWS
>> >
>> > Office: 301-683-3765
>> >
>> > Cell: 301-717-6454
>> >
>> > perry.shafran at noaa.gov
>> >
>> >
>> >
>> >
>>
>>
>
> --
> Perry C. Shafran
> Verification/MEG Group Leader for IMSG
> VPPPG Branch of EMC/NCEP/NOAA/NWS
> Office: 301-683-3765
> Cell: 301-717-6454
> perry.shafran at noaa.gov
>
--
Edward Strobach
EMC/NCEP/NWS/
IMSG Contractor
Cubicle#: 2029
301-683-3717
------------------------------------------------
Subject: changing names of variables in METplus
From: John Halley Gotway
Time: Fri Oct 02 09:47:21 2020
Perry,
That's a good point about precip. You're right, the code appends the
accumulation interval to the variable name. But there is currently no
logic
to append an "averaging period" for something like PM. So we have
custom
code that handles accumulations but not averaging periods.
If there's some simple logic that could be defined, we could look into
automatically appending the averaging period. However, that's the sort
of
change that makes me worry about unintended consequences.
Ed, is "point_stat_pmave.conf" the name of your METplus config file or
is
it the Point-Stat config file? If you're running this through METplus,
you'd add an entry for FCST_VAR1_OPTIONS. If you're running Point-Stat
directly, you'd add "set_attr_name" to the Point-Stat config file
immediately after you define the variable "name" and "level" string.
John
On Fri, Oct 2, 2020 at 9:37 AM perry.shafran at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=96930 >
>
> Thanks! I am sending this to Ed Strobach, who is having trouble
with this
> issue. It seems to easily be done for precip, as I see the
accumulating
> length appended to the end of the variable, while all instances of
precip
> are identified as APCP in the grib2 files. This must be a bit
different.
>
> We do want to make sure that this setting will still find the
variable name
> PMTF in the grib file but then write something else out like PMAVE
or
> something like that.
>
> Ed - take a look at this and let us know if it works.
>
> Thanks!
>
> Perry
>
> On Fri, Oct 2, 2020 at 11:30 AM John Halley Gotway via RT <
> met_help at ucar.edu>
> wrote:
>
> > Perry,
> >
> > Indeed there is! New as of met-9.1. And your question makes me
glad we
> > added it.
> >
> > Listed below are several config file options we added that begin
with
> > “set_attr”. This is taken from the user's guide on this page:
> > https://dtcenter.github.io/MET/Users_Guide/data_io.html
> >
> > // // Data attributes
> > // set_attr_name = "string";
> > // set_attr_level = "string";
> > // set_attr_units = "string";
> > // set_attr_long_name = "string";
> > //
> > // // Time attributes
> > // set_attr_init = "YYYYMMDD[_HH[MMSS]]";
> > // set_attr_valid = "YYYYMMDD[_HH[MMSS]]";
> > // set_attr_lead = "HH[MMSS]";
> > // set_attr_accum = "HH[MMSS]";
> > //
> > // // Grid definition (must match the actual data
dimensions)
> > // set_attr_grid = "named grid or grid specification
string";
> >
> >
> > Since you want to update the variable name, you'd use:
> > set_attr_name = "AVGPMTF"; // or whatever string you'd like to
use
> >
> > And since you're running this through METplus, you'd put this into
the
> > METplus config file like this:
> >
> > FCST_VAR1_OPTIONS = set_attr_name = "AVGPMTF";
> >
> > Now I haven't actually tested this myself through METplus to
confirm that
> > it works as expected, but that's how it *should* work. Similarly,
you can
> > define the output level string, units, long name (only written to
NetCDF
> > output files), timing information, and even grid definition. In
fact, the
> > original reason for adding these options was a GRIB file with an
> incorrect
> > grid definition. It was supposed to be over the north pole but the
grid
> > spec defined it's location as Australia.
> >
> > Please let me know if this does the trick.
> >
> > Thanks,
> > John
> >
> > On Fri, Oct 2, 2020 at 6:51 AM perry.shafran at noaa.gov via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > >
> > > Fri Oct 02 06:51:57 2020: Request 96930 was acted upon.
> > >
> > > Transaction: Ticket created by perry.shafran at noaa.gov
> > >
> > > Queue: met_help
> > >
> > > Subject: changing names of variables in METplus
> > >
> > > Owner: Nobody
> > >
> > > Requestors: perry.shafran at noaa.gov
> > >
> > > Status: new
> > >
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=96930
> >
> > >
> > >
> > >
> > >
> > >
> > > Hi, there,
> > >
> > >
> > >
> > > Got a question. Is there a way to change the name of the
variable
> > written
> > >
> > > out to the .stat file in point_stat than what the FCST_VAR1_NAME
is?
> > >
> > >
> > >
> > > The reason why I ask is that PMTF is the variable for the hourly
PM,
> but
> > >
> > > it's also the name of the variable (in the grib2 file) for the
daily
> > >
> > > average PM. But for the .stat files, we need to be able to
> differentiate
> > >
> > > between the hourly PM and the daily average PM. Can we change
the name
> > of
> > >
> > > the forecast variable so that it is different than the grib
search
> term?
> > >
> > >
> > >
> > > Thanks!
> > >
> > >
> > >
> > > Perry
> > >
> > >
> > >
> > > --
> > >
> > > Perry C. Shafran
> > >
> > > Verification/MEG Group Leader for IMSG
> > >
> > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > >
> > > Office: 301-683-3765
> > >
> > > Cell: 301-717-6454
> > >
> > > perry.shafran at noaa.gov
> > >
> > >
> > >
> > >
> >
> >
>
> --
> Perry C. Shafran
> Verification/MEG Group Leader for IMSG
> VPPPG Branch of EMC/NCEP/NOAA/NWS
> Office: 301-683-3765
> Cell: 301-717-6454
> perry.shafran at noaa.gov
>
>
------------------------------------------------
Subject: changing names of variables in METplus
From: perry.shafran at noaa.gov
Time: Fri Oct 02 10:33:13 2020
I don't think Ed saw your message, but I think he's going to try it to
see
what happens.
Thanks!
Perry
On Fri, Oct 2, 2020 at 11:47 AM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
> Perry,
>
> That's a good point about precip. You're right, the code appends the
> accumulation interval to the variable name. But there is currently
no logic
> to append an "averaging period" for something like PM. So we have
custom
> code that handles accumulations but not averaging periods.
>
> If there's some simple logic that could be defined, we could look
into
> automatically appending the averaging period. However, that's the
sort of
> change that makes me worry about unintended consequences.
>
> Ed, is "point_stat_pmave.conf" the name of your METplus config file
or is
> it the Point-Stat config file? If you're running this through
METplus,
> you'd add an entry for FCST_VAR1_OPTIONS. If you're running Point-
Stat
> directly, you'd add "set_attr_name" to the Point-Stat config file
> immediately after you define the variable "name" and "level" string.
>
> John
>
> On Fri, Oct 2, 2020 at 9:37 AM perry.shafran at noaa.gov via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=96930 >
> >
> > Thanks! I am sending this to Ed Strobach, who is having trouble
with
> this
> > issue. It seems to easily be done for precip, as I see the
accumulating
> > length appended to the end of the variable, while all instances of
precip
> > are identified as APCP in the grib2 files. This must be a bit
different.
> >
> > We do want to make sure that this setting will still find the
variable
> name
> > PMTF in the grib file but then write something else out like PMAVE
or
> > something like that.
> >
> > Ed - take a look at this and let us know if it works.
> >
> > Thanks!
> >
> > Perry
> >
> > On Fri, Oct 2, 2020 at 11:30 AM John Halley Gotway via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > > Perry,
> > >
> > > Indeed there is! New as of met-9.1. And your question makes me
glad we
> > > added it.
> > >
> > > Listed below are several config file options we added that begin
with
> > > “set_attr”. This is taken from the user's guide on this page:
> > > https://dtcenter.github.io/MET/Users_Guide/data_io.html
> > >
> > > // // Data attributes
> > > // set_attr_name = "string";
> > > // set_attr_level = "string";
> > > // set_attr_units = "string";
> > > // set_attr_long_name = "string";
> > > //
> > > // // Time attributes
> > > // set_attr_init = "YYYYMMDD[_HH[MMSS]]";
> > > // set_attr_valid = "YYYYMMDD[_HH[MMSS]]";
> > > // set_attr_lead = "HH[MMSS]";
> > > // set_attr_accum = "HH[MMSS]";
> > > //
> > > // // Grid definition (must match the actual data
dimensions)
> > > // set_attr_grid = "named grid or grid specification
string";
> > >
> > >
> > > Since you want to update the variable name, you'd use:
> > > set_attr_name = "AVGPMTF"; // or whatever string you'd like
to use
> > >
> > > And since you're running this through METplus, you'd put this
into the
> > > METplus config file like this:
> > >
> > > FCST_VAR1_OPTIONS = set_attr_name = "AVGPMTF";
> > >
> > > Now I haven't actually tested this myself through METplus to
confirm
> that
> > > it works as expected, but that's how it *should* work.
Similarly, you
> can
> > > define the output level string, units, long name (only written
to
> NetCDF
> > > output files), timing information, and even grid definition. In
fact,
> the
> > > original reason for adding these options was a GRIB file with an
> > incorrect
> > > grid definition. It was supposed to be over the north pole but
the grid
> > > spec defined it's location as Australia.
> > >
> > > Please let me know if this does the trick.
> > >
> > > Thanks,
> > > John
> > >
> > > On Fri, Oct 2, 2020 at 6:51 AM perry.shafran at noaa.gov via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > >
> > > > Fri Oct 02 06:51:57 2020: Request 96930 was acted upon.
> > > >
> > > > Transaction: Ticket created by perry.shafran at noaa.gov
> > > >
> > > > Queue: met_help
> > > >
> > > > Subject: changing names of variables in METplus
> > > >
> > > > Owner: Nobody
> > > >
> > > > Requestors: perry.shafran at noaa.gov
> > > >
> > > > Status: new
> > > >
> > > > Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=96930
> > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Hi, there,
> > > >
> > > >
> > > >
> > > > Got a question. Is there a way to change the name of the
variable
> > > written
> > > >
> > > > out to the .stat file in point_stat than what the
FCST_VAR1_NAME is?
> > > >
> > > >
> > > >
> > > > The reason why I ask is that PMTF is the variable for the
hourly PM,
> > but
> > > >
> > > > it's also the name of the variable (in the grib2 file) for the
daily
> > > >
> > > > average PM. But for the .stat files, we need to be able to
> > differentiate
> > > >
> > > > between the hourly PM and the daily average PM. Can we change
the
> name
> > > of
> > > >
> > > > the forecast variable so that it is different than the grib
search
> > term?
> > > >
> > > >
> > > >
> > > > Thanks!
> > > >
> > > >
> > > >
> > > > Perry
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Perry C. Shafran
> > > >
> > > > Verification/MEG Group Leader for IMSG
> > > >
> > > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > >
> > > > Office: 301-683-3765
> > > >
> > > > Cell: 301-717-6454
> > > >
> > > > perry.shafran at noaa.gov
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> > --
> > Perry C. Shafran
> > Verification/MEG Group Leader for IMSG
> > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > Office: 301-683-3765
> > Cell: 301-717-6454
> > perry.shafran at noaa.gov
> >
> >
>
>
--
Perry C. Shafran
Verification/MEG Group Leader for IMSG
VPPPG Branch of EMC/NCEP/NOAA/NWS
Office: 301-683-3765
Cell: 301-717-6454
perry.shafran at noaa.gov
------------------------------------------------
Subject: changing names of variables in METplus
From: John Halley Gotway
Time: Tue Oct 13 12:41:52 2020
Perry and Ed,
Just wanted to follow up. Is this still an ongoing METplus issue? Or
should I resolve this met_help ticket?
Thanks,
John
------------------------------------------------
Subject: changing names of variables in METplus
From: perry.shafran at noaa.gov
Time: Tue Oct 13 12:43:13 2020
I believe it's resolved.
Ed - are we good with this one?
Thanks!
Perry
On Tue, Oct 13, 2020 at 2:42 PM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
> Perry and Ed,
>
> Just wanted to follow up. Is this still an ongoing METplus issue? Or
> should I resolve this met_help ticket?
>
> Thanks,
> John
>
--
Perry C. Shafran
Verification/MEG Group Leader for IMSG
VPPPG Branch of EMC/NCEP/NOAA/NWS
Office: 301-683-3765
Cell: 301-717-6454
perry.shafran at noaa.gov
------------------------------------------------
Subject: changing names of variables in METplus
From: Edward Strobach - NOAA Affiliate
Time: Tue Oct 13 12:44:32 2020
oh yeah, we are good! Thanks!
On Tue, Oct 13, 2020 at 2:43 PM Perry Shafran - NOAA Affiliate <
perry.shafran at noaa.gov> wrote:
> I believe it's resolved.
>
> Ed - are we good with this one?
>
> Thanks!
>
> Perry
>
> On Tue, Oct 13, 2020 at 2:42 PM John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
>> Perry and Ed,
>>
>> Just wanted to follow up. Is this still an ongoing METplus issue?
Or
>> should I resolve this met_help ticket?
>>
>> Thanks,
>> John
>>
>
>
> --
> Perry C. Shafran
> Verification/MEG Group Leader for IMSG
> VPPPG Branch of EMC/NCEP/NOAA/NWS
> Office: 301-683-3765
> Cell: 301-717-6454
> perry.shafran at noaa.gov
>
--
Edward Strobach
EMC/NCEP/NWS/
IMSG Contractor
Cubicle#: 2029
301-683-3717
------------------------------------------------
More information about the Met_help
mailing list