It took much longer than expected but we set up the beam path for the RTP test in the OSB optics lab.
Since more power makes it easier to see the ghost beams, I removed the beam dump that used to receive most of the red power (~530mW) and directed the beam to the front of the table (red path in the attached). I stole the steering mirror that used to be used for the low power P-pol path (circled in red). The low power p-pol path is now simply blocked. No other change was made to low power S-pol path (orange) as well as green path (green), but the beams are blocked by beam dumps. If you want to use these, simply unblock.
The beam radius will be 300~400 um or so at the location we plan to put the RTP (represented by a green rectangle in the second attachment). Elenna will post the plot of the beam size measurement.
The third picture shows the containers for different RTP. Left is the one for the crystal in HAM1. The middle seems to be from the same batch. Right looks different, on the bottom of the container there's a label saying "I/O something something 2017" so this is likely the old one.
We didn't have time to actually test the crystals, wait for tomorrow's udpate.
I made a mistake when providing calculations to Keita about the beam profile- I incorrectly input our distances as mm instead of cm. However, I think it's ok overall.
Keita and I put an available lens (f = 286.5 mm) into the beam path, and then used a thorlabs profiler on a rail to profile the resulting beam at five points. We measured distances from the lens to the profiler and accounted for the set back of our profiler from the edge of the mount, etc. This measurement allowed us to measure that the beam waist is roughly around the location of the laser, and is about 130 um in the x direction and 202 um in the y direction. Unfortunately, the beam quality isn't great, this is the best we could do. (Note, because of my mistake we chose not to use this particular lens, but it probably would have been fine for our measurements after all).
After some iteration, we determined that a f=401 mm lens was suitable, and we ended up placing it pretty close to the original lens location. We ran another profile measurement and found that we could achieve a beamsize of about 313 um in the y direction and 251 um in the x direction (different than Keita's reported numbers above because I originally fit an incorrect seed waist).
I have attached two plots. The first shows the profile of the beam with the original lens, and the second with the resulting lens that we have now used to measure the EOM crystal.
So, the beam is maybe a bit smaller than the beamsize on HAM1 that goes into the EOM crystal (around 350 um).
Cables have been staged in front of the TCSX table enclosure on the floor. As this is a trip hazard, the area is tapped off with caution tape. Cables will be removed/pulled tomorrow.
On Friday, Oli and I moved four HRTSes over to their dedicated desicant cabinet in the VPW. Serial numbers 01 - H1BHDL1, 08 - H1BHDBS1, 03 - H1BHDBS2, and 04 - L1 Spare. These suspensions are locked with their wires tension relieved, the flags, magnets, magnet spacers, and BOSEMs have all been removed. We were already planning on moving them over but upon finding some corrosion on two parts we moved up that time frame. The two parts are D1900350 and D2100059, which are respectively the BOSEM Adj Mechanism Cams (12 per SUS), and the Top Mass Magnet Spacers (12 per SUS). The findings are discussed in FRS 36538 for the spacers and 36627 for the cams. I looked over and replaced the worst looking BOSEM cams before wrapping and bagging these suspensions.
We loaded them up into individual pelican cases (two at a time, there's two good pelican cases with padding), padded them as if we were going to ship them, loaded them into a site car then drove them from the staging building to the VPW. There we carefully unloaded them, brought them inside, unpacked and transfered them to the desicant cabinets. We did this twice for four total suspensions.
WP13018 Upgrade h1oaf0 18bit-DAC to 20bit-DAC
Fil, Oli, Anamaria, Robert, Ryan S, EJ, Dave:
We replaced the first DAC in h1oaf0 (a 18bit-DAC) with a 20bit-DAC. We reused the IO Chassis ribbon cable and Interface card, they are identical for these types of DAC.
This DAC is only being used by the PEM model.
A new h1iopoaf0 model was installed with the DAC change, its INI file was not changed.
A new h1pemcs model was installed with several changes:
. All 8 DAC channels are now being driven (previously last channel was not driven)
. An excitation stage was added to the model, a copy from LLO's PEM models. This comprises two Oscillators and a Noise_generator (see medm below)
. An additional DACOUTF filter bank as added just prior to the DAC part, each with a x4 filter in the FM10 slot.
A DAQ restart was required.
| 18bit-DAC (removed) | 101208-66 |
| 20bit-DAC (installed, originally in h1susb123) | 210303-49 |
Attached image shows H1PEM_CS_DAC_DRIVES_CUST.adl MEDM which maps the excitation path from OSC/NOISE_GEN through the filters for each DAC channel. Note on DACOUTF, each FM10 has a 20BitDAC filter, which is a x4 gain.
As an example, image shows chan0 being driven by a 0.1Hz sine wave with amp=1.0. The image is caught when the input is 0.988, but the DAC_chan0 drive is 3.953.
Recovery of PSL camera images.
Fil, Corey, Dave:
Following the replacement of camera power supplies, I recovered the PSL cameras and quad video server images.
DAQ Restart
Dave:
The DAQ was restarted for the h1pemcs model change. There were no problems with this restart.
Tue10Feb2026
LOC TIME HOSTNAME MODEL/REBOOT
11:28:08 h1oaf0 ***REBOOT*** <<< Power cycle of h10af0 to upgrade to 20bit-DAC
11:29:51 h1oaf0 h1iopoaf0 <<< new iop model
11:30:04 h1oaf0 h1pemcs <<< new pem model
11:30:17 h1oaf0 h1tcscs
11:30:30 h1oaf0 h1susprocpi
11:30:43 h1oaf0 h1seiproc
11:30:56 h1oaf0 h1oaf
11:31:09 h1oaf0 h1calcs
11:31:22 h1oaf0 h1susproc
11:31:35 h1oaf0 h1calinj
11:31:48 h1oaf0 h1bos
11:38:10 h1daqdc1 [DAQ] <<< 1-leg restart
11:38:22 h1daqfw1 [DAQ]
11:38:23 h1daqtw1 [DAQ]
11:38:24 h1daqnds1 [DAQ]
11:38:31 h1daqgds1 [DAQ]
11:44:32 h1daqgds0 [DAQ] <<< 0-leg restart
11:44:39 h1daqfw0 [DAQ]
11:44:39 h1daqtw0 [DAQ]
11:44:40 h1daqnds0 [DAQ]
(Jordan V., Travis S., Betsy W., Richard M., Gerardo M.)
We inspected all the viewports currently installed on HAM7, inspection was done to verify the serial number on the viewports or viewport assembly.
Most viewports passed visual inspection, however we did note that one viewport assembly on port A2F3 has some blemishes, they are located on the glass of the assembly on both, air and vacuum side. We asked others for a second opinion, we decided to leave current viewport assembly in place and replace it on the next vent. This particular viewport was inspected "recently" by others, see aLOG entry.
-Y door viewports:
Port A1F2 a ZV-800 serial number R144, nothing noted.
Port A1F1 a ZV-800 serial number R134, nothing noted.
+Y door viewports;
Port A2F1 has a ZV-800 serial number R146, nothing noted.
Port A2F2 has a ZV-800 serial number R109, nothing noted. Side note, this viewport has a AR1064 coating.
Port A2F3 has a D1100999, high quality non-wedged 6" viewport. Serial number 011. Some blemishes on the air side of the glass, located around 12 O'clock. Blemishes vacuum side of the glass, located around 2:30 to 3:30 O'clock.
Port A2F4 has a D1100999, high quality non-wedged 6" viewport. Serial number 022, nothing noted.
Pictures of the coating blemishes.
Viewports installed on HAM7 (PN, SN, and inspection notes) are recorded in spreadsheet on E2400096. This spreadsheet only includes the viewports installed for the A+ filter cavity line (HAM& & HAM8). Future in situ viewport inspections will be recorded here as well.
Jenne Drigger, Sheila Dwyer, Jennie Wright and Oli in chamber
The IMC guardian is now working when we put 3W into HAM1. Jenne held the output of MC2 M1 length drive, because that has not been working. We also edited the ISC_library is_locked(IMC function), by lowering the threshold used when the input power is above 2W. Since the IMC transmission has since improved it could probably be put back.
We engaged the WFS DOF1+2 which use MC refl WFS, and offloaded them. We then saw that we are well off center in MC2 trans P + Y, which were well centered on our reference time of 11:25 UTC Dec 3rd.
Jenne Driggers moved the IMs to match the top mass osems to the values from 89068. We also noticed that the whitening gain on IM4 trans was changed to 0Db (should be 18dB), making the power seem low in 89046.
| Dec3 | now | ||
| power into HAM1 | 2W | 3W (plus 30% loss on JM3) | |
| MC2 trans sum | 310 counts | 200-250 counts | 80% |
| IM4 trans NSUM (power into PRM) | 1.8W | fluctuating between 1W-3W | 1.45W expected |
| AS_C in single bounce | 3-4mW | 1.45*0.03*0.25*0.3 = 3.3mW into HAM6 | |
| IM4 trans pit | 0.23 | ||
| IM4 trans yaw | -0.04 |
Jennie and Oli are still working in chamber, so these numbers are still changing.
Olli and I went in and monitored IMC-MC2 YAW while changing the JM3 mirror in pitch, I loosened the locking screws for the pitvh adjustment to make it easier to move. Moving anti-lockwise in JM3 pitch moves down in yaw on the MC TRANS QPD due to the HAM1 periscope. We overshot a bit and had to correct the opposite way.
Every step I made we waited for the WFS to converge.
Every couple of steps we offloaded the WFS.
Then once we thought we couldn't get much closer we switched to adjusting YAW on JM3 to bring the MC2 TRANS pitch nearer to 0. The steps I made in yaw of JM3 didn't have as large an effect on MC2 TRANS as pitch so this was easier to tune.
I have included a plot showing our final values, 0.04 counts for yaw and 0.01 counts for pitch.
TITLE: 02/10 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:
JAC team worked on two fronts (one group in the optics lab getting a set up for measurements for the eom crystal and the other to do alignment work in HAM1). HAM7 continues the pumpdown. There was a DAC upgrade for OAF0 (in the morning Dave [remotely] will need to finish one task here which should NOT require a DAQ restart).
LOG:
J. Kissel, S. Koehlenbeck Executive Summary: after some more modeling of the beam profiles from LHO:89047, we identify that there's nothing fundamentally wrong in the analysis -- it's just that the out-going waist position of the beam exiting the SPI fiber collimators is just *extremely* sensitive to lens position -- to the tune of z_lens = 11 [mm] +/- 50 [um] can swing the waist position z0 = +/- 1.5 [m], and that makes it extremely challenging to set the waist at z0 = 0.0 [m] with out a better measurement setup/method for adjusting the position. The full story: Trying to better understand the results from LHO:89047, in this aLOG I: (0) Verified Beam Profile Fit with JAMMT instead of A La Mode: Imported the beam profile data from each laser into JaMMT, with the z-axis inverted (i.e. z = [-5.41, -4.496, ... , -0.508] [m]), and confirmed that JaMMT agrees with a la mode in terms of waist radius, w0, and waist position, z0 -- except now with the beam "incoming" into the collimator/lens/fiber. The fit predicts a waist w0 at position z0 of JaMMT A La Mode (Matlab) w0y' w0x' w0x w0y (assume w0x = w0y', w0y = w0x') OzOptics = (0.7041, 0.6766) [mm] (0.7040, 0.6766) [mm] AxcelPhotonics = (0.6807, 0.7048) [mm] (0.6807, 0.7049) [mm] at position z0y' z0x' z0x z0y (assume z0z = z0y', z0y = z0x') OzOptics = (-1.4940, -1.5840) [m] (1.4940, 1.5837) [m] AxcelPhotonics = (-1.5803, -1.4870) [m] (1.5803, 1.4869) [m] where -- you're reading that right, it's not a copy and paste error -- the difference between the matlab fit and jammt fits are at the \delta(w0) = 0.1 [um] and \delta(z0) = 0.1 [mm] level (though for some silly reason the convention of which is the x and y dimension is flipped between the two fitting programs). This reconfirms/is consistent with LHO:89047 fit of data and their statement that the waist radius, w0 = 0.6915 +/- 0.015 [um] at z0 = 1.5362 +/- 0.053 [m] See GREEN boxed answers in attached screenshots of OzOptics and AxcelPhotonics JaMMT sessions (1) Found Mode Field Diameter inside Fiber: Used each of those JaMMT sessions with imported / fit beam profile from both lasers (in the fiber collimator's current lens position) to model the mode field diameter of the fiber (thus validating the SPI conceptual design Slide 60 of G2301177 calculation MFD = 7.14 [um]). To do so, we install the f = 11 [mm] focal length lens at z = 0.0 mm -- i.e. finding the new beam parameters "down stream" (in the +Z direction, "in towards the fiber") post-lens assuming a f = 11 [mm] focal length lens placed at the ideal position. In JaMMT speak, we add a substrate that's a thin lens at position 0.0 [m], with aperture 5.5 [mm], and focal length 0.011 [m]. As can be seen in RED, the now-augmented OzOptics and AxcelPhotonics JaMMT sessions, inserting the fast lens dramatically increases the beam radius (+z of the lens, the red beam extends out as essentially vertically off the scale); which is indicative if really high divergence of the free-space beam as it is mode-matched into the fiber. Said in the direction of our experiment -- the beam coming from the fiber is highly divergent (extremely small waist radius in the fiber), and the fast lens brings the outgoing free-space beam "in check" dramatically reducing the beam divergence, i.e. "collimating" it. The JaMMT fit results remain in terms of radius, w0, but to distinguish this in-fiber waist radius from the free-space waist radius, I'll call these the Mode Field radii, MFw0. Those results are MFw0y', MFw0x' OzOptics (3.589 , 3.717) [um] @ MFz0y' = MFz0x' = 0.011 [m] AxcelPhotonics (3.597 , 3.726) [um] @ MFz0y' = MFz0x' = 0.011 [m] Note the order of magnitude on the units -- microns, not millimeters. Also note that the fit for position of the waist is 0.011 [m], or 11 [mm] for all four waist radius data points (to the precision of the display). This matches the ideal/expectation -- that we *want* the f = 11 [mm] lens to focus the free space beam down to the size of the waist of the beam in the fiber core, and to have that waist 11 [mm] away from the lens. In terms of diameter, that's MFDy', MFDx' OzOptics (7.1780, 7.4340) [um] AxcelPhotonics (7.1940, 7.4520) [um] This modeled MFD based on the out-going beam measurement, MFD_mean = 7.3145 +/- 0.1487 [um] is within 2.5% of the expected value for the MFD = 7.14 [um]. from a core radius of a = 2.75 [um], and *fiber* numerical aperture, NA = 0.12. (I was wrong to suggest that we might have needed to use the NA from the fiber collimator. Sina was right to use the NA of the optical fiber.) And just to hit that "highly divergent" point home, turning the mode field radii into a Rayleigh range [with MFzR = pi * (MFw0^2) / \lambda]: that's MFzR_mean = 39.49e-6 [m] as opposed to the collimated free-space beam that has a range of ~3.25 [m]. (2) Re-create the real system as a function of lens position With that modeled mode field diameter (radii) in the fiber, we can restart JaMMT with those initial beam parameters, but the position of the waist at z0 = 0.0 [m] rather than the +0.011 [m] we found from Step (1). This changes our frame of reference -- we now assume we know the field waist coming out of the fiber, and we position that field waist, MFz0 = -0.011 [m] behind the lens, and we're trying to *create* a collimated beam with the f = 11 [mm] lens, with a new waist at z0 = 0.0 [m]. In JaMMT speak, we (a) Reset and Clear Plot, then Edit the Initial Beam to have w0 z0 tangential w0 tangential w0 wavelength MFw0y' MFw0x' [um] [m] [um] [m] [nm] OzOptics 3.589 0.0 3.717 0.0 1064 AxcelPhotonics 3.597 0.0 3.726 0.0 1064 (b) Add a substrate; a thin lens, at position z = 0.011 (for now), with aperture 5.5 [mm], and focal length 0.011 [m]. (c) Add beam analyzers at each z position point of the originally measured vector, z = [0.508 0.991 1.499 2.007 3.251 4.496 5.41] [m] The results of (a) and (b) create the screenshots OzOptics and AxcelPhotonics, which show that with the lens at *exactly* z = 0.011 [m], or z = 11 [mm], that puts the waist at z_lens = 0.011 [m] ( w0x , w0y ) @ (z0x, z0y) [mm] [mm] [mm] [mm] OzOptics 1.0830 , 1.0023 22 22 AxcelPhotonics 1.0357 , 0.9999 22 22 This confirms that the original guess of the waist radius written in the assembly procedure of w0 = 1.05 +/- 0.1 [mm] when setting the lens position to have the waist position z0 = 0.0 [m], and thus a Rayleigh Range, zR = 3.25 [m] was not wrong at all. After adding in the analyzers (c), you get displays that look like OzOptics and AxcelPhotonics, from which you can read off the model of what the measured beam profile should ideally be. (3) Model/Discover just how sensitive beam profile of the out-going beam is to lens position: positioning needs to be accurate within 50 [um] (ridiculous!). Now, nudge the z position of the beam splitter in each data set until you reproduce the beam you measured / fit in Step 0. I find that a lens position of z = 0.011045 [m] = 11.045 [m] = 11 [mm] + 45 [um] reproduces a real focus that matches the beam profiles we measured and waist radius and position we fit consistent with w0 = 0.6915 +/- 0.015 [um] at z0 = 1.5362 +/- 0.053 [m]. 45 [um]!! A lens position 45 [um] the other way, z = 11 [mm] - 45 [um] = 0.10955 [m] pushes the waist position ~ 1.5 [m] behind the lens (z0 = ~ -1.5 [m]), i.e. it creates a virtual focus. See OzOptics z_lens = nom + 45 [um] OzOptics z_lens = nom - 45 [um] AxcelPhotonics z_lens = nom + 45 [um] AxcelPhotonics z_lens = nom - 45 [um] I conclude from this that with the existing measurement setup and great lack of precision in adjustability of the lens position, it's no wonder we ended up with a waist position off by 1.5 [m]. For the record, with the (OzOptics, AxcelPhotonics) laser's data set, to get the waist position z0 to actually be at 0.0 +/- 0.005 [m] ***, you need the lens position to be z_lens = (10.9997, 10.99969) [mm] = 11 [mm] - 0.3 [um]. Just ridiculous. *** Since the beam is a bit astigmatic, you can only model one axis to be exactly z0 = 0.0 at a time, so the 5 [mm] uncertainty covers the z0y position when you set the z0x to 0.0 [m]. After corroborating all of this with Sina, she's not surprised. In fact, she was more surprised when I claimed that collimating the beam was easy back in Jun / Aug of 2025. (4) Sina and I conclude the best hope we have is to (a) Don't worry about having the position of the collimator within the collimator adapter ring be as shown in T2400413. What's critical is that the alignment of the outgoing beam doesn't change in between lens position iterations. (b) Instead of entirely backing off the 2x tiny set screws that hold a given lens position, back off only 1x to try to reduce the freedom of the lens position a bit to hopefully increase the precision of the adjustment (c) Set up a measurement system the measures and fits the beam position at multiple points with rapid iteration (d) Change the density of measured z position points to get more near the collimator (e) If you *must* measure the beam diameter / adjust the lens position at one position -- do it near the collimator, rather than past the Rayleigh Range. But also, see steps (c) and (d).
Tony and myself are here at EX finishing up the EX ES measurement.
We did find that the excitations were turned on at GPS time: 1454787583, but no excitations came through the channel PCAL_EX_SUM_MON until after we were finished.
We did however have to restart a measurement due to a gap in the data. measurement #7 Both beams on the Working standard inside the RX module.
What we did not realize until after, was that at the time the gap happened the excitation switch INJ_MASTER_SW was turned back on and remained on for the remainder of the measurement.
Also Note:
PCAL laser here at End X is shuttered inside the TX module. The shutter control is turned to Local and intentionally closed, because we have stolen the RX sensor for lab measurements.
anthony.sanchez@cdsdell428: python generate_measurement_data.py --WS PS4 --date 2026-02-09
Reading in config file from python file in scripts
../../../Common/O4PSparams.yaml
PS4 rho, kappa, u_rel on 2026-02-09 corrected to ES temperature 299.7 K :
-4.701132373259706 -0.0002694340454223 2.8588448124243135e-05
Copying the scripts into tD directory...
Connected to h1daqnds1
martel run
reading data at start_time: 1454784870
reading data at start_time: 1454785410
reading data at start_time: 1454785815
reading data at start_time: 1454786310
reading data at start_time: 1454786835
reading data at start_time: 1454787210
reading data at start_time: 1454787660
reading data at start_time: 1454788220
reading data at start_time: 1454788740
Ratios: -0.46019480202307234 -0.46642274644534126
writing nds2 data to files
finishing writing
Background Values:
bg1 = 9.788561; Background of TX when WS is at TX
bg2 = 4.347145; Background of WS when WS is at TX
bg3 = 9.849034; Background of TX when WS is at RX
bg4 = 4.403818; Background of WS when WS is at RX
bg5 = 9.795756; Background of TX
bg6 = 0.716216; Background of RX
The uncertainty reported below are Relative Standard Deviation in percent
Intermediate Ratios
RatioWS_TX_it = -0.460195;
RatioWS_TX_ot = -0.466423;
RatioWS_TX_ir = -0.454775;
RatioWS_TX_or = -0.461187;
RatioWS_TX_it_unc = 0.087118;
RatioWS_TX_ot_unc = 0.081615;
RatioWS_TX_ir_unc = 0.080454;
RatioWS_TX_or_unc = 0.079252;
Optical Efficiency
OE_Inner_beam = 0.988331;
OE_Outer_beam = 0.989282;
Weighted_Optical_Efficiency = 0.988806;
OE_Inner_beam_unc = 0.054963;
OE_Outer_beam_unc = 0.053369;
Weighted_Optical_Efficiency_unc = 0.076611;
Martel Voltage fit:
Gradient = 1636.958979;
Intercept = 0.082747;
Power Imbalance = 0.986647;
Endstation Power sensors to WS ratios::
Ratio_WS_TX = -1.079194;
Ratio_WS_RX = -1.393794;
Ratio_WS_TX_unc = 0.051228;
Ratio_WS_RX_unc = 0.200042;
=============================================================
============= Values for Force Coefficients =================
=============================================================
Key Pcal Values :
GS = -5.135100; Gold Standard Value in (V/W)
WS = -4.701132; Working Standard Value
costheta = 0.988362; Angle of incidence
c = 299792458.000000; Speed of Light
End Station Values :
TXWS = -1.079194; Tx to WS Rel responsivity (V/V)
sigma_TXWS = 0.000553; Uncertainity of Tx to WS Rel responsivity (V/V)
RXWS = -1.393794; Rx to WS Rel responsivity (V/V)
sigma_RXWS = 0.002788; Uncertainity of Rx to WS Rel responsivity (V/V)
e = 0.988806; Optical Efficiency
sigma_e = 0.000758; Uncertainity in Optical Efficiency
Martel Voltage fit :
Martel_gradient = 1636.958979; Martel to output channel (C/V)
Martel_intercept = 0.082747; Intercept of fit of Martel to output (C/V)
Power Loss Apportion :
beta = 0.998895; Ratio between input and output (Beta)
E_T = 0.993838; TX Optical efficiency
sigma_E_T = 0.000381; Uncertainity in TX Optical efficiency
E_R = 0.994937; RX Optical Efficiency
sigma_E_R = 0.000381; Uncertainity in RX Optical efficiency
Force Coefficients :
FC_TxPD = 7.890432e-13; TxPD Force Coefficient
FC_RxPD = 6.178607e-13; RxPD Force Coefficient
sigma_FC_TxPD = 5.070187e-16; TxPD Force Coefficient
sigma_FC_RxPD = 1.259006e-15; RxPD Force Coefficient
data written to ../../measurements/LHO_EndX/tD20260210/
Obligitory before and after beam spot pics.
The problem we saw on measurement #7 where we saw a gap in the data was a DAQ restart which cuased the H1:CAL-INJ_MASTER_SW to turn back on. Which then caused H1:CAL-INJ_MASTER_OUTPUT so have a signal. So in the future if we see something like that again we should check the status of those CAL Line Injection switches before continuing again, as it apparently may increase our error bars.
Tue Feb 10 10:11:14 2026 INFO: Fill completed in 11min 11secs
We replaced the failed +/-12V Kepco supplies in VDD-C6 U34 which power the PSL dome cameras
U34_LHS: +12V supply S1201947 removed due to failed fan, replaced with upgraded supply S1202017
U34_RHS: -12V supply S1201992 removed due to failed fan, replaced with upgraded supply S1300289
F. Clara, M. Pirello
We turned off the HV bypass for upcoming HAM7 pump down. The power is located in the racks on the Mezannine in the Mechanical Room.
We followed Fil's instruction by first turning off the 24V for the interlock chassis, followed by removal of the bypass from the interlock chassis and then switching off the SQZ_PZT power. Finally I switched off the SQZ_TTFSS power, so that all high voltage is off.
We reconnected the pressure sensor while we were there in place of the bypass.
M. Pirello, G. Moreno, J. Vanosky
(Travis S., Jordan V., Gerardo M.)
Yesterday after inspecting the viewports on the +Y door, the pumpdown was started. The annulus was first, no issues with the pumpdown, pressure dropped nominally, indicates a good seal on the -Y door, then the main volume was blown down, dew point at -24.9 degrees C. Main volume was pumped for about 1 hour and 40 minutes, taking the pressure down to 33.4 Torr, then pumpdown was stopped for the night. We will continue with the pumpdown this morning.
Note, the cleanroom fans were turned off yesterday after the viewport inspection.
TITLE: 02/10 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
SEI_ENV state: MAINTENANCE
Wind: 9mph Gusts, 6mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.47 μm/s
QUICK SUMMARY:
HAM1 JAC investigation work will continue. Randy is testing out the new BSC2 Cleanroom Tent. LVEA continues in unique Bifurcated Laser Safe state.
Happy -Eve- of the10-year Anniversary of GW150914 Announcement!
Jennie W, Jason O, Keita K.
As reported in this alog (#89073) from Masayuki and Keita, after we turned the power in HAM1 up to 1W we found a series of vertically spread ghost beams aroubnd the main beam after the EOM and before JM3.
These could not be removed by translating, yawing or pitching the EOM position relative to the beam. It was decided in a larger meeting with EOM design personnel that we would first check if the crystal was cracked or damaged anywhere in case this is the cause.
First photo shows the EOM from above, using a green torch to illuminate the beam path. I can't see any scatter from defects or cracks in the crystal.
Second photo shows possibly a chip at the corner, but this should not affect the beam as its right at the edge.
Third and fourth show side view with illumination from the top at an angle.
In summary we did not see any 'smoking gun' to cause these ghost beams.
Very rough power estimate for the ghost beam(s) is ~O(1%)
Jennie and Jason set up another temporary iris between JM2 and JM3, centered it with 1W into HAM1 to carefully block the ghost beams without blocking the main beam, then changed the power to 100mW (for safety) and measured the power at various places. Measurement accuracy cannot be great (Jennie and Jason says the numbers were jumping around as it was difficult to hold the power meter head at a fixed position mid-air) but I would say the power in the ghost beams is ~O(1%).
| JAC out | ~105mW |
| Between JM2 and the iris (includes wrong-pol beam) | 104~105mW |
| After the iris (wrong pol as well as ghosts blocked) | 99~100mW |
| Wrong-pol beam | 1~3mW |
| Background light (no beam) | 1~2uW |
Where do they go?
After opening the temporary iris that we just put in all the way, the iris just downstream of JM3 was already blocking some of the ghost beams as well as the wrong polarization beam (JM3iris.jpg). Vertical beams don't look vertical because the iris is not a flat plane and we have a large parallax here. Anyway, it seems that we can block further if we want to from the top and the bottom.
The picture of the last iris on HAM1 shows that something is blocked on the left (+Y) side (outputiris.jpg). Looks like the iris is clipping something on the right but the camera couldn't be positioned to have a good view for both sides.
The last picture (after_last_iris.jpg) shows the beam right after the last iris on HAM1. You can see that some ghost beams are still coming through.
With this beam injected into HAM2 and misaligning MC2, we looked into IOT2L to see the MC REFL beam. We weren't able to find ghost beams there, though Jason and I felt that the beam is not super clean.
One question Jason had was whether or not the diverging beams that originate from the EOM location are supposed to keep diverging after lenses.
The beam after the second lens is actually not diverging. According to this plot, we suppose to be able to find the splitted beams in the IOT2 table.
EPO taggin'.
Following on from this log (alog #89046), we have already checked that the MC mirrors are restored to their previous positions from before the power cut in December. We know the seismic state now should be as close as we can manage to this time 2025-12-03 11:28:44 UTC when the mode cleaner was locked at 2W input power and before any HEPIs were locked for the vent.:
Summary of seismic state now:
HAM ISI locked. HAM 2, 3, 4, 5, 6 ISI isolated.
HAM1,2 and BSC2 HEPI locked. HAM 3,4,5,6 HEPI isolated - ie. as per nominal operation.
I trended the IM osems and the MC2 and IM4 QPDs in HAM2 while the mode cleaner was locked for mode scans yesterday (reference time is 2026-02-05 18:44:36 UTC).
It seem as though the MC2 and IM4 trans powers we have are lower now, but also the IM mirrors have changed.
As Sheila did yesterday I will try and summarise these changes in a table and compare whether this makes sense with the greater HAM1 loss we have because of the JAC (~40 %).
Just posting an updated version of Sheila's table to compare this new time (3rd December).
| 2025-12-03 | 2026-02-05 | ||
| seismic state | nominal | HAM1 ISI, HEPI locked, HAM2 HEPI locked. | MC mirrors should be at or close to nominal assuming table alignment didn't change much. |
| power into HAM1 H1:IMC-PWR_IN_OUT16 | 2W | 1W | |
| MC2 trans | 310 counts | 90 counts | consistent with 60% HAM1 throughput measured with a power meter (extra loss due to temporary mirror for JM3) |
|
IM4 trans nsum |
1.8W | 0.1W | should be 0.54 W so not consistent with JAC loss. |
| IM1 position P, Y | 3130, -679 | changed by -11, -0.44 | Off in pitch |
| IM2 P, Y | 915, -226 | -50, -3 | Off in both, mainly pitch. |
| IM3 P, Y | 44, -1634 | +4, -13 | Off in both, mainly yaw |
| IM4 P, Y | -2815, -22 | +64, -8 | Off in both, mainly pitch. |
So after this Sheila and I are going to try turning on the IMC ASC and working out if we can tune the alignment onto IM4-TRANS using the IMs.
Since the IMC is nicely locked, and we're only seeing 0.2 W on IM4 trans at a time when we expect ~1W, I moved the IM1, IM2, and IM3 to these positions. Still not very much on IM4_Trans.