[Met_help] point_stat: interp method inconsistency

[John Halley Gotway]

Jonathan,

I did actually find a bug related to that this morning when running
Grid-Stat and Point-Stat using MULTIPLE interpolation raddii and methods. 
I haven't looked to see if it's in METv2.0beta6 or not - but it was in the
devleopment version.

BUT... I don't think that's what you're seeing.

When you request an interpolation width of 1, which I'm guessing is what
you're doing, that really just means to use the "nearest neighbor".  So by
convention, when you request an interpolation width of 1, the
interpolation method is harded coded as "UW_MEAN".  So if you're
requesting interpolation width = 1 and interpolation method = DW_MEAN, in
the output, you'll see UW_MEAN and not DW_MEAN.

Suppose you selected an interpolation width of 1 and 5 interpolation
methods - UW_MEAN, DW_MEAN, LS_FIT, MIN, MAX... and so on.  Since we're
just using the nearest neighbor, those methods really would have no
impact.  So we decided to just write out UW_MEAN instead.

If you're using an interpolation width > 1, then you should actually see
DW_MEAN in the output files.

Does that make sense?

John

> John,
>
>
>
> I don't know if I've stumbled on another bug, but here goes:
>
>
>
> I just double-checked to confirm that I specified distance-weighted mean
> (DW_MEAN) for the interp method in the point_stat config file.
>
> However, in my output files, the INTERP_MTHD is listed as UW_MEAN
> instead of DW_MEAN.
>
>
>
> Could you confirm that you have this inconsistency as well?  Either the
> labeling in the point_stat output files is wrong, or the DW_MEAN option
> is not being used correctly.
>
>
>
> Please advise,
> Jonathan
>
>
>
> ***********************************************************
> Jonathan Case, ENSCO, Inc.
> Aerospace Sciences & Engineering Division
> Short-term Prediction Research and Transition Center
> 320 Sparkman Drive, Room 3062
> Huntsville, AL 35805-1912
> Voice: (256) 961-7504   Fax: (256) 961-7788
> Emails: Jonathan.Case-1 at nasa.gov
>
>              case.jonathan at ensco.com
>
> ***********************************************************
>
>
>
>