#####################################################################
#                                                                   #
#                             Heli-2-Go                             #
#                                                                   #
#                                          7/28/2000 Jim Luetgert   #
#####################################################################

Heli-2-Go is a web interface for producing custom helicorder plots.
This is of particular use for monitoring data quality and diagnosing
problems for network operations. It is not recommended for the public
because of its slow response and potential for server overloading 
under heavy usage.

Heli-2-Go should be installed on a machine configured as a webserver.
It consists of three modules. Put the perl script heli2go.pl in the 
cgi-bin directory; put heli2go and menulist in the appropriate /bin 
directory. You will also need a config file for heli2go which will 
also be used by menulist.  Optionally (though recommended) you should 
have a database file describing the channels in your network.

Here's how it works - when you decide to build a new helicorder, 
heli2go.pl looks for a file containing the waveserver menu entries 
for the waveservers you are using.  If it is successful, it parses 
the site/net entries into a pop-up menu and asks you for the location.
I don't list the channel at this point because the list can become
tediously long.  If the menulist file is not found, it should be there 
by the time you re-load because heli2go.pl has already started the 
program menulist to build the file.  By rebuilding the menulist file
every time heli2go.pl is run, we are always up-to-date with the
configuration of the waveservers.  Because menulist uses the same
configuration file as heli2go, the module which builds the helicorders,
we are guaranteed that if the data shows up in the heli2go selection 
list, heli2go can find it.  After heli2go.pl lets you make a few 
more display decisions, you submit the job to heli2go.  
Building a helicorder plot can take several minutes.  Rather than 
forcing you to wait for each one to complete before submitting the next, 
each helicorder job is spawned and allowed to run to completion on its own. 
The only way to know if a helicorder is done is by periodically 
re-loading the data index to see if it has shown up.

To see Heli-2-Go in action, take a look at 
http://campbell.wr.usgs.gov/waveforms/cgi-bin/heli2go.pl

