\*\*\* Please take the time to register this software on the LAD for
your site \*\*\*

New features:

1.  You will not need to edit rr3.pl or getrr3.pl files for
    configuration purposes any longer for upgrades. Control.pm file will
    control the configuration, now.

2.  Changed the structure of the archived data directories to be
    strictly numerical directory names.

3.  RR3TODAY pil and the archived data will have the co-op sites
    alphabetically listed which will aid in viewing.

\*\*\* Note: This upgrade/installation will overwrite your rr3.pl and
getrr3.pl files. You do not need to backup your mandatory.XXX or
nonmandatory.XXX files!

Make a backup copy of your ksh files, so you do not have to re-edit
them. Also,

make a backup copy of your rr3.pl file for reference.

\*\*\*

Installation for first-time users:

1\. Copy the rr3.tar.gz file to your coop check directory on ds1.

2\. Untar & unzip the file with: gunzip -c rr3.tar.gz \| tar xvf -

3\. Edit the beginning of the rr3.ksh, getrr3.ksh and configure.ksh
scripts to your office\'s specifications.

4\. Edit Control.pm to include your office's information.

5\. Run configure.ksh and then follow the steps in the next section for
configuration for new users.

See the very end of this file for my contact info if you have problems
or questions!

Installation for existing users:

1\. Copy the rr3.tar.gz file to your coop check directory on ds1.

2\. Untar & unzip the file with: gunzip -c rr3.tar.gz \| tar xvf -

3\. Edit Control.pm to include your office's information from the rr3.pl
file you backed up earlier.

4\. Run reconfigure.pl to restructure your coop data directory.

5\. No additional configuration is needed.

Configuration (for new users):

1\. Copy mandatory.LCH to mandatory.XXX where XXX is your site's office
ID. This

CSV file is pretty straight forward except for the fourth field which
looks like a bunch of numbers compressed together. Actually, each number
stands for a particular type of weather element that the co-op site will
report and will be quality-controlled for. For example,

ADSL1,ALEXANDRIA 5 SSE,(318) 445-1418,125

Site ID, Site Description, Site Phone #, Site Weather Reporting Info

The 125 in the fourth field says that ADSL1 will report max, min and at
ob temps (1), soil max, soil min and soil at ob temps (2), and
precipitation (5).

You can combine as many of the following numbers to describe your sites
to Co-op Check:

1 -- max, min and at ob temps

2 -- soil max, soil min and soil at ob temps

3 -- river or dam discharge

4 -- river, pool or dam height

5 -- precipitation

6 -- evaporation

7 -- max and min water temps

8 -- miles of wind

9 -- snowfall and snow depth

The mandatory.XXX file is for your sites that are supposed to call in
their data daily. The nonmandatory.XXX file is for sites that do not
call in regularly like precip or snowfall/snow depth only sites...sites
that only call in when there is an event happening.

2\. I have added a mouse-over feature to show the user if all your
office\'s current river forecast guidance is in. You do not have to use
this feature\.....you can simply set the userivers variable to 0 and not
have to use this. If you decide to use the rivers feature, you will have
to insert your site\'s data into the Control.pm file. You will see this
in your script:

Position 0 Position 1

my \@riverpils = (\"NEWRVFLCH\",\"FTWRVFLCH\"); Line1

my %riverdescriptions = ( Line2

0 =\> \[\"CALCASIEU-MERMENTAU\",\"LOWER RED BASIN\"\], Line3

1 =\> \[\"SABI\",\"NECH\"\], Line4

); Line5

If you receive all of your office\'s river forecast in one pil\.....then
you will only need to insert one pil on Line1 (above). You can include
as many pils as you need in Line1\...\...the only thing you need to keep
in mind is that Position 0 corresponds to Line3 and Position 1
corresponds to Line4 and so on. Line3 and Line4 in the example are
descriptions found at the beginning of the river forecast
product\...\...which helps the script determine if that river\'s data
has arrived. The example (below) shows the header of one of our
office\'s river forecast products. Notice the \"NECH\" in the
header\...\....this is the description of the river that I would insert
in Line3 or Line4 which corresponds to the pil from that RFC.

> FGUS54 KFWR 241321

RVFLCH

RIVER FORECASTS

NATIONAL WEATHER SERVICE\...WEST GULF RFC\...FORT WORTH, TEXAS

0819 AM CDT FRI OCT 24 2003

:

: NECH

:

The river mouse over feature prevents the program from having to request
the river forecast products from the database each time the Co-op Check
refreshes. The products are only called in if you mouse over the river
section.

3\. Make a trigger to compile all of your co-op reports. Simply put this
line in your trigger file:

NNNRR3CCC /your/co-opcheck/directory/getrr3.ksh

Then run "mainscript.csh --trigger" to install your new trigger.

4\. Errors no longer \*just\* color the button of a site a particular
color; they are listed out in detail when you click on the site\'s
information button. Also, the ability to compare a site\'s max, min or
at ob temp to the respective average

of the max, min or at ob temps was there with the previous release. But,
now, you will have the ability to control which difference off of the
average you want to use. For example, if a site reports a max temp of
75, but the average of all the sites\' max temps is 62\.....then co-op
check will flag the site as a possible data quality problem. The
conditions could actually result in this type of scenario
happening\...\....but, it\'s better to let the user know that there
could be a quality control problem. A bug in the program has been fixed
which caused bad reports being used to calculate a site\'s averages.

Also, you have the ability to change what quality control values the
program will flag as possible problems. These values can be found in the
Control.pm file.

\$tempqcvalue = 10; This controls which difference off of the average
you want to use.

\$precipqcvalue = 2.00; This controls the threshold greater than which
is a possible precip data quality problem.

\$maxtempqcvalue = 120; This controls the threshold greater than which
is a possible max temp data quality problem.

\$mintempqcvalue = 90; This controls the threshold greater than which is
a possible min temp data quality problem.

\$atobtempqcvalue = 90; This controls the threshold greater than which
is a possible at ob temp data quality problem.

\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

If you have any problems or concerns call or e-mail:

\(337\) 477-3422

Matthew.Duplantis@noaa.gov

LCH ITO