M1 Test and Deployment Procedure
16 Sept 1998, herlien

I've written a few scripts to help with the software configuration
for testing and deployment of M1.  Although they should run in any
user environment, it's best to log in as user "oasisa" to run them
(everyone involved remembers the oasisa password, right?).  In any
case, make sure /oasis/bin is in your path, as that's where these
scripts live.

TESTING
To run M1 in test mode, while the old M1 is still in the field, cd to
/oasis/bin and run 'test'.  This starts downloads from the new M1 into
the directory tree /oasis/test.  That is, raw data in /oasis/test/raw,
decoded data in /oasis/test/m1, config files in /oasis/test/cfg, etc.

To turn off the test mode, run 'notest'.


DEPLOYMENT PROCEDURE
1) Do your normal pre-deployment setup and testing on the boat.  Zorba,
   Mike K, and Tom T should know how to run the mooring via laptop.  The
   baud rate of the user serial port is 9600 N 8 1.

2) Due to previous experience with bent shutters, you should turn off the
   PRRs/Shutters prior to deployment.  From the user serial port, type
   "drvparm specprr", and change parameter 0 (Interval) to 0.  That turns
   off the PRRs, and hence the shutters won't open.

3) Deploy

4) After deployment, when you're sure the mooring has stopped moving, log
   onto M1 via radio and again do a "drvparm specprr".  Change parameter 0
   back to 600 (that's in seconds).

5) As soon as practical when you're back on shore, log into tsunami as
   user "oasisa", cd to /oasis/bin, and run 'deploy'.  This moves a
   considerable amount of data and scripts around, and should take a
   while.  It does so in a non-destructive way -- that is, the old data
   will still be in /oasis as well as being in /oasis/may97.  That's because
   the script is untested -- I didn't want to disturb the existing deployment
   until it was time.  Hopefully, if there's any problem, Tom can help
   figure out where I screwed up.  The script should be painfully obvious.

	-Bob