In the past couple of days, somewhat more than the usual amount of water required to top off the chiller has been added.
This morning I added ~200 ml.  Yesterday JeffB added a similar amount.

    I took a look under where the air trap was installed last week and sure enough there are some drops hanging onto
the pipes and a wet spot on the floor underneath.

Owing to the much warmer weather and ongoing 3 IFO work at the mid stations, I have restarted the chillers at both buildings. Temperature set points are at 74 degrees [F] for both.

J. Kissel

Measurements were driven and the data was recorded successfully, but the log files that are written during the measurement to record what was driven when for offline later analysis were corrupted this time around because of some sort of missing SIStrLog /broken function and/or file access issue. I've got emails out to Dave Barker, T. Shaffer, and S. Aston in hopes that this code (written years ago over months by transient guest stars B. Sorazu, B. Barr, and L. Prokorov) can be fixed.

Will try again tomorrow after some expert help debugging (or, rather, after Fil gets finished pulling cables for this new... vacuum gauge thing? I dunno, didn't see an aLOG. Maybe comes as a consequence of the new ESD driver power supplies that were replaced while I was out, and coincidentally while I was out).

J. Kissel

Now the that LVEA temperature is stable and normal, I've gathered transfer functions will all the "nominal" O2 offsets in place:
   - Reaction Chain has +150000 V, -5000 P of drive from the test bank, originally installed to alleviate suspected rubbing during our cold January
   - Main chain has normal*** P and Y alignment offsets in place. 

*** Although the main chain offsets have been used to align the optic to its optical lever reference position prior to the vent, and we suspect that optical lever is a bad reference more on this in a future comment below. However, with this restoration, we're now using up ~85% of the DAC range on the F1 OSEM (where we had been using 35%).

With these offsets in place, preliminary results (i.e. from eyeballing the DTT sessions) show no signs of rubbing. 

The data lives here:
/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGM0/Data/
    2017-05-22_2056_H1SUSITMX_M0_WhiteNoise_L_0p01to50Hz.xml
    2017-05-22_2056_H1SUSITMX_M0_WhiteNoise_P_0p01to50Hz.xml
    2017-05-22_2056_H1SUSITMX_M0_WhiteNoise_R_0p01to50Hz.xml
    2017-05-22_2056_H1SUSITMX_M0_WhiteNoise_T_0p01to50Hz.xml
    2017-05-22_2056_H1SUSITMX_M0_WhiteNoise_V_0p01to50Hz.xml
    2017-05-22_2056_H1SUSITMX_M0_WhiteNoise_Y_0p01to50Hz.xml
/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGR0/Data/
    2017-05-23_0047_H1SUSITMX_R0_WhiteNoise_L_0p01to50Hz.xml
    2017-05-23_0047_H1SUSITMX_R0_WhiteNoise_P_0p01to50Hz.xml
    2017-05-23_0047_H1SUSITMX_R0_WhiteNoise_R_0p01to50Hz.xml
    2017-05-23_0047_H1SUSITMX_R0_WhiteNoise_T_0p01to50Hz.xml
    2017-05-23_0047_H1SUSITMX_R0_WhiteNoise_V_0p01to50Hz.xml
    2017-05-23_0047_H1SUSITMX_R0_WhiteNoise_Y_0p01to50Hz.xml

We should consider these offsets a "worst case scenario." I suspect once we get all optics re-aligned to form some sort of Michelson in the corner and/or we open to the arms that we'll find that the optical lever reference was indeed wrong, and we'll end up removing most of the main chain offsets. Plus, I think we now might be able to run with out any reaction chain offsets. Stay tuned for full matlab assessment using the exported data.

This morning Jenne brought the the ITMX suspension back to good values, according to the oplev, so that we could try a to search for a HWSX return beam. I followed Aidan's instructions and did the search  just as before:

1. Check that the SLED is ON and the irises are open.
2. Swap the fiber for HWSX back into h1hwsmsr and then start the streaming code in a tmux session.
3. Start two excitations on SR3:
   1. H1:SUS-SR3_M1_TEST_P_EXC, amp=1200, freq=0.01Hz
   2. H1:SUS-SR3_M1_TEST_Y_EXC, amp=1200, freq=0.0085025Hz

I ran the measurement from 22:03-23:30 UTC (+/- a few minutes) before I thought it was easy enough to confirm that there was still nothing showing up, and then handed the ITM back to Jeff to complete his measurements. With more time all of the gaps could have been filled, but this does not show any higher intensity points unlike previous tests (alog36179).

After talking with Aidan, he thinks that ITMX is still not within an acceptable aligned range, and the upper periscope mirror may be misaligned. If there is more time later this week we can try again with the amplitude doubled, increasing the search area, but just waiting for the green beam and his arrival might be best.

Note to myself: I left the HWSX fiber in h1hwsmsr

Though I did valve-in the Vertex RGA this morning I took no additional steps listed on WP #6644 as no one is now calling for the premature opening of GV5 and GV7.  As such, we will continue to let the Vertex+YBM+XBM "dry out" on the turbo pumps until further notice.

Per request from Jeff K. I have raised the temperature at EX by 2 degrees F. from 64 to 66 degrees.

This afternoon while looking into some temperature issues at EY, I found a large puddle of glycol  on the roof of the air handler room near the make up tank and on the floor. I traced this back to a PRV that has failed open. The PRV is on the non potable water line which is tied into the glycol return line from the chillers. 
This appears to be some type of auto fill system that was not used and probably has never worked. Not even sure why it was tied into this system.
Anyway, I valved the PRV off and refilled the glycol lines back to normal operating pressure,~30 psi. 
At this point, I do not intend to replace the PRV because we will not use that system for auto fill.

[Vaishali, Jenne]

We went again to have a look at the IMC trans path on IOT2L, and we think that the main beam is just not coming out of the vacuum.

Kiwamu pointed us to alog 17310 from March 2015, where he notes that something happened in vacuum and the IMC trans beam went from somewhat clipped but still somewhat normal looking to totally abnormal looking (which we've had consistently for the last 2 years).  Vaishali is currently looking into Cheryl's IMC spot measurements to see if the beam spot motion is consistent with the beam moving closer to a position where the trans beam is clipped on the IM1 suspension cage.

We still have the ghost beam on the trans camera, but no beam bright enough (by a factor of ~100, as measured by the PD) to be the main beam.

This is my final Ops Summary alog.

Activities: 

16:16 Carlos -> EY

16:57 Corey to squeezer bay and open roll up door

17:33 Corey out

17:59 Kiwamu to optics lab looking for AM laser

19:20 Richard -> roof

19:33 Richard back

19:36 Fil -> EY

19:49 Kiwamu starting measurement

19:55 Jeff measuring ITMX TF (subbing test)
20:47 Jeff B. to end stations

          Kiwamu out

21:22 Jeff B. back

21:43 LVEA transitioned to LASER HAZARD

          TJ(HWS table)+Jenne+Vaishali (IOT2L) -> LVEA

21:53 TJ out

22:02 TJ starting SR3 excitation (HWS measurement)

22:13 Carlos to EX

          Jenne+Vaishali out

22:36 Carlos back

22:47 PEP-> EY (line hunting)

22:51 Dave -> MY

Added 250ml water to Crystal Chiller to silence low water alarm.  

Reference alog: 6294

FRS8170

Jonathan, Dave

The DAQ was restarted at 19:06 Thursday 5/18 UTC (for vacuum controls IP6 work). If an NDS1 request for second trend data for certain channels is sent which spans the restart time, then the data preceding the restart is correct, but post data is bogus. In the case of H0:VAC-EY_Y3_410_PIRANI_INTLK, data at the tail end of the 19:00-19:10 second trend file is a static 2.2, and from 19:10 onwards is a noisy 2.2

We conclude that only the second trend frame from 19:00-19:10 is suspect. Both framewriters wrote the same frame, both nds servers show the same issues if spanning this frame. Investigation continues. I've saved the frame and its md5 file under h1nds1 control's homedirectory (dave subdirectory).

-rw-r--r--  1 controls controls 434M May 22 11:27 H-H1_T-1179169200-600.gwf
-rw-r--r--  1 controls controls   33 May 22 11:27 H-H1_T-1179169200-600.md5

Starting CP3 fill. TC A error. TC B error. Fill aborted.
Starting CP4 fill. LLCV enabled. LLCV set to manual control. LLCV set to 70% open. Fill completed in 2620 seconds. TC B did not register fill. LLCV set back to 36.0% open.

Kyle 

(Tasks part of WP #6644)

~1015 hrs local -> I valved-in the Vertex RGA to the combined vacuum volumes of the Vertex+YBM+XBM while these volumes were being pumped by their respective turbo pumps.  PT120's response is attached (1 hour of second data).  "From my head" 10-9 torr/10-5 L = 10-4 torr/L of gas accumulated in the unpumped ~5L RGA volume in 14 days?  So, no significant air leaks in the RGA joints.

~1045 hrs. local -> I energized the Vertex RGA filament (note: I am confused with the Pfeiffer software's naming of my connect/scan session with the included phrase "Airdemo..".  The other versions of this software don't do this and I makes me question as to whether I am actually connected to the Vertex RGA (h0rgacs) or am I connected to their "Simulator" or virtual RGA in this connect/scan session?