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  Fri Nov 4 00:25:49 2011, Zach, Update, SUS, Dr. SUS paths updated--question of human oversight remains 
    Reply  Fri Nov 4 19:30:06 2011, rana, Update, SUS, Dr. SUS paths updated--question of human oversight remains 
       Reply  Sat Nov 5 21:19:08 2011, Zach, Update, SUS, Dr. SUS paths updated--question of human oversight remains 
Message ID: 5822     Entry time: Sat Nov 5 21:19:08 2011     In reply to: 5814
Author: Zach 
Type: Update 
Category: SUS 
Subject: Dr. SUS paths updated--question of human oversight remains 

Ok, here's the deal:

  • For the time being, I have written a "doirun" bit into runDrSUS (i.e. it runs if doirun is 1 and doesn't if it's 0). This is a bad way of doing this, so in the end I think we should put a switch on the IFO MEDM and have the script read the value when the cron job is run. If you want it to be an opt-in rather than a toggle, we can have the script write it back to 0 every time. I don't know how to do this yet because I am an MEDM n00b, but I will do it soon.
  • Since we have decided to keep a human in the loop on the writing to the frontend, I have kept the elog results push.
  • I have also edited diagAllSUS.m so that it archives all computed matrices (hierarchy: .../scripts/SUS/peakFit/inMats/(gps_time_of_kick)/inMat(optic_name).mat). There is a 'writematrices' bit in the M-file, currently set to 0.
  • I have written the script 'writeAllInMats' and the accompanying M-file 'writeAllInMats.m'. This allows the user to write whichever set of input matrices he or she desires (syntax: writeAllInMats (gps_time_of_kick)). If no argument is given, then it reads the most recent kick time from 'kickAll.time' and writes the corresponding matrices.

So, here is an example of how this works:

  1. Someone decides to do a diagonalization on a particular weekend, (eventually) clicking a switch in MEDM
  2. Cron runs runDrSUS at 8am that Sunday. This:
    1. Kicks all the optics, lets them swing for 5 hours, then reengages the watchdogs. The kick time is saved in kickAll.time, and an alert is posted to the elog
    2. Runs diagAllSUS, which computes and saves all matrix data. A report of the results is posted to the elog.
  3. On Monday morning---or whenever---someone looks at the entry and decides whether or not to write the files
    1. If the results are good, he or she runs writeAllInMats and the latest matrices are written
    2. If the results are bad, he or she does nothing. The matrices are still archived and can be written at any time in the future.

The code is set to run tomorrow morning. Everything but the writing will be done.


My inclination is to not do the writing of the matrices automatically nor to do the weekly kicks. Its nice to have long locks of the MC, etc.

I suggest just making the kick on Sundays when someone intentionally asks for it (e.g. by pressing a button on Friday). The free-swinging ringdown ought to be a opt-in kind of feature, not opt-out.


ELOG V3.1.3-