Script		When to use it
======		==============
MONITOR		Any time you want to see what the sky looks like, but don't
		want to record images.  It's quite good at showing whether 
		there are clouds.

WAIRGLOW	When you want to record data during a UARS/WINDII overpass
(13m20s/call)	(and the emission pattern is changing slowly enough to make
		the recorded images meaningful), or when the aurora is faint
		enough to require a long exposure time to see any detail.

		I have not used WFAURORA since I noticed that it frequently
		got only partway through an execution of WFAUROR1 before going
		back to filters 0/0 and starting again.  I haven't noticed 
		this problem with WAIRGLOW.  I'm not sure why they behave
		differently, although it may have to do with the greater length
		of WFAURORA (all 10 filters) compared with WAIRGLOW (only 4
		filters).

WAURORA		Any time you want to record images of an aurora, and don't mind
(21m50s/call)	the slightly greater interval between images caused by VIEWing
		each 10-s image pair as it's acquired.

(13m10s/call)	I wrote a very similar script called WMAURORA (Write Moderate
		AURORA) which takes only 10-s images (no 1-s images), and runs
		VIEW while waiting for the next 10-s image pair to come down 
		the cables.  It runs noticeably faster than WAURORA, but has
		the initially confusing feature that by the time the images are
		displayed, the header data structures have been updated to 
		reflect the images now being acquired, so the filter labels on
		the screen are always wrong.  For example, the EMPTY hole images
		are displayed while the cameras are exposing the 820bg and 608bg
		images, so those labels appear on the screen.  I judge that it's
		a small price to pay for the speed.  In order to keep things
		simple, I deleted the line to acquire 1-s images, but all exper-
		ience thus far shows that those images are of value only in the
		brightest auroras (of which I have seen none here this year).

WFREJA		As you said, during any satellite overflight.  The critical
(13m40s/call)	thing for Freja overflights (when we thought the imager was
		working) was to get as many images as possible in the shortest
		possible time.  Hence, only one image pair per cycle was 
		displayed.  If we still want to take 1-s images as well as 10-s
		images, WFREJA is our best bet.  But if 10-s images only will
		suffice, as they generally will, then WMAURORA is perfectly
		adequate, even during satellite overflights.