J. Kissel, T. Sadecki

Travis and I have taken close out transfer functions of H1SUSMC1, H1SUSMC2, H1SUSMC3, H1SUSPRM, and H1SUSPR2. After some hiccups with PR2 (aLOG pending), all suspensions look great. Note, PRM TFs were accidentally taken with extra TEST P&Y misalignment gains on the excitation, which is why it appears to have errantly high response.

Excellent work team!! We're ready to finish this vent!!

The data templates live here: 
/ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/
    MC1/SAGM1/Data/2017-12-21_2155_H1SUSMC1_M1_WhiteNoise_L_0p01to50Hz.xml
    MC1/SAGM1/Data/2017-12-21_2155_H1SUSMC1_M1_WhiteNoise_P_0p01to50Hz.xml
    MC1/SAGM1/Data/2017-12-21_2155_H1SUSMC1_M1_WhiteNoise_R_0p01to50Hz.xml
    MC1/SAGM1/Data/2017-12-21_2155_H1SUSMC1_M1_WhiteNoise_T_0p01to50Hz.xml
    MC1/SAGM1/Data/2017-12-21_2155_H1SUSMC1_M1_WhiteNoise_V_0p01to50Hz.xml
    MC1/SAGM1/Data/2017-12-21_2155_H1SUSMC1_M1_WhiteNoise_Y_0p01to50Hz.xml

    MC2/SAGM1/Data/2017-12-21_2044_H1SUSMC2_M1_WhiteNoise_L_0p01to50Hz.xml
    MC2/SAGM1/Data/2017-12-21_2044_H1SUSMC2_M1_WhiteNoise_P_0p01to50Hz.xml
    MC2/SAGM1/Data/2017-12-21_2044_H1SUSMC2_M1_WhiteNoise_R_0p01to50Hz.xml
    MC2/SAGM1/Data/2017-12-21_2044_H1SUSMC2_M1_WhiteNoise_T_0p01to50Hz.xml
    MC2/SAGM1/Data/2017-12-21_2044_H1SUSMC2_M1_WhiteNoise_V_0p01to50Hz.xml
    MC2/SAGM1/Data/2017-12-21_2044_H1SUSMC2_M1_WhiteNoise_Y_0p01to50Hz.xml

    MC3/SAGM1/Data/2017-12-21_2155_H1SUSMC3_M1_WhiteNoise_L_0p01to50Hz.xml
    MC3/SAGM1/Data/2017-12-21_2155_H1SUSMC3_M1_WhiteNoise_P_0p01to50Hz.xml
    MC3/SAGM1/Data/2017-12-21_2155_H1SUSMC3_M1_WhiteNoise_R_0p01to50Hz.xml
    MC3/SAGM1/Data/2017-12-21_2155_H1SUSMC3_M1_WhiteNoise_T_0p01to50Hz.xml
    MC3/SAGM1/Data/2017-12-21_2155_H1SUSMC3_M1_WhiteNoise_V_0p01to50Hz.xml
    MC3/SAGM1/Data/2017-12-21_2155_H1SUSMC3_M1_WhiteNoise_Y_0p01to50Hz.xml

    PR2/SAGM1/Data/2017-12-21_2035_H1SUSPR2_M1_WhiteNoise_L_0p01to50Hz.xml
    PR2/SAGM1/Data/2017-12-21_2035_H1SUSPR2_M1_WhiteNoise_P_0p01to50Hz.xml
    PR2/SAGM1/Data/2017-12-21_2035_H1SUSPR2_M1_WhiteNoise_R_0p01to50Hz.xml
    PR2/SAGM1/Data/2017-12-21_2035_H1SUSPR2_M1_WhiteNoise_T_0p01to50Hz.xml
    PR2/SAGM1/Data/2017-12-21_2035_H1SUSPR2_M1_WhiteNoise_V_0p01to50Hz.xml
    PR2/SAGM1/Data/2017-12-21_2035_H1SUSPR2_M1_WhiteNoise_Y_0p01to50Hz.xml

    PRM/SAGM1/Data/2017-12-21_2155_H1SUSPRM_M1_WhiteNoise_L_0p01to50Hz.xml
    PRM/SAGM1/Data/2017-12-21_2155_H1SUSPRM_M1_WhiteNoise_P_0p01to50Hz.xml
    PRM/SAGM1/Data/2017-12-21_2155_H1SUSPRM_M1_WhiteNoise_R_0p01to50Hz.xml
    PRM/SAGM1/Data/2017-12-21_2155_H1SUSPRM_M1_WhiteNoise_T_0p01to50Hz.xml
    PRM/SAGM1/Data/2017-12-21_2155_H1SUSPRM_M1_WhiteNoise_V_0p01to50Hz.xml
    PRM/SAGM1/Data/2017-12-21_2155_H1SUSPRM_M1_WhiteNoise_Y_0p01to50Hz.xml 

