1. I can't use the stand up desk because OPSWS12 won't bring up dataviewer and moving screens is so delayed that I can't put them where I want them
2. on ther OPS workstation, dtt has an error I've neer seen before, I've manually set the range for the X axis on two plots and get different actual range on the coherance plot
   1. the top plot starts at 121 and ends at 700 as I've requested
   2. the bottom plot starts below 121, and ends at what looks like 760, when I asked for 121 to 700

I had to set the bottom plot to "transfer function" and back to coherance to get the X axis to start at 121 and end at 700

Restarted the laser a few minutes ago.  No configuration changes per se.  This time the crystal chiller was
explicitly power cycled, ie turned off and then back on again.

    Next attempt will include installation of the "electronic" flow sensor unless something more obvious
comes to the fore.

OverallView.png is the top level signals related to the cooling system.  Clearly there is an oscillation with the flow in the
power meter circuit that is not apparent in the front end cooling circuit.

PowerMeterCircuitFlow.png shows the laser output and the flow in the power meter circuit.

Flows.png shows the flows in the power meter circuit and the front end circuit.

CrystalChillerFlow.png shows the flow in the power meter circuit and the flow from the crystal chiller.

    Unfortunately the laser was being restarted when I got in, so I cannot tell if the error condition on the Beckhoff terminal
that reads the flow rate was latched or not.  In this particular case it appears that the problem lay with the flow rate in the
power meter circuit and not the chiller, at least at first glance.

    At this point the prime candidate for installation of the "electronic" flow sensor would be in the power meter cooling
circuit.

Kiwamu is heading out, and so am I.

Passed Kiwamu on route 10 and turned around. Kiwamu has reset the laser.

It appears that the PSL may have tripped after the last lock loss. The NPRO output power is 0.

Start of shift: Sitting at DRMI_LOCKED. SRC1 Pitch and Yaw are not converging. EX constantly saturating. Diag message that PSL_ISS diffracted power is high (around 9%).
23:56 UTC H1IOPASC0 has its TIM bit red. Diag Reset cleared it.
00:01 UTC Cleared history for H1ASC-SRC1_P filter to see if it would help SRC1 Pitch converge. It did not.
00:06 UTC Stepped to DRMI_ASC_OFFLOAD. SRC1 Pitch and Yaw converged. EX still saturating.
00:09 UTC Stepped to PREP_TR_CARM. EX still saturating. ISS second loop is on.
00:13 UTC Stepped to CARM_ON_TR. EX still saturating.
00:14 UTC Stepped to REDUCE_CARM_OFFSET. EX still saturating.
00:15 UTC Stepped to SWITCH_TO_QPDS. EX still saturating. AS Air looks unstable.
00:17 UTC Stepped to RF_DARM. EX no longer saturating.
00:24 UTC Stepped to DHARD_WFS.
00:27 UTC Stepped to REDUCE_CARM_OFFSET more.
00:30 UTC Stepped to CARM_15PM. PRC2 YAW error signal stepped up.
00:34 UTC Stepped to CARM_10PM. PRC2 YAW error signal stepped up.
00:38 UTC Stepped to CARM_5PM. Almost immediately lost lock.
00:40 UTC Starting initial alignment.
00:47 UTC Video 5 images frozen. Power cycled.

Trouble locking Y arm on green. Loses lock when WFS engage. Set to LOCKED_NO_SLOW_NO_WFS and it remains fairly stable around .5. Brought Y arm to around 0.8 by adjusting ETMY, TMSY and ITMY at LOCKED_NO_SLOW_NO_WFS. Cleared WFS history. Lost the lock on Y. Put ITMY and TMSY back to original values. This time able to lock just by adjusting ETMY. It remained locked and the power increased when I changed the state back to INITIAL_ALIGNMENT.

02:16 UTC Video 4 striptool jittery. Power cycled.
02:31 UTC Initial alignment done.
02:57 UTC Stopping at CARM_10PM to try and diagnose.
03:12 UTC Lost lock sitting at CARM_10PM some time after setting the following in guardian by hand:
ezca.switch('LSC-REFLBIAS', 'FM2', 'ON')
ezca['LSC-TR_CARM_TRAMP'] = 5
ezca['LSC-PD_DOF_MTRX_TRAMP'] = 5

03:23 UTC Back to CARM_10PM. Will wait to see how stable this is.

Something happened early in the morning today (about 2016-10-08 12:50 UTC +- 10 min) and the transmission is only 78W as of now while the reflection is 38W or so.

State of H1: no locking beyond DRMI, breaking lock at CARM_5PM

Assistance: Peter King

Details:

• H1 can reach DRMI, but cannot make it through CARM_5PM
• ISS Inner Loop has been ocillating at random times during locks, and toggling the AUTO servo has helped get it back
• FSS on lockloss has gone into oscillation almost every lock
• Peter was helpful in showing me how to turn the ISS Second Loop OFF during locking
• However, the ISS Second Loop is turned on in DRMI_LOCKED
• I tried getting past CARM_5PM without the ISS Second Loop on, but that didn't work

Diagnostics:

• I tried to run the lockloss tool, but it's giving me an error and not showing anything after 10/8, 00:07UTC - no help
• What I did capture on the StripTool on Video0 is... PRC2_Y rang up and then dove toward 0 in the last minute of lock - picture attached
• Then I looked up that PRC2_Y comes from RF9I, which I believe was worked on yesterday
• Having just found this, and assuming settings were changed on RF9, the next step is to set RF9 back to Thursday's settings and attempt lock

A scan of coherences during last night's lock can be found here:

https://ldas-jobs.ligo.caltech.edu/~gabriele.vajente/bruco_1159948817/

Nothing new:

• The low frequency seems dominated by ASC-CHARD_P
• MICH/SRCL/PRCL are still very high
• Jitter is still visible in the IMC WFS signals
• It looks like the diagnostic breadboard signals are not transfered to the frames in the local cluster, so they are not included in the scan

Additional BruCo scans are available for the PRCL and SRCL error signals:

https://ldas-jobs.ligo.caltech.edu/~gabriele.vajente/bruco_prcl_1159948817/

https://ldas-jobs.ligo.caltech.edu/~gabriele.vajente/bruco_srcl_1159948817/