Jeff K, Sheila, Nutsinee, Dave (on phone)

We got a verbal alarm warning that TCS chillers are about to trip. On OAFIOP GDS TP screen -- ADC, DAC, IPC, and DK were red. We restarted the model following procedure from alog27435. For the record temperature goes down 0.1 C per minute, which gives us about 50 minutes to recover as soon as OAF crashed (Sorry Jeff, we probably could have waited until your measurement was finished). As soon as the model got restarted PI Mode27 jumped up and broke the lock. That part was unclear why.

CDS Overview

For each model, if their SDF diff count channel is greater then zero and the ALL button is pressed, an additional pink rectangle is displayed next to the red circle

DAQ Overview

while h1fw2 is running with a later version of frame-cpp, the 64 second frame file it writes should be 2 bytes smaller than fw0,1 frame. The RED/GREEN bars next to FW2 frame size will be GREEN,GREEN if this is the case. This modification has not been applied to fw0,1's comparison with fw2, so their bars should be GREEN,RED. The MD5 sums will always differ between fw0,1 and fw2 by an unknown factor.

MEDM snipet attached

24V was tied from CER power racks to junction boxes in LVEA. New 24V will power the following:

1. Photodiode amplifier units (Beckhoff terminals)
2. New ITM spool camera (to be installed, Beckhoff terminal)
3. BRS system (next to BSC3)
4. RGA installed next to HAM4
 

Cable run goes from CER mezzanine to junction box on top of SUS-R3 (next to HAM4). From this junction box, we split to junction boxes on top of SUS-R5 and SUS-R6. As of now, nothing on the floor is being powered off the new 24V line. New work permit will be required as certain items will need to be powered off.

Compressors #1 and #2 were greased and pressure tested @ X-MID station.
Compression test results:  #1 at 135 psi, and #2 at 130 psi.
All compressors and electrical motors were greased.

Both relief valves passed their test.

Both compressors were run tested after service was performed.

Work performed under WP#6309.

Today we took calibration measurements of both end station PCals.  See full reports attached if interested.  In summary, the newest calibration for EX looks good with the new RX/WS and TX/WS ratios being less than a tenth of a percent from the old values.  For EY, the ratios are ~0.5% from the old values.  Looking at the raw plots, there is some biased noise showing up from the WS and a very suspect shelf that comes and goes during separate measurements.  We would like to retake the EY measurements at the next availability since Darkhan and I believe that it is possibly due to a funky power source we have been using with the WS current amplifier (a 3-way extension cord with a power strip plugged in). 

Carlos set the BRS Beckoffs to run on the KVM display.  The display cables are right next to the GIGE cable coming from the BRS camera.  While the Y and X situation appeared different because Carlos restarted EndY but not EndX, neither system was working correctly as it would appear the camera data was not getting to the computer.

Patrick spotted this suttlety as the cable was sort of plugged in but not snapped/latched and had no indication of data stream.  Once these were secured, and the codes restarted, the BEAMs damped quickly and appear to be running normally.

DaveB feels this cable will likely work its way loose with any activity wiggling the connection and may be best to re-terminate the connector.

State of H1: made it locked in NLN

Assistance: Betsy, JeffK, Sheila, Richard

Activities: 

• visits to EY and EX for BRS
• some alignment was needed in Check MICH, PRMI, and then DRMI locked - JeffK, Sheila
• lock loss as shift change
• handing off to Nutsinee

Currently:

• Hugh at EX working on BRS
• Dave and Jim heading to EY to look at the computer

This morning, all corner station Oplevs were aligned. All suspensions utilizing OpLevs were all aligned and witness sensors trended and returned back to a good, locked, position.

There was a bit of an issue with the BS. It seems that after alignment is executed there's some discharge from the positioner upon disconnecting that causes a predtty moderate 'kick' in pitch which causes the centroid to NOT return to the previously zeroed position, sometimes by as much a 10µrad.  Jason and I tried also tried with AC power connected and disconnected. This did not seem to have any affect either way. I also tried just leaving everything in a good centered place and leaving everything connected. After a while there was some drift in pitch of about 2-3 µrad.  It's when the PIT/YAW or hand controller module is disconnected is when this effect occurs.

