Website Revision History Log

 

Released Version a.15.0 UpdatesReturn to Top

Date: 2012-May-21
Author: Ted McCormack

Changes made to the AIA Health and Safety website for Version a.15.0 include:

Released Version a.14.0 UpdatesReturn to Top

Date: 2012-February-20
Author: Emma Lehman, Ann Kapusta

Changes made to the AIA Health and Safety website for Version a.14.0 include:

Released Version a.13.0 UpdatesReturn to Top

Date: 2012-January-6
Author: Ann Kapusta

Changes made to the AIA Health and Safety website for Version a.13.0 include:

Released Version a.12.1 UpdatesReturn to Top

Date: 2011-November-18
Author: Emma Lehman

Changes made to the AIA Health and Safety website for Version a.12.1 include:

Released Version a.12.0 UpdatesReturn to Top

Date: 2011-September-08
Author: Ann Kapusta

Changes made to the AIA Health and Safety website for Version a.12.0 include:

Released Version a.11.0 UpdatesReturn to Top

Date: 2011-July-28
Author: Ann Kapusta

Changes made to the AIA Health and Safety website for Version a.11.0 include:

Released Version a.10.0 UpdatesReturn to Top

Date: 2011-March-24
Author: Ann Kapusta

Changes made to the AIA Health and Safety website for Version a.10.0 include:

Version a.9.1 (Update to a.9.0)Return to Top

Date: 2011-January-11
Author: Ann Kapusta

It was noted in the checklist, that Question 11 ("Are the ISS Y and Z Error Signals less than 35 for all ATAs?") was duplicating the comment field from Question 10 ("Do the GT Sun Vector Y and Z errors look nominal (mostly between +/-15)?").
Changes were made to the main site to correct this problem without releasing a new version (now version a.9.1). Changes for a.9.1 inclue:

Released Version a.9.0 UpdatesReturn to Top

Date: 2010-December-13
Author: Ann Kapusta

Changes made to the AIA Health and Safety website for Version a.9.0 include:

 

Released Version a.8.0 UpdatesReturn to Top

Date: 2010-November-09
Author: Ann Kapusta

Changes made to the AIA Health and Safety website for Version a.8.0 include:

 

Released Version a.7.0 UpdatesReturn to Top

Date: 2010-October-18
Author: Ann Kapusta

Changes made to the AIA Health and Safety website for Version h.7.0 include:

Version a.6.2 (Update to a.6.1)Return to Top

Date: 2010-September-9
Author: Ann Kapusta

The checklist question asking "Does the Commanded Exposure indicate the AEC functioned?" does not fit the standard "Nominal" or "Atypical" response. It was decided at the September 9th JSOC meeting that while a better solution is developed for the AEC question, that the previous answers (yes=nominal, no=atypical) be switched so that the operator is not forced to enter a comment when the AEC was not used.
Changes were made to the main site to correct this problem without releasing a new version (now version a.6.2). Changes for a.6.2 inclue:

Version a.6.1 (Update to Release a.6.0)Return to Top

Date: 2010-August-26
Author: Ann Kapusta

An error was discovered in the AIA Checklist after the release of version a.6.0. There was a question in the checklist (GT Sun Vector Errors) that was added to the checklist at the last update, but the answer was not being reported in the log summary of the checklist. The error was reported by Sarah M. in the Log on August 26. Changes were made to the main site to correct this problem without releasing a new version (now version a.6.1).
Changes for a.6.1 inclue:

 

Released Version a.6.0 UpdatesReturn to Top

Date: 2010-August-19
Author: Ann Kapusta

Changes made to the AIA Health and Safety website for Version a.6.0 include:

 

Released Version a.5.0 UpdatesReturn to Top

Date: 2010-June-29
Author: Ann Kapusta

Changes made to the AIA Health and Safety website for Version a.5.0 include:

Released Version a.4.0 UpdatesReturn to Top

Date: 2010-May-11
Author: Ann Kapusta

Changes made to the AIA Health and Safety website for Version a.4.0 include:

Released Version a.3.0 UpdatesReturn to Top

Date: 2010-March-23
Author: Ann Kapusta

Changes made to the AIA Health and Safety website for Version a.3.0 include:

Released Version a.2.0 UpdatesReturn to Top

Date: 2010-March-02
Author: Ann Kapusta

