To recover our alignment after the PSL work that happened last week, IM3 was moved pretty significantly (alog 30910).  For the last week or so, it has been regularly running extremely close to the edge of the actuation range for LL and UR.  The MasterOut channels are around 126,000 counts, but the front end model outputs are above 130,000.  It would be great if someone from DetChar could have a look and make sure that we're not causing ourselves trouble by operating so close to the DAC edge here.  Note that the VoltMon channels for these two OSEMs are totally railed, so they will not be useful for looking at - I don't know if those are a regular part of the detchar scripts. 

• SEI -  running fine. EQ mitigation is satisfactory. Wind mitigation is ongoing.
• SUS - nothing to report
• CDS electronics - running ok. there are a few WP items to finish regardgin BIO readbacks and 24V runs in corner.
• CDS SW - HWS work is ongoing
• PSL - Peter is looking to measure water flow into the laser heads using a clamp on meter that is being brought in by a vendor. He hopes that the vendor will leave the device for a period of time.
• VAC - nothing or today
• FAC - the exit gate is malfunctioning and stuck in the UP position
• Work Permits

This will reduce unnecessary HEPI slow system movement.  This movement could be causing creek and maybe slow albiet minor alignment changes.

When both the ISI and HEPI Isolation loops are closed, the first step is to measure the free hanging position so the loop starts with zero DC shift.  Once the loop is fully engaged, the "Target Reference Location" is ramped into the loop to put the alignment of the platform to a repeatable place.  This restoration of position happens for all HEPIs and the HAM ISIs.  The BSC ISIs do not restore a Target position; no evidence to show now, but we don't see large shifts or wanderings of the BSC ISI positions.

Okay, for the HEPIs, the Vertical and Horizontal Pringle modes are overconstrained dofs of the HEPI platforms--8 actuators with 6 degrees of freedom.  As such these isolation loops are not DC coupled as are all the other dofs X Y Z RX RY  & RZ.  As such though, the restoration of a Target position into the AC coupled loop puts a large step into the loop and drives.  Attached are 30 day trends showing four ITMX HEPI trips.  The large step up on the horizontal Actuator drives are the restoration of the old target position of 900nm (upper right trace.)  This HP measurement is literally a distortion of the platform, some taken up by the soft Actuator connection and some by actual stress in the platform.  I would be most worried about yaw alignment shifts but there are none evident in the optical levers.  Given the length of this trend plot though, most of the optical lever data here may be in-loop.  There is probably some ASC output I could trend for that.

The bottom line is that since these are AC coupled loops and over some time, the offsets are AC'd out of the loop, why put them in in the first place.  Start the loop in the free hanging location like all loops and let this AC loop slowly go where it will.  We don't expect them to go much of anywhere.  Just avoid the potential problems no matter how minor.

I propose all HEPI Pringle loops be removed from the Target location restoration list (Guardian chamber edits.)  This has been discussed in the weekly SEI subsystem call and principals agree.

J. Kissel for S. Karki

I've moved the roaming high frequency calibration line driven by PCAL X from 1501.3 to 1001.3 Hz at Oct 31 2016 15:44:29 UTC (1161963886, 08:44:29 PDT). Note, O2 reference measurements for PCALX will be taken tomorrow, we should be sure to scale any results to those measurements.

