Sheila, Alexa, Dan, Evan

Summary

Tonight on dc readout, we started to reduce the coupling of alignment fluctuations into DARM by closing some more ASC loops. We focused mainly on the input and power-recycling optics.

During this work, the lowest value of REFL_A_LF observed was 0.4 ct (compared with 21 ct on resonance), meaning the interferometer visibility is 98%. The highest arm power observed was 1150× single-arm buildup, meaning the interferometer recycling gain is 34 W/W.

Details

List of loops, and things tried:

• We were able to close REFLB9I → IM4 pitch with an OK bandwidth (> 0.1 Hz, based on step response). Here we have a 1/f loop shape everywhere (FM2+FM3 in INP1), and a gain of −1.0 ct/ct. We may want to use REFLA9I − REFLB9I instead (see below). Closing the loop had an immediate improvement on the mode seen on the REFL camera.
• For IM4 yaw, we noticed that the combination REFLA9I − REFLB9I gave a sensible error signal (as was the experience at Livingston [LLO#16254]). But the lock broke while trying to close the loop, and we did not pursue it further. The most egregeous alignment fluctuations in the corner appear to be in pitch anyway.
• At one point were able to close REFLA9I →PRM pitch, but it seems this error signal is only good intermittently. Possibly it requires the input pointing into the PRC to be good already (i.e., we may need to close it after the IM4 loops).
• We looked for a while for a good signal for the common ETM motion, but none of the responses in REFL9 or REFL45 seemed immediately good.
• The situation with AS36 → BS is still mysterious; neither ASA36Q nor ASB36Q seemed to give good error signals.
• The differential ETM loops ("DHARD", but not actually DHARD) seem to have more optical gain now that the SR2 position has been moved. Good filter module gains are 8 ct/ct for pitch and 80 ct/ct for yaw; these are possibly conservative for the 2.8 W lock. For the 8 W lock they may need to be reduced a bit further still. Otherwise they continue to work fine.

Alexa, Sheila, Evan, Dan

Peter had noted that our suspension compenstation for the LSC DARM filter was different than the one used at LLO. In his plot LHO#16728 he had actually missed a Lead filter at 200 Hz (FM9) that we turn on once we are on RF DARM. See new sus compenstation comparison plot. Even with this lead filer on, we still do not have as much phase as Livingston.

Today, I loaded LLO's suspension compenstation filter into FM1 of LSC DARM. We tried enaging this for ALS DIFF but immediately saturared L3. Our next plan in attempt to acquire more phase margin is to develop a filter which can be engaged along with the lead filter (FM9) once we are on RF DARM with our original sus compensation filter (FM8), and see if this causes saturation. TBD.

Before tuesday, we had been listening to IFO channels through the computer speakers using z audio.  It seems like z audio has disapeared. 

Since Betsy found out that SR2 is rubbing at its nominal alignment, (alog 16811), I've tried to investigate if we can move SR2 so that it is not rubbing without introducing clipping.  This was done by moving SR2 pitch, then adjusting SR3 to center on AS_C.  The attached plot shows the power on each of the PDs we have at the AS port, each PD is normalized to the mean powers at different alingments so they can be displayed on the same plot.  While we get some clipping on AS_C and AS_A when we are in the non rubbing zone, happily the best location for the OMC QPDs are in the middle of the SR2 alingments where betsy says there should not be clipping. 

Keita had previoulsy set the alingment of the SRC cavity and the pios to AS_C (alog 15145 ).

Dave O, Evan, Elli

This morning we prepared for a measurement of the SRC length we plan to take tomorrow.  We were working on IOT2R.  We realigned the Auxiliary laser beam going into HAM1 so that in follows the reflection of the carrier from the PRM onto IOT2R.  This realigned the Aux laser beam returning frm HAM1 onto the 1611 photodiode on IOT2R.  The beat note of the Aux laser and carrier is -34dBm, the same as what we saw in December.  We tried locking the beat note to the spectrum analyser but ran out of LVEA time, so this is a job for tomorrow the settings were the same as used in December.

While we had been playing with things, I kept the alarm levels a little sloppy but now that we'll likely leave this alone for a time, I've closed down the range of operating pressures.

The alarm handler will alarm (as it has for some time) at differential pressures outside of +-2PSI.  The servo should have no problems keeping the pressure within that range.  Further it will alarm MAJOR at +- 5 psi.  If the minor alarm goes off and stays out of major alarm, it is likely the servo has frozen or someone left it in manual mode.  Please address asap and feel free to seek realtime help from me.  There is an OPS wiki too.  If the alarm is ignored, an avoidable HEPI trip will likely be the result.

LVEA: Laser Hazard
Observation Bit: Commissioning  

07:15 Cris & Karen – Cleaning in the LVEA
07:15 Jodi – In the LVEA
07:52 Corey – Working in the Squeezer Bay
08:05 Elli & Dave – Working on IOT2R 
08:20 Jim – Running TFs on HAM4
10:00 Corey – Out of the Squeezer Bay
11:00 Kyle – Going to HAM5 area to get bolts for HAM1
11:14 Kyle – Out of the LVEA
11:17 Keita – Going into the LVEA to look for 3IFO parts
11:21 - Adjusted the ISS diffracted power from 5.2% to 8.1%
11:35 Keita – Out of the LVEA
12:13 Elli & Dave – Out of the LVEA
12:49 Ed – Retrieving totes from Mid-Y
13:21 John, Bubba, & Kyle – Going to Mid stations and end stations to check the weather stations
13:42 Dan & UM Students – Going to LVEA roof. 
13:54 Ed – Opening high-bay roll-up door to bring in totes. 
14:10 Ed – Going back to Mid-Y
14:30 Ed – Back from Mid-Y
15:05 John, Bubba, & Kyle – Back from mid and end stations

Looking for missing VE chamber door bolts! -> Also, noticed X-end turbo pump controller still energized from most recent pump down (fan has been running unnecessarily) -> Turned off controller and brushed up against OPLEV pier accidentally in the process

Finished bolting HAM1 East door -> Noticed West door also missing half of its bolts -> Will need to bolt West door Monday morning for anticipated pump of HAM1 on Tuesday

Several commissioners feel that our new seismic defenses leave H1 insensitive enough to truck traffic that our Hanford site contacts no longer need to email me weekly with reports of their levels of activity.  A quick glance at the 1-3Hz seismic trace in the control room will always settle the question of whether the trucks are hauling or not.    

We've built up a good bank of contacts related to site operations.  Feel free to email me any time if you have questions about the possibility of earth-shaking things occurring near LHO.  

Adjusted ISS diffracted power from ~ 5% to ~ 8%.

  Estimates are at least 10 working days needed to complete the 3IFO tasks before the end of March. To reach this goal, Tuesday’s and Thursday’s will be open access to LVEA and VEAs and noisy work (craning, forklifts, etc.) will be permitted between 08:00 and 16:00. During this time, the LVEA and VEAs can be transitioned to Laser Safe as needed. Always check in with the operator before starting a task.
  
The 08:00 to 10:00 noise windows are suspended while the extended Tuesday and Thursday noise hours are in effect.
 
Summary: No commissioning and noisy work on Tuesday and Thursday between 08:00 and 16:00. Commissioning during all other hours. These times can be altered due to special requirements, with agreement of the commissioners.
 
Fred brought up the need to review and refine the alarms, alarm handlers, and system monitoring. Fred asked that that the staff think about how these systems can be improved. This will be the subject of the next Science Team meeting.    

Tuesday 02/24 - GV5 and GV7 will be closed to support the pump down of HAM1.
Kyle – will be installing the remaining bolts on the HAM1 doors. 
Filiberto – Will be shutting down the Test Stand in the West Bay area to prep for rack removal.
Jim – running TFs on HAM4
    

model restarts logged for Thu 19/Feb/2015
2015_02_19 07:56 h1fw0
2015_02_19 16:34 h1nds1

Two unexpected restarts, nds1 most probably due to request overload. Conlog frequently changing channels report attached.

Dan, Sheila, Evan, Jeff, Alexa

Tonight locked many times (on RF) but didn't stay locked verry long.  We found two new lockloss causes that were relatively easy to solve:

• The ALS_DIFF guardian was going into the DOWN state (and setting the DARM gain to 0) even though it was stalled.  We have a temporary solution (which is awkward and can sometimes cause the DIFF guardian to get stuck in the DIFF_LOCKLOSS state) and Jamie is looking into why this happened.  
• The COMM (fast) Tidal was not happening.  The offset was off for END X, and the TIDAL_HACK guardian was also not running.  We updated the safe.snaps for h1alsex and h1alsey.
• By the time that we understood and fixed these two problems we got another large earthquake. 

During one of our short locks early in he evening ,  we made an attempt to align the green to the arm cavities after the DHARD WFS had come on. For the X arm the only thing we needed to do to get a good build up was move the TMS, we saw the spot move on the ITMX green camera and updated the spot positions for the green WFS (248.3 for PITCH, and 354.8 for YAW).  For the Y arm we saw that moving TMS was not good enough, we needed to also adjust QPD offsets.  We lost the lock in the middle of this process.  Note: the recycling gain tonight was low, around 25, but we think that having the green co-alinged even for this low build up would be better than our original situation.

During the earth quake we have spent some time on the new COMM IR search state that evan wrote.  We modified it, it is now 100% successful, but it can take a couple of minutes (generally under 5).  This is still faster on average than having a human do it, and we can think about something else while this is working now.  

J. Kissel, S. Dwyer

During the earthquake we captured new safe.snaps  for the ETMs. Note that in doing so, I brought the SUSs to "safe" by hand, then requested the guardian to go to "SAFE", and vice versa brought the sus to "ALIGNED" via guardian, then restored everything that the guardian didn't touch -- all because I finally wanted to compare what my impression of what the guardian should be doing is different from what the guardian currently does after months of neglect from me, and commissioning by others. Most notably, it DOES NOT touch any part of the locking filters, and it DID turn on BOTH degrees of freedom of optical lever damping. For the record, the safe I gathered, I turned OFF ALL euler basis output switches: LOCK, DITHER, DAMP, OL DAMP, DARM DAMP, etc. Further, I've turned OFF the large offsets installed by Keita reference in LHo aLOG 16591. Those offsets, and all the expected LOCK filter banks and optical lever Pitch damping has been turned back ON. I've committed the new safe.snap the the userapps repo.

Currently, we want optical lever damping to be either under human control or ISC guardian control, so we have commented out the lines in the INIT and ENGAGE_DAMPING states with call the function susobj.olDampOutputSwitchWrite to turn the levers ON. I've commited SUS.py to the userapps repo.

J. Kissel, S. Dwyer, D. Hoak

We were cruising along trying to align green beams to a red lock when an earthquake in Japan killed the lock. 
Interesting notes:
- There have been two EQs in the past 16 hours,
2015-02-19 13:18 UTC in Vanuatu, 6.4 M
2015-02-20 04:25 UTC in Japan, 6.3 M
- Attached is a band-limited RMS velocity of the 0.03 to 0.1 [Hz] band over the past 24 hours. This shows that, on site, the Japanese earthquake hit harder, almost 2/3rds more amplitude than the slightly stronger (at epicenter) Vanuatu quake.
- The SEI systems, HEPI and ISIs rode out the EQs without a problem. In fact, looking at the BLRMS colored performance matrices of all the ISIs, the only non-green blocks are the very lowest band, (0.03 - 0.1 [Hz]) that have gone orange (indicating the displacement is between a factor of 100-1000 larger than requirement in this frequency band). 

@DetChar -- it would be great to get ASDs and time series of lots of sensors during these two quakes and compare them against each other and "quiet" time. Note this would note just be a pull of the summary pages, 'cause I want a few averages, just around the EQ time.
(1) Check the arm length stabilization control signals: H1:ALS-[X/Y]_REFL_CTRL_OUT_DQ, roughly pre-calibrated [um] (the calibration may be off by a factor of two, and there's a minus sign between the two arms). Note that they also saturate near the limit of their range
(2) Check the GND STSs' (a) time series to *see* if they saturate, and (b) their ASDs (in displacement, preferably) to see how loud all frequency bands get. H1:ISI-GND_[ETMX,ETMY,ITMY,HAM2,HAM5]_[X,Y,Z]_DQ -- should be calibrated into 1 [nm/s] (only above ~10 [mHz], so be careful when looking at 30 [mHz] data)
(3) Check the Beam rotation sensor: H1:ISI-GND_BRS_ETMX_RY_OUT_DQ -- should be calibrated into [rad]. Good also down to ~10 [mHz]
(4) BSC ISI T240s
(5) HAM ISI GS13s

LVEA: Laser Hazard
Observation Bit: Commissioning  

07:15 Cris – Cleaning in the LVEA
08:00 - Cannot login to CR terminals – CDSFS0 had crashed. Ryan rebooted computer 
08:00 Jamie – Restarting Guardian to pick up new patches
08:15 Corey – 3IFO work in H2 Squeezer Bay 
08:18 Elli & Dave – Working around HAM6 
08:20 Filiberto – Working on PR3 OpLev
08:30 Betsy – Running TFs on SRM and SR2
08:40 Andres – In LVEA looking for tooling
08:45 Andres – Out of the LVEA
09:00 Kyle – Looking for the bolts for the HAM1 door – Prep for pump down
09:45* Kyle – Out of the LVEA
09:55 Jodi – Working at Mid-Y on 3IFO stuff
10:00* Dave & Elli – Out of the LVEA
10:00* Filiberto – Out of the LVEA
10:30* Corey out of the LVEA
12:13 Vending provider on site to stock machines
13:48 Apollo – On site to work on CDS AC units
15:35 Kyle – Going to End-X to recover tools for the HAM1 vacuum work

I had noticed on the Detchar pages that ITMY had been doing a lot better between 1 and 10 hz than the other BSCs, so I started poking around in filters to see what was wrong. The FF filters were all the same and isolation loops all looked roughly similar. On Hugo's suggestion I looked at the L4C blend in on HEPI and the FF in on the ISI. The signals should have been exactly the same, but the ISI showed less signal at 1hz by a factor of  ~2 (first image, HEPI is red, ISI FF is blue). The only filters applied on both platforms a that point are a calibration filter and a symmetrization filter. On HEPI (second image), the calibration is just a gain (red trace), the symmetrization is a notch filter that smooths the L4C response(blue). On the ISI (third image), the calibration filter is a notch filter (red again), and the symmetrization filter is mostly flat filter that tunes the calibration filter slightly (blue trace). Either approach is fine, as the product of the cal and sym filters stays the same, (green taces on both pictures). Unfortunately, the ISI HEPI FF L4C cal and sym filters were not loaded in a consistent manner on most chambers (ITMY was done correctly, so FF worked there!). Basically the other chambers were using the blue trace on the first plot with the red filter on the second plot. This effectively cut the FF L4C signal in the region we needed it most. I've now loaded right, consistent set of filters from HEPI on the ISI FF path, so we should see a good improvement on most of the chambers in the 1-10hz region. One dof for ETMX is shown in my fourth image, blue before, red is after, I'll try to get a more complete comparison tomorrow morning. I haven't finished the doing gain matching on these chambers yet for the FF path, whcih should improve this a little more.