It seems like the laser shut down at around 11 pm local time friday night after being on for about 14 hours.  Attached is a screenshot of the laser medm screen as it look now, and some trends, the first is 4 seconds around the time it shut down (2016-05-07 4:46:56 UTC). Of the channels I looked at the HPO watchdog (PSL-OSC_PWRDOGON?) and the LRA seem to be the first to go. The third screenshot shows the power outputs over the 14 hours the laser was on, along with the humidity trend.  The humitidty looked alarming at first, but the last attachment shows a 10 day trend where the humidity seems to fluctuate this much and more.

Delivery already ordered for Tues. (CP7 and CP8) 

Filament is off

Kyle, Chandra

We plan to initially install this unit on CP4's exhaust with CDS power and signal read back so as to accumulate data from a typical "representative" 80K pump.  After which, we would then install it on CP3's exhaust and use it as part of a low-tech control loop to keep CP3's LN2 level within an acceptable range without the need to manually overfill it every few days.  Recall that one of the LN2 level transducer sensing lines (at lowest point of pump's LN2 reservoir) used to determine CP3's LN2 level became clogged in Dec. 2015 rendering the normal CDS PID control loop non-functioning and requiring manually filling the pump every 72 hours.  

Today we just wanted to install it temporarily to verify that the resulting back pressure was as advertised by the manufacturer.  The "before" exhaust pressure was nominally 1.0 psig and the "after installation" value increased 0.1 psig to 1.1 psig - this is as advertised.  After a few hours however it looks like it causes periodic "spikes" in the exhaust pressure.  Since the exhaust pressure is one of the two differential values used to determine the 80K pumps level, we also see these spikes in the pump level (see attached).  I later removed the unit and restored the piping to as found.   

~1330 hrs. local? - not sure, some time after lunch

Opened exhaust check valve bypass, opened LLCV bypass 1/2 turn ccw, LN2 at exhaust in 55 seconds -> Restored valves to as found -> Next overfill to be Monday, May 9th.

I ran a script to let PSL roration stage go back and forth 100 times between 0 and 3 Watts. The result of measured power vs. requested power is ~2% uncertainty. The ISS first loop wasn't locked at the time of the measurement. Repeating the test by letting the rotation stage go between 0, mid power (~30 W), and max power (~56W) yielded similiar result. We could expect even a better performance when ISS is locked.

Repeated the same test for CO2X and CO2Y rotation stages. Later realized that the laser weren't locked due to today's Guardian computer restart. CO2X RS yielded .3% uncertainty and CO2Y RS yielded 3% uncertainty. I'm not sure if our powermeters are a thermopiles. I would disregard this number if they are.

In trying to figure out what's happening with the power stabilisation, I looked at the "dark" noise
of the power stabilisation photodiodes.  pda-dark1.png shows the measured "dark" noise for both the
AC and DC output of the photodiode.  Both are the same.  I suspect that both photodiodes are damaged.

    The ISS will lock but is very temperamental and depends on the set point (reference level).  When
running the diffraction level should be between 12-14%.  There is a problem with the reported DC output
and that measured at the photodiode.  Often they do not agree.  For example the MEDM screen will report
that the DC output is ~11V but measured at the photodiode it is ~7V.  Whilst the reason might be related
to how the DC value is calculated from the AC value of the photodiode, it still is not consistent with
the measured value.

Morning Meeting

- It's Friday. Don't do anything goofy.

- More PSL tweaking today.

- Avoid end station (SEI)

- Shutdown HAM6 pump today (VAC)

- IM measurement continue

- RS measurement continue

#################################3

Activities. All time in UTC:

15:11 Carlos/Jeff B. going to PSL (conputer boot)

15:41 Jeff B. out, Carlos still in with Peter.

16:04 Jason joining Peter in the PSL

16:11 Kyle to HAM4-5

16:26 Carlos out

16:30 Kristaina and Karen to LVEA.

16:50 Joe to LVEA retrieve some equipment

17:01 Fil to CER to fire up UPS.

17:03 Joe out.

17:40 Kyle to EY. NOT into the VEA. He'll be turning on the light and look for quipment.

18:04 Kyle out

18:43 Jason and Peter out for lunch.

19:10 Kyle putting a fan near RCG (HAM4-5)

19:16 Kyle out

20:13 Jeff K. to LVEA

20:22 Jeff K and Evan G going to EY near chamber. I ramped off BRS. Jeff will also be turning off high voltage supple. Make sure he turn it back on.

20:27 Kyle to vertex RGA to plug "stuff" in.

20:50 Jeff B. to rack near PSL.

21:01 Peter done for the day

21:57 Bryn and David to LVEA to take some pictures.

21:58 Evan to ISCT1 working on POPX.

22:18 Bryn out

22:30 Kyle to MidY to do CP3 overflow and get rid of CP2 alarm.

22:35 Jeff B to cleaning area

22:39 Jeff B. out

22:53 Kyle back from Mid Y. Now going to vertex RGC.

23:01 Jeff K back from end station, putting tuff in the LVEA

Jeff K, Evan G

We (finally!) measured the ESD driver quadrant control voltage path transfer functions, which was needed because of the change made on Feb 9 (see ECR E1500341 and LHO aLOG 25468) for calibration/compensation use. Measurements are stored under 

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER9/H1/Measurements/Electronics/2016-05-06