Here's the status: 
Frequency    Planned Amplitude        Planned Duration      Actual Amplitude    Start Time                 Stop Time                    Achieved Duration
(Hz)         (ct)                     (hh:mm)                   (ct)               (UTC)                    (UTC)                         (hh:mm)
---------------------------------------------------------------------------------------------------------------------------------------------------------
1001.3       35k                      02:00                   39322.0           Oct 31 2016 15:44:29 UTC
1501.3       35k                      02:00                   39322.0           Oct 24 2016 15:26:57 UTC    Oct 31 2016 15:44:29 UTC      ~week @ 25 W
2001.3       35k                      02:00                   39322.0           Oct 17 2016 21:22:03 UTC    Oct 24 2016 15:26:57 UTC      several days (at both 50W and 25 W)
2501.3       35k                      05:00                   39322.0           Oct 12 2016 03:20:41 UTC    Oct 17 2016 21:22:03 UTC      days     @ 50 W
3001.3       35k                      05:00                   39322.0           Oct 06 2016 18:39:26 UTC    Oct 12 2016 03:20:41 UTC      days     @ 50 W
3501.3       35k                      05:00                   39322.0           Jul 06 2016 18:56:13 UTC    Oct 06 2016 18:39:26 UTC      months   @ 50 W
4001.3       40k                      10:00
4301.3       40k                      10:00       
4501.3       40k                      10:00
4801.3       40k                      10:00  
5001.3       40k                      10:00

• Gusts have actually been in excess of 40mph at times.
• hand aligned PR3 a bit after DRMI ASC engaged

TITLE: 10/31 Owl Shift: 07:00-15:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ed
SHIFT SUMMARY:
Locked for most of the shift. 4753Hz line was slowly ringing up so I reconfigured the damping filter. Range were up and down likely due to wind. Lockloss seems to coincide with ~40 mph wind gust. PI mode18 rang up once, flipped the phase sign and never saw it again. Verbal alarm complains about TCSY chiller flow towards the end of shift but this is bogus. As Kiwamu requested I also increased CO2 power thoughout the shift, 90 minutes at a time.

LOG

08:33 Increased CO2X from 0.2W to 0.3W, CO2Y from 0W to 0.1 W

9:18 Got an unknown external call

10:04 CO2X 0.3-->0.4W, CO2Y 0.1-->0.2W

11:35 CO2X 0.4-->0.5W, CO2Y 0.2-->0.3W

13:06 Co2X 0.5-->0.6W, CO2Y 0.3-->0.4W

13:40 Intent bit dropped for a second due to Guardian code load

14:11 Lockloss. SRC1 suddenly ran away. Coincide with ~40mph wind gust but this happened before earlier in the shift without breaking the lock.

Got a verbal alarm complaining about TCSY chiller flow so I went out to check the chiller on the mezzanine. At the TCSY chiller itself reported flow rate to be ~4Gpm. I also went out and check the mechanical flow meter in the LVEA and it appeared to be reporting >3Gpm. I don't know why the flow channel (H1:TCS-ITMY_CO2_FLOWRATE) is reporting something bogus.

The mode is made of two lines, 4735.05 Hz and 4735.09 Hz. Not sure why I didn't see this before. I increased the BP to be 1 Hz wide so the phase change between the two lines are not too far apart. Now damping at -60 deg phase, 0.02 gain.

Robert and I tried using Stefan's PR2 move and PR3 move states while Robert had a shaker on near HAM2.  We ddin't suceed in reducing the noise at the injection frequency, but we did find some POP offsets that gave us better recycling gain:

We got a recycling gain of 33 (35 according to the transmission QPDs) with POP A at -0.24 for pit, and -0.26 for yaw.  This didn't have much of an impact on the noise once I reran a2L.  

For now I'm leaving the offsets at the values we have been using (0 for Pit, 0.44 for yaw offset) because that is the position where we can power up without a braodband lump from 200Hz -1kHz.  With the higher recycling gain we didn't get a lump, but we did start to have coherence with DBB QPD1Y.

A quick request for operators:

Let's try a test of running the a2l test every lock.  If you see that the low frequency noise is degrading over the course of a long lock, you can rerun it to see if that helps. 

As a reminder:

get to nominal low noise

go to userapps/isc/common/scripts/decoup/

type:    ./a2l_min_LHO.py

8 lines around 20 Hz will appear in the spectrum and slowly get turned off one by one as the script becomes satisfied that it is done with each optic. 

