Displaying reports 1-20 of 536.Go to page 1 2 3 4 5 6 7 8 9 10 End

Search criteria
Section: H1
Task: INS

REMOVE SEARCH FILTER
SEARCH AGAIN
Reports until 14:57, Thursday 25 June 2026
H1 ISC (INS, IOO, ISC)
keita.kawabe@LIGO.ORG - posted 14:57, Thursday 25 June 2026 (90759)
BS alignment is as good as we can get (at this point with available resources)

After in-chamber crews physically moved the BS, I was able to restore both the IMC flashes and the sqz beam reflected by ITMX as well as ITMY in AS as well as ISCT1 REFL camera by just using the BS sliders. sqzbeam_as_isct1.png and the video PXL_20260625_204834048TS.mp4

show the sqz beam in the AS (left) and ISCT1 (right) camera when IMC was misaligned, while PXL_20260625_204905669TS~2.mp4 is the video of the IMC flashes when SQZ beam diverter was closed.

BS top suspension offsets were  H1:SUS-BS_M1_OPTICALIGN_P_OFFSET = 107.00 and H1:SUS-BS_M1_OPTICALIGN_Y_OFFSET = 441.00.

Right now F2 coil is using ~10% of the DAC range (~13.3 million counts out of 135 million), F2 ~ 6%, and others are small. See BS_DAC_range.png. I don't think further trying to relieve this will be fruitful or useful.

Camilla found that ZM4 and ZM5 had additional rotation because of unintentional ASC output while in-chamber adjustments were being made. When they cleared the asc outputs the beam spot of ITMY reflection on the AS camera didn't change so the impact sshould be small.
The BS alignment looks as good as we can get with available resources at this point. Even though we know that the BS alignment nor the input alignment from PR3 to BS is perfect and that SQZ beam and the IFO beam are not co-aligned with each other, those things should be dealt with after pumping down.
sliders.png is the screen shot of most alignment sliders as of now.
Images attached to this report
Non-image files attached to this report
H1 INS
keita.kawabe@LIGO.ORG - posted 14:56, Wednesday 24 June 2026 (90745)
Dark offset for OMC DCPD

Adjusted the dark offset of OMC DCPDs in A0 and B0 filters and zero-ed A and B offsets (and disabled them).

  H1:OMC-DCPD_A0_OFFSET A_OFFSET B0_OFFSET B_OFFSET
Old -158 68e-6 -134 -803e-6
New -81.6 0 -89.5 0

I don't know exactly why people split these offsets in two different places, maybe that's because dark offset scripts was written when 512k ADC didn't exist?

Let's use A0 and B0 offsets for ADC rather than putting ridiculously small numbers in A and B.

H1 IOO (INS, IOO, SYS)
keita.kawabe@LIGO.ORG - posted 17:22, Tuesday 09 June 2026 - last comment - 14:00, Wednesday 10 June 2026(90549)
Mystery scatter/clipping in/on IFI, it's not the main beam clipping, don't know what it is but we should move on (Disha, Rahul, Keita)

We tried to diagnose the scattering or clipping or whatever that is visible inside the IFI output baffle aperture (alog 90536, especiall this video from that alog). It's not subtle, is always there even when the beam is blocked between PRM and IM4, and it's not just once in a while, it looks to be as frequent as strong flashes from IMC.

This is not the clipping of the forward propagating beam on the baffle as the beam height is pretty good (beamheight_dkdp_baffle.mp4) and YAW is also OK on dkdp baffle as well as IFI output baffle (dkdp_baffle_yaw.mp4IFI_output_yaw.mp4).

