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.

WP 6069

The copying of raw minuted trend files from h1tw1 is complete and the copied files have been verified.  The nds1 service on h1nds1 has been restarted with a new configuration to read the copied files from their new location.

[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.

HEPI BS Tripped few minutes before ITMX ISI.  This is the only HEPI that tripped in the neighborhood of the large quake.

ITMY ISI tripped--timing (H1:ISI-ITMY_ST2_WD_MON_GPS_TIME) indicates stage2 tripped on ACTuators 1 second before Stage1 on T240s but looking at the plots, the Actuators have only registered a few counts, nothing near saturation/trip level.  But the T240s hit their rail almost instantly.  It seems the Stage2 Last Trip (H1:ISI-ITMY_ST2_WD_MON_FIRSTTRIG_LATCH) should be indicating ST1WD rather than Actuator. On ETMY, the Trip Time is the same for the two stages and Stage2 notes it is an actuator trip but again, there are only a few counts on the MASTER DRIVE; seems this too should have been a ST1WD trip[ indication trip on Stage2--I'll look into the logic.

On the BS ISI, the Stage1 and Stage2 trip times are the same, and the Last Trip for Stage2 indicates ST1WD.  The Stage2 sensors are very rung up after the trip time but not before unlike the T240s which are ramping to to the rail a few seconds before trip.  ETMX shows this same logical pattern in the trip sequence indicators.

On the ITMX ISI, Stage1 Tripped 20 minutes before the last Stage2 trip. This indicates the Stage1 did not trip at the last Stage2 trip.

No HAM ISI Tripped on this EQ.

Bottom line: the logical output of the WDs are not consistent from this common model code--needs investigating. Maybe I should open an FRS...

Attachment 1) Trip plots showing Stage2 trip time 1 second before the stage1 trip where the stage2 actuators do not go anywhere near saturation levels.

Attachment 2) Dataviewer plot showing the EQ on the CS ground STS and the platform trip times indicated.

In an effort to eliminate the need to connect and disconnect shutter cables during vent we have moved the shutter logic controler to the rack from the table.  Also replaced the BNC cables with Yellow BNC cables so they can be easily identified.
See attachment.

Krishna,

Jenna and I had noticed that L4C 7 didn't appear to be working. L4C is close to the c-BRS, so it would have been good for comparison. In order to test if it was the instrument or the electronics, I temporarily swapped the cables with those of L4C 8 going in to the SUS rack at the LVEA. Now L4C "7" appears to be working and L4C "8" is not, indicating that the problem must be on the instrument side (or the pre-amp, I guess?). I'll swap it back in the afternoon.

Stefan and Sheila working on shutter control logic. I helped resolve problems with h1ecatc1. Had to restart EPICS IOC and copy updated PLC2 to target.

23:32 UTC Gerardo to HAM6 area to check on vacuum equipment
23:39 UTC Gerardo back
03:05 UTC Joe to Y2-5 to watch meteor shower with telescope
04:30 UTC Stefan and Sheila done working on shutter control logic. Kiwamu starting work.
06:17 UTC Kiwamu to end X to investigate green laser electronics
07:00 UTC Kiwamu back

I was able to get the Y arm green power to around 1 with LOCKED_NO_SLOW_NO_WFS, but if I put it on INITIAL_ALIGNMENT it would start to be driven away. Kiwamu was investigating the X arm.

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

Krishna

Here are the recorded c-BRS associated channels and their calibrations (I think it is accurate to <20%):

1. H1:NGN-CS_CBRS_RY_PZT1_CTRL_IN1_DQ  :   PhotoDiode 1 output  :  1.6e-10 rad/count

2. H1:NGN-CS_CBRS_RY_PZT1_MASTER_OUT_DQ : PZT1 output  :  2.8e-10 rad/count

3. H1:NGN-CS_CBRS_RY_PZT2_CTRL_IN1_DQ  :   PhotoDiode 2 output  :  1.23e-10 rad/count

4. H1:NGN-CS_CBRS_RY_PZT2_MASTER_OUT_DQ : PZT2 output  :  2.8e-10 rad/count

I've also attached more spectra recorded this morning after the clean room fans were turned off. Many of the noise peaks went away, especially above 100 Hz, but some lines remain which are common to the seismometers and c-BRS. The DIFF signal above 100 Hz, drops to ~10 picorad/rt(Hz), indicating that it's noise floor is indeed well below the SUM channel. I expect that the current SNR at ~10 Hz is between 10-30. I've attached Matlab code showing the analysis.