Jenne D. Thomas V.

After Robert finished his PEM injections, we wanted to try to change the pointing into the interferometer after IMC using the IM1 and IM3 to put IM4 Trans QPD back to the pre-EQ location, this seemed to help the range a bit as well as increase the power recycling gain.

Since we were convinced the pointing was satisfactory, we began to try to optimize the spot locations using the reverse A2L procedure using the June 18th data as a good reference.  However, this really screwed up the sensitivity so we're leaving the SOFT loop offsets back at zero.

So in the end, there's a bit of change to the input pointing, spot positions remain unchanged, A2L gains remain unchanged.

TITLE: 07/15 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Calibration
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    Wind: 5mph Gusts, 3mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY:

• H1 locked and made it to NLN without removing OMC whitening
• Robert to EY for injections
• currently Jenne and ThomasV moving beam spots

TITLE: 07/14 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1:  CALIBRATION ("PEM Injections")
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY:

Violin Modes rung up while locking up!  Please watch Violin Modes to confirm Guaridan settings are OK (watch them around the VIOLIN_MODE_DAMPING_1 steps).
LOG:

• 20:17-21:02 OBSERVING
  • OMC_LOCK NO LONGER MANAGED  (to fix this, can:  "z write H1:GRD-OMC_LOCK_MANAGER ISC_LOCK")
  • Knocked out due to "Loading" a Safe.snap file to look at.  
  • Since we were out, I made OMC_LOCK re-managed by ISC_LOCK.
• 21:06-22:37 OBSERVING
• 22:37 Out of OBSERVING for coordinated L1/H1 PEM Injection work (Obs Mode:  CALIBRATION).
  • 22:47 Had a lockloss while Robert was doing ETMy ERM adjustments
  • Relocking now & looks like violin modes look OK.
  • Robert/Anamaria plan to have 1-2hrs of detector time.

Since there are no tasks on deck for H1, going to take this opportunity to get some multiple-coincidence data (w/ L1 & V1). 

There were some SDF Diffs:

• SUSITMy:  Related to MODE9 (this is due to violin mode damping), ACCEPTED
• ASCIMC:  Related to PZTs (this is due to IMC this morning), ACCEPTED

Guardian Note: 

Since OMC_LOCK was needed to go to MANUAL to REMOVE_WHITENING,

I made two BruCo scans, the first from before the Montana EQ at:

https://ldas-jobs.ligo-wa.caltech.edu/~brian.oreilly/bruco_1183356018/

the second from July 14th 0300 UTC at:

https://ldas-jobs.ligo-wa.caltech.edu/~brian.oreilly/bruco_1184036418/

