I put a camera on the HAM2 West door, which looks at CW1, the back side of the wedge, which is carefully aligned to shoot through the IM1 tower.

This week I developed a procedure to use PRM with a single bounce, to move the REFL beam on CW1, and and look for clipping.  The procedure revealed that when PRM is in it's aligned position plus an additional 200urad in yaw, there's an increase in light on the baffle, consistent with the REFL beam starting to clip.  With PRM at -1000urad, the REFL beam is clearly seen on CW1 to thr right of the main input beam.

Using the image and a beam path simulation I wrote in matlab, I've measured the main input beam to be between 2mm and 3mm from center.

I need to adjust my HAM2 top camera to improve the view of the IO Faraday output side, which is planned for next Tuesday, in order to realign through the Faraday, to correct the mis-centering at both the input and output Calcite Wedges.

compared to the main input beam, which I've used to identify the location of the main input beam on the wedge.  A diagram and images attached.

Danny, Craig, Koji, TVo

We were hoping to run an SR3 Heater measurement and track the DARM cavity pole but we've been running into locking issues with microseisms at just under 1 um/s and winds around 30 mph.  At first there seemed to be some of those high frequency glitches in both ALS systems but they went away when we played with the TMSs (maybe it's a coincidence).

We manually aligned DRMI to get POP18 ~65 counts and POP90~15 which is the build-up levels we "normally" get but when we engage the ASC after locking DRMI 1f it pushes the beamsplitter till we lose lock which happened a couple times until we stopped at DRMI_LOCKED_PREP_ASC and manually tried to zero the MICH error signal, this seemed to help.  We were able to get up to NLN for maybe 15 minutes but ASC  rang up which I'm not able to tell which mode is starting it.  This makes our measurement hard because we were trying to wait for the IFO to reach thermal equilibrium (or at least 20-30 minutes) before turning on the SR3 heater.  We got back to NLN but lost it again with a relatively fast lock loss, I'm reminded of Craig/Koji's measurement of the PRCL UGF being closer to 30 Hz which might make it go unstable given our high useisms.

TITLE: 01/17 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    Wind: 11mph Gusts, 9mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.74 μm/s
QUICK SUMMARY:  PSL encoursion for FSS invest., visit to vault for PEM, DAQ restart

• 17-01-19 11:53 - 15:09  PeterK to PSL, FSS evaluation
• 17-01-19 18:23 Karen back from MY and MX
• 17-01-19 18:44 TJ to LVEA - looking for TCS spare parts
• 17-01-19 18:45 Terry to HAM6 to clean fibers
• 17-01-19 19:39 DAQ restart, second trends out from 19:39 to 19:49
• 17-01-19 21:50 Fil and Marc to the vault
• 17-01-19 22:10 Hanford Fire Department here for LPT at EX
• 17-01-19 23:17 Gerardo to EX to visit solar cell
• 17-01-19 23:17 Gerardo to MX to retrieve parts
• 17-01-19 23:17 Marc and Fil back from vault

OPS Maintenance:

• VAC Alarm for PT527 can be ignored for now - low battery from solar - Chandra
• on the OPS checksheet, Dust Monitor Check is not running, a snapshot of the errors is attached

Filiberto C, Marc P, Robert S

We tracked the failure to an XLR cable that runs between the LEMI breakout black box and the FIBOX.  Upon inspection we found that the connector had two broken internal wires.  We repaired and reinstalled the cable and everything looks goodish.  There is still a 300Hz - 500Hz lump on the X channel which we hope will go away once the LEMI has a few days to warm up.  Attached is an image of the broken connector.

We verified that the lump originates upstream from the FIBOX.

For T240s:

Averaging Mass Centering channels for 10 [sec] ...
2019-01-17 15:24:39.368344

There are 5 T240 proof masses out of range ( > 0.3 [V] )!
ETMX T240 1 DOF X/U = 0.357 [V]
ETMX T240 1 DOF Z/W = 0.319 [V]
ETMX T240 2 DOF Y/V = -0.539 [V]
ITMX T240 1 DOF X/U = -0.309 [V]
ITMY T240 3 DOF Z/W = -0.401 [V]

