MDI Continuous Period Procedures
	--------------------------------	
					MDM Ver 1.0 18-Nov-96
					MDM Ver 2.0 20-Nov-96
					MDM Ver 3.0  4-Apr-97

		Pure-Dynamics		Campaign

Preparation:	* Set "Term Cam" Flag	* Clear "Term Cam" Flag
		* Set ONE "Chain Addr"	* Set all chain addresses
		  to PAGE_DUMP (or to	  to campaign for the run
		  "no-ops")		  (by SEQ_OPTIONS or
		* Set R5 to		  xset_chains.pro)
		   =0 for mag in 160k
		   =1 for mag in 5k

FOT every 12hrs	* Run FL_DYNLOIL	* Run FL_LOIDUMP
during VC2		(or)
		  run FL_DYNLOIC

FOT every 24hrs	* Run FL_DYNPAGE
during VC2

VC0 Recovery	* Standard ID2MM	* Standard ID2MM

VC2 Times	* 01:00 - 02:00		* 01:00 - 02:00
		  14:00 - 15:00		  14:00 - 15:00

PURE-DYNAMICS NOTES:
   * In the event that we enter VC0 by accident (or design), the
     the standard ID2MM (VC0 to VC2) should be run.  It will run
     CAM_VC2_OBS (12 minutes) and then PAGE_DUMP (6 minutes) and
     will then terminate the campaign mode and enter dynamics.
     If the chain addresses are all set to NO-OPS ("FFFF") then
     it will only run CAM_VC2_OBS.
   * Do not use SEQ_OPTIONS to set the chain address (unless it's
     to the NO-OPS ("FFFF").  Use XSET_CHAINS.PRO to set it since
     it will load chain addresses after the first address with
     NO-OPS.  Otherwise there will be 8 full runs of the campaign
     in a row.
   * FL_DYNLOIL dumps one minute of linedepth data product and
     then LOI-V and LOI-C circular buffer (by overwriting the
     second data product downlinked)
   * FL_DYNLOIC dumps one minute of continuum data product and
     then LOI-V and LOI-C circular buffer (by overwriting the
     second data product downlinked)
   * FL_DYNPAGE dumps portions of pages 12, 14 and 16
   * If R5=0, then VC2 times should be when an ALT period happens 
     so that we get 2 FD mags per day in VC2.
   * Interruptions to data
	5K Medium-L:	If R5=1, then 25 min lost/96 minutes
	160K 2nd Obs:	If R5=0, then  2 min lost/96 minutes
			3 min/12 hours for FL_DYNLOIL (or C)
			11 min/24 hours for FL_DYNPAGE
CAMPAIGN NOTES:
   * In the event that we enter VC0 by accident (or design), the
     the standard ID2MM (VC0 to VC2) should be run.  It will run
     CAM_VC2_OBS (12 minutes) and then chain into the continuous
     contact campaign.
   * FL_LOIDUMP starts a campaign (CAM_CONT_CONT1) which dumps
     LOI-V and LOI-C circular buffer, 1 minute of FD continuum
     observable and filtergram, and 3 minutes of 1/2 page
     dumps (cycles through pages 12,14 and 16)
   * We will lose one minute on either end of CAM_CONT_CONT1
     because of the way that chaining does a head and tail
     at the beginning/end of each campaign list.
   * Because FL_LOIDUMP uses the chaining option, the chain
     index will increment up to 8 in the first 8 runs
     of FL_LOIDUMP and it will then sit there (since the
     chain flag is not reset).  We will **NOT** lose an 
     additional minute of observations when the end of the chain 
     list is reached (when the chain index will reset and start 
     over, thereby doing an extra head/tail).
   * Interruptions to data:
	All cam data:	7 min/12 hrs for CAM_CONT_CONT1

GENERAL NOTES:
   * The mag in 5K will only happen when in dynamics mode.  When
     the mode is structure or campaign, any mag D/L happening is
     aborted and the medium-l is resumed.