The positioner has been taken into the EE lab for investigation into some dicharge that may be occuring. This work permit will remain open until the End stations can be re-aligned

Attached are the ~weekly ETM charge measurement trends with today's data appended.

Both ETMs have mostly near-zero charge now on all quadrants (plus or minus a quadrant)...

State of H1: issues are preventing lock

Current Issues:

• BRSX - on, rung up, and not damping
• BRSY - Beckoff issues, dead

Activities since the end of Maintenance:

• OAF restarted
• DAQ restarted
• TCS restarted, now ok
• Initial alignment was done, with some dificulty, but did complete
• locking has not yet made it past Check IR
• currently troubleshooting in the CR
• currently Hugh and Patrick heading to EY to fix BRSY, then heading to EX to work on BRSX

State of the Site:

• winds are below 5mph
• useism is above 0.5, around 0.6-0.7

Activities up to 19:41UTC: all times UTC

• 15:00 - Rick, Peter, Jason, Kiwamu, psl mode matching / alignment
• 16:00 - Jim - OAF restart for TCS electronics hardware
• 16:03 - Bubba, John - LVEA - water check
• 16:15 - Ed - Oplev centering in LVEA
• 16:25 - Fil, Alfredo - LVEA 24V cabling
• 16:26 - Karen, Christina - EY, EX - cleaning
• 16:27 - Travis - EX pcal
• 16:29 - BRS off
• 16:34 - Carlos - WP6307
• 16:43 - TCS restarted - issues due to no connection for analog signals
• 16:54 - Hugh - EX SEI, de-isolating/re-isolating ISI and HEPI
• 17:11 - Joe - LVEA, battery check
• 17:11 - Richard - restarting both TCS chilllers
• 17:27 - Jonathan - working on frame writer 2
• 17:40 - Betsy - charge measurement on EY
• 17:57 - TCS is back
• 17:57 - Dave - EX PEM restart
• 17:57 - Karen back
• 18:20 - Hugh - from EY to EX
• 18:20 - Travis - back from EX, pcal
• 18:22 - PSL testing output, needs max power, 61.876 requested at this time = 40.6W
• 18:22 - Daniel - working on dark offsets
• 18:22 - Daniel - closes shutter between PSL and HAM1
• 18:34 - Greg - WP 6308, DMT update
• 18:35 - Travis, Sudarshan - EY, pcal
• 18:46 - PSL done, laser power back down to 2W
• 18:58 - OAF dies, TCS issues, being worked on
• 18:59 - PSL work is done
• 19:04 - Daniel - LVEA, PMC servo work, electronics
• 19:06 - Gerardo to MX, VAC
• 19:08 - Alfredo to EX
• 19:19 - Hugh - done at EX
• 19:36 - Alfredo back from EX
• 20:00 - Vern - LVEA, tour
• 20:18 - Travis - back from EY

Just to clarify Robert's work last weekend (alog 31243), he has confirmed that the CPY pitch should be set to -150.  I've written this to the SDF DOWN snap file.

P. King, R. Savage, J. Oberling, Yuki

This morning we went in and tweaked up the PSL in advance of LHO's entrance into ER10 next Tuesday.  The main activity was to improve the mode matching (MM) to the PMC, although the beam alignment into the FSS RefCav was also tweaked.  The ISS was turned OFF for the duration of this work.

PMC Mode Matching

Before tweaking the position of the mode matching lenses (L02 and L03), the PMC visibility was measured:

• Locked: 1.365V
• Unlocked: 0.425V
• Visibility: 68.9%

Since L02 was butting up against the mount for M37, M37 had to be moved out of the way; M37 is the final turning mirror in the path that dumps the 1st order diffracted beam from the ISS AOM into the beam dump immediately to the right of the DBB enclosure (see D0902114 for a layout of the PSL table).  This beam path was then realigned so that the 1st order diffracted beam was still dumped in the same beam dump.

