Laser Status: SysStat is good

Front End Power is 34.78W (should be around 30 W)

Front End Watch is GREEN

HPO Watch is GREEN

PMC: It has been locked 0.0 days, 2.0 hr 12.0 minutes (should be days/weeks)

Reflected power is 34.32Watts and PowerSum = 135.1Watts.

FSS: It has been locked for 0.0 days 1.0 hr and 27.0 min (should be days/weeks)

TPD[V] = 3.682V (min 0.9V)

ISS: The diffracted power is around 4.339% (should be 5-9%)

Last saturation event was 0.0 days 1.0 hours and 27.0 minutes ago (should be days/weeks)

Possible Issues:

Dave, Kiwamu, Nutsinee

--------------------------------------------------------------------------------------------------------

Quick conclusion: It's probably related to the CO2Y rotation stage.

Lengthy details: Dave notcied TCSY chiller DAC output went crazy yesterday. After making sure that it wasn't the model update (alog30429, alog30384) that did it we investigated further. The crazy output to the chiller was due to TCS guardian trying to lock the laser when there were no laser (as the result the guadian keeps increasing and decrasing chiller temperature by about 1 deg C).

The cause of CO2 laser trips was due to RTD/IR ALARM interlock tripped, which always coincide with either power-up state and lockloss state. Although not every power-up or locklosses caused CO2Y to trip. We also looked at POP but it's not showing here.

This immediately made us think of the CO2Y rotation stage that would only move during these times. Could this be either Beckhoff or electronics issue? The fact that it actually tripped the interlock box made me think of grounding issue. But I always blame grounding.

Also Kiwamu was able to untrip the RTD/IR interlock and get the CO2 into "ready" state just by toggling LASER ON/OFF button. This is what we don't understand. How is this even possible?

The End.

Tried the new feedforward path, adding the DBB Q1Y signal to the DARM IN1 signal. It's working.

First, I measured the transfer function from Q1Y to DARM (no noise injection), and fitted it. The result is shown in the first figure (I removed from the fit the 2kHz sharp feature which is clearly a misfit artifact). The filter is implemented in the LSC-JITTERFF bank.

The second plot shows the improvement in the DARM signal and the reduction of coherence whe the feedforward is on (blue reference with FF off, red with FF on). All the peaks remaining in the DARM signal are not due to the HPO jitter.

We shall see how stable this is over time.

A temporary MEDM screen for the jitter feedforward can be found here

/opt/rtcds/userapps/release/isc/h1/medm/JITTER_DBB_FF.adl

It's been linked to the LSC menu in the sitemap.

The model modifications are described in 30412.

On Tuesday 11th October we installed the ITMX and ETMX hardware watchdog chassis (HWWD) in monitor mode, which completes the install of the four HWWD chassis.

Previously we had found that the ITMY HWWD reported LED-current-monitor undervoltages which were not been seen on ETMY. In the past 24 hours we have now seen similar events on ITMX, which suggests the longer cabling to the ITM systems may be a factor.

For the past 20 hours, I plotted the ITMX HWWD LED-current-monitor status against an OSEM coil drive signal (I chose top stage F1 as a representative example). There is a clear correlation between coil drive activity and the detection of a low voltage on the LED-current-monitor as seen by the HWWD (shows up as STAT_OUT = 8). I've attached two plots, one showing the two signals separately, on the other I have scaled the coil drive signal to a compatible Y-axis scale and plotted them together.

State of H1: locking, some issues with PI, with Tara's fix H1 is going to Nominal Low Noise

Assistance:  Tara, Jenne, (Richard, Jason, earlier today)

NOTE:  If TCSY tripps off, please call Kiwamu or Nutsinee before restarting, they are hunting errors, so need to see the system before restart

Activities:

• Chandra MY CP4 work - red on VAC overview and in alarm
• Gabriele H1 alignment investigation
• Tara PI mode 26 changed, and damping wasn't working, she fixed, see her alog
• I set the ALS wrong polarization for Y and X arms  - see my alog, and comment
• Once aligned, locking H1 has gone well up to DC readout, then PI modes need to be watched

Currently:

• Gabriele and Jenne working on alignment and offsets

Not much IFO up time so far, but this morning I managed to move SRM in both pitch and yaw, and see a reduction of the noise. I recall this was already know. Moving pitch by about +20 urad seems to give the best position. Also the SRC1_P error signal respond quite well to the motion, and it seems to cross zero at the right position. Also, after SRM pitch is aligned, the SRC1_Y error signal repond to yaw motion of the SRM. So it looks like we should be able to close SRC1 both P and Y, although with small bandwidth.

