PSL ALS path redone (Ed, Thomas, Dan, Keita)

Summary

ALS path on the PSL table was realigned (it was totally misaligned after the main IO path was redone on May 09, alog 41924).

The beam is already going to the SHG in ISCT1 but we need to refine the alignment there. We don't have to go back into PSL to do this work, the rest should be done in ISCT1 in laser hazard some time next week (or earlier when there's an opportunity).

Details

See https://dcc.ligo.org/D0902114 for nomenclature.

At first the beam was blocked by the Faraday aperture (first attachment). I and Ed used ALS-M1 and ALS-M2 to clear the Faraday and center the beam on two irises between ALS-M3 and the periscope. After we were satisfied, however, Thomas and Dan couldn't find the beam in ISCT1. We also found that the beam was clipping on the top periscope mirror (ALS-M5) on the PSL table though the beam went into HAM1 (first attachment, in this picture two irises are almost closed so it's easier to see the beam position).

Dan found that the beam was already hitting the in-chamber steering mirror, and we regained the beam in ISCT1 by turning the top peri mirror mostly in YAW in the PSL room.

From there on, I tried to use the top (ALS-M5) and bottom (ALS-M4) peri mirror on the PSL table to walk the beam on ALS-M5 while keeping the beam in ISCT1. That worked  until the bottom peri mirror hit some hard stop in YAW. There's plenty of actuator threads left, but it seems like the mirror mount and the 45 deg mounting block had a mechanical interference. I ended up using ALS-M3 also. We just stopped doing this when the beam position on the top peri mirror on the psl table was not as terrible as before (attachment 2, same caveat as the first picture). Then we used the ALS-M5 to steer the beam at the center of the bottom peri mirror in ISCT1.

In the PSL room we moved the irises so the beams are centered on them. 

GV11 and GV12 status

Gerardo M., Chandra R., Kyle R.

Today we removed the two paper clip jumpers that had been added to the terminal strip withing the vacuum rack back during the CP4 bake.  Filberto C. and Gerardo M. had added these in order to mimic the GV11 CLOSED and GV12 CLOSED signals required by CDS in order for us to utilize the CP4 regeneration PI loop.  The nominal wiring for both of these gate valves had been removed so that they could be baked along with CP4.  As such, these two signals had to be simulated via these jumpers.  Ultimately, this ended up being a mute exercise as we eventually abandoned this approach altogether, opting instead to go "old school" and using a manually controlled variac instead.  Today we also had to re-install the fuses associated with these two signals.  Following this, Gerardo noticed a discrepancy between the Y-mid Station-specific MEDM screen vs. the overall Site Overview MEDM screen.  One screen showed the correct valve status following today's signal restoration but other screen did not.  He and Patrick T. sorted this out later somehow. 

Chandra R. and I had both heard a noise last Friday when attempting to fully open GV11.  The sound seemed to have emanated from the limit switch area so we opted to not fully open the valve at that time until we could fully investigate (today).  The motor drive is entirely dependent upon proper setup of the limit switches and we wanted to confirm that nothing had been changed during the removal of the signal wiring.   So, this morning, Chandra R. contacted Ken D. (electrician) to confirm that he had only removed the wiring from the GV11 and GV12's limit switches when preparing for the CP4 bake out and had not changed any of the mechanical setup.  Ken D. confirmed that only the wiring had been removed and that the mechanical setup of the switches had been left alone.  Even so, I removed the limit switch box cover plate and observed the internal workings as GV11 was stroked up and down (a few inches in each direction).  I tested the OPEN and CLOSED limit switches by manually changing their states and observing that the CDS MEDM screens responded accordingly.  Additionally, I confirmed that the motor drive stopped driving the valve in response to my manually closing the OPEN limit switch.  Convinced that everything was normal, we fully opened GV11. 

Next, we re-installed all of GV12's annulus piping (new modified version) minus the gate portion.  We will finish this up tomorrow and, assuming no issues, start the hours long process of opening GV12. 

IO path on the PSL: EOM PD restored, IO GigE camera 2 installed, IMC IN PD recalibrated

EOM PD restored:

• the Thorlabs PD that was originally installed on the EOM pick off path, has been restored to this location
• it was replaced by the ISS PD for a while, but the ISS PD is back in the ISS box
• this Thorlabs PD will be replaced with a large area PD

