Today I attempted to find the short in the HV cable for the X2-8 BT ion pump (before proceeding with cutting off the extra cable length-unrelated task) as follows: 

I cut off the connector at the controller end and left the pump end connected to the pump.  I then connected the "Megger" (5000VDC @ 12mA) to the controller end of the cable and demonstrated that the short was still present.  I visually inspected the 100'+ excess cable for any obvious nicks or cuts (I did note one feature that looked like a clean incision or sharp slice).  I disconnected the pump end connector from the pump and let it hang in space -> No change.  Cable still shorted.  Finally, I cut-off the connector at the pump end and separated the conductors -> No change.  Cable short still present.  

Tomorrow I'll double check/inspect the run of cable that is in the HV raceway in the VEA and then proceed with cutting of the 100' extra cable length which will eliminate the incision "feature" previously noted and which I was going to do anyway prior to the appearance of the short.

Modified the ETM LVLN ESD Drivers (ECR E1500341):

1. Changed C32 in the monitoring amplifier from 1uF to 10nF to put the pole frequency at 4.244kHz
2. Changed C36 in the summing node from 1uF to 0.047uF to increase the dynamic range

EY Unit SN S1500066
EX Unit SN S1500073

Replaced the ESD AI chassis in SUS-C1 (EX/EY). New AI Chassis contains the PI Band Pass Filter D1500177. Cable H1:SUS_ESD-05 had to be re-terminated with a DB9 male connector to accommodate new AI front panel interface.
 
EY Old D1100815 Unit SN S1103824
EY New D1500177 Unit SN S1500300

EX Old D1100815 Unit SN S1103820
EX New D1500177 Unit SN S1500299

This should give a non-red state now for the VE unless something else is problematic so please respond to vacuum alarms.

The charge measurements for ETMX went well, but not great for ETMY. The measurement will loop through 5 times and we had almost finished the 2nd time when the SEI WD tripped and forced me to exit the running script, but I am not sure how good the data will be before the trip anyway. There wasn't enough time to run them again, so I tried to put back all of the settings differences, but I'm not 100% I did that correctly. I took screenshots, trended channels, and tried to mirror restored settings seen from the ending of the ETMX script. Hopefully it is all back where it should be.

I will post the plots in a few minutes from another computer.

(All Times UTC)

Turned out to be a fairly long Maintenance Day, but hope to be locking soon.  Maintenance Activities ended just before 0:00UTC (4pmPST).

• 15:15 Beam tube sealing on Xarm near EX (Chris)
• 15:43-16:09 Dust Monitor work (Bartlett)
• 15:43 LVEA Crane shimming/GATE VALVES CLOSED(Bubba)
• 16:10 HEPI fluid level check (Hugh)
• 16:25 Cleaning VEAs (C & K)
• 16:27-17:11 90MHz centering, swapping a whitening chasis (Richard)
• 16:30 wp5720Low Noise ESD (Fil)
• 16:32 update h1ecatc1 to add AsAmp90m channels (Patrick)
• 16:34-19:42 Fire Dept working at Auditorium
• 16:43 neg regeneration @EY (gerardo)
• 17:00 GRB (aka supernova) Maintenance Day TEST Alarm acknowledged
• 17:20 Main Crane went down.  Being repaired
• 17:40 PSL watchdog reset (Jason)
• 17:45 CP1 fill
• ----NO!---18:00 BS/PR2 Calibrate align sliders (ellie)----a few hours
• 18:00-19:00 EX compressor room (Kyle)
• 18:00 ISS Model change/test (Kiwamu)
• 18:10 Guoy phase measurement while gate valves closed (elli)
• 18:14 Battery check in LVEA (Joe D)
• 19:25 EX/EY fast computer install (Jim/Dave)
• 18:20 King soft on-site
• 19:20 Crane repair (Ken)
• 21:25 EX compressor work (Kyle)
• 22:30 Charge Measurements (EY attempted first, but SUS trippped.  ETMx completed.)  [TJ]
• Main crain appears to be operational.  Note that the trolley is on the south wall vs north wall.  

We decided to forego the ETMy Charge measurement this week, and Nutsinee will proceed with locking H1.

WP 5728, Dave, Jim, Carlos

Install newer "Fast" computers for h1susex, h1susey.  These are the computers which were briefly installed in July of 2015 and were removed because they caused timing, ADC, and IPC errors.

The BIOS parameters for the computers are set to the optimal default with the exception of hyperthreading is turned off, the computers are set to stay off on power loss, the CPU power profile is set to maximum performance, and the boot order is changed to only look for DVD or PXE boot.  Initially, a much more restrictive set of parameters was tried, which disabled nearly all of the features settable from the BIOS, but it was found the models wouldn't run.

We have done nothing to correct the timing, ADC, and IPC errors which were observed in July.  We are monitoring the error rate so we have a good baseline for possible fixes in the future.

Updated channel list for h1conlog1-master. Channel changes attached.

The slow controls SDF IOCs have been updated to a newer release.  It is running RCG from trunk at revision 4114.

The SDF IOCs are configured to load straight to the OBSERVE.snap file (skipping the safe.snap which we do not use).

Changes:

• Autodetection of channel types (eases sysadmin workload).
• Fixed a bug with revert that was discovered last power outage.
• Better precission in the saved snap files.
• Configured to load OBSERVE.snap.