Measurement notes attached. Analysis to come...

CP4 was sending out a yellow alarm on CP4 so I looked more closely and noticed one of the temp sensors (from heat tape) is reading bogus value. Attached is trend. It started yesterday in the morning. 

Re-initalized HWSX matlab files.

Included is the RPN image from the injection locked HPO for comparison. The 10Hz comb feature that was present in the Freq scan from Apr 29th is gone. The pointing seems to be slightly out of spec and I believe tha modescan looks relatively ok.

PSL might need another tweak after HPO work is done. I noticed maximum power changed day-to-day basis.

model restarts logged for Thu 05/May/2016 ISC and SUS-PI model work, h1tw0 rebuild, some unexpected fw restarts
2016_05_05 11:48 h1iscex
2016_05_05 11:50 h1iscey
2016_05_05 12:00 h1omc
2016_05_05 12:00 h1omcpi
2016_05_05 12:02 h1pemex
2016_05_05 12:02 h1susetmxpi
2016_05_05 12:06 h1broadcast0
2016_05_05 12:06 h1dc0
2016_05_05 12:06 h1fw0
2016_05_05 12:06 h1fw1
2016_05_05 12:06 h1nds0
2016_05_05 12:06 h1nds1
2016_05_05 12:06 h1tw1
2016_05_05 12:56 h1pemex
2016_05_05 12:57 h1broadcast0
2016_05_05 12:57 h1dc0
2016_05_05 12:57 h1fw0
2016_05_05 12:57 h1fw1
2016_05_05 12:57 h1nds0
2016_05_05 12:57 h1nds1
2016_05_05 12:57 h1tw1
2016_05_05 14:52 h1broadcast0
2016_05_05 14:52 h1dc0
2016_05_05 14:52 h1fw0
2016_05_05 14:52 h1fw1
2016_05_05 14:52 h1nds0
2016_05_05 14:52 h1nds1
2016_05_05 14:52 h1susetmxpi
2016_05_05 14:52 h1tw1
2016_05_05 15:06 h1fw0
2016_05_05 15:13 h1fw0
2016_05_05 15:23 h1fw0
2016_05_05 16:35 h1tw0
2016_05_05 17:06 h1tw0

model restarts logged for Wed 04/May/2016 No restarts reported

model restarts logged for Tue 03/May/2016 ALL SYSTEMS RESTARTED. RCG upgrade to 3.0.2. Front end and DAQ upgrade.

model restarts logged for Mon 02/May/2016 No restarts reported

model restarts logged for Sun 01/May/2016 No restarts reported

model restarts logged for Sat 30/Apr/2016 fw1 instability
2016_04_30 04:33 h1fw1
2016_04_30 06:24 h1fw1
2016_04_30 09:03 h1fw1
2016_04_30 11:26 h1fw1
2016_04_30 19:14 h1fw1
2016_04_30 19:44 h1fw1
2016_04_30 21:03 h1fw1
2016_04_30 21:53 h1fw1

model restarts logged for Fri 29/Apr/2016 No restarted reported

model restarts logged for Thu 28/Apr/2016 hw1 and nds1 instability
2016_04_28 00:34 h1fw1
2016_04_28 04:34 h1fw1
2016_04_28 04:54 h1fw1
2016_04_28 05:12 h1fw1
2016_04_28 06:05 h1fw1
2016_04_28 07:13 h1fw1
2016_04_28 07:43 h1fw1
2016_04_28 07:56 h1fw1
2016_04_28 08:02 h1fw1
2016_04_28 08:34 h1fw1
2016_04_28 08:54 h1fw1
2016_04_28 16:28 h1nds1
2016_04_28 16:29 h1nds1
2016_04_28 16:30 h1nds1

model restarts logged for Wed 27/Apr/2016 fw0+1 unstable. OMC and SUS PI IPC model work
2016_04_27 08:33 h1fw1
2016_04_27 09:53 h1fw1
2016_04_27 11:13 h1fw1
2016_04_27 11:30 h1fw1
2016_04_27 11:59 h1omcpi
2016_04_27 12:01 h1dc0
2016_04_27 12:01 h1susitmpi
2016_04_27 12:03 h1broadcast0
2016_04_27 12:03 h1fw0
2016_04_27 12:03 h1fw1
2016_04_27 12:03 h1nds0
2016_04_27 12:03 h1nds1
2016_04_27 12:03 h1tw1
2016_04_27 13:06 h1fw0
2016_04_27 14:33 h1fw0
2016_04_27 17:54 h1fw1
2016_04_27 20:33 h1fw1

I just pushed a minor upgrade to guardian to fix a small issue with the guardlog client when following node logs.  The new version is r1542.

The client was overly buffering stream data from the server, which was causing data from the stream to not be output in a timely manner.  This issue should be fixed in the version I just pushed.

As always make sure you have a fresh session to get the new version:

jameson.rollins@operator1:~ 0$ which guardlog
/ligo/apps/linux-x86_64/guardian-1542/bin/guardlog
jameson.rollins@operator1:~ 0$ 

Jim rebooted h1guardian0 at 10:53 local. I was hoping this would help with the logging issues that we have had here alog26965. But no luck.