[Met_help] [rt.rap.ucar.edu #84975] History for pointstat question
John Halley Gotway via RT
met_help at ucar.edu
Mon May 7 16:26:44 MDT 2018
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hello,
I created a month long (30) of grib files each containing the analysis plus hourly fcsts to 24 hours. I also have observations formatted by ascii2nc for the whole 30-day period in a single file. I ‘d like to run pointstat to create statistics for 0 and 24hrs leads. Is it possible to do that/how should I configure the run? Is there a ready R script in the distribution that I can use to plot such stats?
Thanks,
Mariusz
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #84975] AutoReply: pointstat question
From: Mariusz Pagowski
Time: Wed May 02 15:43:58 2018
I found this entires in the manual
fcst = {
init_time = "${year}${month}${day}_${hour}";
lead_time = "$fcst_hour";
}
That puts me a step further but still looking for a way to create
average stats for hourly fcst leads the whole period without writing
an R script.
Thanks for any suggestions,
Mariusz
> On May 2, 2018, at 2:53 PM, met_help at ucar.edu via RT
<met_help at ucar.edu> wrote:
>
> Greetings,
>
> This message has been automatically generated in response to the
> creation of a trouble ticket regarding:
> "pointstat question",
> a summary of which appears below.
>
> There is no need to reply to this message right now. Your ticket
has been
> assigned an ID of [rt.rap.ucar.edu #84975].
>
> Please include the string:
>
> [rt.rap.ucar.edu #84975]
>
> in the subject line of all future correspondence about this issue.
To do so,
> you may reply to this message.
>
> For more information, please see:
>
> MET Online Tutorial:
>
https://www.dtcenter.org/met/users/support/online_tutorial/index.php
>
> MET Users Guide:
> https://www.dtcenter.org/met/users/docs/overview.php
>
> MET FAQs:
> https://www.dtcenter.org/met/users/support/faqs/index.php
>
> MET-Help Email Archive:
> http://mailman.ucar.edu/pipermail/met_help
>
> Thank you,
> met_help at ucar.edu
>
>
-------------------------------------------------------------------------
> Hello,
> I created a month long (30) of grib files each containing the
analysis plus hourly fcsts to 24 hours. I also have observations
formatted by ascii2nc for the whole 30-day period in a single file. I
‘d like to run pointstat to create statistics for 0 and 24hrs leads.
Is it possible to do that/how should I configure the run? Is there a
ready R script in the distribution that I can use to plot such stats?
> Thanks,
> Mariusz
>
>
>
------------------------------------------------
Subject: pointstat question
From: John Halley Gotway
Time: Fri May 04 14:56:26 2018
Hi Mariusz,
Sorry for the delay in responding. I see that you have grouped an
entire
month's worth of data into a single GRIB file. Generally, the MET
tools
are designed to be run once per forecast valid time. We typically
find
that users have separate GRIB output files for each combination of
model
initialization and forecast lead time.
Let's say you run Point-Stat, ask it to verify 2-meter temperature,
and
pass it that GRIB file containing a month of data. It'll search for
2-m
temperature in that file and find many, many matching records! It'll
print
a warning message and just use the first one it finds.
For this reason, in the Point-Stat configuration file, you can specify
timing information. Included below, I've copied-and-pasted a
selection
from the file named met-7.0/data/config/README. It describes what
time
filtering is supported.
I would recommend using a script to loop over your timing information,
set
environment variables, and then call Point-Stat to verify the current
time.
For example:
fcst = {
field = [
{
name = "TMP";
level = [ "Z2" ];
init_time = "${CUR_INIT_TIME}";
lead_time = "${CUR_LEAD_TIME}";
}
];
Where CUR_INIT_TIME is set to 20180501_00 and CUR_LEAD_TIME is set to
12.
That'd verify the 12-hour forecast from the model initialized on May
1st at
00Z.
Hope this helps clarify.
Thanks,
John
//
// - The "init_time" entry specifies the initialization time in
YYYYMMDD[_HH[MMSS]]
// format. This entry can be included in the "fcst" entry as
shown
below or
// included in the "field" entry if the user would like to use
different
// initialization times for different fields.
//
// - The "valid_time" entry specifies the valid time in
YYYYMMDD[_HH[MMSS]]
// format. This entry can be included in the "fcst" entry as
shown
below or
// included in the "field" entry if the user would like to use
different
// valid times for different fields.
//
// - The "lead_time" entry specifies the lead time in HH[MMSS]
// format. This entry can be included in the "fcst" entry as
shown
below or
// included in the "field" entry if the user would like to use
different
// lead times for different fields.
//
// It is only necessary to use the "init_time", "valid_time", and/or
"lead_time"
// settings when verifying a file containing data for multiple output
times.
// For example, to verify a GRIB file containing data for many lead
times,
you
// could use "lead_time" to specify the record to be verified.
//
On Wed, May 2, 2018 at 3:43 PM, Mariusz Pagowski via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84975 >
>
> I found this entires in the manual
> fcst = {
> init_time = "${year}${month}${day}_${hour}";
> lead_time = "$fcst_hour";
> }
> That puts me a step further but still looking for a way to create
average
> stats for hourly fcst leads the whole period without writing
> an R script.
> Thanks for any suggestions,
> Mariusz
>
>
>
> > On May 2, 2018, at 2:53 PM, met_help at ucar.edu via RT
<met_help at ucar.edu>
> wrote:
> >
> > Greetings,
> >
> > This message has been automatically generated in response to the
> > creation of a trouble ticket regarding:
> > "pointstat question",
> > a summary of which appears below.
> >
> > There is no need to reply to this message right now. Your ticket
has
> been
> > assigned an ID of [rt.rap.ucar.edu #84975].
> >
> > Please include the string:
> >
> > [rt.rap.ucar.edu #84975]
> >
> > in the subject line of all future correspondence about this issue.
To do
> so,
> > you may reply to this message.
> >
> > For more information, please see:
> >
> > MET Online Tutorial:
> >
https://www.dtcenter.org/met/users/support/online_tutorial/index.php
> >
> > MET Users Guide:
> > https://www.dtcenter.org/met/users/docs/overview.php
> >
> > MET FAQs:
> > https://www.dtcenter.org/met/users/support/faqs/index.php
> >
> > MET-Help Email Archive:
> > http://mailman.ucar.edu/pipermail/met_help
> >
> > Thank you,
> > met_help at ucar.edu
> >
> > ------------------------------------------------------------
> -------------
> > Hello,
> > I created a month long (30) of grib files each containing the
analysis
> plus hourly fcsts to 24 hours. I also have observations formatted by
> ascii2nc for the whole 30-day period in a single file. I ‘d like to
run
> pointstat to create statistics for 0 and 24hrs leads. Is it
possible to do
> that/how should I configure the run? Is there a ready R script in
the
> distribution that I can use to plot such stats?
> > Thanks,
> > Mariusz
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #84975] AutoReply: pointstat question
From: Mariusz Pagowski
Time: Fri May 04 15:12:43 2018
Thanks John,
I grouped 24-hr forecasts in to daily grib files but put all month-
long obs (there are not that many) into a single file.
Your delayed reply made me learn something in the meantime by reading
the manual more carefully as answers to my questions are mostly there.
I used Point-Stat and then Stat-Analysis to get what I needed for
plotting average stats.
Thanks again,
Mariusz
> On May 4, 2018, at 2:56 PM, John Halley Gotway via RT
<met_help at ucar.edu> wrote:
>
> Hi Mariusz,
>
> Sorry for the delay in responding. I see that you have grouped an
entire
> month's worth of data into a single GRIB file. Generally, the MET
tools
> are designed to be run once per forecast valid time. We typically
find
> that users have separate GRIB output files for each combination of
model
> initialization and forecast lead time.
>
> Let's say you run Point-Stat, ask it to verify 2-meter temperature,
and
> pass it that GRIB file containing a month of data. It'll search for
2-m
> temperature in that file and find many, many matching records!
It'll print
> a warning message and just use the first one it finds.
>
> For this reason, in the Point-Stat configuration file, you can
specify
> timing information. Included below, I've copied-and-pasted a
selection
> from the file named met-7.0/data/config/README. It describes what
time
> filtering is supported.
>
> I would recommend using a script to loop over your timing
information, set
> environment variables, and then call Point-Stat to verify the
current time.
>
> For example:
>
> fcst = {
> field = [
> {
> name = "TMP";
> level = [ "Z2" ];
> init_time = "${CUR_INIT_TIME}";
> lead_time = "${CUR_LEAD_TIME}";
> }
> ];
>
> Where CUR_INIT_TIME is set to 20180501_00 and CUR_LEAD_TIME is set
to 12.
>
> That'd verify the 12-hour forecast from the model initialized on May
1st at
> 00Z.
>
> Hope this helps clarify.
>
> Thanks,
> John
>
> //
> // - The "init_time" entry specifies the initialization time in
> YYYYMMDD[_HH[MMSS]]
> // format. This entry can be included in the "fcst" entry as
shown
> below or
> // included in the "field" entry if the user would like to use
different
> // initialization times for different fields.
> //
> // - The "valid_time" entry specifies the valid time in
> YYYYMMDD[_HH[MMSS]]
> // format. This entry can be included in the "fcst" entry as
shown
> below or
> // included in the "field" entry if the user would like to use
different
> // valid times for different fields.
> //
> // - The "lead_time" entry specifies the lead time in HH[MMSS]
> // format. This entry can be included in the "fcst" entry as
shown
> below or
> // included in the "field" entry if the user would like to use
different
> // lead times for different fields.
> //
> // It is only necessary to use the "init_time", "valid_time", and/or
> "lead_time"
> // settings when verifying a file containing data for multiple
output times.
> // For example, to verify a GRIB file containing data for many lead
times,
> you
> // could use "lead_time" to specify the record to be verified.
> //
>
> On Wed, May 2, 2018 at 3:43 PM, Mariusz Pagowski via RT
<met_help at ucar.edu>
> wrote:
>
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84975 >
>>
>> I found this entires in the manual
>> fcst = {
>> init_time = "${year}${month}${day}_${hour}";
>> lead_time = "$fcst_hour";
>> }
>> That puts me a step further but still looking for a way to create
average
>> stats for hourly fcst leads the whole period without writing
>> an R script.
>> Thanks for any suggestions,
>> Mariusz
>>
>>
>>
>>> On May 2, 2018, at 2:53 PM, met_help at ucar.edu via RT
<met_help at ucar.edu>
>> wrote:
>>>
>>> Greetings,
>>>
>>> This message has been automatically generated in response to the
>>> creation of a trouble ticket regarding:
>>> "pointstat question",
>>> a summary of which appears below.
>>>
>>> There is no need to reply to this message right now. Your ticket
has
>> been
>>> assigned an ID of [rt.rap.ucar.edu #84975].
>>>
>>> Please include the string:
>>>
>>> [rt.rap.ucar.edu #84975]
>>>
>>> in the subject line of all future correspondence about this issue.
To do
>> so,
>>> you may reply to this message.
>>>
>>> For more information, please see:
>>>
>>> MET Online Tutorial:
>>>
https://www.dtcenter.org/met/users/support/online_tutorial/index.php
>>>
>>> MET Users Guide:
>>> https://www.dtcenter.org/met/users/docs/overview.php
>>>
>>> MET FAQs:
>>> https://www.dtcenter.org/met/users/support/faqs/index.php
>>>
>>> MET-Help Email Archive:
>>> http://mailman.ucar.edu/pipermail/met_help
>>>
>>> Thank you,
>>> met_help at ucar.edu
>>>
>>> ------------------------------------------------------------
>> -------------
>>> Hello,
>>> I created a month long (30) of grib files each containing the
analysis
>> plus hourly fcsts to 24 hours. I also have observations formatted
by
>> ascii2nc for the whole 30-day period in a single file. I ‘d like to
run
>> pointstat to create statistics for 0 and 24hrs leads. Is it
possible to do
>> that/how should I configure the run? Is there a ready R script in
the
>> distribution that I can use to plot such stats?
>>> Thanks,
>>> Mariusz
>>>
>>>
>>>
>>
>>
>>
>>
>
------------------------------------------------
Subject: pointstat question
From: John Halley Gotway
Time: Mon May 07 15:08:37 2018
Mariusz,
Just wanted to follow up on this ticket. Do you have any more open
questions or issues or should I resolve it?
Thanks,
John
On Fri, May 4, 2018 at 3:12 PM, Mariusz Pagowski via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84975 >
>
> Thanks John,
> I grouped 24-hr forecasts in to daily grib files but put all month-
long
> obs (there are not that many) into a single file.
> Your delayed reply made me learn something in the meantime by
reading the
> manual more carefully as answers to my questions are mostly there.
> I used Point-Stat and then Stat-Analysis to get what I needed for
plotting
> average stats.
> Thanks again,
> Mariusz
>
>
> > On May 4, 2018, at 2:56 PM, John Halley Gotway via RT
<met_help at ucar.edu>
> wrote:
> >
> > Hi Mariusz,
> >
> > Sorry for the delay in responding. I see that you have grouped an
entire
> > month's worth of data into a single GRIB file. Generally, the MET
tools
> > are designed to be run once per forecast valid time. We typically
find
> > that users have separate GRIB output files for each combination of
model
> > initialization and forecast lead time.
> >
> > Let's say you run Point-Stat, ask it to verify 2-meter
temperature, and
> > pass it that GRIB file containing a month of data. It'll search
for 2-m
> > temperature in that file and find many, many matching records!
It'll
> print
> > a warning message and just use the first one it finds.
> >
> > For this reason, in the Point-Stat configuration file, you can
specify
> > timing information. Included below, I've copied-and-pasted a
selection
> > from the file named met-7.0/data/config/README. It describes what
time
> > filtering is supported.
> >
> > I would recommend using a script to loop over your timing
information,
> set
> > environment variables, and then call Point-Stat to verify the
current
> time.
> >
> > For example:
> >
> > fcst = {
> > field = [
> > {
> > name = "TMP";
> > level = [ "Z2" ];
> > init_time = "${CUR_INIT_TIME}";
> > lead_time = "${CUR_LEAD_TIME}";
> > }
> > ];
> >
> > Where CUR_INIT_TIME is set to 20180501_00 and CUR_LEAD_TIME is set
to 12.
> >
> > That'd verify the 12-hour forecast from the model initialized on
May 1st
> at
> > 00Z.
> >
> > Hope this helps clarify.
> >
> > Thanks,
> > John
> >
> > //
> > // - The "init_time" entry specifies the initialization time in
> > YYYYMMDD[_HH[MMSS]]
> > // format. This entry can be included in the "fcst" entry as
shown
> > below or
> > // included in the "field" entry if the user would like to use
> different
> > // initialization times for different fields.
> > //
> > // - The "valid_time" entry specifies the valid time in
> > YYYYMMDD[_HH[MMSS]]
> > // format. This entry can be included in the "fcst" entry as
shown
> > below or
> > // included in the "field" entry if the user would like to use
> different
> > // valid times for different fields.
> > //
> > // - The "lead_time" entry specifies the lead time in HH[MMSS]
> > // format. This entry can be included in the "fcst" entry as
shown
> > below or
> > // included in the "field" entry if the user would like to use
> different
> > // lead times for different fields.
> > //
> > // It is only necessary to use the "init_time", "valid_time",
and/or
> > "lead_time"
> > // settings when verifying a file containing data for multiple
output
> times.
> > // For example, to verify a GRIB file containing data for many
lead
> times,
> > you
> > // could use "lead_time" to specify the record to be verified.
> > //
> >
> > On Wed, May 2, 2018 at 3:43 PM, Mariusz Pagowski via RT <
> met_help at ucar.edu>
> > wrote:
> >
> >>
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84975 >
> >>
> >> I found this entires in the manual
> >> fcst = {
> >> init_time = "${year}${month}${day}_${hour}";
> >> lead_time = "$fcst_hour";
> >> }
> >> That puts me a step further but still looking for a way to create
> average
> >> stats for hourly fcst leads the whole period without writing
> >> an R script.
> >> Thanks for any suggestions,
> >> Mariusz
> >>
> >>
> >>
> >>> On May 2, 2018, at 2:53 PM, met_help at ucar.edu via RT <
> met_help at ucar.edu>
> >> wrote:
> >>>
> >>> Greetings,
> >>>
> >>> This message has been automatically generated in response to the
> >>> creation of a trouble ticket regarding:
> >>> "pointstat question",
> >>> a summary of which appears below.
> >>>
> >>> There is no need to reply to this message right now. Your
ticket has
> >> been
> >>> assigned an ID of [rt.rap.ucar.edu #84975].
> >>>
> >>> Please include the string:
> >>>
> >>> [rt.rap.ucar.edu #84975]
> >>>
> >>> in the subject line of all future correspondence about this
issue. To
> do
> >> so,
> >>> you may reply to this message.
> >>>
> >>> For more information, please see:
> >>>
> >>> MET Online Tutorial:
> >>>
https://www.dtcenter.org/met/users/support/online_tutorial/index.php
> >>>
> >>> MET Users Guide:
> >>> https://www.dtcenter.org/met/users/docs/overview.php
> >>>
> >>> MET FAQs:
> >>> https://www.dtcenter.org/met/users/support/faqs/index.php
> >>>
> >>> MET-Help Email Archive:
> >>> http://mailman.ucar.edu/pipermail/met_help
> >>>
> >>> Thank you,
> >>> met_help at ucar.edu
> >>>
> >>> ------------------------------------------------------------
> >> -------------
> >>> Hello,
> >>> I created a month long (30) of grib files each containing the
analysis
> >> plus hourly fcsts to 24 hours. I also have observations formatted
by
> >> ascii2nc for the whole 30-day period in a single file. I ‘d like
to run
> >> pointstat to create statistics for 0 and 24hrs leads. Is it
possible
> to do
> >> that/how should I configure the run? Is there a ready R script in
the
> >> distribution that I can use to plot such stats?
> >>> Thanks,
> >>> Mariusz
> >>>
> >>>
> >>>
> >>
> >>
> >>
> >>
> >
>
>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #84975] AutoReply: pointstat question
From: Mariusz Pagowski
Time: Mon May 07 15:10:11 2018
John,
No, I don’t have any more question on that ticket, thanks,
Mariusz
> On May 7, 2018, at 3:08 PM, John Halley Gotway via RT
<met_help at ucar.edu> wrote:
>
> Mariusz,
>
> Just wanted to follow up on this ticket. Do you have any more open
> questions or issues or should I resolve it?
>
> Thanks,
> John
>
> On Fri, May 4, 2018 at 3:12 PM, Mariusz Pagowski via RT
<met_help at ucar.edu>
> wrote:
>
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84975 >
>>
>> Thanks John,
>> I grouped 24-hr forecasts in to daily grib files but put all month-
long
>> obs (there are not that many) into a single file.
>> Your delayed reply made me learn something in the meantime by
reading the
>> manual more carefully as answers to my questions are mostly there.
>> I used Point-Stat and then Stat-Analysis to get what I needed for
plotting
>> average stats.
>> Thanks again,
>> Mariusz
>>
>>
>>> On May 4, 2018, at 2:56 PM, John Halley Gotway via RT
<met_help at ucar.edu>
>> wrote:
>>>
>>> Hi Mariusz,
>>>
>>> Sorry for the delay in responding. I see that you have grouped an
entire
>>> month's worth of data into a single GRIB file. Generally, the MET
tools
>>> are designed to be run once per forecast valid time. We typically
find
>>> that users have separate GRIB output files for each combination of
model
>>> initialization and forecast lead time.
>>>
>>> Let's say you run Point-Stat, ask it to verify 2-meter
temperature, and
>>> pass it that GRIB file containing a month of data. It'll search
for 2-m
>>> temperature in that file and find many, many matching records!
It'll
>> print
>>> a warning message and just use the first one it finds.
>>>
>>> For this reason, in the Point-Stat configuration file, you can
specify
>>> timing information. Included below, I've copied-and-pasted a
selection
>>> from the file named met-7.0/data/config/README. It describes what
time
>>> filtering is supported.
>>>
>>> I would recommend using a script to loop over your timing
information,
>> set
>>> environment variables, and then call Point-Stat to verify the
current
>> time.
>>>
>>> For example:
>>>
>>> fcst = {
>>> field = [
>>> {
>>> name = "TMP";
>>> level = [ "Z2" ];
>>> init_time = "${CUR_INIT_TIME}";
>>> lead_time = "${CUR_LEAD_TIME}";
>>> }
>>> ];
>>>
>>> Where CUR_INIT_TIME is set to 20180501_00 and CUR_LEAD_TIME is set
to 12.
>>>
>>> That'd verify the 12-hour forecast from the model initialized on
May 1st
>> at
>>> 00Z.
>>>
>>> Hope this helps clarify.
>>>
>>> Thanks,
>>> John
>>>
>>> //
>>> // - The "init_time" entry specifies the initialization time in
>>> YYYYMMDD[_HH[MMSS]]
>>> // format. This entry can be included in the "fcst" entry as
shown
>>> below or
>>> // included in the "field" entry if the user would like to use
>> different
>>> // initialization times for different fields.
>>> //
>>> // - The "valid_time" entry specifies the valid time in
>>> YYYYMMDD[_HH[MMSS]]
>>> // format. This entry can be included in the "fcst" entry as
shown
>>> below or
>>> // included in the "field" entry if the user would like to use
>> different
>>> // valid times for different fields.
>>> //
>>> // - The "lead_time" entry specifies the lead time in HH[MMSS]
>>> // format. This entry can be included in the "fcst" entry as
shown
>>> below or
>>> // included in the "field" entry if the user would like to use
>> different
>>> // lead times for different fields.
>>> //
>>> // It is only necessary to use the "init_time", "valid_time",
and/or
>>> "lead_time"
>>> // settings when verifying a file containing data for multiple
output
>> times.
>>> // For example, to verify a GRIB file containing data for many
lead
>> times,
>>> you
>>> // could use "lead_time" to specify the record to be verified.
>>> //
>>>
>>> On Wed, May 2, 2018 at 3:43 PM, Mariusz Pagowski via RT <
>> met_help at ucar.edu>
>>> wrote:
>>>
>>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84975 >
>>>>
>>>> I found this entires in the manual
>>>> fcst = {
>>>> init_time = "${year}${month}${day}_${hour}";
>>>> lead_time = "$fcst_hour";
>>>> }
>>>> That puts me a step further but still looking for a way to create
>> average
>>>> stats for hourly fcst leads the whole period without writing
>>>> an R script.
>>>> Thanks for any suggestions,
>>>> Mariusz
>>>>
>>>>
>>>>
>>>>> On May 2, 2018, at 2:53 PM, met_help at ucar.edu via RT <
>> met_help at ucar.edu>
>>>> wrote:
>>>>>
>>>>> Greetings,
>>>>>
>>>>> This message has been automatically generated in response to the
>>>>> creation of a trouble ticket regarding:
>>>>> "pointstat question",
>>>>> a summary of which appears below.
>>>>>
>>>>> There is no need to reply to this message right now. Your
ticket has
>>>> been
>>>>> assigned an ID of [rt.rap.ucar.edu #84975].
>>>>>
>>>>> Please include the string:
>>>>>
>>>>> [rt.rap.ucar.edu #84975]
>>>>>
>>>>> in the subject line of all future correspondence about this
issue. To
>> do
>>>> so,
>>>>> you may reply to this message.
>>>>>
>>>>> For more information, please see:
>>>>>
>>>>> MET Online Tutorial:
>>>>>
https://www.dtcenter.org/met/users/support/online_tutorial/index.php
>>>>>
>>>>> MET Users Guide:
>>>>> https://www.dtcenter.org/met/users/docs/overview.php
>>>>>
>>>>> MET FAQs:
>>>>> https://www.dtcenter.org/met/users/support/faqs/index.php
>>>>>
>>>>> MET-Help Email Archive:
>>>>> http://mailman.ucar.edu/pipermail/met_help
>>>>>
>>>>> Thank you,
>>>>> met_help at ucar.edu
>>>>>
>>>>> ------------------------------------------------------------
>>>> -------------
>>>>> Hello,
>>>>> I created a month long (30) of grib files each containing the
analysis
>>>> plus hourly fcsts to 24 hours. I also have observations formatted
by
>>>> ascii2nc for the whole 30-day period in a single file. I ‘d like
to run
>>>> pointstat to create statistics for 0 and 24hrs leads. Is it
possible
>> to do
>>>> that/how should I configure the run? Is there a ready R script in
the
>>>> distribution that I can use to plot such stats?
>>>>> Thanks,
>>>>> Mariusz
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>>
>
------------------------------------------------
More information about the Met_help
mailing list