Evan G., Rick S.

We transitioned the EY VEA to laser hazard and then turned on and unshuttered the EY Pcal laser (previously turned off before the Thanksgiving break). Next we checked the positioning of the two beams on the receiver module relay mirrors. The outer beam mirror required more adjustment than the inner beam mirror. The positioning was adjusted to center the Pcal beams and both beams were aligned to the center of the integrating sphere aperture. After this procedure, we shuttered the laser, turned it off, and transitioned the EY VEA back to laser safe. This work was done in preparation for the EY vent to take place in January.

We did not have any ITM OPLEV data from the 2014 vent/pump down because gatevalves were closed and blocking beams at just the correct times.  Today, I tried to trend the ITM OPLEV data from the vent this last Sept.  Of course, there had been a power outage the weekend before the Monday vent (Sept 18, alog 38708), which blinded us from actually being able to "watch" the wobble of the ITMs during the vent since they had glitched/died and didn't come back up until Tuesday.  Foiled again.

HOWEVER, the before and after trends of the PITCH and YAW of ITMY indicate that it did not misalign by more than ~10uRad during the vent.  See the attached - note, ignore any data correlated when the SUM is near 0.

New TFs match well with previously healthy TFs taken in July.  Results can be found at:

/ligo/svncommon/SusSVN/sus/trunk/HLTS/Common/Data/allhltss_2017-12-21_H1_HLTS_Phase3a_PR3_M1_Doff_ALL_TFs.pdf
/ligo/svncommon/SusSVN/sus/trunk/HLTS/Common/Data/allhltss_2017-12-21_H1_HLTS_Phase3a_PR3_M1_Doff_ALL_ZOOMED_TFs.pdf

Snaps attached of P and Y for example.

Summary: 

Main activities today have been closing out HAM2 & HAM3 (the latter had doors installed).  There were also some model/front end/DAQ restarts as well.

Day's Activities:

• 15:30-17:00 Craning work (Mark & Tyler)...will work on NEG pump after
• 16:04 Dust Monitor 10 (BSC1) started having counts of up to 250.
• 16:05-16:22 Apollo consulting (Bubba)
• 16:06:  HAM2 close out work (Betsy, Travis )
  • 17:08:  Transfer functions for MCs (Betsy/Travis) & PRs (Kissel)
• 16:18 - 17:20  Cleaning Room work & Dust Monitor work in LVEA (Jeff B)
• 16:22  HAM6/CER Squeezer cabling (Fil, Richard, Elizabeth)
• 16:55 Squeezer Bay work (Terry)
• 17:08, 17:42, 17:58:  "Noise Eater out of range" alarms, notified Jason (sounds like a bug)
• 17:23-17:57 NEG pump work in output (Mark & Tyler)
• 17:27-20:00 Optics Lab work (Nutsinee)
• 17:29-17:34:  Reset Noise Eater (Jason)
• 17: 40-18:35 EX & EY Dust Monitor work (Jeff B)
• 18:00  Moving items from HiBay to EY (Mark & Tyler)
• 18:26 Moving cable for PSL Bullseye (related to ASC change) (Marc)
• 18:34 HAM6 ISI WD tripped (probably due to squeezer cable-pulling, will leave tripped)
• 18:36 PSL tour to Brijesh & SR3 oplev centering (Jason/Brijesh)
• 18:46 PSL Crystal Chiller top off (Corey)
• ~19:00 CDS  SUSH2b & SUSH2a glitched (RED on CDS Overview).  We suspect the rack was shorted with nearby VOPO/Squeezer cable pulling work.
• 19:15-20:00 HAM3 unlock/balance (Hugh)
• 19:47 HWS4 Table work (Greg)---ONGOING at 0:00utc
• 19:45 CDS Activities:  Restarting H2A, H2B, ASC front ends & also DAQ Restart (Dave)
  • Took H2A (MC2, MC3, PRM, PR3) optics to SAFE
  • Restarting NDS needed
