40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log  Not logged in ELOG logo
Entry  Tue Sep 9 00:34:34 2014, Jenne, Update, LSC, Figuring out where to do DARM->AS55 
    Reply  Tue Sep 9 14:25:46 2014, jamie, Update, LSC, Figuring out where to do DARM->AS55 
    Reply  Wed Sep 10 10:49:39 2014, Manasa, Update, LSC, Y arm green + PSL green mode overlap 
       Reply  Wed Sep 10 21:05:43 2014, Jenne, Update, LSC, Holy sensitivity, Batman! ALS_Y_outOfLoop_10Sept2014.pdfALS_XY_outOfLoop_10Sept2014.pdf
          Reply  Fri Sep 12 00:28:04 2014, ericq, Update, LSC, Holy sensitivity, Batman! ALSoutOfLoop.pdf
Message ID: 10478     Entry time: Tue Sep 9 14:25:46 2014     In reply to: 10474
Author: jamie 
Type: Update 
Category: LSC 
Subject: Figuring out where to do DARM->AS55 

Quote:

I have made a ruidimentary lockloss plotting script, that I have put in ..../scripts/LSC/LockLossData, but I'm not satisfied with it yet.  Somehow it's not catching the lockloss, even though it's supposed to run when the ALS watch/down scripts run.  I'll need to look into this when I'm not so sleepy.

We developed a fairly sophisticated lockloss script at the sites, which you could try using as well.  It's at:

USERAPPS/sys/common/scripts/lockloss

It requires a reasonably up-to-date install of cdsutils, and the tconvert utility.  It uses guardian at the sites to determine when locklosses happen, but you can use it without guardian by just feeding it a specific time to plot.  It also accepts a list of channels to plot, one per line.

ELOG V3.1.3-