IO GigE camera 2 installed:

• IO_AB_M12 was swapped, the super polished mirror removed, and a 98% beam splitter installe
• at 7.6W incident on the bottom periscope mirror, there is 6uW on the camera
• since this camera is downstream of the rotation stage, it's SUM will vary as IMC INPUT power varies
• I've set the gain to 1850
• when the IMC IN power is 20W, the camera 2 gain will, in theory, produce a SUM of around 2.7e8, and closely match camera 1's SUM
• camera 1 incident power is 15uW, with the PMC transmitted power of 42.2W
• camera 2 incident power is 6uW, with 7.6W incident on the bottom periscope mirror

IMC power recalibrated:

• before any recalibration,  measured the power before the bottom periscope mirror was 7.6W, with a requested power on the rotation stage of 6.9W
• Keita recalibrated the IMC IN PD
• his notes are attached, as a snapshot

Failed Attempt at B&K Hammering PCAL EX Periscope after Upgraded Baffle Install

J. Kissel, J. Warner

Jim and I went to B&K hammer EX’s PCAL periscope this afternoon and came across a new bug I hadn’t seen before: the hammer channel’s BNC input spigot was constantly red while connected, and after activating a known functional template (which showed the 3-axis accelerometer working as normal), the hammer’s sensor input bar was flashing red and reporting that it was saturating / overloaded. However, between the ~1sec cadence flashes, you can see the glimpses of a normal hammer behavior. We tried:
	- Power cycling the satellite box
	- Closing and re-opening a known functional template (and a different template)
	- Physically disconnecting the hammer from the satellite box, (the spigot stays red — but that happens normally when a sensor is disconnected)  and reconnecting it
	- Swapping out the hammer’s B&K BNC with a normal BNC
	- Shifting all of the inputs down by one (doesn’t work at ALL! Sad… why have 6 channels then?)
	- Clearing and Re-selecting the hammer species in the template (8206-003)
	- “Clear and Detect Hardware” in the Hardware setup
	- Physically disconnecting the hammer’s accelerometer from the head and reconnecting it (grasping at straws … )
	- Changing the input gain on that channel in the template’s hardware properties (really grasping for straws… )

Attached are pictures of the satellite box in error, and the activated template in error.

I've got emails out to the experts and we'll continue to debug the hardware outside of the clean room, but this may mean we forgo B&K hammering of this periscope. 

This failure is being tracked by FRS Ticket 10817.

OPO TEC turned on

Turned on the OPO TEC with the same loop shape as in air. Takes about 50 minutes to reach equilibrium.

BRDs Tuned for H1 SUS ETMX

J. Kissel,

Using the data gathered by Travis and Betsy last week (LHO aLOG 42149), I've tuned BRD S/Ns 013 and 004 to match the highest vertical (a.k.a bounce) and roll mode frequencies of the newly suspended H1 SUS ETMX. Results are attached and tabulated below:

    'Target [Hz]'    'BRD S/N'    'Mean Fit Freq. [Hz]'    '% Diff [%]'
    '9.697'          '004'        '9.69'                   '0.071'     
    ''               '013'        '9.685'                  '0.13'      
    ''               ''           ''                       ''          
    '13.775'         '004'        '13.812'                 '0.27'      
    ''               '013'        '13.73'                  '0.33' 

The uncertainty in the frequency corresponds to the original binwidth of the measured vibrometer / QPD data, +/-15 mHz.

Setup for measurement is as described in the HAM ISI TMDs (see LHO aLOG 38741) using corroborating evidence from both the laser vibrometer and a primitive shadow sensor setup. To calculate the above "Mean Fit Frequency," I used a least square's minimization with a Lorentzian seed function,
    fit(f) = (1/Q)^2 ./((f - f0).^2 + (1/Q)^2) + C 
to fit both sensors' data to obtain the measured frequency within the noise, and then took the mean of the two sensors' results.
The mean frequencies are less than 1% different from the target frequency of H1 SUS ETMX, which means the tuning is within requirements of "match target frequency to better than +/-1%."

I've left the tuned valentines on Betsy and Travis' desk.

BSC9/ETMX installation status - BRDs, Balance, and B&K, oh my