• 20:04 HAM2 unlock/balance (Hugh)
• 20:13 HAM3 transfer functions (Jim)
• 20:20 Autoburt & matlab servers reboot completed (Carlos)
• 20:57 Oplev work completed this morning (Jason)
• 21:30 HAM2 transfer functions (Jim)
• 21:44 0:00 HAM3 Doors installed (Mark, Tyler, Bubba)
  • Will do HAM2 doors tomorrow.
• 21:46 LVEA clean-up work (Chris S., Betsy)
• 22:17-23:02 EY Oplev laser swap (Jason)
• 23:13-0:05 Check Pcal Alignment at EY (Evan, Darkhan, Rick)
• 23:23 Centering EY Oplev (Jason)
• 0:03 Turning off environmental controls for the PSL & turning OFF the PSL (Jason)

WHAM2--This platform had not been unlocked for some time, ~Nov 6 when Jim did TFs.

After unlocking, balanced the tilt as close as possible to the locked position of the last few days.  Limited mass choice and position only allows getting so close.

After Jim ran TFs today, the free hanging positions are 41, 7, & 96 urads for RX, RY, & RZ.  The positions while locked the last few days have been 43, 8, & 82 urads.  So the Tilt are very close but the RZ difference is some 14 urads. Sadly, we can't do anything about the RZ now.  The solution should be that when we first vent, give SEI some time to adjust the lockers to minimize this--probably a day or two at least.  And, as the payload changes and the platform is climbed on, this free hanging/locked position difference will change further.  We can do two things now going forward, servo RZ to the locked position which might make the ISI Isolation loops turn-on a bit touchy, or, as SEI would prefer, servo to the free hanging position and we'll see if IO notices/cares.  Alternatively, if the ISI is touchy and IO does care, we can twist the platform with HEPI--which we are perfectly happy to do.  For what it is worth, when Jim had the platform unlocked for the TFs in early November, the RZ position was similar to now.

For WHAM3--Comparing the locked position over the last couple days to the last couple months, the tilts and RZ are consistent: -6, -6, & -5 urads for RX, RY, & RZ.  The current now free hanging positions are -9, -8, & 5 urads.  So, similar to HAM2, the RX & RYs are within a few urads but the RZ has an ~10 urads twist when unlocked.  Like HAM2, will let IO decide if this twist is too much and if so, SEI will decide if we can tolerate it on the ISI or if it needs to be offloaded to HEPI.

Attached photos show a couple of bundles of cables on the +X-Y and -X+Y corners of the ISI Stage0 of HAM2 heading to the chamber feedthrus.  HEPI won't have any difficulty dealing with it now but may be an issue if we attempt any real isolation--could complicate the TFs.  Maybe these cable bundles could be done differently if it seems to be a problem.

Carlos, Dave:

Carlos patched and restarted cdslogin this morning. I restarted the cell phone notification system at 13:09 PST.

The DAQ was restarted today to install several changes:

new h1asc code (see alog 39868)

latest H0EDCU_SAFETY.ini

new nds configurations

The NDS reconfigurations are:

h1nds0: New daqdrc file to serve h1ldasgw0's archived raw minute trends from its SATABOY RAID.

h1nds1 (the default nds): now NFS mounts h1ldaswg1's /frames-1 and /trend-1 exports (was temporarily serving h1ldasgw0 while the E18 upgrade was progressing). Also new daqdrc file to serve h1ldasgw1's archived raw minute trends from its SATABOY RAID.

After the restart the EDCU did not connect to many of h1ecaty1's EPICS channels. Remember that the hourly autoburt machine started having connection issues to h1ecaty1 over the weekend. The autoburt machine was rebooted today, which did not fix its connection problems. This coupled with the EDCU issues leads us to think a restart of the IOCs on h1ecaty1plc[1,2,3] is needed. We will see if this can be scheduled pre-holidays.