With the precision changes I have accepted all numeric differences smaller than 10^-16.   These should not need to be accepted again until there is an actual change.

I ran BruCo on half a hour of data starting at GPS 1138960800. The full report is available here:

https://ldas-jobs.ligo.caltech.edu/~gabriele.vajente/bruco_1138960800/

Some interesting things:

• there's again significant coherence with DHARD_PIT at low frequencies. Maybe the P2L gains have changed again? It would be good to check if ETMY is again the culprit. If so, it might indicate something wrong with that suspension. Fig. 1
• SRCL and MICH seem far enough from the measured noise. Fig. 2
• some other angular degrees of freedom start to show (low) coherence, like CHARD_Y and SR2_Y. Fig. 3 and 4
• There is some (low) coherence at low frequency (mostly <15 Hz) with ISI-GND_STS_HAM5. Fig. 5
• The 1 Hz comb of lines is very well visible in many magnetometers, mostly PEM-EY_MAG_EBAY_SEIRACK. Fig. 6
• At the beam jitter periscope peaks, there is coherence with IMC degrees of freedom. Maybe it's time to optimze the IMC alignment. Fig. 7

Related: https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=25449

This morning Richard swapped the whitening chassis with the correct variant. Whitening seems to be working for all quadrants of 90MHz AS_A and AS_B.

WP 5727

Yesterday Daniel and I changed h1ecatc1 PLC2 to replace IscRfCSpareAmp[1] of IscRfCSpareAmp[1..5] with IscRfCAsAmp90m. This morning I rescanned PLC2 in the system manager and added the links for IscRfCAsAmp90mIn and the lost links for the remaining IscRfCSpareAmpIn (now IscRfCSpareAmpIn[1..4]).

IscRfCAsAmp90mIn.OutputMon linked to Corner Chassis 6 L1 Channel 4
IscRfCAsAmp90mIn.PowerOk linked to Corner Chassis 6 L3 Channel 4

IscRfCSpareAmpIn[1..4].OutputMon linked to Corner Chassis 6 L2 Channel 1..4
IscRfCSpareAmpIn[1..4].PowerOk linked to Corner Chassis 6 L4 Channel 1..4

The wiring diagram also needs to be updated to show that IscRfCTcsAom40mIn.OutputMon is linked to Corner Chassis 6 L1 Channel 3 and IscRfCTcsAom40mIn.PowerOk is linked to Corner Chassis 6 L3 Channel 3.

Since everything was restarted I burtrestored PLC1, PLC2 and PLC3 to 6:10 this morning local time.

I reset the PSL 35W FE power watchdog at 17:55 UTC (9:55 PST).

BS had saturation count of 712 & was RESET.

H1 was down overnight.

Observatory Mode was Preventative Maintenance when I arrived.  

A few activities were already started (beamtube sealing, dust monitor work, & crane work).  We also transitioned to Laser SAFE.

Now we other activities are starting to roll in.

All time in UTC

00:12 Kyle fill out CP3, then head to EY

00:20 Elli & Nutsinee to HAM6 to adjust AS Air camera

00:44 Robert to EY debugging seismometer

00:51 Kyle back from EY

01:18 Robert back

01:20 Robert head back to EY

07:50 Lost lock trying to engage ISS 2nd loop. Too tired to relock. Leaving the ifo DOWN for the night. Evan switched RF45 modulator to OCXO.

Note for Day Shift Op: There were two relocks during my shift, roll modes were high both times. Engage DC READOUT with caution. Maybe it's a good idea to hang out at BOUNCE_VIOLIN_MODE_DAMPING for a while?

Related: 20559, 19911

Summary

I remeasured the RFAM-to-DARM TFs for the 9 MHz and 45 MHz sidebands.

The 45 MHz measurement agrees with the previous result of ~0.1 mA/RAN. However, the 9 MHz measurement is also ~0.1 mA/RAN, which is a factor of 10 higher than what was measured previously. Note that the previous "9 MHz" RFAM measurement was really a simultaneous measurement of 9 MHz and 45 MHz RFAM, since we had no 45 MHz RFAM stabilization in place.

Details

For the 45 MHz measurement, I injected into the error point of the 45 MHz RFAM stabilization servo and measured the TF from the OOL RFAM stabilization detector (which is already calibrated into RAN) to the DCPD sum.

For the 9 MHz measurement, I temporarily replaced the OXCO with an IFR running at 9.1 MHz and +10 dBm. Then I used the spare DAC channel to inject into the IFR modulation port, which was set to 10 % deviation, dc-coupled (which means a RAN of 0.071 for 1 V of input, though I did not measure this directly). The signal from the spare DAC is buffered by an SR560 and sent back into one of the spare ADC channels. Then I measured the TF from the spare ADC channel to the DCPD sum. This measurement relies on the 45 MHz RFAM servo suppressing the resulting fluctuations in the 45 MHz sidebands before they are applied to the EOM; looking at the OOL readback, this seems to be satisfied below 1 kHz. Above 1 kHz, there is a RAN increase of <2 compared to no 9 MHz injection.

Templates live in my folder under Public/Templates/Osc/(45|9)_RFAM_2016-02-08.xml.

Per FAMIS request 4391, attached are oplev 7-day trends.