TITLE: 03/02 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: We've been having some trouble with the PSL and also with some noise around 30-200Hz. Not sure where the noise is coming from. We just got to low noise and are now Observing.
LOG:

• 00:06 Observing
• 03:59 GRB
• 06:10 Observing
• 07:56 Observing

PSL head flow error 1-4 again. I have Jason on the phone.

I ran an initial alignment because it kept losing lock before DRMI locking and I was hoping maybe it would help the 30-200Hz noise from before. It didn't. Range is still in the mid 50'sMpc and the breathing noise continues.

I had to accept some SDF diffs that I'm a bit confused by, but everything seems to be running fine.

PSL tripped with a head 1-4 flow error. I am on the phone with Jason getting things running again.

5.6 Anchor Point, Alaska

• Seen on USGS, Seismon, but NOT Terramon
• USGS reports time of EQ at 02:11 UTC
• Starting seeming a rise in the BLRMS at around 02:22 UTC
• L1 lost lock, H1 survived

Aidan asked me to look at scanning the arm cavities immediately after a lockloss, so that we can look at the higher-order-mode spacing as a function of time as the interferometer cools off.  We hope to be able to infer from this the absorption in each of the individual arms, to help separate if there is anomalously high absorption in one of the arms and if so, which one. 

The procedure was basically identical to that of Kiwamu's back in 2014 at LLO (LLO alog 13768).  The general idea is to lock the arms on green and hold them steady with ALS, then put an offset in the ALS COMM to adjust the PSL frequency relative to the arm cavities. 

Since we do have the frequency difference discriminator (FDD) in the ALS COMM system, we can't scan more than 1.5 or 2 FSR in our nominal configuration.  During the commissioning period today, Sheila showed me how to bypass the FDD.  After she bypassed it, I was able to scan almost 10 FSR per arm.  The cold-cavity scan I took today was much too slow, so the data isn't particularly clean.  Also, I neglected to add a small misalignment to the input IR beam, which will help the higher order modes to resonate.  At the end of the commissioning window, we put the FDD back into the signal chain.

So, our plan for the next time we have a commissioning window, or perhaps just at the beginning of maintenece on Tuesday, is the following:

• While the IFO is locked, gently go into the LVEA ISC racks and bypass the ALS COMM FDD (this way we don't have to acquire lock without it, but can run the scan without it).
• Unlock the IFO, after it's been locked for several hours (so it's nice and thermalized).
• Relock ALS as quickly as possible (I was able to get there within about 2 min this afternoon).
• Run scan script (attached) to step the ALS COMM VCO offset - should run for 20 - 30 min.
• Put FDD back in the ALS comm system.
• Done with test.  Relock IFO or begin maintenance or other activities.

(see attached plots) This looks like a typical response to a building temperature increase.  I'll check with Bubba G. 

