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