[Met_help] [rt.rap.ucar.edu #59438] History for Corrections in documentation needed (UNCLASSIFIED)

[John Halley Gotway via RT]

----------------------------------------------------------------
  Initial Request
----------------------------------------------------------------

Classification: UNCLASSIFIED
Caveats: NONE

I have updated all our scripts for running MET V4.0 PB2NC, Point-Stat,
Grid-Stat and MODE here and noticed a couple of things which you might
consider for corrections to the REAMDME file and the User's Guide (v4.0.1).

For guidance on the MODE config file, noticed that there is no mention of
the "plot_valid_flag" in the README. The User's Guide does mention it, but
it shows valid entries of 0 and 1 instead of FALSE/TRUE which his given in
the default config file. The same problem occurs with "plot_gcarc_flag"

I was unable to find a description of the "ct_stats_flag" in the REAEDME,
but I did find it in the User's Guide.

I was pleased to see the duplicate_flag added in V4.0. I tested it and the
functionality for both SINGLE and UNIQUE appears to work fine. Is there a
way to run Point-Stat where both types of duplicates have been removed at
the same time?

Thanks.

R/
John

Mr John W. Raby, Meteorologist
U.S. Army Research Laboratory
White Sands Missile Range, NM 88002
(575) 678-2004 DSN 258-2004
FAX (575) 678-1230 DSN 258-1230
Email: john.w.raby2.civ at mail.mil



Classification: UNCLASSIFIED
Caveats: NONE




----------------------------------------------------------------
  Complete Ticket History
----------------------------------------------------------------

Subject: Re: [rt.rap.ucar.edu #59438] Corrections in documentation needed (UNCLASSIFIED)
From: John Halley Gotway
Time: Thu Nov 29 09:11:47 2012

John,

It's a difficult balance to decide where to put information about each
of
the configuration settings.  In previous versions of MET, we made the
configuration files very verbose with a lot of comments, but that led
to a
lot of repetition across tools and made the comments cumbersome to
maintain.

Our goal in METv4.0 was to strip out comments for configuration
settings
common to multiple tools and put that information into a README file.
However, some of the settings are specific to the individual tools.
For
example, plot_valid_flag, plot_gcarc_flag, and ct_stats_flag are
specific
to MODE.  And the following comments do exist in the MODE config file
about them:

   //
   // Boolean for plotting on the region of valid data within the
domain
   //
   plot_valid_flag = FALSE;

   //
   // Plot polyline edges using great circle arcs instead of straight
lines
   //
   plot_gcarc_flag = FALSE;

   //
   // NetCDF matched pairs, PostScript, and contingency table output
files
   //
   ct_stats_flag   = TRUE;

However, based on your input, I did add the following blob to the
README:

In general, settings common to multiple tools are described in this
README
file while settings specific to individual tools are described in the
comments of their configuration files.

But we'll also get those issues resolved in the user's guide.

I took a look at the SINGLE and UNIQUE settings for the duplicate_flag
for
Point-Stat.  Here's the description of them:

//    - "NONE" to use all point observations (legacy behavior)
//    - "UNIQUE" if two or more observations match identically except
in the
//       station ID field, only use a single observation
//    - "SINGLE" if two or more observations appear at a single
location
//      (lat, lon, level, elv), use only the observation that has the
valid
//      time closest to the forecast valid time

Basically, the SINGLE setting is just a more strict version of the
UNIQUE
setting.  With SINGLE, you can have multiple observations at the same
location falling in your time window (e.g. a station reporting every 5
minutes with a 1-hour matching time window).  However with UNIQUE,
only
one of those 5 minute observations will be used for that station - the
one
closest to the forecast valid time.

The SINGLE setting to is to fix the problem of stations showing up
multiple times with different station id names.  The UNIQUE setting
makes
sure that only one observation value is used for each
lat/lon/level/elevation.

Thanks for the feedback.  And let us know if more questions arise.

Thanks,
John

>
> Wed Nov 28 14:19:45 2012: Request 59438 was acted upon.
> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>        Queue: met_help
>      Subject: Corrections in documentation needed (UNCLASSIFIED)
>        Owner: Nobody
>   Requestors: john.w.raby2.civ at mail.mil
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59438 >
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> I have updated all our scripts for running MET V4.0 PB2NC, Point-
Stat,
> Grid-Stat and MODE here and noticed a couple of things which you
might
> consider for corrections to the REAMDME file and the User's Guide
> (v4.0.1).
>
> For guidance on the MODE config file, noticed that there is no
mention of
> the "plot_valid_flag" in the README. The User's Guide does mention
it, but
> it shows valid entries of 0 and 1 instead of FALSE/TRUE which his
given in
> the default config file. The same problem occurs with
"plot_gcarc_flag"
>
> I was unable to find a description of the "ct_stats_flag" in the
REAEDME,
> but I did find it in the User's Guide.
>
> I was pleased to see the duplicate_flag added in V4.0. I tested it
and the
> functionality for both SINGLE and UNIQUE appears to work fine. Is
there a
> way to run Point-Stat where both types of duplicates have been
removed at
> the same time?
>
> Thanks.
>
> R/
> John
>
> Mr John W. Raby, Meteorologist
> U.S. Army Research Laboratory
> White Sands Missile Range, NM 88002
> (575) 678-2004 DSN 258-2004
> FAX (575) 678-1230 DSN 258-1230
> Email: john.w.raby2.civ at mail.mil
>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
>



------------------------------------------------