The attached plot shows:

• first row: BLRMS of the "jitter noise";
• second row: the offsets I was adding to SRM alignment
• third row: SRC1 error signals.

With new thermocouple installed inside vertical section of exhaust pipe, I overfilled CP4 today. TC registered LN2 with very little forewarning. Temp fell to -60 deg C with LN2 trickling out exhaust (bypass exhaust valve open and check valve removed).

1:30 pm local

Took 20 sec to overfill CP3 with 1/2 open on bypass LLCV, but found the entire exhaust line frosted over with a pile of snow on ground. Looking back at last year's LLCV level after a Dewar fill, I decided to lower the LLCV yet again from 17% to 16%. 

Left bypass exhaust valve open.

• Y arm in green wouldn't lock because the wrong polarization was greater than 20.
• Jenne walked me through the procedure to adjust the polarization.
• The Y arm wrong polarization was reduced to 0%, the X arm wrong polarization was at 12% and was reduced to 4%.

I added a second class to (userapps)/sys/common/guardian/cdslib.py for the Beckhoff FEs. This will look through the autoburt.req's that are created upon build, and find the DCUID from the model name, or vise versa. Code is loaded in and committed and the diffs are being reported.

[Jenne, Cheryl, Nutsinee]

We tweaked the calibration of the PSL rotation stage, which hadn't been done since the power incident on the rotation stage was adjusted about a week ago.  Now hopefully a 50W request will give us 50W, rather than some higher value.  Nutsinee has her script ready for next time, so we can try doing it automatically rather than by hand.

State of H1: locking and has made it to Low Noise

Activities:

• early AM, locked from Ed's shift, Gabriele working on alignment
• lock loss
• TCSY laser tripped, Richard and Jason get it back, Jason had to reset electronics to clear a FLOW FAULT
• locking not good until TCSY was back on for 20-30 minutes
• TJ covered for about an hour
• handled and H1 alignment issues
• ushered H1 to DC Readout
• damping since bounce and roll rang up, mode 26 rang up
• I return
• H1 to Low Noise and mode 26 killed the lock
• ALSO power from the PSL was 55W, not 47W as requested, which contribulted to H1 issues
• after lock loss requested 2W power out of the PSL was reading 2.4W, which explains the 54W lock
• Jenne recalibrated the rotation stage by hand, Nutsinee has a script modified if we need ot do again, needs a bit more documentation
• back to DC Readout, mode 26 still an issue, waiting here for it to ring down, and also Tara is looking into damping it faster

Other Site Activities:

• Christine to MX
• Chandra to MY, CP4
• Kyle / Joe past card reader to turn on canister for DI water

I have created new DAQ and HWWD oveview screens. The DAQ displays the additional diagnostics information Jonathan's new code produces. The HWWD includes the ITMX and ETMX systems which were installed yesterday, and shows which systems are connected to the ISI coil drivers.

I added 250mL of water to the TCSy chiller this morning, bringing the reading on the scale from 4.5 to 9.0.

