Today we have had some difficulties with alignment in the process of recovering the IFO. 

This morning we moved ETMX by 20 urad in yaw, Patrick checked trends and the top mass osems roughly agree with the alingment sliders that we moved by about 20 urad, while the optical lever indicates that this was moving the test mass back to the position it was in last time we were locking, on August 1st. 

We also saw that even after doing initial alingment twice, the arms atill had a large relative misliagnment which caused a low recycling gain and therefore a lower cam offset than expected while CARM is locked  which cause random locklosses at different points.  Earlier tonight we we seeing a 5% drop in the refl power when the arm transmission was at 5 times the single arm power, while the same arm transmitted power level on August 1st coresponded to only a 1% drop in reflected power.  Koji and Stefan worked on solving this problem, so I will leave it to them to log their solution. 

Today I started a draft of a gaurdain to identify locklosses in which there was significant power build up in the arms, so that a check of the fast shutter should be run.  This is on the medm screens and is running, but there is no shutter check implemented yet.  The idea is that the state of this guardian this will be checked in our watchdog checker, and the ISC_LOCK guardian will require manual intervention to reset the state of this gaurdian before relocking the IFO.  This will be a reminder for the operator to run Stefan's shutter check ploting tool which is accessible from the bottom of the ISC guardian overview before manully resetting the state of this guardian so that you can relock.  Once we have an automated check this can all be automated. 

Since I didn't get a chance to check the arm power thresholds tonight, I will not integrate this into ISC_LOCK, so we are still relying on humans to check that the shutter closed.  This nominally means that if we get the interferometer locked we should set the request of ISC_LOCK to DOWN which will not unlock the interferometer but will preventing it from trying to relock automatically.  Hopefully this will be integrated soon. 

Hope to repeat the success of the Y-end RGA bake at the Vertex using same settings/durations etc...  Maybe can piggyback on the already running pump carts (a.k.a. noise generators) that will continue to be running near HAM5/HAM6 this week?  One more running pump cart should just get buried in the noise - no?  

After decoupling the pumping components used during the recent bake out of the Y-end RGA, I exposed the RGA to the Y-end vacuum volume, energized the filament and let it come into equilibrium for an hour or more.  I then let the RGA scan continuously with the multiplier (SEM) on for an additional hour or so while I gathered up my mess(es).  I periodically checked the scanning as I walked past the screen.  At one point, I noticed that the spectrum was changing rapidly towards the "dirty".  I monitored the scanning and noted that after reaching a temporary maximum, the amus which had increased then returned to near their original values.  

After consulting with the Jeff B. (the operator on shift), I feel that the observed changes in partial pressures were likely the result of IFO locking attempts as they coincide closely in time.  Perhaps something gets hot when the IFO is locked or when mirrors are steered?  

See attached scans 

Using the calibration of alog 28133 (3.0554e+04 cts / Watt from SRM, or 3.273e-05Watt/ct) I added FM10 filters to the segments of ASC-AS_C to cast the output into Watt entering HAM6. I also updated H1:ASC-AS_C_SUM_OFFSET (which avoid astronomic PIT and YAW values).

SDF is updated.

HAM6 Crew, vacuum group and others.

During the vent last week, the glass for the septum viewport was inspected by Betsy W. and she found a rather large smudge, a photo was taken of the glass (see attached) and such photo was circulated among the vacuum group and others.
At first, the intent was to clean the contamination by using first contact, but after careful consideration and following procedure it was determined that, in order for us to clean up the window we would have to vent the other side of the viewport, which would have added more time to the HAM6 incursion.
Betsy checked the beam location at the glass, and the beam is far away from the smudge (the beam is center on the glass), that made the decision somewhat easy to postpone the cleaning of the smudge for the next vent event.

FRS ticket  6053

The attached is just one instance and is fairly representative of the trips.  Most of the time, the ACTuator is called to blame, but as I reported in 29056, I'm not sure the Last Trip is absolutely robust.

The 2 seconds of full data show the ISI in Full Isolation (GRD STATE) when Stefan throws the shutter (FASTSHUTTER A MODE.)  You can see a fraction of a second later, the Actuator MASTER DRIVEs going very large.  All the actuators are contributing to the saturation counting as the threshold is only 32760 counts.  The watch dog trips near the end of the two seconds (WD MON STATE.)  It was going to happen anyway but I can't be sure why the WD tripped because none of the counters (iii SAT COUNT) actually reached the trip threshold.  This is a mystery to me, still.  The SAFE COUNT is 8192, 4096, and 10 for the ACT, GS13, and CPS.  None of the counters reach the SAFE COUNT level....  Regardless, the Actuators where going to reach it so that is another problem to figure out.