All other proof masses are within range ( < 0.3 [V] ):
ETMX T240 1 DOF Y/V = 0.273 [V]
ETMX T240 2 DOF X/U = -0.191 [V]
ETMX T240 2 DOF Z/W = 0.225 [V]
ETMX T240 3 DOF X/U = 0.262 [V]
ETMX T240 3 DOF Y/V = 0.222 [V]
ETMX T240 3 DOF Z/W = 0.245 [V]
ETMY T240 1 DOF X/U = -0.062 [V]
ETMY T240 1 DOF Y/V = 0.264 [V]
ETMY T240 1 DOF Z/W = -0.021 [V]
ETMY T240 2 DOF X/U = 0.018 [V]
ETMY T240 2 DOF Y/V = -0.059 [V]
ETMY T240 2 DOF Z/W = -0.04 [V]
ETMY T240 3 DOF X/U = -0.032 [V]
ETMY T240 3 DOF Y/V = -0.057 [V]
ETMY T240 3 DOF Z/W = 0.166 [V]
ITMX T240 1 DOF Y/V = 0.119 [V]
ITMX T240 1 DOF Z/W = 0.119 [V]
ITMX T240 2 DOF X/U = 0.147 [V]
ITMX T240 2 DOF Y/V = 0.148 [V]
ITMX T240 2 DOF Z/W = 0.235 [V]
ITMX T240 3 DOF X/U = -0.24 [V]
ITMX T240 3 DOF Y/V = 0.137 [V]
ITMX T240 3 DOF Z/W = 0.033 [V]
ITMY T240 1 DOF X/U = 0.201 [V]
ITMY T240 1 DOF Y/V = 0.142 [V]
ITMY T240 1 DOF Z/W = 0.159 [V]
ITMY T240 2 DOF X/U = 0.174 [V]
ITMY T240 2 DOF Y/V = 0.243 [V]
ITMY T240 2 DOF Z/W = 0.211 [V]
ITMY T240 3 DOF X/U = -0.065 [V]
ITMY T240 3 DOF Y/V = 0.21 [V]
BS T240 1 DOF X/U = -0.001 [V]
BS T240 1 DOF Y/V = -0.086 [V]
BS T240 1 DOF Z/W = 0.256 [V]
BS T240 2 DOF X/U = 0.061 [V]
BS T240 2 DOF Y/V = 0.238 [V]
BS T240 2 DOF Z/W = -0.037 [V]
BS T240 3 DOF X/U = 0.058 [V]
BS T240 3 DOF Y/V = -0.163 [V]
BS T240 3 DOF Z/W = -0.17 [V]

For STSs:

Averaging Mass Centering channels for 10 [sec] ...

2019-01-17 15:26:33.360168
There are 1 STS proof masses out of range ( > 2.0 [V] )!
STS A DOF X/U = -7.959 [V]

All other proof masses are within range ( < 2.0 [V] ):
STS A DOF Y/V = -0.885 [V]
STS A DOF Z/W = -0.314 [V]
STS B DOF X/U = 0.325 [V]
STS B DOF Y/V = 0.373 [V]
STS B DOF Z/W = -0.38 [V]
STS C DOF X/U = 0.314 [V]
STS C DOF Y/V = 0.257 [V]
STS C DOF Z/W = 0.603 [V]
STS EX DOF X/U = -0.077 [V]
STS EX DOF Y/V = 0.298 [V]
STS EX DOF Z/W = 0.236 [V]
STS EY DOF X/U = 0.315 [V]
STS EY DOF Y/V = -0.153 [V]
STS EY DOF Z/W = 0.649 [V]

I have been asked what would be the H1 range operating close to the best performance seen so far, with squeezing injected. Here I quantitatively improve my immediate answer ("not 120 Mpc"). 

I made a very simple projection by rescaling an approximate H1 shot noise model by 1, 2 or 3 dB of squeezing (I ignored radiation pressure here). To be clear: the squeezing projection doesn't rely on any loss model, I am only showing the improvement for these hypothetical levels of measured squeezing.

Data set: I used the Dec 9 "Holiday Party" data (200s starting at 2018-12-09T2:45UTC) assumed H1 was shot noise limited around 1 kHz and matched a gwinc model to shot noise. Jeff kindly provided the calibration to convert H1:CAL-DELTAL_EXTERNAL_DQ to strain (with some uncertainty ~10%). At that time SensMon was reporting 90 Mpc - gwinc on averaged data gives, as usual, 5% less range (~86 Mpc).

The plot shows a:

• 7% range improvement with 1 dB of hypothetical measured squeezing (~92 Mpc);
• 14% range improvement with 2 dB of hypothetical measured squeezing (~98Mpc);
• 22% range improvement with 3 dB of hypothetical measured squeezing (~104 Mpc).