In addition, the TCSy CO2 laser tripped out this morning on a flow alarm.  Peter and I reset the laser box (key off, then key on) to clear the alarm and restart the laser.  Cheryl had trended the flow channel for the CO2 laser and indeed the flow dropped to zero and recovered (I don't have the trend, perhaps Cheryl will post it later).  Maybe an air bubble working its way through the system?

J. Kissel

I've used Kiwamu's templates (LHO aLOG 29860) to gather new DARM OLG and PCAL2DARM transfer functions, to help increase the number of data points for darm coupled cavity pole and SRC detuning spring frequencies. In doing so, I've found that PCAL suggests that CAL-DELTAL_EXTERNAL is wrong low by ~20% above 50 Hz, in a frequency dependent fashion (confirmed by the phase and ridiculously high coherence). 

We will analyze the data in-full, and report what the measured pole and spring frequencies are in the morning. We'll also show trends of calibration line heights, such that eventually we can confirm the frequencies over time.

This frequency dependent error in CAL-DELTAL_EXTERNAL may be because the DARM coupled cavity pole frequency programmed into the CAL CS fron end is 342 Hz, and that's just not correct for this lock stretch. We have to turn OFF the PCALY calibration lines during the measurement due to range issues, but the front end calculation of the DARM cavity pole, after the measurement, suggests anywhere for 315 Hz to 340 Hz. Unclear whether we can trust the online calculation just yet, so we're leaving the IFO alone for ~30 minutes after the measurement to be able to confirm offline later.

Recall that we're still not controlling the cavity waist angle/translation of the SRC entirely: the SRC1 loop (nominally controlling SRM alone) is OFF, but the SRC2 loop (controlling SRM and SR2) is ON.

Undisturbed time post-sweeps:
Start    Oct 11 2016 02:36:00 UTC   Oct 10 2016 19:36:00 PDT  1160188577
Stop     Oct 11 2016 03:07:00 UTC   Oct 10 2016 20:07:00 PDT  1160190437
 
The new measurements have not yet been exported, but have been committed to the CalSVN here:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER10/H1/Measurements/
DARMOLGTFs/2016-10-10_H1_DARM_OLGTF_4to1200Hz.xml
PCAL/2016-10-10_H1_PCAL2DARMTF_4to1200Hz.xml


EDIT: I've added two screenshots showing the digital settings relevant to the DARM loop parameters. Unfortunately, the production conlog is down for maintenance/upgrades, but thankfully Patrick setup a test bed a few nights ago (goto http://conlog-test-replica/), I was able to pull the list of channels I needed. FAlso for the record, some of those channels have changed since O1, so I quote the new list here for easier copy and paste in the future: 
H1:LSC-DARM1_SWSTAT
H1:LSC-DARM1_GAIN
H1:LSC-DARM2_SWSTAT
H1:LSC-DARM2_GAIN
H1:SUS-ETMY_L1_LOCK_L_SWSTAT
H1:SUS-ETMY_L1_LOCK_L_GAIN
H1:SUS-ETMY_L1_DRIVEALIGN_L2L_SWSTAT
H1:SUS-ETMY_L1_DRIVEALIGN_L2L_GAIN
H1:SUS-ETMY_L2_LOCK_L_SWSTAT
H1:SUS-ETMY_L2_LOCK_L_GAIN
H1:SUS-ETMY_L2_DRIVEALIGN_L2L_SWSTAT
H1:SUS-ETMY_L2_DRIVEALIGN_L2L_GAIN
H1:SUS-ETMY_L3_ISCINF_L_SWSTAT
H1:SUS-ETMY_L3_ISCINF_L_GAIN
H1:SUS-ETMY_L3_LOCK_L_SWSTAT
H1:SUS-ETMY_L3_LOCK_L_GAIN
H1:SUS-ETMY_L3_DRIVEALIGN_L2L_SWSTAT
H1:SUS-ETMY_L3_DRIVEALIGN_L2L_GAIN
H1:SUS-ETMY_L3_LOCK_INBIAS
H1:SUS-ETMY_L3_ESDOUTF_LIN_BYPASS_SW
H1:SUS-ETMY_L3_ESDOUTF_LIN_FORCE_COEFF
H1:SUS-ETMY_BIO_M0_STATEREQ
H1:SUS-ETMY_BIO_L1_STATEREQ
H1:SUS-ETMY_BIO_L2_UL_STATEREQ
H1:SUS-ETMY_BIO_L2_LL_STATEREQ
H1:SUS-ETMY_BIO_L2_UR_STATEREQ
H1:SUS-ETMY_BIO_L2_LR_STATEREQ
H1:SUS-ETMY_BIO_L3_UL_STATEREQ
H1:SUS-ETMY_BIO_L3_UR_STATEREQ
H1:SUS-ETMY_BIO_L3_LL_STATEREQ
H1:SUS-ETMY_BIO_L3_LR_STATEREQ

Evan, Daniel

17:12:30 UTC Oct 7 2016:

• RF modulation off for 9 and 45 MHz
• 45 dB whitening gain compensated by a filter gain of 0.0056
• 1 stage of whitening, compensated
• V/ct filter engaged, referred to TNC ouptut of 2-chn demod board
• Dark

17:16:30 UTC Oct 7 2016:

• same input configuration
• 29 mA of photocurrent

17:18:30 UTC Oct 7 2016:

• turn DC centering of REFL WFS on

17:24:30 UTC Oct 7 2016:

• turn DC centering off again
• 14.8 mA of photocurrent

17:32:00 UTC Oct 7 2016:

• 9 MHz modulation on
• 14.8 mA of photocurrent
• DC values: 9I = 3.7 mV; 9Q = 9.5mV

17:34:30 UTC Oct 7 2016:

• 9 MHz modulation on
• 29 mA of photocurrent
• DC values: 9I = +7.2 mV; 9Q = +18.1mV

18:06:30 UTC Oct 7 2016:

• 9 MHz and 45 MHz modulation on
• 29 mA of photocurrent
• DC values: 45I = –14.3 mV; 45Q = +62 mV