Unless the shutter softens its blow on the ISI, the trips are going to happen almost everytime.  For now, we are running with HAM6 in the DAMPED state.  There the HAM6 sees a few saturations on the GS13s when the Shutter triggers but literally just a few.  The HAM6 will be transitioned to ISOLATED by the ISC after the FAST SHUTTER is tested.

Summary
I checked that the sign of the Pcal inverse actuation filters is correct by injecting a known sine wave into the TRANSIENT filter bank and measuring at TRANSIENT_OUT and also the calibrated Tx PD signal, H1:CAL-PCALX_TX_PD_OUT_DQ. The signals are consistent and no minus sign is missing.

Details
To check the sign consistency, I made a 100 Hz sine wave with zero phase in Matlab and saved to an ASCII text file. Then I used awgstream to inject the waveform into H1:CAL-PINJX_TRANSIENT_EXC. I wanted to make sure that the output of H1:CAL-PCALX_TX_PD_OUT_DQ was correctly calibrated (not whitened) so I turned on the [:1,1] filter module, FM7. I then injected the waveform using awgstream and then measured the output in DTT, using a bandpass filter to see the 100 Hz signal.

I expect the Tx PD signal to be in phase with the injected waveform, while the TRANSIENT_OUT signal should be 180 degrees out of phase. The attached plot shows the output of H1:CAL-PCALX_TX_PD_OUT_DQ and H1:CAL-PINJX_TRANSIENT_OUT_DQ. The two signals are indeed 180 degrees out of phase, with the Tx PD output rising on the integer second as it should be, while the TRANSIENT_OUT is falling on the integer second (with some small delay, ~240 usec).

Thus, I conclude the sign of the inverse actuation filter (and, by extension, the actuation functions provided for the CW injections) is correct. If there is a sign flip, perhaps it is on the output side? This needs to be investigated.

Title:  08/12/2016, Day Shift 15:00 – 23:00 (08:00 –16:00) All times in UTC (PT)
State of H1: IFO is unlocked.  
Commissioning: Recovering the IFO.
Outgoing Operator:  N/A
 
Activity Log: All Times in UTC (PT)

14:56 (07:56) Chris – Going down Y-Arm to deliver tools to Ed 
15:00 (08:00) Start of shift
15:19 (08:19) Jim & Krishna – Going the End-Y to reset BRS
15:50 (08:50) Stephen – Going into the Optics lab
16:00 (09:00) Karen – Going into the LVEA to cleanup around HAM6
16:01 (09:01) Kiwamu – Transitioning End-X to Laser Hazard
16:11 (09:11) Gerardo – Checking Ion pumps at HAM5/6
16:20 (09:20) Gerardo – Out of the LVEA
16:25 (09:25) Jim – Restarting NDS1
16:33 (09:33) Ed – Going to End-X to work on wind instrument install
17:12 (10:12) Krishna & Jim – Back from End-Y
17:13 (10:13) Krishna – Going into the Biergarten to work on Compact BRS
17:58 (10:58) Koji & Stefan – Going to ISCT6 to test shutter timing
19:05 (12:05) Koji & Stefan – Out of the LVEA
19:06 (12:06) Krishna – Out of the LVEA
19:14 (12:14) Ed – Back from End-X
20:04 (13:04) Kyle – Going to End-Y for RGA work
20:57 (13:57) Gerardo – Going to both Ends to check on test stands
22:14 (15:14) Kiwamu – Going out to check on PDs
22:15 (15:15) Gerardo – Going into LVEA 
22:25 (15:25) Kiwamu – Out of the LVEA
22:30 (15:30) Kyle – At End-Y doing RGA sweeps – Seeing contamination spikes in vac
22:58 (15:58) Kyle – Back from End-Y

Title: 08/12/2016, Day Shift 15:00 – 23:00 (08:00 – 16:00) All times in UTC (PT)
Support:  Kiwamu, Stefan, Sheila, 
Incoming Operator: Patrick

Shift Detail Summary: Commissioners testing fast shutter operation in the morning. Around 12:00 started to align the IFO. Took several tries and a lot of work by the commissioning team to complete the alignment. Started locking. Commissioners are working through various challenges. 
IFO locked at DRMI_LOCKED. Commissioners continuing working on the fast shutter and locking.
Dale – brought a small tour (his last) into the control room. He was given a hearty round of applause by all present. Good luck to Dale, from his LIGO family, as he starts this next journey.        

Updated the FAST_SHUTTER guardian to  check ASC-AS_A and ASC-AS_B light levels during shutter test.

The "light on diodes" level is scaled from the trigger PD levels from beckhoff (H1:SYS-MOTION_C_SHUTTER_G_TRIGGER_LOW and H1:SYS-MOTION_C_SHUTTER_G_TRIGGER_HIGH), using a relative gain specified in the FAST_SHUTTER guardian.
The dark limits are specified in in the FAST_SHUTTER guardian.