J. Kissel, (and remotely, J. Betzwieser)
WP 8054

Joe had identified some further bugs in the user-developed code that conditions the time-dependent correction factors calculated in front-end calibration pipeline, namely:
 - the median-ing function,
    /opt/rtcds/userapps/release/cds/common/src/BUFFER_AND_MEDIAN.c
 - and the average-ing function,
    /opt/rtcds/userapps/release/cds/common/src/BUFFER_AND_AVERAGE.c
and their calls and parameters inputs to them in the TDEP block of the front-end code library part,
    /opt/rtcds/userapps/release/cal/common/models/CAL_CS_MASTER.mdl

Check out the details in LLO aLOG LLO aLOG 42794.

I've svn up'd the above mentioned codes and part, and have installed them, rebooting the h1calcs model. This did NOT require a DAQ restart. 

Stay tuned for confirmation of goodness (though Joe confirms that things look good at LLO after these changes).

Jenne Sheila

Summary:

We measured the RIN on the 9 MHz sideband 00 mode through the OMC, and see that it is about a factor of 10 higher than the RIN predicted by the RF AM monitor.  

Details:

The first time I tried this measurement, we were limited by the OMC DCPD dark noise 46197.  These are the steps we followed this time:

• engage 3 whitening stages + 18dB whitening gain on OMC DCPDs, measure DCPD dark noise with IMC offline (18:51 UTC Jan 17)
• Lock IMC at 2 W, request guardian to ISS_ON (we have to engage ISS before powering up, but can't DC couple it until we are powered up, don't use ISS_AC_COUPLED state)
• increase power to 30W using Power guardain
• ISS DC coupled
• Align IFO for single bounce, engage AS centering loops, OMC ASC
• reduced 45MHz modulation depth to 3.3dBm on driver, increased 9 MHz to 27dBm
• turn off OMC whitening (no filters, 0dB gain), and reduce OMC length dither line to 0 to take OMC scans to identify 9MHz modes
• turn dither line and whitening back on, lock OMC on 9 MHz mode
• measurement with no excitation: 19:25 UTC
• enable excitation on EOM driver, measurement with excitation at 19:31:59 UTC

The OMC DCPD signals (and dark noise) are calibrated into RIN here taking into account the extra 18dB of whitening gain.  The EOM driver channel is normally calibrated into RIN assuming that the drive level is 17dBm according to Daniel, so this is divided by 3 because we are using 27dBm out of the EOM driver here. 

The measurement with the excitation on shows good agreement between the RF AM monitor and the measured amplitude noise, so these calibrations are OK.  We also have OK clearance above dark noise and the intensity noise seen by the ISS. So there is some additional source of intensity noise on the 9 MHz sidebands.  

The STS seismometer located in the BRS enclosure at EY were added to h1pemey model. They have been top-named to retain their ISI subsystem association. The three channels were added to the DAQ at 256Hz acquisition rate

+: fast channel H1:ISI-GND_STS_ETMY_BRS_ENC_X_OUT_DQ added to the DAQ
+: fast channel H1:ISI-GND_STS_ETMY_BRS_ENC_Y_OUT_DQ added to the DAQ
+: fast channel H1:ISI-GND_STS_ETMY_BRS_ENC_Z_OUT_DQ added to the DAQ

h1pemey and DAQ were restarted.

TITLE: 01/17 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    Wind: 10mph Gusts, 8mph 5min avg
    Primary useism: 0.09 μm/s
    Secondary useism: 0.77 μm/s
QUICK SUMMARY:

• PeterK to PSL, FSS evaluation, 11:53 - 15:09 UTC
• Karen to MY and MX, back as of 18:23
• TJ to LVEA - looking for TCS spare parts
• Terry to HAM6 to clean fibers
• Currently: Sheila doing a single bounce measurements

Yasmeen Asali, Dave Barker, Jamie Rollins

We found two problems with the Timing System MEDM screens:

1. Yasmeen noticed that the Timing Master in READONLY mode will not display any of the fiber ports at the bottom. In EXPERT mode, the ports do display. Strangely, this is not a problem on the RemoteMEDM viewer. This should probably be fixed, though it is not a high priority obviously. Screenshots of one of the differences attached as well as a picture of the READONLY/EXPERT option button.
2. I noticed that the 1PPS summary pages still had the wrong labels. I fixed this in the MEDM macros but could not SVN commit due to permissions. If you could commit this, I'd appreciate it! (Attempted) commit message below:

Update 1PPS Second Labels in MEDM summary screens

