The BUF_WxTool

**Version 2.0 (03/27/06)**

John Rozbicki - National Weather Service, Buffalo, NY

phone: (716) 565-0013

email: [John.Rozbicki@noaa.gov]{.underline}

**[Change History:]{.underline}**

**[Version 2.0 (03/27/06):]{.underline}** Based on forecaster feedback,
numerous enhancements have been made to the tool with Version 2.0. These
include:

(1) The ability to override the default probability/coverage obtained
    from the corresponding PoP grid if desired. This can be done
    separately for each individual weather type, and allows the easy
    creation of weather types such as \"Lkly RW:Chc SW\". This approach
    also allows for the use of other weather types (for example, F, L,
    and ZL) which aren\'t necessarily PoP-dependent.

(2) The addition of three new weather types (F (fog), L (drizzle), and
    ZL (freezing drizzle). Coverage terms specific to these elements
    ("Patchy", "Areas") have also been added to the tool.

(3) The addition of "very light" intensities (\--) to the tool GUI. This
    makes it possible to assign weather types such as RW\-- (sprinkles)
    and SW\-- (flurries).

(4) In conjunction with the first three enhancements, new internal
    checks have been added to ensure that the tool does not create
    invalid weather types. These checks include:

```{=html}
<!-- -->
```
(a) A check for the use of \"Patchy\" and \"Areas\" coverages with
    weather types other than L, ZL, and F (this prevents invalid weather
    types such as \"Patchy R\").

(b) A check for the use of Areal Coverage qualifiers other than
    "Patchy", "Areas" and "Wide" with L, ZL, and F (this prevents
    invalid weather types such as "Iso ZL").

(c) A check for the use of very light, light, or moderate intensities
    with F (none of which are valid; the intensity can only be
    \<NoInten\> or + ).

> If the conditions in (a) or (b) are met, the tool displays a message
> indicating that the proposed weather type is invalid, and exits
> without modifying the Wx grid.
>
> If the condition in (c) is met, the tool displays a message indicating
> that the proposed intensity cannot be assigned to fog. It will also
> automatically change the intensity to \<NoInten\> without any further
> action on the part of the forecaster.

(5) The ability to use alternate probability/coverage terms (i.e., other
    than \"Def\" or \"Wide\") for categorical PoPs has been added. In
    such cases, the following additional options are now available:
    \"Ocnl\", \"Frq\", \"Brf\", \"Pds\", and \"Inter\". When used, this
    setting will apply to all categorical precip coverages that are
    derived from the PoP grid.

(6) The ability to specify an alternate probability/coverage for T has
    been added. This setting will override the default
    probability/coverage obtained from the corresponding PoP grid, and
    makes it possible to create precip types such as \"Def RW:Chc T\".

(7) A severe thunderstorm attribute for Tornadoes has been added.
    Coincident with this change, a check has also been added to prevent
    the use of the "Tornadoes" attribute with non-severe thunderstorms -
    as is already done with LgA (large hail) and DmgW (damaging winds).

(8) The tool has been modified to prevent the use of the SmA (small
    hail) and GW (gusty winds) thunderstorm attributes with severe
    thunderstorms (T+).

(9) Coincident with the changes in (7) and (8), the tool will now
    display a message if the user tries to select invalid thunderstorm
    attributes (previously, this was not done). If invalid attributes
    are selected, the tool will still automatically ignore such
    attributes and run to completion as before.

\(10\) The minimum PoP threshold for SChc weather has been made
site-configurable through a new

variable. This allows sites to customize this threshold to meet their
local needs. The default value

is still the ER-default 14.5%.

**[Version 1.2 (2/23/05):]{.underline}** Updated for IFPS 16.2. Hail (A)
is no longer a separate weather type in GFE, so the separate handling of
hail attributes from other thunderstorm attributes was removed. This
resulted in a simplification of the code, and the removal of all
references to \"hailstring\". Also, fixed a potential bug which could
result in \"DmgW\' not being assigned even if it was selected by the
forecaster.

**[Version 1.1 (3/21/03):]{.underline}** Changed the PoP thresholds to
match the precision of the gridded data. For example, the threshold for
Chc/Sct Wx values was 25% before the change, with the change it\'s now
24.5%.

The reason for the change: in Version 1.0, the tool would assign an
incorrect Wx value for PoP values just below the thresholds; for
example, \"SChc\" or \"Iso\" Wx would be assigned for PoPs in the
24.5%-24.9% range. With the change, the tool assigns the correct Wx for
such PoP values - i.e.\"Chc\" or \"Sct\" Wx.

**[Applicable IFPS Builds:]{.underline} IFPS 17.6+**

**[Introduction:]{.underline}**

The BUF_WxTool is a significant enhancement to the original
Wx_SmartTool, which was written by Tracy Hansen (FSL). Both tools assign
Wx based on the corresponding PoP grids; however the BUF_WxTool offers
the following additional functionality:

(1) The forecaster is allowed considerable freedom in choosing
    individual weather types (RW, R, SW, S, IP, ZR, L, ZL, and F are all
    supported).

> \(2\) Up to three weather types may be mixed together and a different
> intensity (very light \[\--\], light \[-\], moderate \[m\], or heavy
> \[+\]) may be assigned to each. So for example, it is possible to
> assign weather such as RmSmIP- with this tool.

(3) The forecaster can also choose whether to include thunder (T) with
    any other supported weather type; if thunder is included, he or she
    also has the option of specifying whether the thunder is severe in
    nature (T+).

> \(4\) The forecaster can assign either probability qualifiers or areal
> coverage qualifiers (where allowed) to the chosen weather types. If a
> forecaster attempts to use an invalid qualifier for a weather type,
> the tool will generate an error message appears indicating that this
> is not allowed.

\(5\) For each individual weather type, the forecaster can override the
default probability/coverage obtained

from the PoP grid if desired. The same is also true for thunder (T).
This makes it possible to:

-   create weather combinations such as "Lkly RW:Chc SW" or "Def RW:Chc
    T".

```{=html}
<!-- -->
```
-   assign weather types of F, L, or ZL, which aren't necessarily
    derived from the PoP grids.

> \(6\) For categorical PoPs, the forecaster can use alternate
> probability/coverage terms (other than \"Def\" or
>
> \"Wide\") if desired. The following options are available: \"Ocnl\",
> \"Frq\", \"Brf\", \"Pds\", and \"Inter\". When
>
> used, this setting applies to all categorical precip coverages that
> are derived from the PoP grid.
>
> \(7\) If thunder is included with the precipitation, the forecaster
> also has the additional option of specifying the following
> thunderstorm attributes, if desired:

-   Small Hail (SmA)

-   Heavy Rain (HvyRn)

-   Gusty Winds (GW)

-   Frequent Lightning (FL)

-   Large Hail (LgA)

-   Damaging Winds (DmgW)

-   Tornadoes (TOR)

> The tool is designed so that the last three attributes (LgA, DmgW, and
> TOR) can only be assigned when severe thunderstorms (T+) are forecast.
> Similarly, the tool will also only allow SmA and GW to be used with
> non-severe thunderstorms (T). If the forecaster tries to assign a
> thunderstorm attribute that is invalid, the tool will display a
> message indicating this, and will automatically ignore such attributes
> and run to completion.

It should be noted that the tool does not apply any scientific principle
to derive the final Wx type; the Wx type assigned is solely decided upon
by the forecaster. The forecaster chooses the Wx type through the use of
a GUI interface that appears when the tool is executed.

**[Requirements:]{.underline}**

-   The floating PoP grids for the time period in question must exist
    before running the tool.

**[Usage:]{.underline}**

After creating all of the necessary floating PoP grids, to run the tool
the forecaster needs only to select the BUF_WxTool from the list of
available smart tools in GFE; this action brings up the following GUI:

![](media/image1.png){width="7.495833333333334in"
height="2.2131944444444445in"}

As you can see from the above image, the tool GUI has a number of new
entries with version 2.0. What follows next is a brief overview of each
section:

[Qualifier Type:]{.underline} Allows you to toggle between the use of
Probability and Areal Coverage terms. The default setting is "Prob".

[Alter Terms Cat PoPs *(new)*:]{.underline} Allows you to use alternate
probability/coverage terms (\"Ocnl\", \"Frq\", \"Brf\", \"Pds\", and
\"Inter\") when categorical PoPs are used. When used, this setting will
apply to all categorical precipitation probabilities/coverages that are
derived from the PoP grid. The default setting is "None".

[1^st^/2^nd^/3^rd^ Type:]{.underline} Allows you to select/combine up to
3 different weather types. In version 2.0, the lists of available
weather types have been expanded to include L, ZL, and F.

[1^st^/2^nd^/3^rd^ Inten:]{.underline} Allows you to specify the
intensity of each weather type (\--, -, m, or +). In the case of fog
(F), only + (dense) is a valid intensity. If F is selected with any
other intensity, the tool will automatically remove the intensity to
prevent any errors. The default setting is "-" (light).

[1^st^/2^nd^/3^rd^ Type Alternate Prob/Cov *(new)*:]{.underline} Allows
you to override the default probability/coverage obtained from the
corresponding PoP grid for each individual weather type. This allows the
easy creation of weather types such as \"Lkly RW:Chc SW\". This approach
also allows for the use of other weather types (for example, F, L, and
ZL) which aren\'t necessarily PoP-dependent. The default setting is
"None" - meaning the probability/coverage terms for each weather type
are derived from the PoP grid by default.

[Thunder?:]{.underline} Allows you to specify whether you want thunder
included with the other weather type(s) selected. Options are "No", "Yes
(T)", and "Yes (T+)" (severe T). The default setting is "No".

[Thunder Alternate Prob/Cov *(new)*:]{.underline} Allows you to specify
an alternate probability/coverage for T if desired. This setting will
override the default probability/coverage obtained from the
corresponding PoP grid, and makes it possible to create precip types
such as \"Def RW:Chc T\". The default setting is "None" - meaning the
probability/coverage term for T is derived from the PoP grid by default.

[Tstm Attributes?:]{.underline} Allows you to specify Thunderstorm
Attributes if you choose to include Thunder in the Wx grid.

Once the forecaster has made their selections from the above GUI, he/she
then assigns the desired weather by clicking either of the ARun@ or
ARun/Dismiss@ buttons within the GUI. When this is done, a single
weather type is created based on the forecaster input. Unless
specifically overridden by the forecaster, probability or areal coverage
qualifiers will be determined from the PoP grid in accordance with the
following table:

  ---------------------------- ---------------------- -----------------------
  **PoP Value (rounded to the  **Probability          **Areal Coverage
  nearest %)**                 Qualifier**            Qualifier**

  0 - SChc_min_PoP_threshold\* None; \<NoWx\> is      None; \<NoWx\> is
                               assigned               assigned

  SChc_min_PoP_threshold\* -   Slight Chance (SChc)   Isolated (Iso)
  24                                                  

  25 - 54                      Chance (Chc)           Scattered (Sct)

  55 - 74                      Likely (Lkly)          Numerous (Num)

  75 - 100                     Definite (Def)         Widespread (Wide)
  ---------------------------- ---------------------- -----------------------

\* - SChc_min_PoP_threshold is the minimum PoP needed for a SChc (slight
chance) of weather to

> be included in the Wx grid. This value is site-customizable; the
> default value is 14.5%. Please see the Installation/Configuration
> section below if you would like to change this setting at your site.

**[Installation/Configuration:]{.underline}**

Installation and customization should be done by the IFPS focal point or
other knowledgeable person. It is assumed that the Smart Tool file has
been downloaded from the national Smart Tool repository and moved inside
the AWIPS LAN before performing the following steps.

[**[IMPORTANT:]{.underline}** With Version 2.0, there have been numerous
changes to the tool GUI and the tool code. If you have previously
customized the tool for your site, it is thus strongly recommended that
you use the following procedure when upgrading:]{.mark}

[]{.mark}

[(1) Save off a copy of the existing BUF_WxTool under a different
name.]{.mark}

[(2) Install Version 2.0 of the BUF_WxTool.]{.mark}

[(3) After installing Version 2.0, merge any local changes back into the
tool (if needed).]{.mark}

*[Installation:]{.underline}*

1.  Copy the BUF_WxTool.tool file to the /tmp directory of the machine
    where you will be

installing the tool (normally, this would be lx1).

2.  Switch to the /awips/GFESuite/bin directory, and use the
    ifpServerText utility to install the

tool into GFE via the following command:

ifpServerText -u SITE -s -n BUF_WxTool -f /tmp/BUF_WxTool.tool -c
SmartTool

3\. Start up GFE as user SITE.

4.  From the GFE menu, select "Define Smart Tools". Right-click in the
    Smart Tools listbox and

select BUF_WxTool and click \"Open\"; the Smart Tool will open in a new
IDLE window.

Verify that there are no \"/r\" characters at the end of each line.

[If there are any \"/r\" characters:]{.underline}

> Highlight any \"/r\" character and select Replace from the Edit menu.
> Middle-click paste the \"/r\" into the Find box and click Replace All.
> Then, select File\--\>Save, then File\--\>Exit.

[Otherwise:]{.underline}

Select File--\>Exit.

Once you have finished this step, installation of the tool is complete.

*[Configuration:]{.underline}*

New with version 2.0, you can customize the minimum PoP value needed for
a SChc (slight chance) of weather to be included in the Wx grid. By
default, this value is set to the Eastern Region standard threshold of
14.5%. To change, scroll down to the site configuration section at the
beginning of the tool code, and change the value of the
SChc_min_PoP_threshold variable to the desired value. Save your changes
to have them take effect.