Kiwamu reminded me that we started seeing this weird breathing noise between about 40-200Hz just at the beginning of our commissioning time today.  We're still not sure what it is, but I've double-checked that everything from commissioning time is put back to nominal positions (PR3 spot position from Kiwamu and Vaishali, ERM positions from Sheila and Heather, and ALS COMM FDD from me (although that shouldn't have anything to do with NomLowNoise) ). 

If DetChar or anyone has any thoughts on what this breathing noise might be, that would be helpful.  We're starting to run out of ideas....

The /ligo/www/www was incorrectly upgraded from an SVN 1.6 working directory to 1.8 several years ago, meaning that most CDS machines (which default to 1.6) could not perform any svn operations in this directory. FRS6119 was to revert this working directory back to a 1.6, while at the same time preserving all the non-version controlled data files which reside under this path. This task was complicated by the fact that we had conflicting files and one tree conflict between local modifications and the repo.

Here is the tortuous procedure I came up with

1. update the directory to include pending additions for files with  no conflict

2. commit local mods for files with no conflict

3. resolve the conflicting files and tree

All the above were done using svn-version1.8 on MacOS.

At this point the 1.8 working directory and the repo were synchronized. I then made the working directory a non-working-directory by deleting all the .svn meta directories.

Now, using svn-1.6, I checked out  /ligo/www over the top of this non-working-directory to make it a 1.6 working directory. But first I had to rename those files which are in the repo because checkout has a safety mechanism which prevents file overwriting.

TITLE: 03/02 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 51Mpc
OUTGOING OPERATOR: Travis
CURRENT ENVIRONMENT:
    Wind: 16mph Gusts, 12mph 5min avg
    Primary useism: 0.07 μm/s
    Secondary useism: 0.19 μm/s
QUICK SUMMARY: Range is a bit lower and there is some noise from 30-200Hz that is being investigated. Seems like everything was set back from the commissioning break, but perhaps something was missed.

TITLE: 03/01 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 55Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:  Locked in Observe until the 19:00-23:00 UTC commissioning break.  After the commissioning period ended, we locked back up without IA.  No issues with locking, but the range looks a bit low (~55 MPc since relocking).
LOG: 

19:00-23:00 Commissioning interlude

22:30-23:00 Jim to EY centering T240 in BRS enclosure

23:44 Observing

23:54 Out of Observe to run A2L

0:06 Back to Observe

[Kiwamu Izumi,Sheila Dwyer,Vaishali Adya]

Objective : Reproduce the measurements from 34389 with 'the' correct power normalization, investigate the most dominant beam jitter coupling mechanism into DARM

Method : We tried to move the PR3 spot position by moving the PRM in pitch and yaw and measured the coherence from the four channels of the BullsEye photodiode namely PIT,YAW,Beam Size and Sum into DARM.  The channels have now been named in accordance to what we expect to see ie. PIT=pitch, YAW=yaw, WID=beam size,SUM=sum.
We tried to go to configuration (B) where POP_A_PIT = -0.4, POP_A_YAW = +0.3, PRG = 32.5.  Upon doing that we also tried a new Configuration (D) where  POP_A_PIT = -0.03(original position before misaligning the spot), POP_A_YAW = +0.3, PRG = 29.

Results :

Key to the plots 1 and 3 : Blue =Low Noise, Green =configuration B, Red =configuration D

Plot 2 is just the coherences using IOP channels to monitor the high frequency parts(aka 4 kHz noise hunting)

plot 4 is the coherence between the BullsEye degrees of freedom

1. The broadband noise  and the slight elevation in noise between 200 Hz-1kHz was reproduced (see plot 3) with the peculiarity that pitch showed a distinct elevation (of about a factor of five) in comparison to the measurements from 34389 (see plot 1)
2. The coherence plots taken today seem to agree with the hypothesis that the broadband lump might indeed be from some form of beam jitter.
3. Upon going to configuration D we did notice that the coherence of PIT decreased only marginally from 0.6(green) to 0.5(blue)
4. Pitch signals didn't show high coherence with the SUM signal (see plot 4)

Next steps : 

• Calibration of the signals and calculation of the coupling coefficients
• Check whether this noise coupling entirely explains the excess noise in DARM

This lockloss was done on purpose for commissioning work.

JimW HughR

The first attachment is from late afternoon yesterday, before the winds started picking up.  There is still a large difference between it and the ISI GND STS below 100mHz.  This may be thermal equilibrating or maybe the masses need centering again.  I'll look at this today; must be done at EndY.

The second attachment is from early this morning with sustained 20mph winds; pretty steady direction from the SW to SSW. The coherence and spectra look much better with the greater input.

The third attachment looks at coherence to the BRS Tilt.  The coherence to the right is when the wind is low and to the left shows when the wind is high.  Bottom line: not much difference between the colocated sensor and the GND seismo on the floor.

   After relocking there was a SDF difference with the HPI-HAM2_IPS_HP_SETPOINT_NOW. Accepted the difference and went into Observing.