The 1PPS Summary screens, accessible at the bottom of the Timing overview
MEDM screen (SYS_CUST_TIMING.adl), had incorrect descriptions for the
1PPS timing diagnostic signals. The following screens under the summary
button have been fixed:

MSR Comparator/Frequency Counter
CER Comparator/Frequency Counter
EX Comparator/Frequency Counter
EY Comparator/Frequency Counter
--This line, and those below, will be ignored--

M    SYS_CUST_TIMING_MSR_CFC_macro.txt
M    SYS_CUST_TIMING_CER_CFC_macro.txt
M    SYS_CUST_TIMING_XEND_CFC_macro.txt
M    SYS_CUST_TIMING_YEND_CFC_macro.txt

Ana, Yasmeen, Madox, Richard McCarthy

• 7:34am arrive at EX, look for gps antenna cable from roof in VEA
• We could not find antenna cable patch in VEA, though we do have the absolute timing delay measurement of 270' from the GPS clock to the rooftop antenna (calculated from a TDR measurement of ~215' at each end station with a velocity factor of 0.8). It would be great to get the actual cable type and length at some point, but it's not a top priority.
• 8am leave EX

Following on from yesterday's attempt.  I made transfer function and spectra measurements with the input modecleaner locked and
unlocked.  In summary, there wasn't too much difference in the noise spectra above 100 kHz with the input modecleaner locked
or unlocked.

    Attached are transfer function measurements when the input mocdecleaner was unlocked and locked respectively (IMCULKD1.tif,
IMCLKD1.tif).  The noise spectra measurements are IMCULN1.tif and IMCLN1.tif respectively.  The mixer calibration was measured
to be 1.93/77.4 V/kHz.

    More to follow ...

Koji, Craig

- We ran the RF9 modulation depth change test Sheila asked us to do.  Koji will post an alog about those results.

- Koji had me lock the OMC with PZT2 at only 2 volts, rather than the usual ~40 V, for +9MHz 9th order HOM considerations.

- We measured the PRCL OLG after full thermalization at high power, and got a 30 Hz UGF.  This seems much lower than what was reported by Jenne a week ago.

- I carried the laptop in with me as I made my way down to the PSL racks.  
This time, I was able to make it without causing a lockloss, but when I got there the SR785 GPIB was gone, and when going to get it from the squeezer bay, while walking between HAM2 and HAM3 I killed the lock.
The area directly in front of the door in the LVEA, between HAM2 and HAM3, is the most sensitive to walking around, according to IMC_F.  Stepping on the lower tier floor directly inside of the LVEA door seemed to produce the largest response in IMC_F, including during my first excursion to the PSL racks.

- We reached nominal low noise again, but lost it within ten minutes, probably due to some CHARD, DHARD pitch ringup.  

- We reach NLN a third time, and this time held it for two hours, during which I was able to get to the PSL racks and measure all CARM spectra.  We eventually lost lock due to a super slowly growing ASC 0.9 Hz oscillation (lost lock about an hour after the ringup started).

- Had to readjust TMSY alignment in pitch significantly to get the guardian to continue locking in FIND_IR.

Added a few filter modules to the ASC-OMC_A and ASC-OMC_B QPD segments to account for the calibration:

• FM5: "–12dB" is the inverse of the whitening gain
• FM6: "cts2V" calibrates counts into Volts 6.1035E-4
• FM7: "trans" goes from Volts to Amps and is the inverse of the transimpedance gain. The later is 2000Ω including the differential amplifier.
• FM8: "A2W" goes from Amps to Watts.
  • For an InGaAs diode at 1064nm this is 1/0.8 = 1.25.
  • For a silicon diode at 532nm this is 1/0.3 =3.333.
  • For a silicon diode at 1064nm this is 1/0.16 = 6.25.
• FM9: "milli" goes to mW (multiplies by 1000)

I did some injections on HAM1, for comparison with 42694 and 42722

I reduced the amplitude compared to 44856, so these excitations aren't showing up in DARM, but people can look for them in the REFL WFS and table top L4Cs.  

The Z excitation started at 2:11:50 UTC, was stopped after a large glitch at 2:23 UTC Jan 15th. 

The X excitation started at 2:27 UTC, but there were several large glitches.  a relative glitch free time was from 2:37-2:44, the excitation continued until 2:44 UTC. 

The Y excitation started at 2:55 UTC, and was on until 3:06.  We had to turn the dither lines back on partway through that because the PRC1Y was slowly going unstable.