Instructions for filling out the AIA Health and Safety Checklist

1) Were there any errors in the History Log? Return to Top

• Relevant entries will be located under the "Error Table" heading.
• If an error exists select "Yes". If it is a concern, copy the error message into the comments section along with any other relevant information. (If there are multiple copies of the same error you only need to include one example).

• Daily calibrations may sometimes generate errors at the time of calibration. These errors are not of concern, but should still be noted.
• When filling out the checklist early in a UT day (late in a California night), be sure to look back to the previous UT day to check for information from the last 12 or so hours.
• Error messages may or may not have also generated a MOC ANS alert (see #3).

2) Were there any Limit Violations in the History Log? Return to Top

• Each limit violation notification will contain a limit type (yellow or red and high or low), the time at which the violation was detected, and a message saying which telemetry point limit was violated.
• If a limit violation occurred select "Yes" and copy the notification into the comments section along with any other relevant information. If there are multiple copies of the same error you only need to include one example.

• When filling out the checklist early in a UT day (late in a California night), be sure to look back to the previous UT day to check for information from the last 12 or so hours.
• These limit violations may or may not have also generated a MOC ANS alert (see # 3).

3) Were there any alerts in the MOC ANS mail archive? Return to Top

• If an alert exists, select "Yes". If it is a concern, copy it into the comments section along with any other relevant information.
• If you are carrying a phone, check that you received the alert.

• Weekly FOT test message alerts sent on Thursday at ~18:00 UT are standard, but should still be noted.
• Weekly EGSE test message alerts are sent to the phones on Wednesdays, but do not show up in the email log

4) Are the CCD temperatures appropriately cold (less than -65C) and is the plot up to date? Return to Top

• Temperatures are nominally around -71 C, and vary about ±3 degrees per day (as of 11/05/12). If there is a sharp increase in temperature check the power screen to see if all the decontamination heater relays are off.
• Verify that the plot is up to date, with the x-axis extending to within 30 minutes of the current time.

• Plots are shown in UT Time: UT Time = Local Time + 8 (or + 7 for Daylight Savings)

5) Does the instrument current look nominal (about 4-6 amps) and is the plot up to date? Return to Top

• A nominal current plot will appear like a noisy signal, varying on the order of ~1 A. The range of the noisy signal should be about 4 to 6 amps when the instrument is under nominal thermal control. (As of 9/8/2010).
• Verify that the plot is up to date, with the x-axis extending to within 30 minutes of the current time.

• If the signal is not noisy, check the operational heaters to make sure that they are on and the temperature zones are at the correct temperature.
• A sharp increase in the average current would suggest either that a heater zone has switched to 100% duty cycle, or that there has been a short.
• Plots are shown in UT Time: UT Time = Local Time + 8 (or + 7 for Daylight Savings)

6) Does the motor current look nominal (especially min <5mA)? Return to Top

• A nominal maximum motor current will be around 330 mA, with a minimum around 3.5 mA and an average around 29 mA.
• The blue (MIN) current should be small and constant. A higher value would indicate a stuck motor.
• The average current should be steady, with a few blips due to calibrations or eclipses. Any unanticipated blips should be noted as atypical.
• The maximum current signal will nominally be significantly noisier than the average and minimum current signals.

• The typical current for stuck AIA mechanisms (at 15 V) is shown in the table below:



Mechanism	Stuck Current (mA)*
Filter Wheel	38
Aperture Selector	254
Shutter	130

7) Are the forward and aft telescope temperatures currently nominal and flat at their correct set points? Return to Top

• Aft temperatures should be between 25.1 and 25.4 C for ATA1,2,3 and 30.4 for ATA4 (as of 11/05/12). Noise on the order of 0.1 C is nominal.
• Forward temperatures should be at the following set points:



ATA	Temperature (C)
1	38.6
2	32.6
3	34.9
4	40.7

• If a forward heater is not controlling, a 24-hour cycle will appear in the "Telescope Forward Temperatures" plot.

8) Is the clock delta current and within 50 msec of ground time? Return to Top

• The clock should be within 50 ms of the ground time, and the data should extend to within 30 minutes of the current time.