I did a scattering scan for the entire site, including mid-stations, with a focus on the 50-200 Hz region and on sites that had previously been identified as potential scattering sites in scattering photos (e.g. https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=9564    https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=8281). The worst locations were between the chamber and the gate valve at the end stations (probably similar to what has been seen at LLO) and the input arm, especially between HAM2 and HAM3. The scattering at these three locations was close to showing, or showing in DARM, I can not be sure yet, study of these sites is ongoing. At EY I put black glass in each of the ports, which did not change the scattering peaks I was enhancing with a shaker. I thought the difference with LLO might be that there were no aluminum blocks in any of the LHO ports, so I inserted one in each of the ports but this did not make the coupling worse. We should try black glass at all ports simultaneously, and there are some other tests I would like to do.

At the input arm, the scattering noise, enhanced with a shaker, was clearly modulated with a 0.02 Hz yaw injection at PR2. I observed the input arm through multiple ports and found two spots that especially concerned me, both visible with the digital cameras after I adjusted them: the baffle in front of PRM (see photo) and around PR3.

TITLE: 10/30 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Jim
SHIFT SUMMARY:

Robert had H1 for a good chunk of the day & Jenne had it for a lock or two.  Other than that, just working on keeping H1 up for commissioners.

LOG:

• 16:20 Robert out in LVEA for measurements/injections/etc.
• 17:04 Took TCSx from 0.2 [set by GRD] to 0.4W.  (TCSy remains at 0.0W)
• 17:07 Rebooted video4 since it froze
• ~17:30 Happened to notice RED Terramon EQ from Calif.  Took seismic up to 0.3.  I noticed Terramon a few minutes after the peak already passed.  I reckon if I noticed Terramon earlier, I could have tried EARTH_QUAKE_V2.  Oh well, next time.
• 18:25 PI Mode18 rung up.  Took phase from 160 eventually down to about -30.
• 18:40 Lockloss
• 18:45-20:02 Unlocked investigations by Robert
• 20:02-20:30 H1 at Nominal Low Noise & Jenne taking over
• Had a few locklosses toward the end of the shift, but overall H1 has been fairly reliable getting back to NLN.

