H1's issue can clearly be seen in:

• ASC CONTROL's:  H1:ASC-CSOFT_P_OUTPUT
• ASC ERROR's:  H1:ASC-MICH_P_INMON
• On most of the LSC signals on the PRMIsb striptools as well
• DARM Spectra from 10-100Hz.

snapshot of ASC striptools are attached.

TITLE: 06/20 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 52Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
    Wind: 6mph Gusts, 5mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY:

ASC Pit Control & Error signals are huge & this is resulting in broadband noise on DARM from 10-100Hz & obviously resulting in a low range.  I will start investigating further while we are still locked.  The ITMx & ETMx oplevs have been at/beyond their limits in pit & yaw, but they've been like that for atleast a week.

Shift Summary: After the IFO relocked, ran A2L check script. Pitch is a bit rung up, since we are in commissioning mode decided to run the repair script to make things better.  

LLO called about a GRB alert. LHO did not receive notice from Verbal Alarms. In one hour hold.

Around 06:00 (23:00) the ASC Pitch Control and Error signals started to ring up. Could find no apparent reason. Sheila’s aLOG #35371 talks about this and OpLev damping. ITMX and ETMX OpLevs are off center. However, OpLev damping appears to be off on ITMY and ETMY. Range is suffering.

   LLO called about GRB Alert. In one hour stand-down for the alert. 

   LHO did not receive notice via Verbal Alarms. 

  Back to Observing for about 3 hours. Environmental and seismic conditions are good. Range has been   in the upper 60Mpcs. All monitors are green and clear. 

Today I spent some more time moving POP spot positions as well as soft again.  In the end we have gone back to where we were over the weekend. 

• The first attachment shows that there are some alignments for which we can have lower jitter than the alignment we had over the weekend.  The degradation in sensitivity you see at low frequency is because the A2L was not tuned, and probably also because the SRCL FF might need to be returned for these new alignments. We can move the IFO to the locations where the jitter is better (P= 0.15, Y=0.2 for example) and use the soft offsets to make the recycling gain better (CSOFT +DSOFT Y offsets =0.07 brought the recycling gain back to 28 from about 24).  Returning to these alignments where the jitter coupling had been seen to be better didn't result in a lower noise than over the weekend though- for some reason going back to the same spot on the POP QPD doesn't mean we get the same spectrum.  
• The second attachment shows scatter plots of reycling gains and BLRMS in 3 bands made in the same way as the attachments to alog 36957, but with todays spot move added as well as a BLRMS around our largest jitter peak at 350Hz. You can see again from this plot that things aren't always the same when we return to the same POP A spot locatin, although all this data is taken with our usual soft offsets.  
• We lost lock a couple of times due to what I think is the SRCL FF.  We had an oscillation in SRCL (and the FF path) around 3 to 4 Hz, which does not show up in MICH. 
• It might be possible to move the soft offsets to get better recycling gain at the location where our jitter was good, and redo this scan of POP offsets to see if we can have a better compromise position.  It might not be a good use of time though, especially if we can't rely on the ASC to bring us back to the same spectrum in the future.  
• Things that probably are worth putting some time into:
  • better roll off for DHARD, this noise is worse than CHARD now that we put more agresive filters in CHARD
  • LSC noise- decoupling PRCL from SRCL in the input matrix, turning back on the MICH actuator digitalization, and SRCL FF retuning

At John W.'s request, I took another measurement now that several days have passed since pumping was stopped 

Pumping stopped last week at 14 microns -> Today's "post-pumping" reading was 29 microns (warm day, 92F).

TITLE: 06/19 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Jeff
SHIFT SUMMARY:  locked and then commissioning
LOG:

• 16:15-16:55UTC - Karen in optics lab
• 17:35UTC - commissioning, beam walk, Sheila
• 22:45UTC - end of active active commissioning
• 23:00UTC - end of shift - relocking
• after relocked and in NLN:  EvanG, 15 minutes for hardware injection, WP7046

In the past week we have had two timing alarms:

The first was a short (one minute) alarm from EY GPS (CNS-II). I trended all the EPICS channels on this system and only found that the Dilution of Precision (DOP) and the Receiver mode channels showed any variation at this time (number of satellites locked did not change). Does this mean it is a real or bogus error?