We took a video of the back (i.e. -Y) side of the IFI output baffle through the output CWP by inserting a big dentist mirror between DKDP baffle and CWP and shooting from the +Y side. Video will be posted later (the raw video from IR sensitive camera exceeds 15Mb limit of alog and I don't have a good editor on my laptop).

Anyway, it seems like something is maybe hitting the bottom edge of the baffle from the back, Disha and Rahul think that there's something at the top too but I'm not sure.

We don't know what it is but we've done everything that could be done in situ without resorting to drastic measures (like temporarily removing all suspension baffles that block our view, which takes time despite that we don't know if that helps or not, or moving IFI to the lab which I won't do at this point in time). Since I'm pretty sure that this is NOT the clipping of the main beam as was noted above, my recommendation is to give it up at this point and move on, knowing that this thing does exist.

Together with alog 90536, we're done with HAM1/2/3 alignment today. Let's hope that the IM1 mystery motion won't return.

Fil already started ground check of suspensions, we'll do the ISS unit and the QPDs in HAM2/3 tomorrow.

Non-image files attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 14:00, Wednesday 10 June 2026 (90574)
IFI_out_cwp_back1.mp4 and IFI_out_cwp_back2.mp4 show the flashes from the back of the output CWP.  IRVideo_Apparatus.png shows how the videos were shot.
(dkdp.mp4 shows the back of dkdp holder shot from -Y side of the table, could not find flashes. Not surprising given that we're not seeing the dkdp itself, there's no good position to look at this.)
Images attached to this comment
Non-image files attached to this comment
H1 INS
betsy.weaver@LIGO.ORG - posted 15:41, Tuesday 09 June 2026 (90553)
West Bay Cleanroom turned off

I wrap/bagged/tagged all of the stuff still out in the West Bay Cartridge cleanroom and we turned it off.  I also unplugged the garb room.

No more need to stock that area.  

We will move the bags and finish cleanup after the vent.

 

H1 ISC (INS, IOO, ISC)
keita.kawabe@LIGO.ORG - posted 20:32, Friday 05 June 2026 - last comment - 20:59, Friday 05 June 2026(90499)
Friday HAM1/2/3 alignment: Victory and Disappointment (Disha, Rahul, Jennie, Arnaud, Anamaria, Keita)

Short story:

RM2 was nicely relieved by rotating IM1 in YAW, ASC REFL sensors were centered, RM2 only used 40% of DAC range, people==happy (ASC-REFL-centered-20260605.png).

ISS QPD was nicely centered, it was easy, people==happy (iss_CENTERED.png).

Then suddenly we found that the IFO REFL beam is clipped at the bottom of the IFO REFL baffle, ISS array was totally out of whack, forward-going beam from IM2 was not centered on the retroreflection check iris between IFI input baffle and IFI HWP baffle, people!=happy.

Turns out that something bad happened to IM1 about 10 minutes after ISS was centered (IM1_bad.png). Without any change in the drive, H1:SUS-IM1_M1_OSEMINF_LL jumped by negative 172 counts causing apparent positive 1570urad jump in DAMP_P and DAMP_Y.  UR changed by 12 counts, which is like O(100urad) type change. 

This doesn't necessarily mean that IM1 moved that much, maybe one OSEM was bumped while we're trying to put the cover on the ISS, but the thing is that this must have caused physical rotation somehow because we see the beam moved downstream of IM1.

We tried to diagnose the IM1 but found no obvious touching, transfer functions didn't look wrong, EQ stops have gaps, magnets look as if they're OK.

You don't have to read further, below is our memo to remember what was done.

Details you don't want to remember:

We've made another YAW move (of positive 300urad) for IM1, i.e. [P,Y]=[517, -687] -> [517, -387] to relieve RM2 further.

Based on calculation, also moved IM2 and IM3 to roughly align things. IM2 [P,Y]=[0, -588.7] -> [0, -19] IM3 [P,Y]=[35.3, -415] -> [35.3, -86].

Checked the IFI output baffle and noticed that it seems to have an offset in -X direction relative to DKDP baffle. The beam was well centered on DKDP baffle, but was too much in +X direction on the IFI output baffle.

Moving IM2 further, [P,Y]=[35.3,  381] to split the difference.  Distance between the forward-going beam and the parking beamdump pickoff was ok.

This resulted in large IM3 Yaw step (IM3 [P, Y] = [35, 654]) to bring the beam close to the nominal position in front of PRM.  Horizontally, the beam was off by 0.5+-1mm in negative Y direction. Nominal beam height at the measurement point for PRM 159.05mm. Measured 157.1+-1mm.

IM4 Yaw moved by positive 350 ([IM4 [P,Y]=[761, -205]) to set the beam position in front of PR2. Horizontally, the beam was off by 0.5+-2mm in positive Y direction. Nominal beam height at the measurement point for PR2 168.56mm, measured 169.8+-2mm.

Centered the retro-reflection check iris to the forward-going beam between IFI input and IFI HWP baffle. Aligned PRM to center back-propagation on that iris. 

PRM [P, Y] = [-1185, -270].

Centered refl asc sensors. This worked really well, RM2 DAC was only using 40% of its range after centering ASC REFL sensors. Even though this was one attempt, I'm comfortable enough to say that we'll be fine.

Moved on to center ISS array. We removed the ISS array cover from the assembly to use the input aperture tool to make things easier. Large hole aperture as well as medium was used, didn't bother to use the small aperture. We used two pico mirrors (had to use hand because no driver is connected until the IOT2L is back). Iteration between two mirrors was easy and the centering was done by 22:37 UTC.

RM1 P, Y = -196, 209 (13% of DAC range)

RM2 P, Y = 609, -602 (40% of DAC range)

Happily we put the ISS array cover back on. Unknown to us, something happened to IM1 at around 22:46 UTC.  
 

Remaining task:

solve IM1 mystery?

shoot the pic of pico mirrors to see how much range we have.

center IM4_TRANS

take aperture photo for IFI inpjt and IM4 baffle, recenter IM4 baffle if necessary.

ground check.

Images attached to this report
Comments related to this report
jennifer.wright@LIGO.ORG - 20:59, Friday 05 June 2026 (90517)

I post this picture showing the separate osem trends for IM1 and also the CPS Z and RX motion of the chamber. The big step in LL IM1 osem was coincidental with noise in Z and RX  of HAM2 ISI so we think it was when we were leaning into the chamber to p6ut the cover on the ISS. Later on there is a step change in the Z and RX motion, I think this was when Rahul actually stepped into chamber to screw the cover screws down. I conclude that whatever happened was when we were leaning past the IM1 from outside the chamber.

I ran the rubbing scripts from this LHO alog #77383 for IM1 but wasn't sure how to interpret the results, reference time was midnight last night. The only one that looks really different is the yaw degree of freedom.

Annamaria drove some signals through each IM1 OSEM in turn to check for rubbing.

Time of test 02:00 UTC

Response in each OSEM UL push UR push LL push LR push
UL 17.7 0.6 8 10
UR 0.4 17 10.7 7
LL 6.6 7.5 15 1
LR 11 8 1 18

We used an actuation of 60000 counts offset added ther the COILOUT filter bank. We can't see any obvious imbalance in the response of the four osems.

Annamaria also ran an undamped TF in pitch, shown here compared to a reference measurement from 2024. This doesn't really seem to show any obvious rubbing.

Summary: As Keita said above we are confused as to what exactly is wrong with IM1.

 

 

Images attached to this comment
H1 ISC (INS, IOO, ISC)
keita.kawabe@LIGO.ORG - posted 00:32, Friday 05 June 2026 (90464)
Wednesday HAM1/2/3 alignment (Disha, Rahul, Keita)

Belated, as usual.

Things make more sense, no railing of RM2

We continued HAM2/3/1 alignment. Things are making more sense now after realizing that RM1 and RM2 slider polarity was wrong but we're still finding things.

1st attempt: We rotated IM1 to relieve RM2 YAW (IM1 y -987->-687 i.e. +300 from Tuesday value), aligned PRM so the beam retroreflects (but didn't touch up other IMs in the interest of time). After some confusion it worked and we were able to center REFL ASC sensors without railing RM2. Happy. (See ASCREFL_centered_RMs_dont_rail.png. If you do the math using flash peaks, REFL_A PIT=0.034, YAW=0.013, REFL_B PIT=-0.0097, YAW= -0.017, so it was very good.)

2nd attempt: Encouraged, we proceeded to center the beam on the IFI output baffle using IM2, steer the beam to the nominal beam position in front of PRM using IM3, steer the beam to the nominal position in front of PR2 using IM4 (which moves the beam position on PRM by a small amount but we didn't bother to iterate), and finally aligned the PRM so the retroreflection is restored. We were able to center REFL ASC sensors without railing RM2. Happy again.  (eod.png, REFL_A P= 0.034, Y=-0.009, REFL_B P=-0.023, Y=-0.022.)

We looked at the beam position on IFO REFL baffle and it was off in YAW,  so we changed the baffle position slightly in +Y direction.

Large difference in RM2 DAC output for two attempts, 80% or DAC range used in the 2nd attempt

We didn't change IM1-IM2 line, which means that the alignment into HAM1 should not have changed assuming that the PRM was retroreflecting, but the YAW offset necessary for RM2 to center the ASC sensors in the 1st and 2nd attempt were very much different.

all numbers are in urad

1st attempt

(PRM P, Y = -1165, 320)

2nd attempt

(PRM P, Y= -1165, -300)

2nd [P,Y]  - 1st [P,Y]
RM1 [P, Y] [-243, -45.3] [-257, -114] [-14, -68.7]
RM2 [P, Y] [930, -989] [950, -1489] [20, -500]

In the 2nd attempt, RM2 Y offset changed by negative 500urad and the DAC output of two of the RM2 coils reached ~107 million, which is about 80% of the DAC range. That's closer than I'd be comfortable with before closing down the chamber.

That's consistent with the retroreflection error 

It turns out that this is consistent with our retroreflection accuracy which I claimed to be "like +-50urad" in PRM rotation (not the beam rotation) in alog 90451.

Equivalent of positive PRM rotation of 50urad in YAW is replicated by the combination of physical negative 55urad for RM1 and physical negative 380urad for RM2 (note that the sliders for RMs as of now has the opposite sign as the physical rotation). 

If retroreflection is off in terms of PRM YAW rotation by +-50urad, when the REFL ASC sensors are centered, RM2 YAW would be off by +-380urad from what would be required to center the beam that is truly retroreflecting. See attached script. 500urad difference between two attempts is consistent with that.

On top of that, it's possible that +-50urad error estimate is too optimistic. We set the PRM angle by centering an iris (placed between IFI input and IFI HWP) to the forward going beam and centering the back propagating beam on the back of the iris. The basis for the accuracy is that we could start seeing how the circumference of the back of the iris is unevenly illuminated by the back-propagating beam when we gave the PRM 50urad offset, but the beam is always moving in YAW and sometimes rather slowly, so we have to eyeball the average beam position.

We don't know if the 2nd attempt was closer to the true retroreflection or, for that matter, if the true retroreflection is "on the other side of" the 2nd attempt relative to the 1st.

As such, it's prudent to relieve RM2 YAW offset further.

Tomorrow

Relieve RM2 further by giving IM1 a positive 300urad YAW rotation. IM2, IM3, IM4 and PRM should be readjusted accordingly.

IM1 YAW offset hasn't changed much in the past 2 years except for this week, and we'll go back to that neighborhood. Even though this means that the beam on IFI input baffle will be off-centered (probably it's been like that for years),  I'm absolutely sure that the forward-going beam won't be clipped, I'm also quite sure that the clipping-like thing of the IFO REFL beam on the IFI input baffle won't come back as far as PRM is retro-reflecting.

We might have to move the IFO refl baffle again.

We WILL move the IM4 baffle because whenever the beam is aligned to the nominal position in front of PRM the beam is too close to the +X edge of the baffle.

Images attached to this report
Non-image files attached to this report
H1 ISC (INS, IOO, ISC)
keita.kawabe@LIGO.ORG - posted 19:49, Tuesday 02 June 2026 (90451)
HAM1/HAM2 alignment: RM sliders sign seems to be consistently wrong, confusing us (Disha, Rahul, Keita)

Good thing:

In the morning, we placed an iris placed between the IFI input baffle and the IFI HWP baffle (irisposition.png). We used an IR sensitive DSLR as a viewer to center the iris for the forward-going beam, and observed the back side of the iris using the same camera to see the PRM reflection.

This allowed us to set the PRM angle in much better accuracy than using a card with a bigger-than-needed hole handheld at an inconvenient location and observe with naked eyes through the laser glasses. We had to close down HAM3 cover as well as one side of HAM2 so PRM quiets down, but the retro-reflection accuracy was like +-50 urad (rather than +-500urad of yesterday).

With this new PRM alignment ([P, Y]=[-1165, +750]), I was able to center REFL sensors despite that RM2 was so close to railing, RM2 YAW offset was -1800urad. (ASC_REFL_balanced_20260602_morning.png and ASC_REFL_balanced_but_RM2_close_to_railing_20260602_morning.png.)

Nice thing was, at this point the beam was much closer to the center of IFI input baffle, IFO REFL beam clipping-like thing observed on the IFI input baffle was completely gone as well as the clipping on IM4 baffle. So things looked better in general than they were yesterday.

Bad thing:

RM2 was so uncomfortably close to railing nobody should leave it like that before pumping down, so I decided to relieve RM2 by tilting IM1. (Calculation is in alog 90404.)

I thought RM2 should be rotated counter-clockwise seen from the top because that would mean the positive YAW offset, we added negative 100urad to IM1 YAW offset (i.e. from -887.1 to -987.1 urad) based on my calculation, expecting to shave off 300 or 400 urad from the RM2 YAW. We reset the iris position for the forward-going beam, then reset the PRM angle, fully opened the iris and started centering the REFL sensors. Disappointingly, we couldn't center them, RM2 railed.

What was wrong:

We wasted some time trying to somehow find a magic slider values for RMs and going through how the angle of IM1 propagates to RMs, but it turns out that RM alignment sliders seem to have the opposite sign than all other suspensions. As far as we believe that the OSEM sensor (not actuator) produces positive DAC output that is proportional to the number of photons, the conclusion is that the sign of the sliders is wrong for both RM1 and RM2.

This is clearly shown in wrongsign.png where slider offsets of RMs were zero-ed one by one (top row) while the OSEM sensors in Euler bassis (bottom) were observed. Ignore the cross coupling from P actuation to Y sensing. In a suspension that follows the LIGO sign convention, the slider and the sensors move in the same direction roughly by the same amount. RM is the opposite of that, sensors move in the opposite direction of the sliders. We have done the same test for RMs, PM1 (see PM_is_good.png), OM1 (because they're all tip-tilts) and IM1 (because we touched it today) and confirmed that RMs are an exception.

If you're not sure about the rotation convention of LIGO optics, positive YAW rotation means counter-clockwise seen from the top. This will increase the light power on RIGHT OSEM sensors and decrease it on the LEFT. Given that the ADC reports positive voltage (i.e. positive counts), and given that usually OSEM YAW signal is proportional to voltage(RIGHT)-voltage(LEFT), positive physical YAW rotation will produce positive OSEM YAW change.  See my cartoon (LIGO_YAW_sign_convention.jpg).

Now, RM1, RM2 and PM1 sensing look identical to me (osemsensors_look_good.png).

All OSEMs produce positive numbers for all three suspensions, there's no sign flip in the filters, filter output sign is only determined by whether or not the input is bigger or smaller than the mid-point offset, they all use identical OSEM2EULER matrix as well as SENSALIGN matrix, and the sign of DAMP_P as well as DAMP_Y are all according to the filter outputs and these matrices. So the sensors for RM1 and RM2 are working in the same way as PM1, they're fine.

The conclusion to me is that somehow the actuation sign is wrong for RM1 and RM2.

Rahul told me that the magnet polarity was wrong for RM1 or RM2 and people spent some time to address that issue. But that sounds like the actuation side issue which should NOT affect the validity of the sensors. Unless people tell me that somehow the physical UL/UR/LL/LR sensors are wired to the LR/LL/UR/Ul channel or something, we just believe the OSEM sensors and assume that the sign of sliders is flipped.

Tomorrow:

Regardless of the reason of the sign flip, we'll proceed to move IM1 in the opposite direction, i.e. somewhere between this morning and Friday. 

FYI below is the history of IM1 YAW offset in the past week. The change made on Monday was motivated by the "need" to relieve RM2, but now that we know that the PRM retroreflection accuracy matters, I'm not sure if it would have been impossible to center REFL ASC sensors on Friday if we used the iris technique to align PRM. 

  Friday last week Monday Monday This morning This afternoon
IM1 YAW slider -387urad -887urad -887urad -887 -987
PRM retroreflection questionable questionable (YAW offset = 1000urad) questionable (YAW offset = 700 urad)

better (YAW offset = 750)

better (YAW offset = 1000)
REFL ASC centered No (RM2 rails) No (RM2 rails) yes yes (RM2 close to railing) no (RM2 rails)

 

 

Images attached to this report
H1 IOO (INS, IOO, ISC)
keita.kawabe@LIGO.ORG - posted 12:34, Monday 01 June 2026 - last comment - 12:34, Monday 01 June 2026(90404)
IMC, IM2/3/4 and PRM are aligned, cannot center ASC REFL sensors (JennieW, Rahul, Keita)

Belated alog from Friday.

Summary:

After realigning IMC and IM2 on Thursday, we continued aligning IM3 to put the beam in front of the PRM to the nominal position, IM4 to set the beam position in front of PR2, and PRM so the beam retroreflects. IM1 was left untouched, so the only change in IM1-IM2 line is from the change in the IMC alignment.

Clipping on IM4 baffle (HA12) disappeared completely. Beam position on IFI output baffle looked OK. Beam position on IFI input baffle didn't change (as expected) and still looked OK. There are some mystery 

We saw flashes on ASC REFL sensors but they were weak. We tried to center them using RMs but RM2 seems to rail in YAW.

  Before P, Y [urad] After P, Y difference P,Y
RM1 -196, 281.8 -242, -19.3 -46, -301.1
RM2 910, 490 912.1, -2125.15 (railing) +2.1, -2615.15

What to do:

Scan PRM to make sure that we're NOT looking at some kind of ghost beam on ASC REFL sensors.

Assuming that we're looking at the real beam on REFL sensors, we can do either (or some of) these:

Images attached to this report
Non-image files attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 01:09, Monday 01 June 2026 (90405)

See screenshot for before/after slider values for RM, IM and other optics.

Images attached to this comment
keita.kawabe@LIGO.ORG - 11:36, Monday 01 June 2026 (90412)

Baffle pictures. Whenever appropriate, there are two pictures (one to access PIT and the other to access YAW) to avoid the parallax problem as the thickness of the baffles cannot be ignored.

IFO REFL looks good on the IFO REFL baffle (HA13) in front of the HAM2-HAM1 septum window (IFO_REFL_HA13.jpg).

IM4 baffle (HA12) is good in PIT (IM4_HA12_PIT_good.jpg), not great in YAW but is OK (IM4_HA12_YAW_OFF.jpg). Next time I'll take a picture through IM4 to show you it's quite acceptable than it looks from these pictures.

IR picture of the IM4 baffle (HA12) shot from IM3 side shows a ghost beam it catches when there's a flash (IM4_HA12_ghostbeam.jpg). Circled in red is the ghost beam (in this case it was 10 mode flash). Circled in green are things that are always visible (IM4_HA12_noflash.jpg) and aren't the ghost beam.

IFI input beam position is great in PIT, not great in YAW (IFI_INPUT_PIT_GREAT_YAW_OFF.jpgIFI_INPUT_PIT_GREAT.jpg).

However, I still see some kind of clipping of bacdkward-going beam once in a while. See the IR photo shot from IM3 direction IFI_INPUT_clipping.jpg. You're looking at the baffle aperture through calcite wedge from the direction of IM1. Compare with IFI_INPUT_noflash.jpg where there was no flashing.

Not every flash shows this clipping-like thing, it seems to happen less frequently than the flashing. 

To make things more confusing, there's a reflection of something shiny in IFI and the edge of that shiny thing is almost on top of the edge of the IFI input baffle aperture so it's hard to say what's going on.  Nothing like this was visible on the input side facing IM2.

We temporarily moved IM1 to move the beam spot on IM2 more centered (IFI_INPUT_IM1movedtocenter.jpg) and I can see something closer to the center (probably scattering from the CWP?) but no clipping. So probably it's a good thing to move IM1 counter-clockwise as I indicated in the alog above. We cannot do it too much as we rail RM2 in the opposite direction, but we can probably move the beam by a mm or so on IM2.

Images attached to this comment
H1 ISC (INS, IOO, ISC)
keita.kawabe@LIGO.ORG - posted 13:45, Wednesday 27 May 2026 - last comment - 13:46, Wednesday 27 May 2026(90343)
IM4 beam position (Rahul, Elenna, Keita)

IM4 (and IM4 baffle) beam position

This is a belated alog from Tuesday.

Starting point: Same alignment for MC123, IM123 as last Friday, i.e. the IM4 baffle NOT centered nor unclipped.

Without touching IMC and IM1/2/3, we rotated IM4 to steer the beam close enough to the nominal beam position in front of PR2, and measured the beam position horizontally and vertically relative to the known screw hole in front of PR2 and PRM.

The distance between IM4-PRM beam line as of now relative to the nominal PRM-PR2 center line was calculated to be 3.9+-1.1mm in -Y direction and too low by 2.9+-1.1mm. See measurement_cartoon.jpg for the horizontal position case. Height is derived in the same way. Since the beam position in front of PR2 is not grossly off, and since IM4 is much, much closer to PRM than PR2, you can use these numbers as the spot position on PRM, too.

From IM4baffle_20260526.jpg, centering the beam on PRM will correct the height on IM4 baffle (HA12). Horizontally it will within a couple mm or so from the center.

What we should do

As we're running out of time, give up the idea to understand what happened to the alignment during the vent before closing HAM2. We should recenter things whenever possible (but only when the IFO REFL path and POP sled path are not disturbed to the point we clip or lose the beam).

For IMC, 

 

For IMs,

following is the table of slider offsets as of now.

  IM1 IM2 IM3 IM4
PIT 517 810 -614 531
YAW -387 -88 385 64

Even though the physical PIT angle of the optics relative to the local vertical axis is arbitrary, it seems that IM1 is bringing the beam down on IM2, IM2 is bringing down the beam further on IM3, and IM3 is bringing up the beam on IM4 and PRM. But IM2 is twise as efficient as IM3 for changing the beam position on PRM. Besides, the beam is already coming down from MC2 to MC3 (about 10mm height difference over 16m, or about 220urad) and I don't know if it makes sense to use IM2 to bring the beam further down. It's worth redistributing PIT as well as YAW offsets to relieve big offsets.

However, note that ultimately IM1-IM2 line defines the IFO REFL path when PRM retroreflects. (Even if you rotate IM2, as far as IM1-IM2 line doesn't change the IFO refl beam won't move.) I won't touch IM1 as moving the beam on e.g. IM2 even just a few mm using IM1 (i.e. a few mm over ~1.8m leverarm) will result in a much bigger change for REFL path in HAM1, potentially risking yet another clipping or maybe the loss of the REFL beam. IMC alignment noted above will change the IM1-IM2 line, but that's basically the angle change of ~3.6mm/16m (i.e. an order of magnitude smaller than when moving IM1 to steer the beam on IM2 in a meangful amplitude). That's small enough it's hard to imagine that the beam will be clipped by IFO refl baffle nor the downstream optics.

So,

PIT

IM2 IM3 IM4 PRM
IM2 (810 -> 310, negative 500urad)  0 1.2 +2.8 +3.5mm
IM3 (-614.7 -> -434.7, positive 180urad)     -0.4 -0.6mm
Total change   1.2 2.4 2.9mm (higher)
Position as of now       -2.9mm (too low)

 

YAW IM2 IM3 IM4 PRM
From MC2 beam spot change

0.4mm (-X)

0.6mm (-X) 1mm (-X) 1.2mm (+Y)
IM2 (-88 -> 112urad, positive 200urad change)   0.5mm (-X) 1.1mm (-X) 1.4mm (+Y)
IM3 (385urad -> 0, negative 385 urad change)     0.9mm (-X) 1.3mm (+Y)
Total change 0.4mm (-X) 1.1mm (-X) 3mm (-X) 3.9mm (+Y)
Position as of now       3.9mm (-Y)

 Of course this is assuming that the slider calibration is correct, so take this as a qualitative reference to get the sense of sign of angle changes. Anyway, when this is done, the DAC counts for IM2 and IM3 will be smaller while the beam height on PR2 will be fine. 

  IM1 (no touch) IM2 IM3 IM4
PIT 517 810-> 310 -614-> -434.7 531-> ?
YAW -387 -88-> 112 385-> 0 64-> ?

After doing the above,

If centering HA12 (IM4) baffle is important, relocate HA12. I'll ask Rodica.

Make sure that PRM retroreflects. Readjust if not. Check IFO REFL beam on IFO REFL baffle, LSC REFL and ASC REFL sensors. 

Recenter IM4_TRANCE by pico. 

Realign ISS array (simply because it's easier to do it in air than in vacuum).

Homework

Think about POP sled path. Is it conceivable that we'll somehow miss the beam there because we change the beam spot position on PRM?

Images attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 13:46, Wednesday 27 May 2026 (90360)

These pictures explain the horizontal beam position measurement in detail.

Images attached to this comment
H1 IOO (INS, IOO, ISC)
keita.kawabe@LIGO.ORG - posted 17:29, Thursday 21 May 2026 - last comment - 11:25, Thursday 28 May 2026(90295)
Beam positions in HAM2 and some thinking (Rahul, Elenna, Keita)

(I learned from T0900486 "IO Stray Light Analysis and Baffle Design" that the IFI input baffle is called HA3, IFI output baffle is HA6, the baffle right in front of IM4 is actually supposed to be a pair of HA12-a and HA12-b but there's only one baffle which I suppose is HA12-a, two-hole baffle for ISS array is HA11, and the last IFO REFL before the beam leaves HAM2 is HA13.)

Clipping on the IFI input baffle (HA3) might not be real

The beam spot on this baffle was OK before we did anything to IM1 on Tuesday (IFIinput_before.jpg). It's low and toward +X, but nowhere near clipping.

This baffle is right in front of the calcite wedge that deflects the IFO REFL beam away from the incoming beam path from IM2 (HA3_calcite_wedge.png). The lever arm from the wedge to the baffle looks to be an inch or so at most. Hard to imagine that the REFL is clipped while forward going beam is not, but the scattering goes away when I block the beam between PRM and IM4.

The reported "IFO REFL beam clipping" on this baffle is either because the PRM is not retroreflecting, or maybe it's some kind of ghost beam produced from the PRM reflection somewhere.

If we establish that the main IFO refl is NOT clipped when PRM retroreflects, we don't have to worry about this baffle too much (though ghost beam is still a problem).

We will have to bring a card with a hole to make sure that the beam is retroreflected as good as we can.

FYI, IFIinput_aftercentering.jpg shows the same baffle after we made a huge change in IM1.

We THINK that the beam on the IFI output baffle (HA6) is OK too but we need to check

We don't have any good view of that baffle so it's hard to assess, and we forgot to check it before making changes to IM123.

However, given how small the change was on IFI input baffle, we don't expect that it was very bad before. We'll have to revisit and confirm.

IMC beam spots

As of now, the measured beam position in front of MC mirrors are as follows this. For measurement points, see mc_beampos_measurement_cartoon.jpg. The height is pretty good for all. MC3 is great horizontally too. Beam spot on MC2 and MC1 are both shifted in -Y direction.  MC2 by 3.6+-1mm, MC1 by a couple +-1mm.

  Height from ISI measured [nominal] Horizontal shift in Y direction from the nominal beam position
MC1 154.3 +- 1.3 [155.5] -1.9 +- 1
MC2 167 [166.7] -3.6 +- 1
MC3 154 +- 0.5 [155.5] +0.3 +- 1

Horizontal positions were determined by covering half of the beam with a vertical hard edge (ruler etc.) and then measuring the position of the edge relative to the neighborhood screw holes using a small ruler, and then using the drawings (D0901088, D901089, D0901099) as well as other IO documents (e.g. T0900486) to figure out the nominal beam location. As an example of tedious work done, see ham2mc1.png. Due to the way it was done, we cannot determine the horizontal position of the beam much better than maybe 1/2 of the beam radius. I just put +-1mm error for all measurements. Height numbers were measured off of a ruler, the error bar (if any) is the difference between Rahul's reading and mine divided by two.

What if we move MC2 or MC3 beam spots (or both) to unclip IM4 baffle (HA12)

To get more sense of magnitude of IMC motion relative to the beam motion on IM4, I calculated how much the IMC alignment should be changed to move the beam on IM4 by 3mm in -Y direction (comfortably far from clipping but not enough to center) without moving IMs.

There are many linear combinations of the MC3 spot position and the angle of the beam coming through MC3 that will move the beam on IM4 by 3mm, so I just chose "parallel transport of MC2-MC3 line" (i.e. no angle change of the angle of the beam coming out of MC3), "rotate MC2-MC3 line around MC3" (i.e. no beam displacement on MC3) and something in-between ("rotate around MC2").

See cartoon_IMC_alignment_to_unclip.png (not to scale but the sign of displacement/rotation is correct along the entire path) and IMC_to_unclip_HA12.png (actual calculation). IMC is not the only thing that moves, we can also move IM2, but anyway. In the "parallel transport" case the beam will be move further away from the center of MC2 (remember it was already 3.6+-1mm in -Y direction to start with so the end result will be 6.8+-1mm in -Y direction). OTOH in the "rotation around MC3" case, the beam on MC2 will move by 11mm in +Y direction so the end result will be 11-3.6+-1=7.4+-1mm in +Y direction.

In all cases the beam will likely still hit the IM4_TRANS because the QPD (Excelitas C30845) has a huge 8mm active diameter, but it will likely be completely in one quadrant. So all of these will be bad solution if we believe that the IM4_TRANS position should be close enough.

Note that the "rotation around MC3" case will result in about 1mrad beam angle change on IM4. This needs to be absorbed by IM4 rotation by about 500urad to send the beam to PR2. 

It's also worth noting that IM4-PRM HR distance is almost the same as IM4-IM4_TRANS distance.

What if we fix the beam on IM4_TRANS?

Instead of IMC alignment, now let's think about the beam positions from the end point (IM4_TRANS).

Again, assume that we want to keep the IM4 TRANS beam position. We tried two different IMC alignment, and the beam was clipped on IM4 baffle (HA12) after bringing the beam back to the target IM4 TRANS position.

Moving the beam position on HA12 by 3mm in -X direction without changing the IM4_TRANS position means that we shift the beam position on IM3 by about 8mm. IM3-IM4 path beam angle changes by 4.8mrad counter-clockwise. This is an absolutely huge change. 

PRM should be moved by 2.4mrad, and 8mm on IM3 is already the radius of IFI output baffle (HA6)  so we'll be worrying about clipping there. There seems to be no solution where the beam is far enough from the IM4 baffle (HA12) edge AND the beam is on the same position on IM4_TRANS as in vacuum. 

As far as we assume that IM4_TRANS is trustworthy, it's very likely that the beam was clipping or at least very close to clipping on HA12 in O4.

However, if IM4_TRANS path moved after HAM2 was opened (i.e. somebody bumped something), IM4_TRANS position as of now doesn't mean anything. We have to at least grab and wiggle the steering mirror as well as the QPD for that path to make sure that nothing is loose. (I already did that test for MC2 TRANS, and they didn't move.)

Images attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 17:42, Thursday 21 May 2026 (90305)

Attached are an example of beam position measurements (in this case MC1).

Images attached to this comment
keita.kawabe@LIGO.ORG - 13:41, Friday 22 May 2026 (90321)

IM4_TRANS path optics (pickoff for the ISS path, pico for IM4_TRANS centering) as well as the IM4_TRANS QPD itself seemed to be firmly attached to the pole and the ISI table. I grabbed them using my hand and wiggled and they didn't move at all.

keita.kawabe@LIGO.ORG - 17:23, Friday 22 May 2026 (90327)

PIT angle of the beam from IM4 to PRM AR to PR2

The beam is level between IM1 and IM4 and then goes up toward PRM, but I cannot easily find how much. So here's a quick note.

  MC3 IM1 IM4 PRM AR PRM
Height [mm] 155.5 155.5- 155.3   158.8
Angle [rad] of the exiting beam relative to the horizontal plane   level 8.5m 628u 628u

Nominal height of MC1 and MC3 center is 155.5mm (D09010088, D0901089). IM1 beam height should be pretty close though MC2-MC3 line is not level.

The beam from PRM HR to PRM is tilted up by 0.035966 deg = 628urad (I'm using the PIT angle of PRM itself in  D0901920 rather than reading the coordinates of PRM and PR2).

PRM has 1 degree vertical wedge (D0901172), the bottom being widest, so the beam is tilted up from IM4 to PRM AR by ~(n-1)*1deg = 0.4497 deg relative to the PRM-PR2 line, n being the refractive index of fused silica for 1064nm (1.4496).

The beam from IM4 to PRM AR is therefore tilted up by (0.4497+0.035996) = 0.4857 deg = 8.5 mrad relative to the horizontal plane.

PRM center height is 158.8mm nominal (D0901090) and the distance from PRM AR to IM4 is 415.9mm (T0900486), so the beam height at IM4 should 158.8-415.9*8.5mrad = 155.3mm, which is good enough of an agreement with MC3 height.

FYI I measured the IM4 baffle height this morning and it was (206+104)/2 =155mm, so the baffle height should be correct. (The beam is low on that baffle though YAW is the worse problem than PIT.)

keita.kawabe@LIGO.ORG - 11:25, Thursday 28 May 2026 (90336)

This is the beam position measurements for MC2 and MC3.

Note: In D0901099-V2 on page 9, it looks as if MC2 HR surface is supposed to be rotated by 0.231 degrees clockwise seen from the top.

I don't think that makes sense unless the ISI table itself is supposed to be rotated 0.231 degrees counter-clockwise because the IMC is an isosceles triangle, MC1-MC3 line is parallel to Y axis and MC2 Y coordinate is the mean of MC1 and MC3 Y coordinate according to the global coordinates of MC1, MC2 and MC3 (E1100494-V4, E1100494-V6).

I assume that the ISI tables aren't nominally rotated around local Z axis.

  Global X Global Y Global Z
MC1

-20,072.0

255.0

-97.3
MC2 -3833.1 487.5 -87.3
MC3

-20,072.0

720.0

-97.3

 

Images attached to this comment
H1 IOO (INS, IOO, ISC)
elenna.capote@LIGO.ORG - posted 17:22, Monday 18 May 2026 - last comment - 08:22, Wednesday 20 May 2026(90267)
Moving input beam to unclip on HAM2 IO baffles

[Keita, Rahul, Elenna]

Today I moved IM2 and IM3 to bring the beam back to our reference position on IM4 trans QPD and center it on ISS QPD after Keita's move of the mode cleaner mirrors in 90259. This requires some iteration back and forth on both suspensions.

Our desired positon on IM4 trans is P = 0.22 and Y = -0.06. On ISS QPD, it is centered, so P=0 and Y=0.

We are driving MC2 in length, so the mode cleaner is flashing, and there are bright flashes on the QPDs. I am pausing ndscope on a flash and measuring the height of the peak in the fast channel and calculating the pit and yaw position from each QDP segment.

  Start   End
IM2 P slider 765 IM2 P slider 810
IM2 Y slider -187.7 IM2 Y slider -88.7
IM3 P slider -560.7 IM3 P slider -614.7
IM3 Y slider 320 IM3 Y slider 385
       
IM4 trans PIT 0.390 IM4 trans P 0.268
IM4 trans YAW 0.450 IM4 trans Y 0.010
ISS QPD PIT -0.379 ISS QPD PIT -0.059
ISS QPD YAW -0.455 ISS QPD YAW 0.08

Unfortunately, this still results in clipping on the baffles Keita notes above, so we will keep going.

At the nominal IM4 trans position, yaw is pretty well centered. I then moved IM2 to both edges of IM4 trans QPD.

I changed the IM2 yaw slider to -250.7, which brought the yaw position on IM4 trans to 0.85. This made the clipping worse.

I changed the IM2 yaw slider to 90.3, which brought the yaw position on IM4 trans to -0.88. This was still not good enough to fix the clipping on the baffle.

By making a very large move to IM2 yaw slider value of 710.3, this centered the beam in the IM4 baffle. This is a ~800 urad move according to the osems and slider. The IFO REFL beam is still clipped.

I undid the 800 urad move, so the IM2 yaw slider is back to -88.7 for now.

Keita and Rahul went out to measure the position of the beam on MCs 1,2 and 3. We think that we need to make a move of these three mirrors to see if we can unclip the beam on these baffles that way.

We want to note that the positive yaw move of IM2 corresponds to unclipping on the IM4 baffle, this is consistent with the beam motion observed in chamber in the -X direction. However, this is contradictory to the sign on IM4 trans QPD, which was moving to negative yaw when we did this move. We suspect that the segment defintion must be wrong somewhere.

Keita will say more later once we have a chance to analyze the positions in chamber.

To clarify, the slider values of IM2 and IM3 are left at the "end" positions on the table above.

Comments related to this report
elenna.capote@LIGO.ORG - 12:54, Tuesday 19 May 2026 (90282)

I trended the power measured at IM4 trans compared to the IMC input power for the entirety of the run. Some notes:

  • IM4 trans was recalibrated July 2022 based on Craig's integrating sphere measurements in HAM1, 63812
  • Sheila picos to center the beam on IM4 trans Dec 2024, 81735
  • Sheila and I recalibrated IM4 trans in O4c because the beam shifted on IM4 trans, we moved the input alignment and the power measured on IM4 trans changed, 82260

Because of this recalibration, I decided to compare both the IM4_TRANS_INMON and IM4_TRANS_OUT16 to IMC-PWR_IN_OUT16

FM10 in the IM4 trans filter bank is a factor that Craig and Georgia determined in the alog linked above, 4.606. I trended the inmon channel and multipled it by this number, ignoring other calibration factors present in the filter bank.

Therefore, the plotted ratio of IM4_trans [IN, OUT] / IMC power IN will help us understand how the power at IM4 trans changed throughout the run, like perhaps if the amount of clipping on the way to IM4 has changed.

I am comparing the ratios of both IM4 trans IN and OUT just in case we get confused by the changing calibration of the diode. I took an hourly median of these channels so we are not confused by random variation and masked the times to only show when IMC lock was either in state 100 (locked) or 70 (ISS ON).

Overall, the amount of power arriving on IM4 trans has definitely changed throughout the run.

Notably, during the vent between O4a and O4b, the amount of power measured at IM4 trans dropped. We chose not to move the IMs, and instead Sheila picoed to recenter on IM4 trans, linked above. Another power drop occured again during O4b. This time, we moved IMs to fix it. At the start of O4c is when Sheila and I recalibrated the diode, hence the disagreement with IN and OUT channels.

The second plot attached shows how the pitch and yaw on IM4 trans has varied alongside the power.

Based on what Keita can see happening in the chamber with baffle clipping, it is possible that during these alignment shifts, the amount of clipping in HAM2 on the IO baffles was changing, so the amount of power making it to IM4 trans and the amount of power going into the IFO was changing.

Specifically, I want to emphasize that with Craig's integrating sphere measurements in HAM1, we assumed that all loss between HAM1 and the PRM in HAM2 was known, i.e. loss from the IFI, etc. However, if there was additional loss on that path that changed with input alignment shifts, that would explain the apparent IM4 trans power changes during O4. Notably, Sheila and I recalibrated IM4 trans in O4c because after we fixed the input alignment in late O4b, we got more power on IM4 trans than we had gotten all run (see the jump around day 600 on the attached plots). I thought this was not physically possible, so we adjusted the calibration. Perhaps instead, we changed the amount of clipping in HAM2, giving us more light on the PRM than we had seen all of O4.

This may also help explain some of our arm power measurement mysteries if we actually had less input power than assumed.

Non-image files attached to this comment
elenna.capote@LIGO.ORG - 08:22, Wednesday 20 May 2026 (90292)

I just want to add a clarification that we have been trying to replicate the alignment onto IM4 trans QPD, so we are trying to align to the previous pitch and yaw position. However, for O4, the beam was nearly falling off the ISS QPD, so we don't want to replicate that alignment (the pitch and yaw values on ISS QPD were like +- 0.9). We have decided to go with centering the beam on ISS QPD, especially since we have adjusted the ISS pico mirrors to find that alignment.

H1 IOO (INS, IOO, ISC)
keita.kawabe@LIGO.ORG - posted 23:19, Saturday 16 May 2026 (90259)
IMC alignment work on Friday, not that much success (Keita, with remote help from Elenna and Sheila)

One problem solved, two problems found.

Clipping on IFO REFL baffle is gone.

The problem of IFO REFL beam clipping by the last IFO REFL baffle in HAM2 (see alog 90251, especially this picture) seems to have been caused by a huge PRM change in the PRM alignment sliders made on Monday May/11/2026 past 1700 local time (that none of us knew/remembered/understood).

Once Sheila reverted PRM back to March/2026 alignment, changing the IFO REFL beam path (but not the alignment into ISS path), IFO REFL was not clipped any more even though it looked low on the baffle (IFOREFL_baffle.mp4). LSC and ASC REFL sensors on HAM1 ISI saw the flashes right away without any adjustment of RMs, and the flash peaks were already reasonable. According to Sheila,  compaing to a time when DRMI was acquiring in November:

All of these were a good sign.

Forward-going beam into the IM4 is clipped by the baffle in front of IM4, and the IFO REFL beam is clipped by the baffle at the -Y edge of the IFI.

Unfortunately I've found that there were two other clipping points that I must have missed yesterday using IR viewer. See clipping.png, sorry for a blurry through-IR-viewer picture shot from the distance. Go back to HAM2layout_annotated2.png to figure out which baffle is what.

There's a baffle in front of IM4 between IM4 and IM3, and the forward-going beam is slightly clipped at the +X edge of that baffle.

Also the IFO REFL beam is clipped by the baffle installed at the -Y edge of the IFI. I know this is IFO REFL because the bright spot goes away when I block the beam on PRM by a sheet of aluminum. I cannot quite tell from the picture which edge of the baffle is clipping, but I think it's also +X edge.

In the past, when PRM spot position was measured with full IFO, it was like a mm off according to Sheila, so it's hard to imagine that the beam was clipping on the baffle in front of IM4.

Changing IMC alignment (trial 1, didn't fix clipping).

We decided to back off the changes we've made  for MC1, 2 and 3 since Monday and revert back to in-vac March alignment. If we have to make a huge adjustment to JM3 to follow the IMC, maybe the beam coming from JM3 is suspect (which means that the MC2 trans path is somehow suspect too).

Before I did anything, the starting point was captured in alignment_2026-05-15_16-14-21.png.

MC1/2/3 was reverted just based on slider values and not using OSEM readings as per alignment_2026-03-18.png.

Then JM3 was adjusted in PIT and YAW to give the maximum transmission measured in IM4_TRANS_NSUM. Actually I didn't move JM3 as much as I expected.

That alone couldn't recover a good 00 mode flashing so I moved MC2 and MC3 to follow the input beam.  MC2 moved back closer to the position this morning.

After that I felt as if it was somehow easier to optimize further using MC1 as well as MC3, thinking that it would be a minor adjustment but somehow ended up moving MC1 by a large amount after iterations.

My end point is captured in alignment_202605151726_sliders.png.

Without IM3 and IM2, the beam was still on IM4_TRANS as well as ISS QPD, the flashes were good, so I looked at the clipping on the baffle in front of IM4 as well as the baffle at the -Y edge of the IFI, and they were still there. IFO REFL baffle was still not clipping.

Will have to think about what these all mean.

Images attached to this report
Non-image files attached to this report
H1 PSL (INS, IOO, ISC, PSL)
keita.kawabe@LIGO.ORG - posted 17:41, Thursday 14 May 2026 - last comment - 20:58, Saturday 16 May 2026(90251)
Done with ISS array alignment, not yet ready to go laser safe due to IFO alignment mystery (Rahul, Elenna, Keita)

Good news is that we're done with the alignment of the ISS path. Pictures and details are to follow.

Then I reinstalled the last IFO REFL baffle right in front of the HAM2-HAM1 septum window. (The baffle was removed after marking the exact position using three temporary dog clamps on the ISI on day 1 because it was in the way, I was supposed to record that in alog 90158 but forgot. I'm absolutely sure that the position of the baffle was restored within 0.1mm of the original position.)

Bad news is the IFO REFL was clipped on that baffle. 00 mode flash isn't clipped that much but horizontal modes certainly are. That was not THAT surprising because the IMC alignment was/is not great (see my comment 90224). This looks to me that the uncontrolled degree of freedom of the IMC is wrong regardless of the reason why a huge alignment change had to be made to center the MC2 TRANS QPD.

Good news is the ISS path alignment is not impacted by that, at least greatly, because we made sure that the beam hit the right location of IM4 TRANS as well as ISS array QPD before we did anything in the ISS path. Note that the baffle clipping the beam is not in the ISS path.

In other words,

However, since we don't want to revisit HAM2 once we close it, I'd like to understand what's going on for the IMC/IFO alignment. 

Comments related to this report
keita.kawabe@LIGO.ORG - 20:58, Saturday 16 May 2026 (90257)

For location of things, refer to HAM2layout_annotated.png. Blue line = IMC reflection. Red line = IMC transmission. Orange line = IFO REFL rejected by the IFI. Green things are baffles (two-hole baffle and the last IFO REFL baffle are circled in green).

The alignment status at the start of Thursday morning:

The beam was very high on the two-hole baffles but was OK on the input hole of the ISS array. See alog 90237, see this picture as well as this, and this video. This just meant that we were shooting down the beam from the 1" lens toward the center of the array QPD.

Work done on Thursday:

We moved the beam down using the two pico mirrors such that ultimately the beam goes through the center of the input hole of the array and reasonably centered on QPD.

Detailed procedure was:

  • Use the first pico mirror until the flash is just seen in segment 3 and 4 of the array QPD (i.e. PIT=-1 if this were a stable DC light) and then use the second pico mirror to bring up the beam until the QPD was roughly centered. Measure the beam position on the baffle holes as well as the ISS input. Repeated until the beam comes close to 1/8" or so of the center of the input hole of the array.
  • Install the biggest array alignment aperture tool (D1300986, -03 variant with 2.4mm diameter hole) in the hole of the array. Use pico mirrors until no clipping at the alignment aperture tool is visible using IR viewer and the QPD is roughly centered at the same time.
  • Repeat with the middle sized alignment aperture (-02 variant with a 1.6mm hole). That is enough as the final adjustment before pumping down.
    • We didn't bother to use the smallest alignment aperture (-01 variant with 0.79mm hole). Refining the alignment at that level for in-air initial alignment is pointless, the beam WILL move once things are in vacuum and the IMC is properly aligned and IMs adjusted. What ultimately matters at this point is to make sure that, once that in-vac adjustment for IMC/IFO is done, the beam could be found on the QPD. From there on we need to fine-tune to find a good ISS array alignment and minimize the jitter coupling.
Status after Thursday's work:
right_baffle_hole_spot.png (seen from +Y), 2nd_pico_spot.png (from -Y), 1inch_lens_spot.png (from -Y) and 2inch_lens_spot.png (from -Y) show the beam spot on various positions in the order of the distance from the array in the ascending order. You can see that the height on the right baffle hole as well as the second pico mirror are pretty good. Pictures of the lenses have significant parralax because of the distance between the card and the lenses and because of the camera height, but the beam doesn't seem to be centered on the lenses. I don't see that as a problem, it's fine as far as the beam is far from clipping. 

We have found no unexpected behavior here, I was surprised that the process was easy and things made sense given the difficulty people had in the past to improve alignment of the array in vacuum with the old unit. That's probably because the beam was already clipping back then.

The only thing was that the YAW actuator of the second pico mirror didn't have much range to start with even before we moved anything. At some point it didn't hit its end of the range but was close (2nd_pico_position_before.jpg). Since we need a healthy headroom for adjustment both ways, I relieved the pico by mechanically rotating the pico mirror assy (2nd_pico_position_after.jpg).

IFO REFL beam was clipping on the baffle:

See IFO_REFL_baffle.jpg
Images attached to this comment
H1 IOO (INS, IOO, ISC)
keita.kawabe@LIGO.ORG - posted 23:19, Wednesday 13 May 2026 - last comment - 11:50, Thursday 14 May 2026(90237)
Swapped the ISS array. Alignment into the new unit started. (Rahul, Elenna, Keita)

Following yesterday's alog 90219:

At this point I and Rahul checked the beam positions in HAM2. Some things to note:

We proceeded to swap the ISS array unit.

At this point we saw flashes on QPDs as well as array PDs right away. INNER as well as OUTER SUM flashes were both about 0.06 (in the old unit it was 0.03 for OUTER but INNER was much smaller).

We started trying to center the QPD using the first pico mirror. Since pico driver is temporary unavailable (IOT2L is moved away) Rahul turned the pico manually while Elena looked at the laptop screen to monitor flashes in the individual segments. We managed an OK job (arrayqpd_centered.jpg) and checked the beam spots again.

The baffle height might not be the same as the lens height and/or the ISS array input hole height, but otherwise it seems that we're shooting down the beam from the 1" lens to the ISS array. We'll check if the lens, baffle and the array are all at the same height or not, and decide how to proceed.

Images attached to this report
Non-image files attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 23:40, Wednesday 13 May 2026 (90239)

1st: Rahul is disconnecting the QPD cable.

2nd, 3rd (photo by Betsy): Rahul in chamber (me outside).

4th: Old unit was extracted. This is S1202971.

5th: New unit (S1202965) to the left, old one to the right.

6th: Rahul after successfully connecting up the new unit in chamber.

7th (photo by Betsy): Elenna (front) is checking the QPD centering, Rahul (a shadow in the back in this photo) is manually moving the pico mirror from -Y door, and I'm somewhere inbetween just observing the two doing a good job.

Images attached to this comment
corey.gray@LIGO.ORG - 08:45, Thursday 14 May 2026 (90243)EPO

epo tagging for photos!

rahul.kumar@LIGO.ORG - 09:39, Thursday 14 May 2026 (90244)

Attaching two pictures in reference to Keita's comment above - "The beam was very high on the left hole of the two-hole baffle (Rahul has a good pic), high on the right hole (right_hole_after_new_array_QPD_centered.mp4)"

Images attached to this comment
keita.kawabe@LIGO.ORG - 11:50, Thursday 14 May 2026 (90248)

We concluded that the height of the baffle and the array unit are both correct, the beam is really too high on the 1" lens and we're shooting down from there to the QPD. (This should have been the case for a long time with the old unit. Right after the new unit was installed the beam was on QPD and the beam stayed on the QPD, the diameter of the QPD is 3mm, i.e. we haven't made any huge change on the height of the beam at the left baffle hole.)

  • Rahul found in solidworks that the design beam height for LHO is 6.132"=155.75mm.
  • Looking at the pictures we took in the chamber, the center height of the two-hole baffle is about 156mm so that's fine.
  • The height of the spacer we have, which is supposed to be D1101074 specifically made for LHO,  has 4.94"~125.5mm nominal height and our measurement shows somewhat larger than 125.5mm, excellent agreement. We didn't measure the thickness of the thin part of the array base plate (https://dcc.ligo.org/LIGO-D1300323, detailed dimensions are only available in solidworks) nor the distance from the bottom to the beam center of the elevator plate D1400140 (again only available in solidoworks) but Rahul's number makes sense, the height of the actual array unit seems to be according to the design.

With this information, what we'll do next is to gradually bring down the height of the beam on the left baffle hole using the first pico mirror, and use the second pico mirror to bring the beam back on the QPD, until the beam line into the array becomes level-ish with the ISI surface. It doesn't have to be perfect but we don't want to be this much tilted.

Images attached to this comment
H1 IOO (INS, IOO, ISC)
keita.kawabe@LIGO.ORG - posted 10:07, Wednesday 13 May 2026 - last comment - 13:46, Wednesday 13 May 2026(90226)
ISS work restarts

Restored the alignment sliders for IM2 and IM3 back to Monday values ([IM2P, Y] =[765, -187.7], [IM3P, Y]=[-560.7, 320]).

Measured the flashes. Chose the flash that gave the MC2 trans sum maximum power, which in general agreed with IM4 trans sum max but didn't with ISS QPD nor array PD inner sum nor outer sum. 

Anyway, 

PIT and YAW numbers were after normalization divided by (seg1+2+3+4), not by SUM, so there's a small difference but that doesn't matter at this point.

IM4 TRANS and ISS QPD PIT and YAW are broadly in agreement with Jenne's alog 90206 i.e.

I haven't compared the ISS Outer SUM with March 2026 when IMC was locked with 2W. Somebody check please. We'll go into chamber and start checking the beam path.

Comments related to this report
elenna.capote@LIGO.ORG - 13:46, Wednesday 13 May 2026 (90232)

On March 11 when we locked the IMC at 2 W, the outersum was 0.062. Today, I measured the outersum flashes (relative to the dark noise) to be 0.031, with 0.18 W input. This means our alignment into the ISS has improved relative to March.

H1 IOO (INS, IOO, ISC)
keita.kawabe@LIGO.ORG - posted 18:24, Monday 11 May 2026 - last comment - 09:19, Tuesday 12 May 2026(90203)
Restoration of IMC alignment continues (Elenna, Sheila, Jenne, Keita)

I went to HAM3 to see that the MC2 beam position wasn't crazy. See the first photo, the beam is to the left (+Y direction) relative to the baffle on the HR side but the baffle itself is offset in -Y direction relative to the cage.  Green lines are extension of the EQ stop screws to guide your eyes.

I also opened the ISCT1 and moved the mirror in front of the REFL BBPD out of the way and directed the beam to IFO REFL camera (because I couldn't see the beam at all without moting the mirror).

While manually aligning the IMC, we found that somehow things are in such a bad state that the MC2 TRANS SUM decreases when IM4 TRANS SUM increases, and vice versa. Improving the IMC alignment using IM4 TRANS as well as IFO REFL camera made the flashes stronger to the point that we can see 00 mode once in a while. I was also able to see the beam in the ISS path. But MC2 TRANS was nowhere near centered. Attempts to resolve this by incremental changes failed.

We wondered if something behind MC2 was bumped and changed the alignment into MC2 trans. I looked at the path and didn't see anything obvious. The beam transmitted through MC2 was visible using a card and a viewer, it was not clipped by the baffle behind MC2 nor the BS for the beam dump. I could not see the transmission of the BS, though, it was too weak, so I cannot confirm if the steering mirror in front of the QPD was bumped or not.

Elenna started making big changes for JM3 in PIT (to make big YAW changes in the beam injected into IMC, remember that YAW and PIT are flipped between JAC and IMC, IMC WFS takes care of this but that won't help when you're manually aligning JM3) and moving MC2 and MC1 so that the IMC follows the input beam. Repeating this in YAW anShe successfully centered the beam on MC2 trans. 

At this point I looked at the MC2 beam position again, see the second picture. Apparently the beam moved in YAW by a few mm to the right (i.e. -Y direction).

Elenna will post which optic was moved by how much in which direction.

Jenne is now trying to put IM4_TRANS and ISS QPD beam position back where they used to be using IM2 and 3.

Images attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 18:14, Monday 11 May 2026 (90204)

We found that people opening BSC door cover(?) somehow disturbs IMC whether or not HAM3 and HAM2 door covers are on. The IMC fringe becomes super fast and it almost becomes impossible to align anything. Purge air seems to go to strange places to do strange things.

OTOH, when people are out of BSC, we had to put 0.2Hz 150cts excitation to MC2 M1 drive align L2L so the IMC goes across the entire FSR.

elenna.capote@LIGO.ORG - 18:29, Monday 11 May 2026 (90205)

At first, I only moved some combination of MC1, 2 and 3 because we believed that the pointing into the IMC was fine. However, as Keita summarizes above, this was a futile process and veru confusing because it sometimes seemed as if the camera, MC2 trans QPD and IM4 trans QPD all gave differing directions.

However, although Keita said that the beam hit MC2 in a good place, he did clarify this was within mm, so this gave us room to move around JM3 by many microradians. Then, we had this whole realization that JM3 pitch and yaw are flipped relative to IMC pitch and yaw, so some of our other confusion about what we were walking (and why it wasn't really working) started to make sense.

In the end, this is the process that worked: move JM3 a large amount, follow up with MC2 move and some MC1 move in opposite dof (so JM3 pitch goes with MC2/1 yaw). At first, I relied only on IM4 trans, but then the flashes on MC2 trans started to improve, so this became a much more useful signal to follow.

Below, I compare the OSEM readbacks of each suspension from before we started moving to now at the end of the day:

JM3 pitch (IMC yaw): -177 urad

JM3 yaw (IMC pitch): -93 urad

MC1 pitch: -186 urad

MC1 yaw: +83 urad

MC2 pitch: +58 urad

MC2 yaw: -62 urad

MC3 pitch: + 12 urad

MC3 yaw: +21 urad

 

We should probably put some note next to the JM3 sliders that the pit/yaw dofs are flipped compared to IMC pit/yaw, or I predict that we will recommit this mistake many times over!

 

Attached is a screenshot of the IMC aligned in air with associated signals (and dog)

Images attached to this comment
jenne.driggers@LIGO.ORG - 18:39, Monday 11 May 2026 (90206)

Once Elenna had the IMC nicely aligned, we moved on to setting the pointing of the beam headed to the IFO.  We need this to be roughly correct, so that we can use it to align the ISS array.

Back in March when the IMC was locked, Elenna found the locations of the beam on IM4 Trans and ISS QPD:

  • IM4 Trans Pit (March 2026): 0.22
  • IM4 Trans Yaw (March 2026): -0.06
  • ISS QPD Pit (March 2026): -0.92
  • ISS QPD Yaw (March 2026): 0.94

We then worked to move IM2 to get to the right spot on IM4 trans, and then IM3 to get to the spot on the ISS QPD.  The tricky thing is that, since we can't lock the IMC (IOT2 is away from the chamber, so no IMC REFL PD, so no IMC locking), we're just looking at flashes.  So, the spot on the QPDs has to be calculated by looking at peak heights when we get a flash, and doing the matrix math to go from segments to pit and yaw.

.....After 23 different iterations of setting IM2 and IM3 based on an educated guess of where they should go, calculating the QPD spots, finding that we weren't quite right, and then tweaking again, we're leaving the IMs such that we're back to the March location on IM4 trans, but we're less on the edge for the ISS QPD.  Current spots (calculated from the peaks of IMC flashes):

  • IM4 Trans Pit (May 2026): 0.2
  • IM4 Trans Yaw (May 2026): 0.05
  • ISS QPD Pit (May 2026): -0.53
  • ISS QPD Yaw (May 2026): 0.85

This helps assure us that we've got a pretty reasonable beam headed toward the ISS array, and that even if we didn't get the IMC alignment quite right earlier, we should be in a pretty reasonable place and we can use this beam to replace the ISS array.

One final thing we could do as a last check is to calculate the spots on POP A and POP B QPDs (or, at least the one that is used for initial alignment and acquisition), and make sure that we can move IM4 to get to that spot.  That would mean that IM4 trans QPD and POP QPDs are both correct, which sets the pointing of the beam into the PRM and into the IFO, so if that line is correct in air and we use it to align the ISS array, then we will certainly be in a good place when we pump down.  Again, this would just be a check that the IM1+IM2+IM3 position that we've got right now to give us good pointing to the ISS array is compatible with some IM4 pointing to the POP QPD.  The individual segments aren't _DQed, so we'll have to check this tomorrow when the light pipe is open again.

Keita closed the light pipe for the night.

keita.kawabe@LIGO.ORG - 09:19, Tuesday 12 May 2026 (90210)

During the work noted above, I disabled IMC-IM4_TRANS whitening OFF (only one stage was on) because the fringe velocity was big-ish and made flash peaks of some quadrants distorted, which means either the whitening/dewhitening mismatch was a problem (likely) or the ADC was railing (unlikely).

Also, I held the output of H1:IMC-IM4_TRANS_SUM (to avoid dividing P and Y by a tiny number, but of course it was useless). NSUM wasn't changed.

Whitening is still OFF but I turned off the holding of H1:IMC-IM4_TRANS_SUM this morning.

I'll turn one stage of IM4_TRANS whitening back ON after we're done with ISS.

H1 ISC (INS)
keita.kawabe@LIGO.ORG - posted 18:16, Friday 08 May 2026 (90191)
Restoring IMC alignment (Jennie, Rahul, Jenne, Keita)

PSL power into JAC 200mW. Jennie was able to lock JAC without much problem.

Jenne put MC2 back to march 2026 (in-lock) alignment in PIT and YAW using osem (not the slider) taking into account ISI (HAM3) Rz. 

To see the fringes, we injected 600 counts 0.2Hz into H1:SUS-MC2_M1_DRIVEALIGN_L2L_EXC. IMC flashed right away but the transmisison fringe looked like a weak horizontal line. Moving MC2 alone did not make the fringe converge.

Jenne moved MC3 and MC2 (and MC3). Improved some but not drastic. Tried JM3, again improved, but not drastic. Jenne was able to see the MC2 TRANS SUM but it was awkward and slow. At this point, at least the beam was not a straight horizontal line any more, we saw HOMs both in PIT and YAW, sometimes even 10 and 01 and what might have been a dim 00 spot. According to Jenne, the maximum MC2_TRANS number observed (about 3 after subtracting DC offset with 200mW input) is about 10% of what we expect with a good alignment (300 counts with nominal 2W).

We need a better alignment to be able to see the beam in the ISS path, though, I couldn't see anything.

I wanted to see the PRM reflection on the ISCT1 REFL camera as it will make the alignment easier (because we can see the IMC transmission beam shape).

Inside ISCT1, the beam was making it to the BS for the 1F diode but was hitting the mirror holder of the mirror for the BBPD. I touched up the common steering mirror for 1F and BB (just downstream of the shutter) so the beam goes to the direction of BBPD (and of course 1F PD) but could not see the transmission of the mirror for the BBPD using a card and a viewer, probably because the power was too small. (We're injecting 200mW, MC2 transmission is a small fraction of that as of now, and the REFL path is supposed to handle 60W.) No beam was seen on the camera either.

On Monday we might temporarilly move the BS for the BBPD out of the way so we can see the beam on the camera.

H1 ISC (INS, ISC, SYS)
keita.kawabe@LIGO.ORG - posted 15:50, Tuesday 28 April 2026 - last comment - 15:50, Tuesday 28 April 2026(90039)
OMC QPD sense pin problem: Solved

Summary:

The problem of "Sense" pin of OMCA QPD1 short-circuited to the BHDS structure (alog 90029 from yesterday) was tracked down to the free "sense" wire inside the QPD enclosure touching the aluminum part inside the enclosure. We solved the problem by trimming the wire short.

Merely opening the QPD enclosure broke the short circuit temporarily:

We lifted the OMCA QPD1 from the BHDS while QPD2 is still attached to the BHDS and confirmed that the sense pin for the QPD1 is conductive to the QPD1 enclosure but not to the BHDS. As soon as we opened the back of the QPD1 enclosure, the short-circuit to the enclosure was broken. 

It seemed that the free part of the sense wire was a bit too long and bowed in the enclosure, allowing the tip of that wire to touch the inside wall of the enclosure itself (see Elenna's first image in her comments).

Cutting the sense wire short broke the short circuit permanently:

I cut the wire short such that it cannot touch the enclosure (Elenna's second picture), reassembled the enclosure and confirmed that there's no short circuit between the sense pin and anything else. 

Repeating the tests:

We put the QPD1 back on the BHDS and connected the cable to the transimpedance amplifier. On the oscilloscope, it was immediately apparent that the terrible 60Hz noise (which was 6.5V p-p) was gone (Elenna's 3rd picture).

We repeated the flashlight test, all segments responded with O(1)mV negative voltage (i.e. positive output minus negative output from the TIA amplifier was negative few mV maximum) while the dark offset was O(0.1mV).

We also measured the dark noise. It seems that all measurements for both QPD1 and QPD2 were limited by the noise of the TIA. Low frequency noise especially 60Hz and its harmonics varied from channel to channel, but in all cases it seemed that there's very little difference between the noise measured with QPD connected VS the noise without QPD. As such, I'll just show here a few examples. First attachment is the QPD1 segment 1 noise with the QPD attached, the second is the same thing but without QPD connected to the front panel of the TIA. They look identical. The third one is the QPD1 segment 4 (with QPD attached, not much different without QPD). The fourth one is the QPD2 segment 3 (with QPD attached, not much different without QPD).

There's no reason to suspect that QPD1 for OMCA is broken (nor QPD2).

Images attached to this report
Comments related to this report
elenna.capote@LIGO.ORG - 15:27, Tuesday 28 April 2026 (90040)

Here are photos of the QPD housing with the back removed. You can see a long unsoldered wire that we identified as the "sense" wire with conducitivity tests. This is pointed out with the pink arrow. You can also see an extra mystery wire pointed out by the blue arrow. We don't know what that wire is attached to. The wire pointed by the blue arrow is actually the shielding wire which is connected to pin 1.

The after photo shows the sense wire after Keita clipped it short, pointed out with a pink arrow.

I have also included a photo of the oscilloscope image of segment 1 of both OMCA QPDs.

Images attached to this comment
H1 ISC (CDS, INS, ISC, SYS)
keita.kawabe@LIGO.ORG - posted 23:16, Monday 27 April 2026 - last comment - 23:46, Monday 27 April 2026(90026)
OMCA-QPD1 sense pin is shorted to the suspension platform, causing massive 60Hz problem (Elenna, Keita)

Problem

We started checking the health of QPDs and were puzzled that all four quadrants of the OMCA QPDA are much, much noisier than OMCA QPDB.

Note, there's a naming inconsistency about the QPD numbering between D2200276 wiring diagram and D0981811 (see "cartoon version"). 

D0981811 OMCA QPD-1 OMCA QPD-2 OMCB QPD-1 OMCB QPD-2
D2200276 QPD-2 QPD-1 QPD-8 QPD-7

Cause of the problem

Anyway, the problem was tracked down to short-circuit of common mode noise sensing line for OMCA-QPD1 (pin 11 of DB25 inside the vacuum, pin 3 outside of the vacuum, see attached) to the metal part of the suspension structure (i.e. ISI surface and the chamber) which in turn is grounded to the lab ground.

OMCA QPD-2 as well as both of the QPDs for OMCB are fine.

All QPD segments (incl. OMCA QPD1) responded to the flashlight.

Dark noise test: OMCB QPDs looks OK, not sure about OMCA QPDs

We connected a dual-QPD trans impedance chassis (S1102832, which is the original version of D1002481) to the OMCB QPDs like this:

QPDs-DB25 assy - in-vac cable (DB25F-DB25F)  - feedthrough simulator - DB25F-to-DB25M-cable - S1102832 front panel.

We looked at the output of the TIA with SR785 when there's only ambient light on QPDs (not much), segment by segment. No segment was extra noisy or anything.

OMCA QPDs are a different story because of the 60Hz problem. 

We'll see if the problem could be solved by somehow reassembling the QPD or cutting the noise line. 

Images attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 23:46, Monday 27 April 2026 (90029)

1st attachment shows the connection from the QPD to TIA. ("S1P" "S2N" etc. mean segment 1 positive pin, segment 2 negative pin etc.) Before the in-vac cable was actually connected to the feedthrough simulator, we confirmed that the positive bias (3V) came to pin 23 and pin 20 of the feedthrough simulator on the in-vac side as per the connection diagram D2200276.

2nd attachment shows how the output of the TIA (all differential) was connected to SR785 or oscilloscope, using QPD1 seg1 as an example.

3rd attachment shows that CH1 (yellow), which is the segment 1 positive pin of the QPD1 for OMCA, was terrible while the segment 1 positive of QPD2 for OMCA (blue) was not. Though there's no picture, the terrible 60Hz noise appeared in the negative pin with the opposite sign (for QPD1) so it's not cancelled.

For OMCB QPDs, DC offset of all segments were smaller than 1mV when there was no light (used a fluke DVM to measure across positive and negative pins). For OMCA QPD2 that was also the case.

OMCB_QPD[12]_SEG[1234].jpg are the noise measurements for OMCB QPDs using SR785. The TIA output (which receives 0.4:40 whitening in the chassis) just shows the TIA noise from 200Hz and higher for the entire frequency range without any light on QPDs, which looks fine to me. There's no reason to suspect that one or more of these segments/QPDs are broken.

The last attachment (QPD_removed.jpg) shows a measurement of OMCB_QPD2_SEG4 after disconnecting the QPD from the front panel, showing the TIA noise floor. SR785 noise floor is lower than this.

Images attached to this comment
H1 INS
disha.kapasi@LIGO.ORG - posted 14:58, Thursday 16 April 2026 (89921)
Calculating SR3 hot radius of curvature

[D. Kapasi, S. Dwyer]

We can calculate the SR3 hot radius of curvature (sr3_roc_hot) from the HWS measurements [1] and readback heater power for SR3 [2].

In our case - 
sr3_roc_cold = 36.013; % radius of curvature in m [3].
Therefore, 2*(1.0735e-05) = 2/36.013 - 2/sr3_roc_hot -> sr3_roc_hot = 36.027 m.

Sources
[1] alog 88413 - this give HWS values in µD/W.
[2] alog 88155 - gives the reported readback power and requested power for SR3 heaters.
[3] git issue #33.

Displaying reports 1-20 of 536.Go to page 1 2 3 4 5 6 7 8 9 10 End