The changes include:

- A check thet the downstream PD levels are OK when the shutter is open on every lock
- During a fast-shutter test:
    - A check that the downstream PD levels are OK with the shutter open.
    - A check that the downstream PD levels are dark for 9 seconds, starting 0.5 sec after the fast shutter closed.
    - A check that the downstream PD levels are OK after the sutter reopens.

We also tested compatibility with the HAM6 ISI - we seem to trip it a lot on shutter firings when isolated. For now we will leave it damped until after the test.
The guardian was checked into svn as version 14028.

Over-filled CP3 with the exhaust bypass valve fully open and the LLCV bypass valve 1/2 turn open.

Flow was noted after 10 minutes 23 seconds, closed LLCV valve, and 3 minutes later the exhaust bypass valve was closed.

The WHAM6 "Fast Shutter" system and OMC were repaired and replaced, respectively, during the recent vent.  The logic for the fast shutter has been augmented,  reviewed, and tested (see recent alogs for test results).  A TRB review of the OMC-shutter incident took place this morning and their recommendation was to return to normal operations.  The new fast shutter monitoring and control software (ECR E1600246) should now be in place and in routine use. Commissioining may resume at the 50W input power level of interferometer operation.

This relieves LHO alog #29010, "Input power to be held to be < 25 W until technical review of fast shutter
Notice from LIGO Systems".
 

This morning I installed the Young Model 81000 Ultrasonic Anemometer next to the wind fence at End-X. It's being powered by a sand alone 18VDC supply. All connections are being routed through two SOLA STC-DRS-038 Isolated Loop Circuit Protectors located in the rear of the electronics rack  in the VEA. There are 3 BNC pigtails awaiting connection through the PEM patch panel. Unfortunately, I didn't take a picture of the actual anemometer.

[Stefan, Koji]

Quick Summary

Shutter timing test has been performed for the OMC PZT shutter and the fast mechanical shutter. Everything seems reasonable.

- The trigger logic fires at the PD input of +2V.

- The trigger logic reacts at 1.5us since the PD input thresholding.

- The PZT shutter detunes the OMC cavity at 4.8us.

- The fast mechanical shutter start blocking the beam at 1.7ms, reaches half blocking at 1.85ms, complete block at 2.0ms.

More about the test comes later.

J. Kissel

I took an opportunity between shutter testing and beckhoff problems to gather the final at-vacuum measurements of the HAM6 SUS. I'll process the data in complete detail tomorrow (I attach a screenshot of an example DOF from the OMC), but the message is that the TFs look just as good as they did before the vent: free, clear of rubbing, and all resonances are at the same frequency with roughly the same Q. 

Excellent!

Watch this space for full analysis and comparison with previous results.

/ligo/svncommon/SusSVN/sus/trunk/OMCS/H1/OMC/SAGM1/Data/
2016-08-11_2305_H1SUSOMC_M1_WhiteNoise_L_0p02to50Hz.xml
2016-08-11_2305_H1SUSOMC_M1_WhiteNoise_P_0p02to50Hz.xml
2016-08-11_2305_H1SUSOMC_M1_WhiteNoise_R_0p02to50Hz.xml
2016-08-11_2305_H1SUSOMC_M1_WhiteNoise_T_0p02to50Hz.xml
2016-08-11_2305_H1SUSOMC_M1_WhiteNoise_V_0p02to50Hz.xml
2016-08-11_2305_H1SUSOMC_M1_WhiteNoise_Y_0p02to50Hz.xml

/ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/OM1/SAGM1/Data/
2016-08-11_2249_H1SUSOM1_M1_WhiteNoise_L_0p03to50Hz.xml
2016-08-11_2249_H1SUSOM1_M1_WhiteNoise_P_0p03to50Hz.xml
2016-08-11_2249_H1SUSOM1_M1_WhiteNoise_Y_0p03to50Hz.xml

/ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/OM2/SAGM1/Data/
2016-08-11_2151_H1SUSOM2_M1_WhiteNoise_L_0p03to50Hz.xml
2016-08-11_2151_H1SUSOM2_M1_WhiteNoise_P_0p03to50Hz.xml
2016-08-11_2151_H1SUSOM2_M1_WhiteNoise_Y_0p03to50Hz.xml

/ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/OM3/SAGM1/Data/
2016-08-11_2257_H1SUSOM3_M1_WhiteNoise_L_0p03to50Hz.xml
2016-08-11_2257_H1SUSOM3_M1_WhiteNoise_P_0p03to50Hz.xml
2016-08-11_2257_H1SUSOM3_M1_WhiteNoise_Y_0p03to50Hz.xml