• Robert has been in the LVEA (judging by the Camera shots, he's checking light scattering in the input arm).
• Have currently been locked 3.5+hrs.  The range is hovering has been hovering between 60-70Mpc even with Robert work & injections.  
• Had a PI Mode18 rung up recently and damped it out via phase change.
• Winds toyed with approaching 20mph but have subsided.  Calif EQ quietly rolled by (no SEI action taken)

Whoops---just dropped out of lock. at 18:40 (11:40am).

TITLE: 10/30 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
    Wind: 9mph Gusts, 6mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.26 μm/s
QUICK SUMMARY:

• Arrived a bit late due to needing to swap a flat tire.
• Cheryl just took H1 up to NLN. 
• I transitioned Observatory Mode to Commissioning.
• Robert's shaker at EY continues to shake (and give us a 65Hz line & harmonics seen on DARM); this has been since yesterday at about noon.
• Robert is staging to get continue his various measurements/investigations/injections.
• Storm continues its downward trend as seen on useism.
• ISI Config was on USEISM_MOD_WIND.  Cheryl took it here during the big EQ & we had higher useism touching the 90percentile.  I am going to take the system to the nominal WINDY state.
• HAM2 HEPI excitation indication still noted on overviews (Guardian/CDS).  Thought of killing it, but Robert mentioned they might run it again, so I held off.
• IM3 continues with "out of nominal range" on DIAG_MAIN (Cheryl will investigate).
• H1IOPASC0 is noting a TIMING ERROR on the CDS Overview (indicated by RED "TIM" box and RED CPU Max box (i.e. H1:FEC-18_CPU_METER_MAX).  Hitting Diag Reset cleared both Timing Errors on the H1IOPASC0 window.
• Conlog continues to have INVALID boxes on CDS Overview.
   

State of H1: relocking

Shift Details / Activites:

• lock loss due to earthquakes in Italy
• used the LARGE EQ state for SEI that JimW reccommended - no platforms tripped
• after EQs rand down, Initial Alignment
• first lock that made it to DC READOUT, paused for roll mode damping, my bad click broke lock
• second lock that made it to DC READOUT, paused for damping, then went to Nominal Low Noise
• set TCSY to 0.4W, and left TCSX at 0.2W
• noticed range dropping fast, thought it might be TCS, turned TCSY off (0W) at 13:47UTC
• went to make some lunch, and did not see the notification of a PI mode ringing up when I came back, can we make it repeat, like the GRBs?
• PI mode 27 broke the lock

Notifications:

• GRB came in while 9:51:19, while H1 was in DRMI

• done with Initial Alignment
• set ISC_LOCK to Down and run Init
• ISC_LOCK says it's done running DOWN, and goes ro Ready
• but ALIGN_IFO is still in SRC_OFFLOADED
• wouldn't it make sense for the ISC_LOCK down script to handle setting all of the nodes to the proper state?
• or maybe ISC_LOCK INIT could do this?
• or maybe they do and I did the wrong guardian sequence?
• screenshot of where H1 landed

J. Kissel

With hints of improvement last night from Sheila (see LHO aLOG 30947) on reducing the most egregious ~41 Hz peak in DARM (which is known to be the HSTS roll modes, a.k.a R3), I launched a campaign of adding similar ~1 Hz wide notches to all HSTS suspensions' local damping loops (M1_DAMP) at both the highest roll mode and highest vertical modes (a.k.a V3 at ~27.5 Hz).

The filter designs are
V3 notch: FM8 "SB27.5" ellip("BandStop",4,1,60,27.05,28.05)gain(1.12202)   [Input -- Always On; Output -- Ramp; Ramp Time -- 2 sec]
R3 notch: FM9 "SB40.9" ellip("BandStop",4,1,60,40.4,41.3)gain(1.12202)     [Input -- Always On; Output -- Ramp; Ramp Time -- 2 sec]
where I've made sure that the lowest and highest frequency V3 modes (coincidentally both IMC mirrors: MC1 @ 27.38 Hz, MC2 @ 27.74 Hz) faLL within the stop band of the notch (and I've confirmed that this is true with Sheila's R3 notch design as well). Further, the V3 notch causes a phase loss of only 2.2 [deg] at 10 Hz, so it will not impact any of the damping loop's phase margins. To confirm, I've spot checked SR2's local damping open loop gain tfs just to be sure. Indeed all DOFs are still quite stable (and quite poorly tuned, as expected).

During the campaign I found that PRM, MC1, and MC3's "ellip50" standard low-pass filters were not engaged, so I engaged them.

I've greened up all ODC status lights, and then accepted all of the changes in the SDF system -- V3 filters ON, R3 filters ON, ellip50 filters ON, and Correct Damp State.

While haven't had an uber-long lock stretch since I've turned on all of these notches, I was at least able to grab 5 averages of a 5 [mHz] BW ASD and compare against the long data set from last night. The notches appear to have done their job -- a large fraction of the modes have been squashed and don't show up in DARM anymore. Success! 

The SR2 damping loop open loop gain TF templates have been committed here:
/ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/SR2/SAGM1/Data/
2016-10-28_2223_H1SUSSR2_M1_openloop_L_WhiteNoise.xml
2016-10-28_2223_H1SUSSR2_M1_openloop_P_WhiteNoise.xml
2016-10-28_2223_H1SUSSR2_M1_openloop_R_WhiteNoise.xml
2016-10-28_2223_H1SUSSR2_M1_openloop_T_WhiteNoise.xml
2016-10-28_2223_H1SUSSR2_M1_openloop_V_WhiteNoise.xml
2016-10-28_2223_H1SUSSR2_M1_openloop_Y_WhiteNoise.xml