• The spacecraft time file is probably not being updated because there is an error with Shelby.
• Use the "Clock Drift WRT SC" plot to determine the delta with respect to the spacecraft.
• If possible, check the spacecraft time on the ASIST page and note how far off the spacecraft clock is WRT ground. The real clock delta is [AIA WRT SC - SC WRT ground].
• The spacecraft clock adjusts to zero periodically. These adjustments are apparent on the plot and can be used to estimate the AIA clock's drift rate (see diagram below).
• You may also use the Clock Adjust Log to estimate the current SC time if you do not have access to the ASIST page.

• The actual limit on the clock drift is ±100 ms WRT ground, but it is still worth noting if the delta is beyond ±50 ms.
• Plots are shown in UT Time: UT Time = Local Time + 8 (or + 7 for Daylight Savings)

9) Do the GT Sun Vector Y and Z errors look nominal (between -20/+20)? Return to Top

• The signals for all four ATA guide telescopes (GTs) should be between -10 and +25 mV for ATA1,2,3 and ~120mV (Z) to ~58mV (Y) for ATA4 (as of August 2016)

10) Are the ISS Y and Z Error Signals less than 250? Return to Top

• If the error is less than 250, select "Yes".
• If the error exceeds 250, select "No". This excess noise could be due to reaction wheel hovering, a maneuver, or a switch to inertial mode for any other reason.
• Note that on the 4 hour plots the data is not smoothed, so signals a little higher than 35 might still be nominal.

11) Does the Commanded Exposure indicate the AEC is functioning properly? Return to Top

• If the AEC functioned you will notice shorter than normal exposure times, presumably in response to a flare. If you see this, you could note which event caused the AEC to function by checking the space weather reports.
• Nominally, the plots should dip to zero every day at 21:00 when the daily darks are taken. ATA 3 dips down to 500 ms once every hour when a 4500 exposure is taken. These dips do not always show up due to sampling on the 48 hour plot, but they should show up in the 4 hour plot.
• Weekly calibrations are usually made on Tuesday around ~20:00 UT, and will be apparent on the plot, especially when the "long exposures" are taken every other week.
• Unexplained blips should be noted in the comments section.

12) Has the FSN been incrementing properly? Return to Top

• Check the Filtergram Sequence Number (FSN) plot on the Quick Look Plots page.
• Check the slope of the 48 hour plot to verify that the FSN has been incrementing at about 58,000 images per day.

13) Are the latest images up to date and typical? Return to Top

• go to the JSOC Watch Level 0 page.
• Click the pink "Images Off" and "Details Off" buttons to display images. (The buttons should now be green and read "Images On" and "Details On").
• Check that the images are up-to-date. One way to do this is to look at the "Last DCS Recieved" time. The typical lag time is around 3 minutes, but it can be on the order of hours if something is wrong. It is worth noting if the lag time is beyond 5 or 10 minutes.
• Scan down the details and check that the various wavelengths are represented with nominal exposure times. (You may need to increase the number of images displayed in the "Images = " box in order to see all wavelengths.)
• Scan down the images and check that they appear nominal.

• If a few images are dark or do not show up, it is probably due to imperfect auto-scaling. If an image is exceptionally dark you should open it in a FITS viewer (such as ds9) and scale it manually to verify that it is not completely black.
• You may also check The Sun Today page, where current images are pre-scaled to a nice color table.

14) Are the Datamin=0 counts green? Return to Top

• If any of the three Datamin=0 lines at the bottom of the page are not green, then send an email to hek_local[at]lmsal[dot]com so the issue can be addressed.

15) Is the ANS System Status all green and current? Return to Top

16) Does the SunToday page look nominal? Return to Top

17) Did you check HMI watch lev0 and if the magnetogram is current? Return to Top

• go to the JSOC Watch Level 0 page.
• Click the pink "Images Off" and "Details Off" buttons to display images. (The buttons should now be green and read "Images On" and "Details On").
• Select radio button next to HMI.
• Check that the images are up-to-date. One way to do this is to look at the "Last DCS Recieved" time. The typical lag time is around 3 minutes, but it can be on the order of hours if something is wrong. It is worth noting if the lag time is beyond 5 or 10 minutes.
• Click on the Latest Magnetogram link on the checklist menu above and verify that the magnetogram is current and typical.