Travis, Betsy, Jim, Kissel

Today,

- Kissel tuned the BRDs for ETMX

- Travis and I installed the BRDs onto the main chain of the QUAD - the pointing of the main chain is still good

- Jim and Travis removed the ~6 large ISI masses on the +Y side of the table in order to shuffle them to new balance locations updated in the table layout drawing (to compensate for the EFM about to be installed)

- I opened the EFM and started looking at the "bracketry" for it's install - will do this install tomorrow morning with Georgia/Craig

- Jim and Kissel attempted to launch the B&K of the PCAL but found a big problem with the B&K driver unit... looks like it'll have to go out for repair.

 

 

Ops Day Shift Summary

TITLE: 05/29 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY: PSL ALS and IOO alignment, EX had B&K hammering and some electronics checks, and the normal maintenance day items.
LOG: See attached

 

New SUS Configuration Guardian (SUS_CONFIG)

New Guardian to allow moving many of the suspension nodes to a state at once. I took this code from LLO, but then made it a bit more general and cleaned it up with pep8. The new management structure that came along with the Guardian upgrade to 1.2.0 allows for this node to make requests of other nodes, without having to manage them entirely. This is a feature that should be handled with care, but I think works very well for this case.

Some example uses:

• Bring all sus to SAFE
• Bring EY to DAMPED
• Reset all WDs
• etc.

I still have a bit of testing to do with it, but since it was mainly just a copy paste from LLO, I imagine it works well.

ISCT6 & SQZT6 Cabling

WP 7600

Moved picomotor chassis from ISCT6 to ISC-R5. Associated cabling was also pulled backed. Cable extensions that were added are no longer needed, alog 42161.
Routed and connected the fibers going to SQZT6.
Connected GigE camera cables to patch panel in SUS-R4. Cameras at patch panel are connected in following order:

Port 1 ISCT6 CAM1
Port 2 ISCT6 CAM2
Port 3 SQZT6 CAM1
Port 4 SQZT6 CAM2
Port 5 HAM6 CAM1

ETMY HWS background noise measurements - TMSY watchdog tripped & reset. And background wavefronts. And 200 micron core fiber. And ALS cross-coupling

We set up the ETMY HWS to run over the weekend to gather background noise data. The SPHERICAL_POWER looks normal for the first 17 hours until it suddenly drops down to a large negative value. It turned out that the WATCHDOGS tripped on TMSY at this time. The HWS continued to run without any other issues over the long weekend. 

TJ reset the watchdogs this morning and the HWS spherical power returned to the nominal zero value (without any interaction with the physical HWS hardware). We will continue to run it like this for the time being (until work needs to be done at ETMY).

Intensity distributions

The intensity distribution illuminating the HWS with the beam from the 50 micron core fiber is shown here. Spatial units = pixels. There is some high spatial frequency structure on the return beam. No doubt from clipping somewhere in the system. The circular aperture is consistent with the annular reaction mass aperture. 

When the Hartmann plate is put on the CCD, the result is the following:

 

200 micron core fiber

We switched to a 200-micron core fiber and achieved more transmission and similar HWS performance with a beam showing noticeably less high spatial frequency intensity fluctuations.

And with the Hartmann plate in place:

 

ALS cross-coupling

We turned on the ALS beam and found that, although s-polarization is incident on the PBS going into vacuum system, there is significant leakage through the PBS for the return beam. The HWS CCD looks like this when the ALS beam is turned on (and the Hartmann plate is removed).