Continuing from yesterday's afternoon closeout festivities, this morning Travis and I finished pulling the rest of the HAM2/HAM3 HSTS/HLTS First Contact and spot cleaning the optic edges.  We did the usual N2 top gun blow during and after the pulls.  We double checked tables for extra parts and tools, and finished laying the 3" and 1" witness optics and wafers.  We wiped tables in lots of places.  There are still a few particle-looking spots on some of the HR surfaces but they do not want to move so we had to leave them behind.

While looking at TFs we re-discovered that the PR3 Pitch Transfer Function looked a bit odd, peaks were in the correct place but the signal was steeper in places than expected.  This was due to a broken relay on the BIO chassis.  Fil swapped the unit and things looked better.

Meanwhile, the PR2 Pitch TF also exhibited this and was tracked down to a "stuck" BIO state which was fixed by unplugging and reseating the cable somewhere in the external chain. 

Kissel and Travis are finishing up the suite of TFs for all 6 of these suspensions (IMs were done yesterday 39845), to be posted in a bit.

Jim and Hugh finished ISI floating, balance tweeks, and TFs, logs pending.

Sign-off sheets were completed.  Vern will file to the DCC after the holiday.

Bubba and crew are starting top put doors on, beginning with HAM3 then to HAM2.

Pump down will likely happen early next week after we let the purge air dry things over the holiday weekend.

WP7230

Richard, Sheila,  Marc, Dave:

The ADC inputs to h1asc were remapped following the addition of the first ADC.

The PSL Bulls Eye photo-diode channels were remapped as-per E1600381 drawings. The 9pin DSUB cable for this PD was moved on the 6th AA chassis from the last 4 channels to the next-to-last 4 channels. The model's four segments were remapped to be in segment order and not ADC channel order (see attachment)

After the h1asc model was restarted:

the DAQ was restarted

the Bullseye Input Matrix was modified to switch SEG1 and SEG3 settings. We think the SEG2,4 settings are still correct.

the ISC_CUST_BULLSEYE.adl medm file was modified to correct the segment drawing (see attachment)

While CER work was ongoing to SUS coil driver repair, the front end systems h1sush2a and h1sush2b were glitched. On h1sush2b all models stopped running. On h1sush2a the IOP model continually ran long, with ADC and TIM errors which would not clear. All models on both FECs were restarted.

Hugh unlocked HAM3 this morning after SUS people finished in there this morning. I've taken dtt tfs and they look ok. Hugh reported purge is high, so tfs look a little ratty, but resonances seem clear. 

• Crystal Chiller topped off with 250mL of water.
• Diode Chiller OK
• Checked Filters and they were OK.
• Closing Out FAMIS # 6554

Nutsinee, Terry, Daniel

We installed all the in-air coax cables for the squeezer that were on hand. Six weeks after the promised delivery date, it still seems ~20% are missing due to being back ordered...

Fil et al. started laying down the long D-sub cables.

While installing the north door on BSC 1 this morning, as we were inspecting the flange,  I saw what appeared to be a rust spot on the flange in the sealing area of the inner O-ring at roughly the 5 o clock position (facing the BSC from inside the biergarten). 

I wiped, rubbed, and wiped again. I repeated this several times.  There was no drag felt on the alcohol wipe, or on my clean gloves, no "rust residue" or any other foreign material came off on the wipe or glove. 

I put a piece of tape on the bolt head located near this position and showed Kyle the picture. Kyle said he would make a comment on this post.

WP7252:

During today's CDS meeting Rolf reported that moving the fast front-end computer's IRIG-B card away from slot-1 resolved timing issues on his test system. To try this out on a production system, this afternoon I moved h1susey's IRIG-B card.

Recall (alog 39361) that on 09nov2017 I had moved h1susey's OneStop from slot-2 to slot-5 as part of this investigation. Today I returned the OneStop back to slot-2, and moved the IRIG-B card from slot-1 to the newly vacated slot-5.

It was a messy restart of h1susey. After taking it out of the Dolphin fabric and issuing the poweroff command, the OS got stuck trying to umount NFS after apparently disabling its network ports. I had to power down using the front panel button, knowing that this would most probably cause a Dolphin glitch. Sure enough, on restoration of power the EY dolphin fabric glitched, requiring a restart of models on h1seiey and h1iscey. EY is now back in operation.