TITLE: 06/23 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 4mph Gusts, 3mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.08 μm/s
QUICK SUMMARY:
GWISTAT has not been listing V1's Observing status (been in "No Data" state for several days); yesterday the V1 operator mentioned they are aware and working on it.
H1's been locked, for almost 2.5hrs, but scanning Verbal Alarms, it said we weren't in Observing. H1 GRDIFO was in the MANAGED state over night, so I took it to AUTOMATIC--this automatically popped H1 back to OBSERVING. All that is understandable, but I guess I'm confused by the Range FOM (attached). A quick glance would tell me H1 was observing since we have the H1 Clean trace (dark red) on the range FOM---maybe I'm not interpreting this correctly.
NEVERMIND!!! Since GRD-IFO was in MANAGED over night, for the quick lockloss which was automatically recovered from, the OBSERVATORY MODE was remained in OBSERVING after that lockloss. I'm assuming the "H1 Clean Range" channel on the range FOM/nuc27 is non-zero when the OBSERVATORY MODE is selected to be in the OBSERVING state.
So:
- 11:02-1436: H1 should NOT be listed as OBSERVING, there was a
- 1102-1214 Lockloss + Locking--which was completely automated AND had NO locklosses & took72min to get to NLN
- 1214-1436 H1 current lock at NLN--where Intention Bit stayed in COMMISSIONING, but Observatory Mode remained in OBSERVING from previous lock.
- 1437: Intention Bit taken to OBSERVING. (Segment plot from Summary page shows Intention Bit in Commissioning for last lock and jumping back to Observing this morning (attachment2), and this last one is showing "Operating Mode" (or OBSERVATORY MODE kept in OBSERVING a few hours over night, attachement3).