We measured the amount of ALS light and found that at least 750 micro-Watts is getting through the PBS. This is a couple of orders of magnitude larger than the HWS beam (which is difficult to measure accurately because of the low power level.

 

 

Background wavefront changes

The background wavefront changes are analyzed below:

• The first (4.5 minute change) compares two times shortly after the HWS was initialized on Friday
  • The wavefront shows a small tilt but not much high frequency noise. The time scale for a point absorber is less than 4.5 minutes and the OPD from the ITMX point absorber was of the order of 80nm (about 50 to 100x larger than the background noise). Provisionally, without doing a full analysis to determine SNR, this looks sufficient to detect point absorbers.
• The second (1000 minute change) compares two times this morning
  • Ditto result from first plot.
• The third (4 day change) compares a reference from Friday with the HWS measurement from this morning
  • There is some clear medium spatial frequency structure to the HWS measurement here. This looks like diffraction fringes across the HWS probe beam. Further investigation is needed. However, we do know that if there are diffraction fringes on the beam we should see these become more pronounced as the time between two HWS measurements increases (assuming that the TMS and other optics slowly drift over time).

Background wavefront change: 4.5 minute change

Background wavefront: 1000s change

Background wavefront: approximately 4 day change

CDS Tuesday Maintenance Summary

New h1asc code

Daniel, Sheila, Dave:

New h1asc model was installed. 522 RF72 slow channels were removed from the DAQ-INI. Prior to the restart the SDF was reporting 158 diffs, these are shown in the attached images.

Reverted h1susim DAQ-DQ channels' rates

Cheryl, Dave:

After the SUS-IM DQ channels were all temporarily increased to 2048Hz on 8th May, this change was removed today, all channels are back to their original rates.

New Guardian Node

TJ added a new SUS_CONFIG node. This was added to the H1EDCU_GRD.ini

DAQ Restart

At 12:10 the DAQ was restarted to support the above changes.

Fix to vacuum site overview

The status of GV12 was using the channel name for GV11. This has been fixed. The medm screens have been updated on each of the vacuum controls computers under WP 7602. TJ has restarted the vacuum overview screen on the control room wall. Dave is looking into the web snapshots.

Front end computers batteries look good

Following the discovery of a DAQ-Test-Stand computer with a dead internal motherboard battery, I scanned the H1 production machines this morning to check their battery status (following Mike T's instructions).

All 28 computers with an active IPMI port reported a good voltage on their 3V battery. The IPMI interface for h1lsc0 (the most recent machine to be upgraded to a Generation-2 computer) is not functional. When we upgrade to Gentoo-3.0.8 the ipmitool command for front ends becomes available so I will be able to set the IPMI configuration without having to resort to BIOS. Since h1lsc0 is a new machine, we can assume its battery is as good or better than h1suse[x,y]

Full listing is shown below. Note that if you round to one decimal place, they are all at 3.2V except for h1suse[x,y] which are at 3.5V. This is expected, all the Generation-1 machines are the same age, the end station SUS are recent Generation-2 machines.

h1psl0 VBAT | 3.192 Volts
h1seih16 VBAT | 3.192 Volts
h1seih23 VBAT | 3.192 Volts
h1seih45 VBAT | 3.192 Volts
h1seib1 VBAT | 3.216 Volts
h1seib2 VBAT | 3.216 Volts
h1seib3 VBAT | 3.216 Volts
h1sush2a VBAT | 3.192 Volts
h1sush2b VBAT | 3.216 Volts
h1sush34 VBAT | 3.192 Volts
h1sush56 VBAT | 3.216 Volts
h1susb123 VBAT | 3.192 Volts
h1susauxh2 VBAT | 3.216 Volts
h1susauxh34 VBAT | 3.216 Volts
h1susauxh56 VBAT | 3.192 Volts
h1susauxb123 VBAT | 3.216 Volts
h1oaf0 VBAT | 3.192 Volts
h1asc0 VBAT | 3.192 Volts
h1pemmx VBAT | 3.192 Volts
h1pemmy VBAT | 3.216 Volts
h1susauxey VBAT | 3.192 Volts
h1susey VBAT | 3.472 Volts
h1seiey VBAT | 3.216 Volts
h1iscey VBAT | 3.168 Volts
h1susauxex VBAT | 3.192 Volts
h1susex VBAT | 3.456 Volts
h1seiex VBAT | 3.192 Volts
h1iscex VBAT | 3.192 Volts

 

More PRMI work

Thomas, Sheila, Jenne, Keita

We locked PRMI tonight, and we think that we are satisfied enough with the rephasing to move on. Fixing the phasing means that we no longer have an unexplained drop in the PRCL optical gain.

• Yesterday afternoon Betsy came to talk to us about the alignment of ITMX.  Betsy had used the optical lever as a reference to align ITMX to before and after the AMD installation.  We looked at trends and saw that she had changed the pitch alignment bias by -320 urad to get the same pointing on the oplev after the AMD installation as before.  We are currently locking PRMI with the ITMX‌ slider -315 urad compared to what it was after the X arm peak in Feb, but this is probably within the precision of how well we have kept the reference.  (Alignment screenshot attached)
• Thomas and I phased the diodes with PRMI locked by driving PRCL at 138 Hz with a notch engaged in both MICH and PRCL loops.  We phased both REFLAIR 9 and REFLAIR 45 to minimize the Q signal from the PRCL drive.  For 9MHz, this required a net phase shift of +40 degrees (in agreement with what Jenne found using PRX (41962).  For 45 MHz, we found a net phase shift (compared to before the EOM swap) of +51 degrees, which is intermediate between what Jenne had found and what Thomas and I found using MICH on Wednesday.
• Once Thomas phased REFLAIR9, the gain of the PRCL is back to normal (ie, the UGF looks good with the gain that we used before the EOM swap). We don't have an explanation for why the gain for REFL 45 needed to be increased, although it could be that this setting was not well tuned for PRMI before the EOM swap. 
• Thomas has found the beam on AS_C with PRMI locked.

Next steps:

• Walk the alignment of PRM, PR2 and MICH to try to maximize build ups and see how our build ups compare to a past time when PRMI was locked without arms. 
• Figure out how to accept changes to AS_A_RF45 settings in SDF
• Get AS AIR camera signal in control room 
• Alignment of SRC
  • Check beam at AS AIR using a card, scan SR2 to center in the aperture from SR2 to HAM6 (the SRM baffle and OFI).  
  • pico AS_C if necessary to center on AS_C 
    • possibly painful step, close centering loop on SR2 from AS_C, walk SR3 to center on SR2 keyhole baffle
  • Align SRY, check if SRM is still at edge of T2 osem 

Net demod phase changes compared to May 4th 

	May 14th change	May22nd	May 23rd	May 25	final value May 25th
POP45	none	no change	-60	-51	16.1
REFL45	-36	-40	-100	-51	-64
POPAIR45	none	none	-60	-51	-89
REFLAIR45	no net change	none	-60	-51	91
REFLAIR135	none	none	+180	-153	133
POP90	none	none	-120	-102	24
ASC ASA+B 45	-40	reset to 0	-60	-51
ASC REFLA+B45	-40	rest to 0	-60	-51
ASC POPX RF	-40	reset to 0	-60	-51
POP9	none	none	+75	+60	-32
REFL9	+60	+59	+59	+60	-29
POPAIR 9	none	none	none	+60	-56
REFLAIR 9	none	none	none	+60	-30
REFLAIR 27	none	none	none	+180	-80
POP 18	none	none	+146	+120	12
ASC REFL A+B 9	+60	reset to 0	none	+60
AS A+B 36	none	none	none	+9

GV11 open...mostly

Kyle and I spent the afternoon with GV11 slowly opening it and releasing gate o-rings is small incremental motions (powered the motor ~10 times up to 1000 rpm first time and then 500 rpm increments, over two days). We heard a loud noise at the top of the valve on the last incremental stroke and then continued to open the valve, observing the ball screw moving up. The status of the valve did not change from red to yellow on MEDM screen, so we suspect the limit switch broke. Therefore, we didn't want to open the valve fully to avoid utilizing the hard stops. We will investigate on Tuesday.

Prior to opening GV11, we leak checked the RGA manifold and new flanges around CP4's 10" GV. There was some sporadic He signal around the full range gauge area but nothing above 2e-9 Torr. The RGA will be rebaked later and that area will get leak checked again.

RGA was scanning before, during, and after GV11 opened. Will process and post results Tuesday.

We also burped dry N2 into GV12's gate annulus and then fully vented it to discover it is also now leak tight!

ETMX ESD - Terminating and HI-POT Testing

Re-terminated the pins for the ERM pigtail connector. See alog 41891 for LR and Bias failing HI-POT test. All pins were tested for the following:

1. Checked no shorts between inner pin and connector body.
2. Tested all segments (LR, UR, BIAS, UL, and LL) were not shorted to each other.
3. Performed HI-POT test to 1kV for each pin, all passed.
4. Connected all cabling in-chamber and repeated HI-POT test on air-side. All passed (UR only tested to ~800V).

R. Abbott, F. Clara, T. Sadecki, B. Weaver