There was a request for a representative example of BSC-ISI performance during ER9. My attached plot shows the ETMY L(ength) suspoint motion of the ST2 GS13s versus the ground motion. The red curve is the ISI's longitudinal motion (using the calibrated SUS_POINT channel), blue is the ETMY BRS/STS Y super sensor (showing the tilt subtracted low frequency ground motion) and green is the calibrated STS Y ground motion. Somethings to note:

1. Below .1hz the height of the green trace above the blue gives you an idea of how windy it was. In this frequency range the L motion is mostly ISI Y, so much of the height of the red trace above blue is due to tilt. The bump between 30 & 100mhz is from the gain peaking of the sensor correction filter. As Conor said on Friday, this should be mostly common mode between all of the tables.

2. Between .1 and 1 hz the blend filters are rolling off from the CPSs to the inertial instruments. It doesn't look like we are getting much at the microseism, but this is probably limited by performance of the sensor correction. We should do "better" here when the microseism comes up, during O2.

3. Above 1 hz the St2 L motion is limited by St2 RX/RY motion, because we can't turn on those loops on St2. GS13 noise is too high below 1 hz so it's hard to make a blend filter that improves  >1 hz motion that doesn't spoil lower frequency motion.

4. Above 10hz we are limited by GS13 noise and loop gain.

Something that we've noticed a lot lately is that if the interferometer drops lock during the CoilDrivers state, guardian doesn't notice the lockloss for a long time. 

This was because all of the coil switching was happening in the "main" part of the state, which included many sleep commands.  Since we were switching 5 optics' coils, and each optic was about 90 seconds long, we had a solid 7+ minutes between lockloss checks.

Yesterday I re-wrote the Coil Drivers state so that the switching happens in the "run" part of the state, and I use a series of guardian timers rather than sleep commands.  So, the state still takes many minutes, but now it's constantly checking for lockloss as guardian is intended to do.

The switching has worked at least once so far with the new code, although since we didn't drop lock, the lockloss catching hasn't been tested yet.

Future work is to test whether we can do all 5 optics in parallel rather than in series, and then change the guardian to do so.

RGA had been valved-in but not running.  Need to finish commissioning this unit via baking "hot" at next available opportunity.

Here is a 60 day trend of the the EndY Drift Monitor channel.  This DC reading of the Beam Mirror Reflection obviously is still 'drifting' down but does continue to slow.  A quick and dirty extrapolation gives a need to recenter date of around July 25.

   All teams have completed search of assigned areas. Two already known TDS3034s locations were confirmed and one was returned to the EE shop. No other items were found.  

EX was transitioned to LASER SAFE.

EY was already LASER SAFE when I got there.  Temporarily transitioned it to LASER HAZARD to enable my
opening of the table enclosure.  Transitioned back to LASER SAFE.

No untoward items of test equipment were found in the table enclosures.

The LVEA has transitioned to LASER SAFE.

No untoward items of test equipment were found in the table enclosures.

[Jenne, AmandaC]

With Sheila and Haocun's work earlier today (alog 28324) putting in the beam splitter on the POPAIR table, we are now able to see a dither drive in POP90.  We shake SRM in pitch at 4Hz with 100 counts, and see a clear peak in POP90.  See snapshot.  We haven't yet put this into a new ASC loop, but we will.

4:15UTC

IFO Mode set to OBSERVING

During the lock today I had to change some of the damping filter settings as different modes rang up. Similarly to what Nutsinee was seeing on Saturday the 18040Hz and the 15009Hz ETMY modes were the ones causing the most trouble. From the strip tool you can see where I have changed the damping filter settings.

The current phase and gain states for these filters are:

• ETMY_PI_OMC_DAMP_MODE1_DAMP (15009Hz): gain=-500 phase=0deg
• ETMY_PI_DAMP_MODE4_DAMP (18040Hz): gain=3000 phase=0deg

Also when I was trying to damp the 18040Hz mode earlier there was a difference in thet rends of the OMC and QPD rms monitors. From the OMC rms it seemed theat the damping was effective but it's clear from the QPD rms that the mode was still ringing up and broke lock. 

The GDS calibration filters were updated for ER9 on July 7, 2016. These filters are designed to correct the output of the front-end CALCS calibration model.

These filters were generated using the script run_td_filters.m located in the calibration SVN under aligocalibration/trunk/Runs/PreER9/H1/Scripts/TDfilters with SVN version #3176.  Information on the exact parameters files used to generate these filters and the version of DARMModel used for these filters can be found in the run file run_td_filters.m.

In addition to the residual and control chain correction filters, the updated filters also include dewhitening filters that are unity since the pipeline is now run by ingesting double precision channels that are no longer whitened.  The next generation of the GDS calibration code will not require dewhitening filters to be present in the filters file.

The new filters file can be found in calibration SVN under aligocalibration/trunk/Runs/ER9/GDSFilters/H1GDS_1151960706.npz.

