[Met_help] Point-Stat output issue

Tue Sep 29 16:13:34 MDT 2009

Ann,

OK, I see what's going on.  I was able to make a couple of changes and got
329 matched pairs for your 10 hour forecast.  I changed all references of
"QKSWND" to "ADPSFC" - so that's in the ASCII point files and in the
PointStatConfig file.

Here's the rationale.  MET considers 2-meter temp and 10-meter winds to be
"surface" variables.  However, the only way MET matches point observations
to surface variables is by the message type - we don't use the elevation
or vertical level.  And the only 2 message types which are considered to
be surface messages are ADPSFC and SFCSHP.  So MET will only match
observations of one of those two types to surface variables - like
10-meter winds.

Now this may be innaccurate on our part.  As a software engineer, I'm
really not familiar with all of the different observation types.  Perhaps,
QKSWND should be considered a surface observation type as well.  Is that
the case?

But at least we know what's going on.  Changing "QKSWND" to "ADPSFC"
should do the trick.  Just let us know if more questions come up.

Thanks,
John

> Thanks, John.  The files are posted!
>
>
>
> From:
> "John Halley Gotway" <johnhg at rap.ucar.edu>
> To:
> "Ann L Mazuk" <Ann.L.Mazuk at aero.org>
> Cc:
> met_help at ucar.edu
> Date:
> 09/29/2009 02:12 PM
> Subject:
> Re: [Met_help] Point-Stat output issue
>
>
>
> Ann,
>
> I was actually just looking at the question you sent in the other day.
> That's fine, go ahead and post some data to the ftp site, and I'll take a
> look and see what's going on.  Here's how you access our anonymous ftp
> site:
>
> ftp ftp.rap.ucar.edu
> username = anonymous
> password = "your email address"
> cd incoming/irap/met_help
> mkdir mazuk_data
> put "your files"
> bye
>
> Please send me a sample forecast file, the corresponding point observation
> file (NetCDF), and the Point-Stat configuraiton file you're using.
>
> Thanks,
> John
>
>> Hi John,
>>
>> I have very similar issues (run point_stat, but only header information
> is
>> outputed because it can't find any matched pairs), but an running
> METv2.0
>> with the latest patches.  Can I ftp you my data & output and have you
> take
>> a look at it?  Everything looks like it is set up properly and should be
>> running, so I can't figure out what is going on.
>>
>> Thanks.
>>
>> Ann
>>
>>
>>
>>
>> From:
>> John Halley Gotway <johnhg at ucar.edu>
>> To:
>> Kathleen Carroll <kathleen.carroll at mines.sdsmt.edu>
>> Cc:
>> met_help <met_help at ucar.edu>
>> Date:
>> 09/29/2009 11:27 AM
>> Subject:
>> Re: [Met_help] Point-Stat output issue
>> Sent by:
>> met_help-bounces at mailman.ucar.edu
>>
>>
>>
>> Kathleen,
>>
>> I think I figured out what's going on.  I tried running your data using
>> the original release of METv2.0 and saw that it found no matched pairs.
>> However, when I ran it using the latest patches applied
>> to METv2.0, it did find 77 matched pairs and create output statistics.
>> FYI, adjust the matching time window with "beg_ds" and "end_ds" in the
>> config file or "valid_beg" and "valid_end" on the command
>> line will affect the number of matched pairs it finds.
>>
>> Here's the Point-Stat command I ran for your reference:
>> /d1/johnhg/MET/MET_Releases/METv2.0_patch/bin/point_stat \
>>    WRFPRS_d03_F000-24_2000100621.grb \
>>    case2_ascii.nc \
>>    PointStatConfig_case2 \
>>    -outdir out \
>>    -v 2
>>
>> I've attached a log file, showing what Point-Stat writes to the screen
>> (with the -v 2) option.
>> I've also attached a tar file containing the output of this command. And
>> each of the output files does contain several lines.
>>
>> So I'd suggest that you retrieve the latest matches for MET, rebuild
> MET,
>> and try again.  It should really only take you a few minutes.  Here's
> how
>> you'd do that:
>> (1) Go to
>> http://www.dtcenter.org/met/users/support/known_issues/METv2.0/index.php
>> (2) Save the file: METv2.0_patches_20090805.tar.gz
>> (3) Place that file in the top-level METv2.0 directory.
>> (4) Untar it: tar -xvzf METv2.0_patches_20090805.tar.gz
>> (5) Type:     make clean
>>     And then: make
>>
>> Now I'm really not sure which patch is fixing your problem, but there's
> a
>> description of them listed on the "known issues" site, and you're
> welcome
>> to look through them.
>>
>> And the answer to your other question is NO.  You should not cat
> together
>> those files.  When you have multiple GRIB records for the same field in
> a
>> single GRIB file, MET isn't able to distinguish them
>> as you'd like.  For example, if you have several records of 3-hourly
>> accumulation of precip in one GRIB file that only differ by valid time,
>> MET will always just use the first one.  So you should keep
>> the GRIB file output of WPP in separate files.  Sorry for the
>> inconvenience.
>>
>> Just let me know if any more problems come up.
>>
>> Thanks,
>> John
>>
>> Kathleen Carroll wrote:
>>> John,
>>>
>>> I have run my WRF output through WPP.  I can now run Point-Stat;
>> however,
>>> when I check my output the only thing in the files is the header
>>> information.  I have uploaded my data onto the ftp site for you and I
>> have
>>> included the output I get when I run Point-Stat below.  If you would
>> like me
>>> to upload the output files too I can, but like I said the only thing in
>>> there is the header info.
>>>
>>> Also, I concatenated my WRFPRS output files into one big file for each
>>> domain.  I wasn't sure if that was ok to do or if I need to run each
> one
>>> separately.  If you have any suggestions on what works best as far as
>> the
>>> WPP output goes I'd appreciate it.  There are quite a few output files
>> after
>>> running WPP and I'm not quite sure which ones to use.
>>>
>>> Thanks,
>>>
>>>
>> GSL_RNG_TYPE=mt19937
>> GSL_RNG_SEED=3863855690
>> Forecast File: WRFPRS_d03_F000-24_2000100621.grb
>> Climatology File: none
>> Configuration File: PointStatConfig_case2
>> Observation File: case2_ascii.nc
>>
>> ----------------------------------------
>>
>> Reading records for PRES/ZSFC.
>> For PRES/ZSFC found 1 forecast levels and 0 climatology levels.
>>
>> ----------------------------------------
>>
>> Reading records for TMP/Z2.
>> For TMP/Z2 found 1 forecast levels and 0 climatology levels.
>>
>> ----------------------------------------
>>
>> Reading records for WIND/Z10.
>> For WIND/Z10 found 1 forecast levels and 0 climatology levels.
>>
>> ----------------------------------------
>>
>> Reading records for UGRD/Z10.
>> For UGRD/Z10 found 1 forecast levels and 0 climatology levels.
>>
>> ----------------------------------------
>>
>> Reading records for VGRD/Z10.
>> For VGRD/Z10 found 1 forecast levels and 0 climatology levels.
>>
>> ----------------------------------------
>>
>> Searching 298524 observations from 3268 PrepBufr messages.
>>
>> ----------------------------------------
>>
>> Processing PRES/ZSFC versus PRES/ZSFC, for observation type ADPUPA, over
>> region G212, for interpolation method UW_MEAN(1), using 0 pairs.
>> Processing PRES/ZSFC versus PRES/ZSFC, for observation type ADPUPA, over
>> region EAST, for interpolation method UW_MEAN(1), using 0 pairs.
>> Processing PRES/ZSFC versus PRES/ZSFC, for observation type ADPUPA, over
>> region WEST, for interpolation method UW_MEAN(1), using 0 pairs.
>> Processing PRES/ZSFC versus PRES/ZSFC, for observation type ADPSFC, over
>> region G212, for interpolation method UW_MEAN(1), using 77 pairs.
>> Computing Categorical Statistics.
>> Computing Continuous Statistics.
>> Computing Scalar Partial Sums.
>> Processing PRES/ZSFC versus PRES/ZSFC, for observation type ADPSFC, over
>> region EAST, for interpolation method UW_MEAN(1), using 0 pairs.
>> Processing PRES/ZSFC versus PRES/ZSFC, for observation type ADPSFC, over
>> region WEST, for interpolation method UW_MEAN(1), using 77 pairs.
>> Computing Categorical Statistics.
>> Computing Continuous Statistics.
>> Computing Scalar Partial Sums.
>>
>> ----------------------------------------
>>
>> Processing TMP/Z2 versus TMP/Z2, for observation type ADPUPA, over
> region
>> G212, for interpolation method UW_MEAN(1), using 0 pairs.
>> Processing TMP/Z2 versus TMP/Z2, for observation type ADPUPA, over
> region
>> EAST, for interpolation method UW_MEAN(1), using 0 pairs.
>> Processing TMP/Z2 versus TMP/Z2, for observation type ADPUPA, over
> region
>> WEST, for interpolation method UW_MEAN(1), using 0 pairs.
>> Processing TMP/Z2 versus TMP/Z2, for observation type ADPSFC, over
> region
>> G212, for interpolation method UW_MEAN(1), using 77 pairs.
>> Computing Categorical Statistics.
>> Computing Continuous Statistics.
>> Computing Scalar Partial Sums.
>> Processing TMP/Z2 versus TMP/Z2, for observation type ADPSFC, over
> region
>> EAST, for interpolation method UW_MEAN(1), using 0 pairs.
>> Processing TMP/Z2 versus TMP/Z2, for observation type ADPSFC, over
> region
>> WEST, for interpolation method UW_MEAN(1), using 77 pairs.
>> Computing Categorical Statistics.
>> Computing Continuous Statistics.
>> Computing Scalar Partial Sums.
>>
>> ----------------------------------------
>>
>> Processing WIND/Z10 versus WIND/Z10, for observation type ADPUPA, over
>> region G212, for interpolation method UW_MEAN(1), using 0 pairs.
>> Processing WIND/Z10 versus WIND/Z10, for observation type ADPUPA, over
>> region EAST, for interpolation method UW_MEAN(1), using 0 pairs.
>> Processing WIND/Z10 versus WIND/Z10, for observation type ADPUPA, over
>> region WEST, for interpolation method UW_MEAN(1), using 0 pairs.
>> Processing WIND/Z10 versus WIND/Z10, for observation type ADPSFC, over
>> region G212, for interpolation method UW_MEAN(1), using 77 pairs.
>> Computing Categorical Statistics.
>> Computing Continuous Statistics.
>> Computing Scalar Partial Sums.
>> Processing WIND/Z10 versus WIND/Z10, for observation type ADPSFC, over
>> region EAST, for interpolation method UW_MEAN(1), using 0 pairs.
>> Processing WIND/Z10 versus WIND/Z10, for observation type ADPSFC, over
>> region WEST, for interpolation method UW_MEAN(1), using 77 pairs.
>> Computing Categorical Statistics.
>> Computing Continuous Statistics.
>> Computing Scalar Partial Sums.
>>
>> ----------------------------------------
>>
>> Processing UGRD/Z10 versus UGRD/Z10, for observation type ADPUPA, over
>> region G212, for interpolation method UW_MEAN(1), using 0 pairs.
>> Processing UGRD/Z10 versus UGRD/Z10, for observation type ADPUPA, over
>> region EAST, for interpolation method UW_MEAN(1), using 0 pairs.
>> Processing UGRD/Z10 versus UGRD/Z10, for observation type ADPUPA, over
>> region WEST, for interpolation method UW_MEAN(1), using 0 pairs.
>> Processing UGRD/Z10 versus UGRD/Z10, for observation type ADPSFC, over
>> region G212, for interpolation method UW_MEAN(1), using 77 pairs.
>> Computing Categorical Statistics.
>> Computing Continuous Statistics.
>> Processing UGRD/Z10 versus UGRD/Z10, for observation type ADPSFC, over
>> region EAST, for interpolation method UW_MEAN(1), using 0 pairs.
>> Processing UGRD/Z10 versus UGRD/Z10, for observation type ADPSFC, over
>> region WEST, for interpolation method UW_MEAN(1), using 77 pairs.
>> Computing Categorical Statistics.
>> Computing Continuous Statistics.
>>
>> ----------------------------------------
>>
>> Processing VGRD/Z10 versus VGRD/Z10, for observation type ADPUPA, over
>> region G212, for interpolation method UW_MEAN(1), using 0 pairs.
>> Processing VGRD/Z10 versus VGRD/Z10, for observation type ADPUPA, over
>> region EAST, for interpolation method UW_MEAN(1), using 0 pairs.
>> Processing VGRD/Z10 versus VGRD/Z10, for observation type ADPUPA, over
>> region WEST, for interpolation method UW_MEAN(1), using 0 pairs.
>> Processing VGRD/Z10 versus VGRD/Z10, for observation type ADPSFC, over
>> region G212, for interpolation method UW_MEAN(1), using 77 pairs.
>> Computing Categorical Statistics.
>> Computing Continuous Statistics.
>> Computing Vector Partial Sums, for forecast wind speed NA, for
> observation
>> wind speed NA, using 77 pairs.
>> Processing VGRD/Z10 versus VGRD/Z10, for observation type ADPSFC, over
>> region EAST, for interpolation method UW_MEAN(1), using 0 pairs.
>> Processing VGRD/Z10 versus VGRD/Z10, for observation type ADPSFC, over
>> region WEST, for interpolation method UW_MEAN(1), using 77 pairs.
>> Computing Categorical Statistics.
>> Computing Continuous Statistics.
>> Computing Vector Partial Sums, for forecast wind speed NA, for
> observation
>> wind speed NA, using 77 pairs.
>>
>> ----------------------------------------
>>
>> Output file: out/point_stat_000000L_20001006_210000V.stat
>> Output file: out/point_stat_000000L_20001006_210000V_fho.txt
>> Output file: out/point_stat_000000L_20001006_210000V_ctc.txt
>> Output file: out/point_stat_000000L_20001006_210000V_cts.txt
>> Output file: out/point_stat_000000L_20001006_210000V_cnt.txt
>> Output file: out/point_stat_000000L_20001006_210000V_sl1l2.txt
>> Output file: out/point_stat_000000L_20001006_210000V_vl1l2.txt
>> [attachment "out.tar.gz" deleted by Ann L Mazuk/West/Aerospace/US]
>> _______________________________________________
>> Met_help mailing list
>> Met_help at mailman.ucar.edu
>> http://mailman.ucar.edu/mailman/listinfo/met_help
>>
>>
>
>
>
>