Displaying report 1-1 of 1.
Reports until 14:53, Tuesday 21 April 2015
H1 CDS (SUS)
betsy.weaver@LIGO.ORG - posted 14:53, Tuesday 21 April 2015 - last comment - 16:09, Tuesday 21 April 2015(17983)
SDF status after upgrade

While clearing out many settings diffs on the SDF after the RCG 2.9.1 upgrade today, Kissel and I discovered a few issues, the worse offender is the first one:

-  OPTICALIGN values are not being monitored on SDF since they constantly change.  However after reboots, these values are read in via a burt from the SAFE.SNAP file.  Often these files are older than 1 day (in many cases weeks old) so therefore restore an old IFO alignment.  We need a better way to save local IFO alignments in the SAFE.SNAP now that we have rerouted how we transition suspensions from aligned to misaligned.

-  Precision of the SDF writing feature is different than the precision in the reading feature, therefore they do not clear from the diff list when you attempt to ACCEPT them.

-  Useage of CONFIRM and LOAD TABLE buttons is still confusing

-  Settings on the DIFFS screen represent the switch settings via reading SWSTAT however the MON list still shows the SW1 and SW2 settings.  This means the TOTAL DIFFs and NOT MONITORED counts never add up to the same number.  1 SW line item on the DIFF screen turns into 2 line items when pushed to the NOT MONITORED screen.

-  The ramp matrix (specifically looking at LSC) is constantly reporting changes.  The time stamp keeps updating even though the value is not actually changing.  Haven't looked at other ramp matrices yet.

Comments related to this report
jeffrey.kissel@LIGO.ORG - 16:09, Tuesday 21 April 2015 (17985)
I've done a little bit more clean up -- this user interface is fantastic once you get to know how to do the operations you want. 

For example, I wanted to 
    - Get rid of the "errant file" red messages on the corner station BSC-ISI tables
    - Reduce the channels "not found" and "not initialized" to zero on the HAM-ISI tables
both of which require one to write (i.e. confirm) something and then force the front end to re-read that newly written table (i.e. load) to clear the errors. So, I've 
    - selected to monitor the ISI's Master Switches (which instantly become a diff, because the "safe" state is still with the master switch OFF, and we're currently using the ISIs), 
    - confirmed the change, (on the main table screen)
    - loaded the table, (on the "SDF RESTORE" screen)
    - selected to unmonitor the master switch, 
    - and confirmed. (on the main table).

Very nice!
Displaying report 1-1 of 1.