Displaying report 1-1 of 1.
Reports until 16:14, Friday 02 December 2016
H1 General
thomas.shaffer@LIGO.ORG - posted 16:14, Friday 02 December 2016 - last comment - 16:18, Friday 02 December 2016(32124)
Operator Lock Summary

Lock# 8
Times are in: GPS (UTC)
Start time: 1164672438.0  (Dec 2 00:07:01 UTC)
  Itbit Engage: [0, 1164672969.0, 1164673578.0, 1164674812.0, 1164700372.0, 1164745711.0]
  Itbit Disengage: [0, 1164673508.0, 1164674325.0, 1164700288.0, 1164745010.0, 1164747085.0]
End time: 1164747085.0  (Dec 2 20:51:02 UTC)
Total length: 74647.0 , 20hr 44min 7sec
Total Science: 72774.0 , 20hr 12min 54sec


Lock# 9
Times are in: GPS (UTC)
Start time: 1164750245.0  (Dec 2 21:43:48 UTC)
  Itbit Engage: [0, 1164750308.0, 1164756280.0, 1164756461.0, 1164757097.0]
  Itbit Disengage: [0, 1164756100.0, 1164756401.0, 1164756773.0, 1164758206.0]
End time: 1164758206.0  (Dec 2 23:56:26 UTC)
Total length: 7961.0 , 2hr 12min 41sec
Total Science: 7334.0 , 2hr 2min 14sec



End of Day Summary
Current Status: Unlocked
Total Day Locked: 22hr 56min 48sec [95.6%] (82608/86400)
Total Day Science: 22hr 15min 8sec [92.7%] (80108/86400)


 

This is the first trial of a daily post by the Day shift operator of a summary of the locks for the UTC day. This information is created by (userapps)/sys/h1/scripts/VerbalAlarms/Lock_Logging.py which runs in the background of the VerbalAlarms program. The Lock# was started at the begining of O2 and is used only as a reference, it is only used in the control room. The idea behind these daily posts is that it will give the CR something to reference. The lock clock that is displayed in the CR will soon show the current Lock# to match these.

Any question, please let me know. Hopefully its helpful!

Comments related to this report
thomas.shaffer@LIGO.ORG - 16:18, Friday 02 December 2016 (32126)OpsInfo

I forgot to tag OpsInfo

Displaying report 1-1 of 1.