(Travis S, Gerardo M)

This time septum viewport was rotated 180 degrees, it's fiducial line is now pointing towards 3 O'Clock.  Bolts aren't torqued yet, this will allow for the installation of a bracket for an accelerometer in the coming days.

Following on from Keita's alog from yesterday, we spent all day attempting to convince ourselves that the SR chain of optics are hanging symmetrically within their structures, using little to no tooling.  Holding rulers up to various optics and structures, and painstakingly logging measurements, I could not find any reason to believe that the beam centering we've done between the center of SR2 and SRM is out by more than ~2mm.  The PSL beam line that we have set between the center of SR2 and SRM looks good to carry on.  Indeed, this may mean that the baffles do not look symmetric on the structures, but at least the beam path appears correct.  We'll revisit baffle positions an drawings tomorrow.

Meanwhile, since I was wandering the tube between HAM4 and HAM5, I took a look at the beam centering going through the newly built SR2 scraper baffle D1003300.  At first I was thrown off by the fact that the beam seemed to go through the baffle off center even though the baffle was installed using a template which I would have thought set it pretty close (within mm's).  A lunch break consult with Keita and Calum pointed out that the beam I was looking at was only the SR3-to-SR2 beam which straddles the centerline of the baffle ellipse hole with the SR2-to-SRM beam which is hard to spot when viewing the SR3-to-SR2 beam with an IR card.  A quick calculation, and a SW confirmation told us the 2 beams should be separated by 20mm and should straddle the centerline.   Now how to find the center of the hole while standing in the dark with a viewer card and not occulting the beam with your body...  I gave up trying to measure in-situ and instead opted for some pictures to scale.

Attached is the PDF scaled pic I used - I'm not spending any more time screwing around with the oddities of why the font is miniscule - what I did was:

- Scale the aperture in the picture to the 161mm dimension I read off the drawing D1003301 (for what ever reason Adobe makes starts the scale at a huge setting like some 40 inches or so)

- Using the new scaler, measure to the beam center shown in the picture

- 161mm /2 = 80.5mm is where the center of the aperture should be, so the beam center should be left of that by 10mm (half of the 20mm), 90mm.

- The beam is at 87.4mm.  Of course it's hard to estimate the beam center since the beam is ~20-30mm in diameter, fuzzy, and moves a bit.  I'd estimate the error of my ability to measure this centering to better than 5mm...  Feel free to redo.

Seriously, please let that be close enough.

I did however, take a picture of what can be seen from the plane of the MCTube Eyeball baffle closest to HAM4 on the beam path (see below).  Not sure I was able to place the camera on the beam line very well...  I can confirm that everything shown in the left lobe cutout of the baffle is in dead all HWS silver mirror reflections (and no metal from mounts).  It's hard to tell if there is a sliver of the right side of the SR2 optic still in the right portion of the right aperture lobe.  Maybe it's the angle of my camera view.  Dunno.

Richard M, Dave B, Fil C, Peter K, Marc P.

WP7226

This morning we completed an investigation of the Bullseye PD signal chain.  It was determined that the ISC250 cable position in AA Chassis S1102766 was incorrectly placed one space to the left and should be attached to (IN 29-32).  This was likely overlooked when these chassis were rearranged to make space for squeezer electronics on November 2nd, .  The cable was moved to the correct position and we verified that the signals are received by the ADC.

This morning I completed the weekly PSL FAMIS tasks.

HPO Pump Diode Current Adjust (FAMIS 8449)

With the ISS OFF, I adjusted the operating current of the HPO DBs.  The changes are summarized in the below table and a screenshot of the PSL Beckhoff main screen is attached for future reference.

This is a large increase for just one week of operation, which can be an indication of a DB nearing the end of its life (remember that DB2, DB3, and DB4 are still the original DBs installed when the H1 PSL was in late 2011/early 2012).  We will keep an eye on this.

I did not adjust the operating temps of the DBs.  The HPO is outputting ~154.0 W and the ISS is back ON.  This completes FAMIS 8449.

PSL Power Watchdog Reset (FAMIS 3920)

I reset both PSL power watchdogs at 17:18 UTC (9:18 PST).  This completes FAMIS 3920.

   Posted below are the 45 day trends for the HEPI pumps. Most plots look reasonable for being in a vent status. The CH6 HPI-PUMP_EX_PS_PRESS signal drops to <0 at 19:02 (11:02PT) on 11/08/2017. This may be due to the HEPI control channels being migrated to Beckhoff.   

(Keita K, Jeff K, Gerardo M)

After centering the beam on SRM the OFI position was way off with respect to the beam, so the cage was moved until the beam made it all the way to HAM6, the beam position is satisfactory on YAW, however the position is off in PITCH at the input of the OFI, fine tuning to continue tomorrow.

1. SRM beam position was off last week by about 3/8 inch.

When the beam is properly centered on SRM, the beam position on SRM is about 3/8" towards -X than we thought last week.

Beam centering on SRM horizontally is almost impossible to do by looking from outside HAM5, and instead it seems as if this was done in the past week by centering on the baffle hole on the back of the SRM.

Today we sent JeffK into the tube between HAM5 and HAM4 and have him look at the beam on SRM while I was holding the card right in front of the SRM. Doing it this way, it turns out that the beam is about 3/8" inch off centered on the back baffle hole in -X direction.

My guess is that the  original centering was not done from the front of the SRM. I also wonder if the cage position itself is off.

TJ repositioned the baffle so the beam is centered on the back baffle, and Gerardo moved OFI such that the beam at least clears the OFI (he'll fine tune tomorrow).

2. Septum window was rotated by 120 degrees counter-clockwise and the beam was great in PIT, but of course not great in YAW.

Gerardo and Travis rotated the septum plate by 120 degrees counter-clockwise so that the beam height becomes good on OM1.

The thickest side went to South, which moved the beam further in -X direction.

The beam was blocked by the fast shutter. When I moved FS to the side, the beam was hitting somewhat to the -X side of OM1 -X damping plate adjuster screw, meaning the height was right but it was off to the side by about 36mm in -X direction.

Table below shows Koji's measurement of beam position on OM1 last week (alog 39460), beam position changes which should have been caused by septum rotation assuming that the wedge angle is 0.89 deg (measured by Koji, instead of 0.75 deg derived from the thickness measurement) (alog 13399), and the beam position measured today. If everything is right "in theory" and "measured" columns should agree. At least they don't look totally wrong.

3. Rotating Septum by 180 degrees will bring the beam to a better position

Assuming that SRM is/was at the correct location (we need to check), the next question is what to do.

Unfortunately, I cannot simply move OM1 and be done with that, it seems like the beam from OM1 to OM2 will be either blocked by OM3 or very close to it. I can move OM2 but that will leave no room for the fast shutter as the OM1-OM2 will be much closer to OM2-OM3 line than before.

We can rotate the septum window by 180 degrees so the thickest side comes to the north. Assuming 0.89 deg wedge, the beam deflection is 7 mrad, so 180 deg rotation will give us 14mrad change in deflection.

The distance from the septum to OM1 is 1930mm, so this will result in the horizontal shift of 27mm  without height change. The beam will be at X=-36+27 = -9mm on OM1 horizontally. Hopefully this will allow us to make room for the fast shutter without moving OM2 sideways.

Laser Status:
SysStat is good
Front End Power is 35.8W (should be around 30 W)
HPO Output Power is 151.5W
Front End Watch is GREEN
HPO Watch is GREEN

PMC:
It has been locked 2 days, 7 hr 43 minutes (should be days/weeks)
Reflected power = 25.37Watts
Transmitted power = 48.21Watts
PowerSum = 73.58Watts.

FSS:
It has been locked for 2 days 7 hr and 43 min (should be days/weeks)
TPD[V] = 2.039V (min 0.9V)

ISS:
The diffracted power is around 1.6% (should be 3-5%)
Last saturation event was 2 days 7 hours and 43 minutes ago (should be days/weeks)

Possible Issues:
PMC reflected power is high
ISS diffracted power is Low

Jeff B and Dave:

Jeff inherited a very red looking CDS overview screen this morning (see attached) which was not being auto-cleared.

Digging deeper, the h1lsc0 user models TIME glitched at 06:56 PST this morning, but the h1ioplsc0 model did not. This is the first time this has happened, the normal glitch behaviour is an IOP glitch with optionally an accompanying user model glitch. My auto-diag-reset script only looks for LSC-IOP glitches, and therefore did not clear this one.

If we see an overview similar to the attached one, please alog it and then press the "! Diag Reset" button on the bottom of the CDS overview screen to clear the errors.

I switched the cables for the PSL table temperature signals, H1:PSL-ENV_LASERRM_TBLS_TEMP_DEGF (table south) and H1:PSL-ENV_LASERRM_TBLN_TEMP_DEGF
(table north) at the back of the PSL environmental chassis.  This corrects the north/south identity problem.  So now the signal labelled TBLN
really is the "north" end of the table, as per the documentation.

Noticed the Corner3 CPS readings were both railed at -23k -32k and the Near Limit light was illuminated on the CPS Satellite box.  I trace this back to the point in time that the ISI was being locked and the Corner3 Feedthru was being reworked back in early October.  For the vertical sensors, the rail cleared when the exterior copper shield was cleared from the BNC bayonet which is used in the circuitry.  The Horizontal would not yield so easily.  On the vacuum side the Horizontal reading would clear if the cable inside was mucked with but it was not satisfying to this troubleshooter.  It seems this corner of cables need serious reworking.

Work plan for week of 11/20-2017

HAM2: Zero out bias sliders
	   IM4 trans alignment 

HAM3/4: Baffle alignment
	     Torque SR2
	     B&K Hammering
	     MC2 alignment and By-Pass work

HAM5: Adjust/mod height of spacers
	    Align OFI, ZM1-6, OM1, OM2, and SRM
	    Septum Window 
	    B&K Hammering
	    SMR alignment

BSCs: Baffle alignment 
	   Chamber closeout tasks

The BRS-X needs to be recentered

VAC: Vacuum group asked to be informed of all changes to Purge Air. Any changes should be communicated through the operator. 
	  

S Cooper, J Warner

We've been investigating the reasons into why HEPI tripped during O2 to see if anything could be done to prevent it. To do this we've been looking at both the time series sensor data in the local basis (H1,H2,V1,V2 etc), for the IPS, STS, L4C's and Actuators, the saturation counts and the watchdog status for every chamber (BSC's and HAM's - with the exception of HAM1). The first earthquake we ran this on was the Montana earthquake (GPS 118335800) as this was the only earthquake where HEPI was the first to trip.

When we if we look at the saturation counts, we find that only the L4C's are hitting their saturation threshold and are therefore likely causing watchdog trips, the horizontal L4C's are the first to saturate. 

If we then compare the levels that the watchdogs trip at across all 10 chambers, we find that ETMX trips at 10% the level of the other chambers. I've attached an annotated PNG highlighting the BSC chambers, and a .fig file that contains the saturation data for all 10 chambers. The dashed lines indicate the watchdog level (multiplied by 10,000 for easier comparison) with the solid lines indicating the specific chambers L4C. 

I'm now running the same script for other earthquakes that HEPI tripped in to see if this is an isolated case. 

[Maddie W., Aaron V., Greg M.]

Here is a summary of the filters and command line arguments that should be used for the C02 frame generation using the DCS calibration pipeline.  This information is compiled from configurations wiki page and aLOGs linked from that wiki page.  The command line arguments should be the same as for C01 except for changes noted in the table below.  (Additionally, the frame names and channel names should be changed appropriately to C02.)

--expected-fcc=347.2
--coherence-uncertainty-threshold=0.004
--wings=(something larger than 600)
--no-fs 
--no-srcQ
--update-fcc
--fcc-averaging-time=600
--fcc-filter-taper-length=32768
--pcal-channel-name CAL-PCALY_TX_PD_OUT_DQ

--expected-fcc=360.0
--coherence-uncertainty-threshold=0.004
--wings=(something larger than 600)
--no-fs
--no-srcQ
--update-fcc
--fcc-averaging-time=600
--fcc-filter-taper-length=32768
--pcal-channel-name CAL-PCALY_TX_PD_OUT_DQ

--expected-fcc=360.0
--coherence-uncertainty-threshold=0.004 
--wings=(something larger than 600)
--update-fcc
--fcc-averaging-time=600
--fcc-filter-taper-length=32768
--pcal-channel-name CAL-PCALY_TX_PD_OUT_DQ