The second was a longer alarm (9 minutes) with the MSR master's GPS receiver (I think the internal one). The only channels in alarm were  "GPS locked", the the MSR comparator channel-01 (MFO GPS). This would suggest a real problem with the Master's GPS receiver?

Time to pass this over to the timing group for further investigation (Daniel, Zsuzsanna, Stefan?)

O2 Update:

• ER 11: graceDB crashed over the weekend, back now
• commissioning on H1, beam walking on ITM, and noise is better (lower)
• commissioning for beam walking will continued

Tuesday Maintenance plans:

• EX beckoff, replace hardware
• Apollo in CER for scaffolding
• line investigation at EX and EY
• fix power supply for EX ISC beckoff module
• GV14 annulus ion pump replacement (MX) - on hold for now
• CBRS (replacement) - IX and IY (LVEA vertex)
• cable pulling into PSL for GigE camera - in PSL
• evaluation of swiss cheese baffle
• RF coupling measurement
• 120MHz measure modulation depth - in PSL, need DRMI or higher
• readback for BRS ion pumps - added to DAC, EY, EX - DAC restart
• 9MHZ RF AM - replace beckhoff module
• oplev - replace EX (glitching) - recenter EX, IX, SR3 - power adjustments EY, IY
• HPO diode test - requires H1 be unlocked (around 30 minutes) - will start first thing in the morning
• inspect HEPI fluid reservoirs - should not effect anything, but might trip HEPI - will do first thing in the morning

Refer back to LHO aLog 36739 to walk back through these reports.  I'll attach the updated map to a comment shortly.

NOTICE--There is a location that may be quieter than ITMY STS2!!

Roam6 is located just west of of BSC4s NE SEI Pier.  So this is certainly now farther from the south wall than ITMY STS2-B as well as any other previous Roam position.  The attached plots show my typical plots comparing quiet time [18 June 1200 utc] to a windy time [16 June at 1800 utc.]  These times are free of EQ activity.

The first plot is just the corner station wind.  The windy time direction is a very steady 90 degrees or right down the Yarm to the CS.

The big news is seen on the X dof plot where the HAM5 roaming seismo is quieter than the ITMY STS2 during the windy period from about 90mHz down by maybe a factor of 2.  Yes, the useism band is generally higher during the windy period.

Bottom line, keep looking while we have a machine functioning with which to look.

While checking on the laser this morning I noticed the diode chiller warning light (on the LASER MEDM screen) turn red briefly, then back to green.  I went to the chiller room and hung out for a few minutes, watching the diode chiller, and sure enough it was intermittently flashing a "Low Water Level" warning (not an alarm, just a warning).  I added 500 mL of water and this behavior quit.

TITLE: 06/19 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 68Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    Wind: 13mph Gusts, 10mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY:

• H1 locked for 3 hours
• windspeed is climbing

TITLE: 06/19 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 68Mpc
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY:

Lock segment of 60+hrs ended during this shift.  Back to observing in 35min.  Have had very steady range hovering at or just under 70Mpc (with minimal glitch drops seen on the Inspiral Range plot).  Had an odd temperature alarm (see earlier alog).
LOG:

• 11:56:04:  Broadband glitch on DARM spectra
• 12:15-12:50 Lockloss (Verbal gave OMC DCPD Saturation).  Lock was 60hrs18min.
• 12:56 PI MODE27 addressed
• 13:41 "Corner Station Temperature is Low" Verbal Alarm (sent an email to TJ).

13:40utc:  Received a "CS temperature is low" Verbal Alarm. 

I checked the FMCS & Dust Monitor temperatures in the LVEA, but I did not see a drop in temperature.  (In fact, the FMCS signals were all trending up at the time.)  I'm wondering if I should be looking at another channel?  Trends of the LVEA FMCS Zone Temps for the last 7days is attached.

Most of the trends are flat on these trends. 

H1:HPI-PUMP_EY_CONTROL_VOUT had a step up from 505 to 515 around May 23rd.

This CLOSES FAMIS #4533.

WP 7031
alog 36571
 

A EL3104 analog input Beckhoff terminal was replaced from EtherCAT End Station Chassis 3. Alog 36571 reported CH3 & CH4 on terminal 7 showing an offset. Used a voltage calibrator to verify offset was from EL3104 terminal and not upstream.