This morning I asked the question: 

"Who is OSEM[*] in the Alarm Handlder??"     (  *  can be 1-6 in the Alarm Handler)

Dr. Kissel handed over a crumpled Post-It note which decrypted the OSEM mystery.  Currently, to understand what a SUS alarm means, one needs this Post It note because the Alarm handler names SUS Watchdog channels as OSEM1, OSEM2, ...OSEM6 (which isn't really useful since the SUS Expert screens don't use the OSEM names; they use F1, F2, F3, Left, Right, Side).  I posted the Post It notes to the CDS SUS wiki.  [As for the actual alarm in question, it was related to OSEM5&6 (Left & Right) "Centering"; and this is most likely due to not being pumped down].

I did actually do something here.  Jeff showed me the IOP Watchdog screen, and how some of the custom medm screens on here have been changed from using "OSEM" to "useful" names.  But we noticed some sub-screens weren't updated (namely EY BSC6).  So, I updated this screen from the OPS Station.  Here are steps taken:

• Open Terminal
• Since we were logged in as ops, we had to log  in as controls with graphical capabilities to make medm changes to custom screens
  • ssh -X controls@operator0
• cd /opt/rtcds/userappsrelease/cds/h1/medm
• Open medm screen you want to edit
  • medm H1CDS_SOFTWARE_SUS_WATCHDOGS_EY.adl &       | this is screen I changed |
• Make changes to screen (here I changed the OSEM names to actual names)
• Save (on medm)
• Back on Terminal, one will want to commit this modified file to SVN
• Check SVN status & then commit
  • svn st
  • svn commit -m "changed names for OSEMs" H1CDS_SOFTWARE_SUS_WATCHDOGS_EY.adl
    • To commit one will need to login with your ligo.org account
• End

(I also changed names on the H1CDS_SOFTWARE_SUS_WATCHDOGS_TST.adl screen as well)