[Fwd: Re: [Met_help] MET v1.1]

[John Halley Gotway]

FYI...

A future user of matched pair data.

John

-------- Original Message --------
Subject: Re: [Met_help] MET v1.1
Date: Tue, 15 Apr 2008 22:12:32 +0000
From: Cory Davis <cory.davis at metservice.com>
To: John Halley Gotway <johnhg at rap.ucar.edu>
CC: andrew.digby at metservice.com
References: <48052336.50108 at metservice.com> <48052594.5050904 at rap.ucar.edu>

Great, this is perfect.  At this point I am not using the VSDB-Analysis
tool.  To be honest I haven't looked at it closely.  Instead I am using
python wrapping code (mainly around point_stat) to automate the routine
verification of our operational model runs.

Cheers,
Cory.

John Halley Gotway wrote:
> Cory,
> 
> I've attached some sample Matched Pair output from MET.
> 
> We realize that it may be helpful to access the matched pair data that 
> went into the calculations.  However, I want to mention that the amount 
> of matched pair data being dumped out could grow quite large!  So you'll 
> be able to toggle a flag in the configuration file to indicate whether 
> or not you'd like it generated.
> 
> Also, we've added new "jobs" to the VSDB-Analysis tool to read and 
> process matched-pair data.  For example, you'll be able to read the 
> matched pair data into VSDB-Analysis (from different times if you'd 
> like) and recompute continuous or categorical statistics.
> 
> In the attached file, you'll see that we've defined a new line type 
> "MPR" to indicate matched-pair data.  And the line consists of...
> TOTAL = total number of points used in the computations for this 
> variable/level
> INDEX = index of current point (from 1 to TOTAL)
> OBS_LAT = latitude of observation
> OBS_LON = longitude of observation
> OBS_LVL = level of observation
> OBS_ELV = elevation of observation
> FCST = forecast value interpolated to this point
> OBS = observation value at this point
> CLIMO = climatological value (if provided) interpolated to this point
> INTERP_MTHD = interpolation method
> INTERP_PNTS = interpolation neighborhood size
> 
> Do you think that will meet your needs?
> 
> We're hoping to have METv1.1 available by late May.  We're working to 
> provide support for Grib2.
> 
> Thanks,
> John
> 
> Cory Davis wrote:
>> Hi there,
>> Firstly thanks for making MET available, I have been using it for a 
>> few months now and it has proved valuable in evaluating our various 
>> mesoscale model configurations.
>> I was about to send you an email requesting a feature: It would be 
>> great to be able to retrieve the matched pair data in point_stat so 
>> that residuals could be plotted on a map so that any spatial pattern 
>> in residuals can be assessed.  Then I noticed that this seems to be a 
>> feature planned for MET v1.1.  I was hoping you could confirm this and 
>> if you could give me a heads up about what fields would be included, 
>> i.e. station id, lat/lon etc.
>> Cheers,
>> Cory.
>> _______________________________________________
>> Met_help mailing list
>> Met_help at mailman.ucar.edu
>> http://mailman.ucar.edu/mailman/listinfo/met_help