Review the history log for any error messages generated by the instrument.
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).
Additional Information:
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).
Review the history log for any error messages generated by the instrument.
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.
Additional Information:
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).
Review the email log for any MOC ANS alerts issued to the ANS phones during the period of interest.
These alerts are usually either instrument error messages or RDL limit violations.
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.
Additional Information:
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
Review the AIA "CCD Temperatures" plot on the Quick Look Plots page.
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.
Nominal (as of 1/13/2011) CCD temperatures plot example:
Additional Information:
Plots are shown in UT Time: UT Time = Local Time + 8 (or + 7 for Daylight Savings)
Review the AIA "Main Bus Current" plot on the Quick Look Plots page.
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.
Nominal (as of 9/9/2010) current plot example:
Additional Information:
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)
Review the AIA "Clock Drift WRT Ground" plot on the Quick Look Plots page.
The clock should be within 50 ms of the ground time, and the
data should extend to within 30 minutes of the current time.
If the plot is not up to date:
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)
If the Clock WRT Ground plot is unavailalbe, please generate a Clock WRT Spacecraft plot using the
48 Hours Plots page and use that to determine the state of the clock drift.
Please do not forget to comment in the log as well.
Review the AIA "Sun Vector Y Error (all GTs)" and "Sun Vector Z Error (all GTs)" plot on the Quick Look Plots page.
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)
Nominal (as of 9/9/2010), GT Sun Vector Errors plot example:
Explanation: The GT sun vectors are measures of pointing. Error
is on the y-axis in units of 0.1", (so an error of 10 would indicate the
pointing was 1" off). Though the pointing varies for each GT, all four
plots should be following the same trend. The control GT (probably ATA 3) should be
centered on zero.
Review the AIA "ISS Average Errors" (Y and Z) plots on the Quick Look Plots page. These plots show the standard deviation of the ISS average errors for each ATA.
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.
Explanation: The error signal is proportional to the offset from
the sun, in arcsec (50 DN ≈ 1 arcsec).
The plotted data is the standard deviation of the ISS error signals. The
standard deviation is calculated over a running time window of
5 minutes for the 48 hour plots and 1 minute for the 4 hour plots.
Review the AIA "Sequencer Commanded Exposure" plots on the Quick Look Plots page.
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.
Nominal (as of 9/9/2010), annotated Commanded Exposure plot example:
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.
Annotated image display page screenshot:
Additional Information:
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.
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.
Check to see if the ANS System indicators (aia-tnc-ANS-AlertUp, hmi-gse-ANS-AlertUp, etc.) are all green. If any of them are yellow or red
please refer to the AIA03789 document: How to Restart the ANS and GSE Alert System.
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.