Attached are the trends of the Oplevs (FAMIS #4736).

Do not see any pressing issues to worry about.

During current lock:

• Many OMC DCPD Saturation Verbal Alarms
• DARM Spectra clearly showed rung up violins

Jenne had me quickly maintain lock by:

• Going to OMC_LOCK node
• Go to MANUAL
• Select REMOVE_WHITENING state & wait for it to complete
• Select READY_FOR_HANDOFF
• Go back to AUTO  Edit:  Go to Manual (& Manager: will list this node as being managed by YOU, "User", etc.  You will want to change this to ISC_LOCK at some point*)

This calmed things down.  Then moved on to Violin Modes.

ETMx MODE4 (505.805Hz) was once again the largest rung up violin mode.  Have stayed with positive gain, and played with increasing it & also fiddling with phase, but not having luck with that yet.

* See Sticky Note for how to change the Manager Flag from "User" to "ISC_LOCK".

Looking at the ALS fiber distribution box:

• The external PD is saturating, needs an ND filter with a factor of 2-4 attenuation.
• The internal PD gain is set at 0dB, but should be 30dB (this also requires adjustments to the lower limit and normalization).

We have 15-20mW into the fiber. With a ~7% splitting ratio (the losses through the AOM are about 3 times higher than specifications would indicate), we will have about 1mW in the SQZ LO fiber output. This is in line with the L1 measurement in alog 28961.

The first plot attached shows 24 hours of Corner3 and other CPS In1s along with Lock state signals.

The two large spikes in the first half of the trend shows saturating spikes on the Corner 3 CPS and concurrently the BS Watchdog tripping.  These glitches only show on C3 and are on all four C# CPSs.  Not shown are earlier locklosses and BS Trips that JimW in aLog 37499 attributed to Corner3 glitching.

First action Jim performed was power cycling the satellite racks at the chamber.  Jim did this by unplugging the rack power cord.

After the first LL on this log's plot, Jim un- and re-seated the gauge boards in the satellite racks.

After the second LL at ~1740pdt, I power cycled the C3 interface chassis and reseated and tightened the power cord of the chassis.

There is a final lockloss on this plot around 6am pdt but there is no to little spiking of the CPS channels and certainly nothing of the WD tripping saturations seen earlier.

So, the 6am lockloss was not the CPS but only time will tell if things are completely cleared up.

I still plan to look closer at the glitching and locklosses here so there may be more.

Attached are 3 day trends of the laser head flow rates in the PSL HPO.  So far everything looks to be holding steady; the jagged-looking nature of the signals at the beginning of the trends is the tail end of the flow rate tests performed by Peter and Jeff on Tuesday.  Will continue to keep an eye on these flows.

TITLE: 07/14 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Earthquake
OUTGOING OPERATOR: Travis
CURRENT ENVIRONMENT:
    Wind: 4mph Gusts, 2mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.07 μm/s

Quiet at the moment with small useism & low winds.
QUICK SUMMARY:

Richard and Travis were troubleshooting IMC when I walked in.  Richard asked me to run the DOWN state (Guardian was in the INITIAL_ALIGNMENT state), and this locked up the IMC.  Will start an initial alignment from scratch now.

Note:  OBSERVATORY MODE is in the EARTHQUAKE state.  It was taken to OBSERVING last night.

TITLE: 07/14 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Earthquake
INCOMING OPERATOR: Corey
SHIFT SUMMARY:  After the lockloss (still not convinced it was due to the EQ), I started an IA since the AS spot looked iffy and DRMI was not locking.  When I got to Input_align, the IMC lost lock and would not relock.  I followed the procedure in the troubleshooting wiki and recovered flashing in the IMC, but it still would not lock.  I started looking around at the MC SUS screen and found a channel that had a huge value coming into it.  Thinking it might be electronics, I called in Richard to have a look.  At the moment, he is still poking through MEDM screens to try to find the source of the signal. 
LOG:  See previous aLogs.

Still drilling into the fine print but this still holds although there may be more details to uncover.

After this glitch, I power cycled the sensor chassis in the CER--this did not include the T240s.  After doing so I noticed the power cable to the Corner3 chassis was not screwed in and the cable was somewhat tight and the connector did not seem square/fully seated.  I pulled a bit of slack in, seated and screwed down the connector--we'll see...

As was alluded to earlier by Corey, it looks like the CPSs on BSC2 started glitching this morning and caused the ISI to trip, breaking several locks. Attached plot shows several hours around the locklosses this morning. The windows where the ST1 WD was at state 4 are when the WD tripped. The long fuzzy period on the left of the CPS plots are the earthquake this morning, only ST1 H3 & V3. It looks like the CPS started glitching some time after the earthquake. I went out, pulled and reconnected the power on the satellite racks on the chamber. I've had a striptool running of the CPS since power-cycling and it looks like the glitching has stopped. Given the glitches start before getting bad enough to trip the ISI, maybe we can come up with some of diagnosing before this becomes a problem, so we at least know what we have to fix. I don't know what that would be though. We could at least get longer trends (an hour or two) of CPS if a "mysterious" ISI trip is suspected of causing a lock loss.

WP 7075

To further proceed with the 72 MHz WFS (Wave Front Sensor)s (37042), today I made the hardware changes (mostly cabling), as summarized below, while the interferometer was in a violin-mode-damping state.

I am going to leave the hardware configuration as it is. If this new setup doesn't cause extra noise in the interferometer, they will stay semi-permanently.

Here is a summary of the new configuration:

• We have the 118 MHz RF modulation signal applied to the EOM with the full RF power (+33dBm@PSL rack).
• And we have the 72 MHz RF local oscillator signal sent to the HAM6 area, providing the 72 MHz WFS signals.

[The modifications]

• I plugged the new 72 MHz RF source to the unused RF Heliax cable so that the signal is sent from the CER to the ISC R3 rack (by HAM6).
  • Additionally, I newly installed a balun at the HAM6 side which was missing for some reason.
• At the ISC R3 rack, I routed the 72 MHz to the distribution amplifier which had been used for the 90 MHz demodulators.
  • In this configuration, the distribution amplifier feeds the WFS demodulators which had been also used for the 90 MHz but now with the 72 MHz signal.
• At the ISC R3 rack, the 90 MHz RF cable was rerouted so that it directly feeds the demodulator for ASAIR_B_RF90.
• I adjusted the RF power level by inserting appropriate RF attenuaters while looking at the EPICS readouts from the distribution amplifier and WFS demodulators.
• In the LSC, I changed the FM8s for LSC_ASAIR_B_RF90_(I|Q) from +3 dB to -1 dB in order to keep the same level of signals. See the attached screenshots for the changes that I made.
  • Also, I have changed the digital demodulation phase of ASAIR_B_RF90 such that the signal is maximized in I when the interferometer was locked at 30 W.

Last entry from Roam position 7, see 37334.

At Roam8, a meter or so further +X from Roam7, the spectra would suggest this location is not as quiet (wind response tilting) as Roam7.  However, this wind is from the NNW rather than our usual S or SW for previous views.  Also, while the Y dof seems more tilty for STS2-C (HAM5), at the lowest frequencies, HAM5 seems less tilty below 100mHz for the X dof.  I'm not sure if this conclusion is valid when the sensor is noisier during the quiet period???

Attached are the usual wind plot and sensor spectra.  The quiet wind time is 11 July 1200utc and the windy time begins 0230utc on 11 July.

J. Kissel

Just posting an update on this -- the H1 PCAL Y RX PD reported displacement continues to decay, likely due to some temperature dependent clipping. This had been a part of the FRS Ticket 8328, but there's little we can do during an observation run to fix this. We've since closed the issue as LONGTERMFIX. AS such, I'll raise to an integration issue, and mark as WHEN VENT (similar to the promised work in Integration Issue 4700).

For now, recall that we've switched over to using TXPD as the calibration reference (see LHO aLOG 37166).