The power into the PMC was then turned down using the high power attenuator immediatly after the HPO to ~40W incident onto the PMC (in hindsight we should have done the mode matching at the full HPO power, more on this below).  Lens L02 was then moved ~1cm closer to the ISS AOM (this was a gross movement along the rail the MM lenses are mounted on, not a fine move with the lens mount's micrometer), the beam was realigned into the PMC and the visibility was measured; visibility came in at 89.5%.  At this point we took a micrometer reading from the micrometer attached to the MM lens mounts as a starting point for fine tuning.  We moved the lens a few times, realigning the beam into the PMC and measuring the visibility each time.  The results are summarized in the below table (the larger the micrometer reading, the closer the lens was to the ISS AOM):

The MM lenses were left in the final position indicated in the table.  In summary we moved L02 by 21mm and L03 by 1.68mm, both moved closer to the ISS AOM.

We then increased the power to maximum and measured the visibility of the PMC at 81.5%.  This difference was unexpected.  The PMC incident power was then lowered to ~50W and the visibility was measured to be 89.6%.  What we think is going on is that at higher powers the ISS AOM is heating up and distorting the beam, which changes the MM into the PMC.  This is why I said above that in hindsight we should have done the MM at the maximum power incident to the PMC. 

Running out of time and wanting to keep as much of the MM improvment we had made as we could, we decided (after consulting with Daniel) to lower the power incident to the PMC to ~80W; this gives ~67W transmitted by the PMC.  To make up for the lost power (we were previously transmitting ~100W through the PMC), we asked Travis (who was watching the operator station) to request "Max Power" from the PSL rotation stage; the max power was reading ~40W.  We then used IO_MB_HWP1 to return the power available to the IFO to ~63W; with the ISS ON and diffracting ~3.5% this results in a maximum of ~62W available to the IFO, which is close to what we had before lowering the PMC incident power.  We then measured the visibility of the PMC with this new incident power (with the ISS OFF):

• Locked: 0.118V
• Unlocked: 1.35V
• Visibility: 86.7%

We left the PMC in this condition and should be sufficient for ER10/O2.

FSS Reference Cavity

The beam alignment into the FSS RefCav was tweaked.  In addition, because of the PMC changes mentioned above the half-wave plate WP4 was adjusted for maximum incident power onto the RefCav.  This gave us a voltage on the RefCav TPD of 4.2V, which is pretty close to where it's been sitting since we turned the HPO on in April.  The FSS was left in this condition and should be sufficient for ER10/O2.

HPO Pump Diode Currents

With time running out for the maintenance period, we decided not to increase the pump diode currents.  They should be good where they are for the duration of ER10 and O2a, but will probably need to be tweaked up before the start of O2b.

Other Miscellanea

Peter measured the AC voltage difference between the PSL table top and AC power ground; this was measured at 108 mVAC.  He also measured a 19 mVDC voltage difference between the PSL table top and the ISS AOM driver (the driver sits on the Southeast corner of the PSL table).

We left the PSL enclosure with all PSL subsytems locked and operational.  We turned off both Mac Minis in the laser room, as well as the Mac in the anteroom, as is required for Engineering and Observing runs.  Should anyone do any work in the PSL enclosure that involves turning these computers back on, please be sure to shut them down when you are done.  This closes out LHO work permits 6300 and 6301.

During a discussion of whether the SDF differences counts should be considered as a factor to whether the IFO is in observation mode, Hugh made the observation that the difference count can be changed by the user when switching between the MASK/ALL channel display filter.

For example, if a system has four channels with differences, three of which are monitored and one which is not, then the difference counter is normally 3 (display button defaults to the MASK setting). But if the user presses the ALL setting, the difference count increases to 4. In this example if the monitored channels were made to have zero differences, then pressing the button to ALL would cause the difference count to become non-zero.

Jamie's SDF MEDM alerts the user to this by highlighting the pink indicator if ALL are being displayed. I will follow suit and mark a non-zero SDF-DIFFs as: PINK if ALL chans are displayed, RED if monitored chans are displayed. Note that PINK does not necessarily mean non-monitored channels have differences, just that there is a possibility that this is the case.

WP6287 Add PEM ADC card to h1oaf0

Jim, Dave, commissioning

this turned into a large task. Please see alog 31316 for details. Currently the ADC card is in the chassis and we are not seeing any errors. We will monitor for any recurrence of ADC/DAC errors on this system, or nf_conntrack table errors.

WP6295 Add PEM-EX chans to DAQ for ESD-PS monitoring

Ansel, Robert, Dave

h1pemex was modified to add three test ADC channels to the DAQ at 2048Hz.

WP6303 Run later version of Frame-cpp on DAQ FW2

Jonathan,

as a test of using frame-cpp version 2.5.2 in the DAQ, the new version is being tested on h1fw2. This is the latest version supported by Ubuntu-12. It does have the leap-second modification needed for 31Dec2016.

WP6307 Add BRS Beckhoff computers to CDS KVM

Carlos

The new Beckhoff branded BRS computers at EX and EY were added to the KVM so we don't need to support an additional monitor, keyboard and mouse. These computers do not have an on/off switch, so we are unable to stop them booting up when power is restored after an outage.

WP6306 Update Hartmann Wavefront Sensor channels into DAQ

Kiwamu, Nutsinee, Dave

I have updated the H1EDCU_HWS.ini file now all four hws systems are running the new python code. Starting with the EPICS database file, I made a list of non-string channels (i.e. binary and analog channels).

Interestingly ITMX was found to be missing 14 channels which appear in the other systems. These channels have ITMM in their names. After discussion with Kiwamu and Nutsinee we decided to remove these from the ini file for now.

DAQ Restart

Jim

DAQ was restarted to: add ADC to h1iopoaf0, add chans to h1pemex, add new H1EDCU_HWS.ini.

With the higher sideband power we were limited to ~2 kHz ugf in the PMC with the lowest gain settings. Today, we changed resistor R19 to 4.75K from 1.21K which reduced the electronics gain by about 2.

While having the servo board in the shop we check R16/R17 which are 9.09K/1.00K rather than the 19.6K/1.00K indicated in the schematics. This explains the gain mystery described in alog 31120. The calibration of the slider has been changed is now accurately going from 0dB to 40dB.

We measured the transfer function with 0 dB, 12 dB and 22 dB of gain. The servo goes unstable at 25 dB, so 22 dB should be the maximum used. The ugf was around 1.1 kHz, 3.2 kHz and 9.4 kHz, respectively.

The reason we are not able to go below 1 kHz ugf is todays PSL change which improved the mode matching into the PMC and increased the optical gain (maybe by a factor of 2).

The online h(t) pipeline has been restarted at LHO, following a software upgrade to gstlal-calibration (see https://versions.ligo.org/cgit/gstlal/tag/?h=gstlal-calibration-1.0.7-v1 and Redmine issue https://bugs.ligo.org/redmine/issues/4813#change-20027). We are applying a coherence uncertainty threshold of 0.004 for the online calculation of kappas, which is consistent with behavior observed during recent lock stretches (see the figure attached).

This update adds six new channels containing kappa values not gated by the calib_state_vector or by coherence uncertainties:

Note, the filters have not been updated for this pipeline restart. We are still using the filters documented in this aLOG: https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=30210.

	[IFO]:GDS-CALIB_KAPPA_A_REAL
        [IFO]:GDS-CALIB_KAPPA_A_IMAGINARY

	[IFO]:GDS-CALIB_KAPPA_A_REAL
        [IFO]:GDS-CALIB_KAPPA_A_IMAGINARY

I have rebuilt daqd fw on h1fw2 using a new ldas-tools build (2.5.2).  This is the version in use at LLO and contains updated leap second tables.

The plan is to compare the output from h1fw2 to h1fw0 and h1fw1 for a week and then migrate h1fw0 and h1fw1 to use the newer framecpp releases next week.

In the mean time the daq status page will show differences in the frames between h1fw2 and the other frame writers. This is due to framecpp encoding a different version string in the frame file.  Dave will update the daq overview screen to help minimize the differences.

This is under workpermit 6303.

J. Kissel, D. Tuyenbayev

Following preliminary results from Darkhan on the individual actuation strength of the UIM and PUM stages for H1SUSETMY (see, thus far LHO aLOG 31275), and the current delightfully long lock stretch with them in place, I'm bringing this study to a close. I've turned off the temporary L1 and L2 calibration lines at 33.7 and 34.7 Hz, respectively. We do not intend on turning on these lines again for the duration of the run.

These lines were turned OFF at Nov 07 2016 21:21:49 UTC.