5. DYNAMICS MODE PROCEDURES AND MONITORING 5.1 Description of the Dynamics Program The detailed study of the solar convection zone DYNAMICS requires all observable modes for a long interval. During high-bandwidth telemetry intervals exceeding 72 hours, MDI transmits full disk Dopplergrams each minute for the primary dynamics program. For most of the time during a dynamics period the DEP is executing a FRAMELIST* titled PRIME60. This is a set 20 pictures (FILTERGRAMS), two 8 picture (4 up and 4 down) scans of the line plus 4 continuum pictures. What is sent down in the high rate telemetry from this is a VELOCITY (DOPPLERGRAMS) image and a either CONTINUUM image or a LINE DEPTH image. The line depth gives a measure of the intensity of the line and is a measure of the strength of the magneti field. All of these images are computed by the IP based on the 20 pictures. (The choice between the continuum and a line depth is made by setting a DEP flag. Currently (6/6/96) line depths images are being sent down) The dynamics program can be interrupted in one of two ways. The first is the ALT SEQ (Alternative Sequence, a better name would be alternative framelist.) The second is from a CAMPAIGN FLAG. The alt seq is an alternative pair of framelist that takes MAGNETIC FIELD (MAGNETOGRAMS) for 30 seconds each minute and takes velocity images for the other 30 seconds. Magnetic field images are made by taking pictures with different polarizations. A register in the DEP controls the cadence of the Alt Seq. Campaigns are started via a ground command. This can be done with a TSTOL (A command sent by the S/C Operators) or with NRT commands (Near Real Time, commanding from the MDI/EOF workstation). During the dynamics period campaigns are used if it is necessary to get dumps of on board data (such as to check if the FLAT FIELD** is still good) or to perform tests that are necessary to check the health of the instrument (such as checking focus or for contamination "ice" buildup). Data from the campaigns are sent down in the high rate channel. When either a campaign or the alt seq is being performed it will use 30 seconds of the 60 second sequence. During the other 30 seconds the frame list being executed is PRIME30. Prime30 is basically the same as prime60 except that it is done in 30 seconds and only 1 sweep up and down of the line instead of 2. (10 pictures instead of 20). A series of data products is made from this data and the data is sent down in the LOW RATE (5KB) channel. The data from this channel is used for the long term structure program. During the periods of the year when we are not in continuous high rate mode MDI has two basic modes. Structure and campaign. During periods of structure the prime60 frame list is executed and the data products are sent down the low rate channel. During periods of campaigns we again have high rate telemetry and various campaigns are performed to take advantage of this. During these campaigns MDI will perform special scientific tasks and offers an opportunity to make coordinated observations with other SoHO experiments and with observatories. The beginning of the campaigns can also be used to perform special tasks like data dumps and tests to check on the health of the instrument as was done in the dynamics periods. As with the dynamic periods, during the campaigns, the other half each minute will be used to perform prime30 and continue the structure program. There are a few special campaigns a that completely displace the structure program. Because of the architecture of the DEP software, there must a prime half, so the prime that goes with such campaigns is called PRIME00. It takes essentially 0 time. * FRAME LIST A frame is a set of instructions in the DEP that set the mechanisms positions, the exposure time, and tells the camera what messages to send to the IP. A frame list is a list of these frames. ** FLAT FIELD A pixel by map used by the on-board processor to adjust for inherent inconstancies in the image. The on-board flat field is used for those images that are sent down in the low rate data and are based on continuum images. For the velocity based images, flat fielding is not necessary since the images are based on differences between pictures. 5.2 LOW RATE DATA Run mon_sci5k continuously There is a CRON job (created by Mons M.) which checks every 15 minutes that mon_sci5k is running and restarts it automatically if it has stopped, this means that mon_sci5k need NOT be started by an EOF person normally. If for some reason it does need to be restarted by an EOF person then type the following to start it: IDL> mon_sci5k, /disp_loi, /log, /file 5.3 HIGH RATE DATA 5.3.1 Data Taking Take Velocity and Continuum or Line Depth data continuously Instance Form to switch from continuum to line depth is below ^000213: Action: dyn_ldepth Status: Open Date_submitted: 24-May-96 SOI_Proposal: Objective: To switch back to line depth downlink in sci160k telemetry IAP_sci_obj: Requestor: Rock Bush Duration: 5 min Requirements: NRT-s; MDI-H VC2; ALT_Seq Enabled; Loop Closed; Stucture Running; Dynamics Mode; Complete 24 to 36 hours of continuum in high rate telemetry Campaign: ALT_Cadence: Preferred_Time: 1996 May 25 Started: Completed: Script: perf dyn_ld_v01 Notes: Starts downlinking LineDepth instead of Continuum as the second dynamics data product. 5.4 HEALTH MONITORING Screens to check: Flight Status (screen 12) xmonseq (on unix) - shows what framelist is being executed by sequencer xmonlog (on unix) - displays operators log mon_sci5k (in IDL) - displays low rate data and loi images mdi_display (in IDL) - displays high rate data products iperr_sea (in IDL) - gives list of IP Errors plots of IP Errors (on web or in IDL using rtplot) DEP Status (on toolchest) Power & Temperature (on toolchest) General Telemetry (on toolchest) Look at the health pages and monitoring schedule on /mdisw/doc/monitor.info or on the web at http://mdiems.nascom.nasa.gov/health_mon/ Snapshot of Health Monitoring Page ***************************************************************************** Health Monitoring Documents Documents describing health monitoring requirements and the various displays can be found here. Monitoring schedule for week of 6/3-6/23. LOI Image Data Products LOI image per 5 minutes for the past hour (postscript) LOI image per hour for the past 24 hours (postscript) LOI image per day for the past ??? (postscript) LOI Time Plots LOI-V and LOI-C Average plots for the past 24 hours (postscript) LOI-V and LOI-C Min/Max/Avg/Dev plots for the past 24 hours (postscript) LOI-V mission plot LOI-C mission plot LOI-V, S/C velocity, and blue shift plot for past 2 days, for past 20 days or for the mission Housekeeping Time Plots IP Error Count and error code for the past 24 hours or for the past 60 days VC Status and Sequence ID for the past 24 hours or for the past 60 days Some Temperatures for the past 24 hours or for the past 60 days Some Voltages for the past 24 hours or for the past 60 days All Currents for the past 24 hours or for the past 60 days Limb Tracker errors (avg and max) for the past 24 hours or for the past 60 days PZT voltages (amount of correction and drift) for the past 24 hours or for the past 60 days PZT adjustments in arcseconds for the past 24 hours or for the past 60 days EDAC Page Error rates (single and multi) for the whole mission Health Log Files Operator's log for last 3 days. Mon5k log for last 50 lines. IP Error listing for last 48 hours. IP Error listing for last 20 days. Dynamics/Campaign and VC2/VC3 listing for last 24 hours. FOT Log of Lost Telemetry PACOR Log of Lost Telemetry Snap shot of MDI Flight Status Display "Screen 12" Directory of Past Screen 12 snapshots SCI5K and SCI160K Data Product Images The last 4 Dopplergrams The last 4 Line Depths The last 4 Full Disk Magnetograms The last 4 High Resolution Magnetograms The lastest processed Dop, LDep, FD Mag, HR Mag All SCI5K image data products for most recent run All SCI5K image data products for 24 hours ago All SCI5K image data products for 48 hours ago ********************************************************************************** 5.5 TROUBLE SHOOTING Failure & Recovery information is on the health pages on the web