[Met_help] [rt.rap.ucar.edu #57438] History for MET PLEASE HELP
John Halley Gotway via RT
met_help at ucar.edu
Thu Aug 23 08:19:10 MDT 2012
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hello Sir/Miss,
I've tried to run the point stat. tools in MET. It seems that t can read the data but not using the data for comparison.
Do you know what's going on with the program?Thank you very much for your attention.
Regards,
Jackie
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #57438] MET PLEASE HELP
From: John Halley Gotway
Time: Mon Jul 16 06:59:05 2012
Jackie,
Please try rerunning the same command but set the verbosity level to 3
using the "-v 3" command line option. That will include in the output
a list of reasons why 0 observations were not used for
each verification task. There are many reasons why you could end up
with 0 matches, and hopefully the additional log messages will help us
figure it out.
Second, I see the following in your configuration file:
fcst_field[] = [ "TMP/P750-900" ];
obs_field[] = [ "TMP/P500" ];
This isn't necessarily a problem but it is the reason you're seeing
this warning message in the log file you sent me:
WARNING: PointStatConfInfo::process_config() -> The range of requested
observation pressure levels is not contained within the range of
requested forecast pressure levels. No vertical interpolation
will be performed for observations falling outside the range of
forecast levels. Instead, they will be matched to the single nearest
forecast level.
You're telling Point-Stat to use temperature observations defined at
the 500 mb level and compare them against the forecasts that are
defined between 750 and 900 mb. What will really happen is that
the obs at 500 mb will only be compared with the forecast at 750 mb,
as described in that warning message. Perhaps you have a good reason
for doing this, but typically the following comparison would
be performed instead:
fcst_field[] = [ "TMP/P750-900" ];
obs_field[] = [ "TMP/P750-900" ];
That compares any observation falling between 750mb and 900mb to the
corresponding forecast levels.
Hope that helps.
Thanks,
John Halley Gotway
met_help at ucar.edu
On 07/15/2012 11:45 PM, NG Ignatius via RT wrote:
>
> Sun Jul 15 23:45:09 2012: Request 57438 was acted upon.
> Transaction: Ticket created by jackie_seek at hotmail.com
> Queue: met_help
> Subject: MET PLEASE HELP
> Owner: Nobody
> Requestors: jackie_seek at hotmail.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=57438 >
>
>
>
> Hello Sir/Miss,
>
> I've tried to run the point stat. tools in MET. It seems that t can
read the data but not using the data for comparison.
> Do you know what's going on with the program?Thank you very much for
your attention.
> Regards,
> Jackie
>
------------------------------------------------
Subject: MET PLEASE HELP
From: NG Ignatius
Time: Mon Jul 16 22:02:34 2012
Hi John,
I tried to follow your suggestions but it seems that there are no any
matching pairs.
And do you know what causes this happened?
thanks
Jackie
> Subject: Re: [rt.rap.ucar.edu #57438] MET PLEASE HELP
> From: met_help at ucar.edu
> To: jackie_seek at hotmail.com
> Date: Mon, 16 Jul 2012 06:59:05 -0600
>
> Jackie,
>
> Please try rerunning the same command but set the verbosity level to
3 using the "-v 3" command line option. That will include in the
output a list of reasons why 0 observations were not used for
> each verification task. There are many reasons why you could end up
with 0 matches, and hopefully the additional log messages will help us
figure it out.
>
> Second, I see the following in your configuration file:
> fcst_field[] = [ "TMP/P750-900" ];
> obs_field[] = [ "TMP/P500" ];
>
> This isn't necessarily a problem but it is the reason you're seeing
this warning message in the log file you sent me:
>
> WARNING: PointStatConfInfo::process_config() -> The range of
requested observation pressure levels is not contained within the
range of requested forecast pressure levels. No vertical
interpolation
> will be performed for observations falling outside the range of
forecast levels. Instead, they will be matched to the single nearest
forecast level.
>
> You're telling Point-Stat to use temperature observations defined at
the 500 mb level and compare them against the forecasts that are
defined between 750 and 900 mb. What will really happen is that
> the obs at 500 mb will only be compared with the forecast at 750 mb,
as described in that warning message. Perhaps you have a good reason
for doing this, but typically the following comparison would
> be performed instead:
> fcst_field[] = [ "TMP/P750-900" ];
> obs_field[] = [ "TMP/P750-900" ];
>
> That compares any observation falling between 750mb and 900mb to the
corresponding forecast levels.
>
> Hope that helps.
>
> Thanks,
> John Halley Gotway
> met_help at ucar.edu
>
> On 07/15/2012 11:45 PM, NG Ignatius via RT wrote:
> >
> > Sun Jul 15 23:45:09 2012: Request 57438 was acted upon.
> > Transaction: Ticket created by jackie_seek at hotmail.com
> > Queue: met_help
> > Subject: MET PLEASE HELP
> > Owner: Nobody
> > Requestors: jackie_seek at hotmail.com
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=57438 >
> >
> >
> >
> > Hello Sir/Miss,
> >
> > I've tried to run the point stat. tools in MET. It seems that t
can read the data but not using the data for comparison.
> > Do you know what's going on with the program?Thank you very much
for your attention.
> > Regards,
> > Jackie
> >
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #57438] MET PLEASE HELP
From: John Halley Gotway
Time: Tue Jul 17 00:05:50 2012
Jackie,
The point of my message was to tell you to try running Point-Stat with
the
"-v 3" command line option to get more diagnostic information about
why
there were not any matched pairs. If you are not able to look at the
output of Point-Stat and figure out what's going on, the next step
would
be for you to send me some sample data to run here.
Once you send me some data, I'll run it here and diagnose what's going
on.
I'll need:
- sample forecast file
- matching observation file
- Point-Stat configuration file
- the command line that you're using to call Point-Stat
- What version of MET are you're using?
You can post that information to our anonymous ftp site, following the
instructions listed here:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
Once the data's up there, please write me back to let me know.
Thanks,
John
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=57438 >
>
>
> Hi John,
>
> I tried to follow your suggestions but it seems that there are no
any
> matching pairs.
> And do you know what causes this happened?
> thanks
>
> Jackie
>
>> Subject: Re: [rt.rap.ucar.edu #57438] MET PLEASE HELP
>> From: met_help at ucar.edu
>> To: jackie_seek at hotmail.com
>> Date: Mon, 16 Jul 2012 06:59:05 -0600
>>
>> Jackie,
>>
>> Please try rerunning the same command but set the verbosity level
to 3
>> using the "-v 3" command line option. That will include in the
output a
>> list of reasons why 0 observations were not used for
>> each verification task. There are many reasons why you could end
up
>> with 0 matches, and hopefully the additional log messages will help
us
>> figure it out.
>>
>> Second, I see the following in your configuration file:
>> fcst_field[] = [ "TMP/P750-900" ];
>> obs_field[] = [ "TMP/P500" ];
>>
>> This isn't necessarily a problem but it is the reason you're seeing
this
>> warning message in the log file you sent me:
>>
>> WARNING: PointStatConfInfo::process_config() -> The range of
requested
>> observation pressure levels is not contained within the range of
>> requested forecast pressure levels. No vertical interpolation
>> will be performed for observations falling outside the range of
forecast
>> levels. Instead, they will be matched to the single nearest
forecast
>> level.
>>
>> You're telling Point-Stat to use temperature observations defined
at the
>> 500 mb level and compare them against the forecasts that are
defined
>> between 750 and 900 mb. What will really happen is that
>> the obs at 500 mb will only be compared with the forecast at 750
mb, as
>> described in that warning message. Perhaps you have a good reason
for
>> doing this, but typically the following comparison would
>> be performed instead:
>> fcst_field[] = [ "TMP/P750-900" ];
>> obs_field[] = [ "TMP/P750-900" ];
>>
>> That compares any observation falling between 750mb and 900mb to
the
>> corresponding forecast levels.
>>
>> Hope that helps.
>>
>> Thanks,
>> John Halley Gotway
>> met_help at ucar.edu
>>
>> On 07/15/2012 11:45 PM, NG Ignatius via RT wrote:
>> >
>> > Sun Jul 15 23:45:09 2012: Request 57438 was acted upon.
>> > Transaction: Ticket created by jackie_seek at hotmail.com
>> > Queue: met_help
>> > Subject: MET PLEASE HELP
>> > Owner: Nobody
>> > Requestors: jackie_seek at hotmail.com
>> > Status: new
>> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=57438
>> >
>> >
>> >
>> >
>> > Hello Sir/Miss,
>> >
>> > I've tried to run the point stat. tools in MET. It seems that t
can
>> read the data but not using the data for comparison.
>> > Do you know what's going on with the program?Thank you very much
for
>> your attention.
>> > Regards,
>> > Jackie
>> >
>>
>>
>
>
------------------------------------------------
More information about the Met_help
mailing list