Attached are plots of the residual and control correction filters.  These plots compare the frequency response of the GDS FIR filters to the true frequency domain model they are based on.  

On June 17, 2016 the GDS calibration pipeline at LHO switched to ingesting double precision channels that are no longer dewhitened.  Therefore, the filters file was updated to include a unity dewhitening filter.  The new filter file can be found in the calibration svn under aligocalibration/trunkRuns/PreER9/GDSFilters/H1GDS_1150213197.npz.

The double precision channels ingested by the GDS pipeline in the current configuration on:

H1:CAL-DELTAL_CTRL_TST_DBL_DQ

H1:CAL-DELTAL_CTRL_PUM_DBL_DQ

H1:CAL-DELTAL_CTRL_UIM_DBL_DQ

H1:CAL-DELTAL_RESIDUAL_DBL_DQ

H1:CAL-DARM_ERR_WHITEN_OUT_DBL_DQ

[Jenne, Robert]

As a result of Keita's alog 28196 regarding the beam position on the BS, we wanted to move the beam splitter around in relation to the beamline, to see if that would change any clipping that we may have on the baffles.  Short answer: nope.

First, we moved ST1 by putting offsets in the isolation loops.  JeffK tells us that these are calibrated in nm, so our 5,000 count offsets correspond to about 0.5mm of motion.  We moved ST1 up and down, as well as laterally along the plane of the beam splitter (+x+y and -x-y).  No effect seen in the power recycling gain. 

Next, we moved HEPI in a similar fashion.  The thought here is that the ITM elliptical baffles are suspended from this ST0, so we weren't moving them earlier.  (By moving both ST1 and ST0 we had hoped to differentiate which set of baffles was causing us trouble.)  We moved up and down, as well as in RZ, rotation about the z-axis.  RZ is calibrated into nrad, and the baffles are order 1m away from the center of the ISI, so they were each moved on the order of 0.5mm also.  Again no effect seen in power recycling gain.

Attached is a snapshot of our striptool, with the first offsets starting at about 0:06:00 UTC, and the last ones ending around 1:00:00 UTC.  Teal is the power recycling gain.  The POP18 seems to be still relaxing from the power up to 40W for the first few minutes of our tests, but doesn't seem to be correlated with our movements.  Red trace is the vertical CPS measure of BS ST1 ISI position, and orange is superimposed with brick red measuring our lateral motion.  Light purple is vertical HEPI motion and light green is RZ HEPI motion.

We felt that if we were really dominated by clipping losses around the beam splitter, moving by 0.5mm in some direction should show us some change in recycling gain.  Since it doesn't, we conclude that the power loss must be somewhere else.

Andy, Duncan, Laura, Ryan, Josh, 

In alog 28299 Andy reported that we were seeing the ER9 range deteriorate due to glitches every 2 seconds. Figure 1 shows the glitches turning on in DARM at 2016-07-09 05:49:34 UTC. 

We think the ALS system not being shuttered and changing state in lock is to blame. Here's why. 

Excavator pointed us to a strong coupling between DARM and the ALS channels. Raw data confirmed a correlation, Figure 2 shows the ALS glitches tuning on at that same time and figure 3 shows that both DARM and ALS are glitching at the same times. 

When we investigated the Guardian ALS state for this time (figure 4), it was not in a nominal configuration to start with and that got worse around the time the glitches started. The shutter was not "Active" and at 05:49:34 UTC the ALS X state changed from "-15 locked transition" to "-19 locking WFS" and at that same time the glitches started in DARM. So at some point, ALS X decided it needed to lock the arm (looks like Y followed an hour or so later). We did not track down exactly how the glitches originated or made it into DARM because this seems non-standard enough that a configuration fix should make it go away. 

Figure 5 shows a summary page plot for nominal ALS X Guardian behavior from O1. So the shutter should be active and we don't expect to see "locking WFS" come on during an analysis ready state. 

Looked at the cameras for PR3, PR2, PRM and all 16 arm baffle PDs during a power up. Bottom line: The lost power is found on the ETM baffle PDs.

- Plot 1 and 2 show the ETMX and ETMY baffle PDs. Note the huge increase in baffle PD4 in both arms. At the same time, baffle PD 1, on the opposite side of PD4, also sees an increase, so we can't explain this with arm alignment.

- The ITM baffle PDs show much less signal - there is some on ITMY baffle PD 4, but nowwhere near as much as on the ETM. (:Plot 3 and 4)

- PRM, PR2 and PR3 roughly track the recycling gain, i.e. they increase less than linear with input power. (Plot 5)

I should also say that the Beckhof whitening and digital gain setting were the same for all 16 PD. I attached a representative snapshot for H1:AOS-ETMX_BAFFLEPD_4.

The y-axis on all these plots (labeled arbitrary) is in Microwatt/Watt input power for the Baffle PDs, and recycling gain for POP_LF.