Now that SDO has launched and real time AIA data is being collected, the websites are being used frequently to monitor the health of the instrument on orbit. Because of this, the websites need to remain extremely stable and reliable. However, as the site gets used, I am receiving a lot of feedback on what people want to see on the website and how things can be changed to make it more functional for health and safety monitoring. I need to be able to keep updating the sites to make them as usable as possible for the operators, but need to make sure that we don't sacrifice the reliability of the website while mkaing these changes. Therefore, the biggest advancement is that we have now created a beta test site to fully test all changes made to the health and safety website before taking the changes live. The address for the AIA test site is: http://hmi.stanford.edu/hktest/AIAHealthSafety/index.jsp

Changes made to the AIA Health and Safety website between initial launch of the site and March 2, 2010 include:

Functionality at Release (Launched February 11, 2010)Return to Top

The HMI and AIA health and safety websites were developed for monitoring the on-orbit health of the instruments. The initial release of the website was in support of launch and early operations. Modifications to the website will be made to support all on-orbit activities for the duration of the mission life. The following summary explains the functionality of the website when initially released and this revision log will keep track of all future changes and modifications to the website.

AIA Website Features:

Near Real-Time Data Plots
This section includes a number of plots that show near-real time (updated every 15 minutes) telemetry data from the AIA instrument. At the time of release, there are 32 different plots that display 93 different AIA telemtry points that can be viewed by clicking on the "View All Plots" link off of the main page. There is also a "Custom" from the main page, but there is currently no support for customizable plots, but there is a desire to do this in the future. From the standard plots, every plot has between 1 and 8 different data series. The current functionality is a drop-down menu with the list of the titles of each of the 32 differnt data plots. The user selects which plot they would like from the menu and then has three different methods of viewing the plots. The first ("Make Plot") opens the plot in the current window. The second ("Open in Popup") will open a new popup window that contains the selected plot. The third ("Open in New Tab") will plot the selection in an entirely new tab in the current browser.
Once open, the user will see the plot with the predetermined telemetry points associated with that title plotted in the screen. The current default time window is 4 hours with updates to the data every 15 minutes. Data is pulled using java source code and displayed using the the Cewolf plot library (based on JFreeChart) from txt files created by an IDL script (discussed in more detail in the IDL section below). Below the plot, there are displayed a few interactive features. Currently there are three ways to change the current plot: define the x-axis (time range), y-axis (data range), and change the plot size. Set Time Range has two entries - start time and stop time. Needs to be given in hh:mm format and can be anytime in the 4 hour time window when there is data available. Set Y-Axis Range has two entries - minimum and maximum. Values need to be numeric but but can be either int or float. Change Plot Size has two entries - width and height. Default values are given in the boxes but can be defined as any integer value representing pixel size. These values are reset whenever a new plot is called.
Instrument Hisotry Log Information
This section includes a sorted subset of the daily history log generated by the EGSE on the host machine (aiasdp-mon). There are two links off of the main page, one for the daily list and one for the tool to create a custom list from any date.
Clicking on the "Daily List" link off of the main page will take you to a new page displaying the current parsed and sorted list of entries in the today's history log. This section of the website is real time and displays the current information as reflected in the current history log. The information is sorted out into 6 sections on the page - error messages, limit violations, INCs (Instrument Notification Commands), stale telemetry notifications, warning messages, and information messages. There is an additional functionality for three of the lists - error, warning, information - that allows you to reduce the displayed information into an even smaller subset based on category of the message. This uses the code given in the history log to sort out common messages. Currently, the limit violations table only reports when the limits are tripped, but do not report when limits come back in to normal range. An update to this section will probably be made in the near future to better signify limit violations. The stale telemetry table reports both when telemetry goes stale and when it is current again.
The customizable tool for the list of housekeeping information essentially creates the "daily" page but for any day that has data in the history log file. Clicking on the "Customized" link from the main page takes you to a page that allows the user to select certain values to create a customized list of acitivities on a give day. The user can specify what type of list they would like to view (or all if that is the desire), the date they would like to view information from, and can narrow the search by category if they so desire. Clicking on the "make list" button will pull up the desired list in the current page. If no information exists for the date selected, a message alerting the user to that will be displayed. If the user attempts to enter a day in the future the user will also be alerted to that error. Clicking on the "Reset Form" button will clear all values in the form. Clicking on the "Return to Homepage" will take the user back to the landing page for the H&S website.
Simulated EGSE Screens
Off of the AIA Health and Safety Main Homepage there is a link to view "Screen Snaps". By clicking this link the user will be taken to a page where a list of available screens are listed. These screens are made to simulate the screens seen on an EGSE terminal in the JSOC or MOC rooms. The source code for creating the screens for the website reads in the .scr files for each of the listed screens, meaning that if any change is made to the screens for the EGSE, this will be automatically reflected in the website as well. Currently, AIA has 17 screens replicated from the EGSE.
Clicking on one of the screen links opens a popup window containing information pertaining to that screen type. The screens are formatted to look identical to the EGSE screens. Data is retrieved using the same IDL script that is run every 15 minutes in the background to collect information for the plots. So, screens are updated every 15 minutes and are not real time. The screens also have some functionality similar to the EGSE screens in how the color coding for the telemetry points works. Currently, blue functions as "current" telemetry and purple is for telemetry that is older than 15 minutes. There is no color coding currently for limit violations.
Checklist and log
This section of the website has a few pages associated with it. All pages that are either associated with the log or the checklist are password protected. The first link is to fill out the daily checklist form for the AIA instrument. Clicking on this link will take the user to a form (after entering password information) to be filled out about the health and status of the instrument. The form allows the users to enter their name and the time frame they are reporting on (defaults to 24 hours, but if a checklist has not been completed in a few days or was completed that morning, the reporting time frame can be changed accordingly). Following that there are a series of questions relating to the health and safety of the instrument using information available throughout the website. There are three ways to answer each question (Yes, No, and Unsure) and room to make comments for each question. There are currently 11 checklist quesions, but these need a serious update. The user answers the questions and enters the information as they see on the website. Once completed, the user can submit the checklist or reset the checklist. If the user chooses to submit the checklist, they will be taken to a page that alerts them that the checklist was successfully submitted. Current functionality does not provide a check before submitting the checklist. Therefore, it is possible for a user to leave sections of the checklist blank and still have it post to the log.
Another section of the Checklist and Logs is the daily log. When a checklist is posted by an operator, it is posted to the daily log. Additionally, there is a field on the log that allows any user (who can access the password protected sites) to create an entry in the log. Log entries are currently sorted from oldest to newest, with oldest at the top of the page and newest appearing at the bottom All entries are date and time stamped for when the entry was made to the log. Current functionality uses the date of the current blog to signify to the code which log to put the information in. Therefore, if you are looking at yesterday's log and make a comment, it will appear on yesterday's log with a time stamp of today. The way the checklist is displayed is still extremely beta and different ways of displaying the answers to the checklist questions are shown. This will be updated as feedback from operators is gained as to how they would like the checklist information displayed.
The final section of the checklist/log part of the website, is the archive of all previous logs. The log is currently sorted by day, so that when a day change occurs, a new log page is created and new entries for the checklist or log are entered there. There is a link from the main page to view the log "Archive". This allows the user to chose any date from a drop down menu and display the log for that day.
Instrument Images
This section is currently a simple link to the JSOC Watch Level-0 data site hosted at Stanford.
Phone List
The phone list is a list of contact information for various personnel supporting the AIA program as well as phone numbers for monitoring rooms, operations centers, and typical meeting lines. The phone list is a duplication of the list on the Team site under document number HMI02151.
Extrernal References
This is a list of additional sites that can be helpful when monitoring the status of the AIA instrument, or just to gain additional information about the instrument. This section currently has links to 6 pages, but can be updated as needed.
Document Access List
This section has not ben created at the time of release, but will contain key documentation for operation of the AIA instrument.
Additional Support to Operate the Website:
CRON Job
On the host machine for the websites (aiasdp-mon), there is a CRON (time based job scheduler on unix machines) job running that is responsible for starting the jobs to collect the data for the plots and screens on the H&S website. The CRON job is currently set to run every 15 minutes and write the results of the task to a log file. Currently, the CRON job calls a shell script that starts IDL to collect the data required.
IDL
The IDL session called by the CRON job every 15 minutes currently runs 4 programs to support the H&S websites - 2 for HMI and 2 for AIA. For AIA, the CRON job calls aia_telem_text.pro which collects the last 4 hours of data (or whatever is available) for the data points needed for all the difrerent plots. The other AIA specific cron job is aia_screen_text.pro which collects data for the telemetry points needed for the screens. aia_screen_text.pro actually reads in the .scr files used for the website and finds the mnemonics in that file to call. Therefore, if the .scr files are updated, the IDL will automatically be updated as well. The screen code looks back 1 minute in time from the current time to collect data. If no data is found, "No Data" is written out to the file and is displayed in the screens on the website. Both aia_telem_text.pro and aia_screen_text.pro use the sag routines in IDL to collect telemetry information from the database and write the information into specifically formatted .txt files for use in the website. Average time to run the IDL scripts for both HMI and AIA when there is current data is about 7 minutes - with 2-3 minutes of that being for the database read and the remaining for collecting all the information from the database.