Mitch, Jim
We got a window this afternoon to try installing L4Cs in HAM2. We just did the horizontal L4Cs and cables, because those were the most difficult, but least in the way parts. The H3 L4C in particular was very difficult, I had to go in and work under the SPI ISIJ telescope, laying on my stomach in the beam tube, while trying not to kick the modecleaner baffle out of place. Also, the gap between bottom edge of St1 and the bottom of the nozzle to the modecleaner tube is just slightly narrower than my elbow, so I could fit my arm in there, but was never sure it would come back out easily. Anyway, the hard part is done, we will finish the verticals next week sometime. I also need to get back with Fil about running the in air cables to the feed thrus. We should have the in rack electronics next week some time as well, so I will try to get the adc wiring in the model set up before interface chassis arrives.
For ADC assignment, see the green boxes on the redline posted to D1101576:
REDLINE_HAM23_Wiring_SPI_CRS_L4C_AA_ASSIGNMENT (P3)
If the Duotone channel is set on ADC0 CH31 as shown in this wiring diagram, we will have to skip the last db9 of the left AA shown on the picture above (or loose the Pod Pressure signal).
In summary, here is the proposal:
ADC0 CH24-25: L4C H1,V1 Signals
ADC0 CH26-27: L4C H1,V1 Diff Pressure/Pressure
ADC1 CH24-25 L4C H2,V2 Signals
ADC1 CH26-27: L4C H2,V2 Diff Pressure/Pressure
ADC1 CH28-29: L4C H3,V3 Signals
ADC1 CH30-31: L4C H3,V3 Diff Pressure/Pressure
On May 19th, 2026, we took our first set of transfer functions for the BBSS after swapping in the glass optic. They all came out looking good, albiet very noisy because the suspension wasn't covered.
Comparing them to the last measurement we did in the staging building, the peaks still all match up well. There is just a consistance difference in magnitude, but that is probably just due to the difference in electronics between the QUAD stand in the staging building and the BS electronics in the LVEA.
Data
/ligo/svncommon/SusSVN/sus/trunk/BBSS/H1/BS/SAGM1/Data/2026-05-19_2000_tfs/2026-05-19_2000_H1SUSBS_M1_WhiteNoise_{L,T,V,R,P,Y}_0p02to50Hz.xml
r13018
Results
/ligo/svncommon/SusSVN/sus/trunk/BBSS/H1/BS/SAGM1/Results/2026-05-19_2000_tfs/2026-05-19_2000_H1SUSBS_M1_ALL_TFs.pdf
r13018
/ligo/svncommon/SusSVN/sus/trunk/BBSS/Common/Results/allbbss_May2026_BBSS_teststand_vs_staging/allbbsss_May2026_BBSS_teststand_vs_staging_ALL_TFs.pdf
/ligo/svncommon/SusSVN/sus/trunk/BBSS/Common/Results/allbbss_May2026_BBSS_teststand_vs_staging/allbbsss_May2026_BBSS_teststand_vs_staging_ALL_ZOOMED_TFs.pdf
r13017
These measurements were taken with BOSEMs. The extra factor of ~4 that these measurements are lower by as compared to the older staging building trace is due to electronics. The BSFM was moved from 18- to 28-bit DACs back in January, so I compensated for this change in the COILOUTF filter bank by adding a filter module with a gain of 1024. However, the BBSS measurements made in the staging building were using a 16-bit DAC, so when we moved the BBSS onto the BSFM system, there was a factor of four of drive missing from excitations, hence these measurements looking lower as compared to the measurements in the staging building. That was remedied after this.
Comparison overnight spectra of the BBSS's M1 LF/RT and M2 UL/UR osems before vs after the installation of the BRDs is showing that the BRDs are correctly damping the Bounce and Roll modes and so don't need to be adjusted.
Bounce and Roll frequencies (measured before installing BRDs) were at 19.80 Hz for Bounce and 32.09 Hz for Roll. Final measurements will be taken in chamber.
No BRDs
- Brighter colors
- Overnight measurement taken over >14 hours
- Starting time: 2026-05-20 00:08:45 UTC
With BRDs
- Darker colors
- Overnight measurement taken over >14 hours
- Starting time: 2026-05-21 00:16:54 UTC
The data file I used for this can be found in /ligo/svncommon/SusSVN/sus/trunk/BBSS/H1/BS/Common/Data/2026-05-21_1900_H1SUSBS_M1M2_BounceRoll_NoBRDs_vs_BRDs.xml as r13015.
J. Kissel
(Belated aLOG)
Here's the continued summary log of what was done on the SPI pathfinder, up to Wednesday Afternoon 2026-05-20.
- Unshuttered laser for the morning (still on overnight, so well past its thermal transients), with o-scope still reading out the MEAS IFO with 400 [usec/DIV] and found the efficiency low.
- Looked around for a bit, still get prepped for the day, and I turn around that MEAS IFO efficiency has recovered. Very weird. Set the scope to measure the MEAS A and B efficiency and input power monitors on 40 [sec/DIV] to gather a long, 400 [sec] = 6.6 [min] trend while I worked on aligning REF IFO. Found the this true
. [FUTURE JEFF] Note, this was true *before* I had issues with OL_QPD_B alignment and swapped out the dumps for big dumps (see below), making the "is the beam clipping?" potential for it being the issue questionable.
- On to continued migration of components, now the MEAS path into the REF IFO.
. Locked down set screws for R_B1 and R_B2 (R_F1 and R_M1 already locked). Since both REF paths are are aligned into the REF and MEAS IFOs, we want to fix it as the LO / reference for the IFOs.
. Dumped REF beam path into REF IFO.
. Installed and aligned M_B2 using holes 90 and 91. (Again: "aligned" or "confirmed alignment" means confirming alignment thru irises with IR camera, as well as maximizing power through irises with power meter.)
. Installed IFO_PWRIN_MEAS PD and dump D_IFO_PWRIN_MEAS.
. Confirmed function of PD.
. Confirmed alignment of beam onto IFO_PWRIN_MEAS PD.
. While checking functions of PDs, went over to OL_QPD_B (never checked this prior to aligning MEAS IFO on 2026-05-19), and found its reflection missing the D2400368-v1 assembled as designed. This is assuming that because I already had ~72% efficiency on the MEAS IFO, that I didn't want to move any mirrors/beam splitters. [FUTURE JEFF] THIS IS AN ERROR IN MY ALIGNMENT PROCEDURE (On 2026-05-19 I should have used M_B1/M_M1 to align to OL_QPD_B, THEN set the alignment of OL_QPD_B to hit the dump D_OL_QPD_B dump location as designed).
:: Increased beam dump "catcher" plate of the v-dump size to 1.16" x 1.16" plate, in first attempt to catch the beam
:: THEN physically rotated the QPD housing in YAW, centered the QPD signals on the incoming beam, but that yawed the reflected beam even further away (in -Z) from the designed D_OL_QPDB location. [FUTURE JEFF] Further indicating the issue was with the incoming beam, not the QPD.
:: So, I increased the dump "catcher" and "receiver" plate to 1.58" x 1.58" plates.
:: This made getting the beams around this big plates really challenging, but I was able to get something that worked, with the ~5 [mm] diameter beam spot on the card not clipping (acknowledging that I don't know the real beam diameter other than "it should be 2 [mm] all over the transceiver").
. Moved on, and migrated M_M3 over confirming alignment with holes 93 and 96.
. With MEAS beam now into R_B3, confirmed alignment with irises with holes 100 and 97.
. Unblocked REF path into REF IFO and began to search for heterodyne beat note. Having much tougher time than with MEAS IFO.
. Remembered Bram trick of temporarily removing IFO_REF_A to project both REF and MEAS beam further off the board to confirm far-field alignment. Was indeed clean misalignment of beams in far field.
. Adjusting only MEAS path by walking M_B2 (for near field adjustments) and M_M3 (for far field adjustments), was able to find the beat note on IFO_REF_B.
. Re-installed IFO_REF_A PD, and maximized beatnote as best I could, but only got 35%.
Max = 3.00 [V]
Min = 1.30 [V]
Amp = 1.70 [V]
Mean = CH1 2.15 [V], CH2 2.22 [V]
Efficiency = Amp / (2*mean)
CH1 1.70/(2*2.15)= 0.395 % yuck!
CH2 1.70/(2*2.22)= 0.383 % yuck!
. But this is just a "reading off the scope" efficiency, wanted to make sure this wasn't dramatically influenced by dark offsets, so spend some time gathering PD DARK offsets. All SPD dark offsets are in the 15 [mV] level FAR below the now-excellent signal voltage levels.
. Also noticed, with both IFOs functional and up on the o-scope, with it triggered on the REF IFO,
:: Phase drift of MEAS IFO w.r.t. REF IFO.
:: Sensitivity of the IFOs to flicking of either MEAS or REF fiber.
- Resolving to take this offline to talk to the SPI crew about it, I re-dressed up all cabling.
. Found picomotor cable was mounted in the Cable Table bracket upside down, making the map of which quadrupus leg goes to which pico-actuated mirror challenging, so I fixed that.
. Hooked them up as designed (mirror names == D2400107; pico cable == D2400342; pico driver board D1100326):
:: M_M1 > J2 > Pins 12,13,24,25 > furthest right when looking at the open D25 connector as the boat floats (with all pins to the left) > Pico Driver page 5, D25-J2 CH5
:: M_B4 > J3 > Pins 10,11,22,23 > 2nd right > Pico Driver page 5, D25-J2 CH6
:: M_M2 > J4 > Pins 8,9,20,21 > 2nd left > Pico Driver page 5, D25-J2 CH7
:: Spare > J5 > Pins 6,7,18,19 > furthest left (where all the missing pins are > Pico Driver page 5, D25-J2 CH8
. Confirmed all cables went "up first," with a soft-bend to breadboard level, and completely clear of all beams.
. Confirmed IFO_MEAS_A cable is neatly threaded through the middle of the periscope mirrors, but doesn't interfere with the mechanical motion of the periscope
. Confirmed all cables were clear of -X perimeter so as to not interfere with installation shelf cylinders D2500142
. Confirmed all cables were clear of the utility holes consumed by SLIC shroud D2400106
. Confirmed all cables won't interfere with installation handles
. Confirmed all cables won't interfere with attaching / reattaching optical fibers.
But at least, the victory from today is : The D2400107-v4 board is completely migrated over to the D2400107-v5
At the end of the day the board was completely migrated, but I now had a list of issues to now tackle ([FUTURE JEFF] prioritized by importance):
(1) Low efficiency of REF IFO.
(2) Beam dump for QPDB. Is this good enough? How can I test quantitatively? Could move rotate the housing back, but -- won't the position of this reflected beam change once we get the real return MEAS beam, and we want "if centered on the QPD, then IFO will heterodyne" as an alignment reference?
(3) Breathing of heterodyne efficiency on MEAS IFO (only MEAS IFO, REF IFO is rock-soiid).
(4) P-pol transmission dependent on physical position of optical fiber
(5) Reflection of PWRIN_REF. Should I crack the enclosure to try to fix it?
(6) Phase drift of MEAS IFO w.r.t. REF IFO.
(7) Sensitivity of the IFOs to flicking of either MEAS or REF fiber.
[FUTURE JEFF] After discussing with the team (in order of how to address the issues):
(4) Fiber polarization state output dependent on fiber position. Check the tiny set screws on the fiber collimator again, make sure they're secure, but not too secure.
(2) QPDB reflection dumping. I didn't follow procedure here, and that has caused a ripple effect. Fixing M_M1 alignment into QPD B is the way to go. That should solve the QPD B reflected beam issue, and thus any potential for clipping, and might clean up (3), BUT, before you do that,
(1) Low REF IFO efficiency might be an issue with the alignment again. 35% is unacceptable, we need both IFOs above 75% at least. Maybe you need to revisit the whole MEAS path alignment, confirming spot position on PWNIN_MEAS, since that confirms M_F1 alignment. If it's off, realign the whole MEAS path and that might clear up the issues with the REF IFO and QPDB. If the PWRIN_MEAS alignment is good, then triple check that you've not put in any optics backwards.
(5) PWRIN_REF PD reflection dumping. This can be a last issue fixed, but everyone votes to go into the PD and fix it albeit using the utmost of caution to protect the PD.
(6) Phase drift between MEAS and REF IFOs -- not a big deal. Likely air-currents. Try waiving your hand over the IFO and seeing it you get a wiggle to confirm.
(7) IFO sensitivity to fiber flicking -- this is why we have two IFOs and subtract the signal, to remove exactly this kind of fiber "acoustic noise" coupling. Nothing to solve here.
Pictures of the QPD Dumps - Pic #1 QPD alignment signals BEFORE yawing the enclosure, confirming just yaw is the issue. - Pic #2 QPD alignment signals AFTER yawing the enclosure. - Pic #3 1.16x1.16" "catcher" Beam dumper, prior to moving QPDB enclosure in yaw, looking at IFO_MEAS_B - Pic #4 Top down view of D_OL_QPDB prior to moving QPDB enclosure in yaw. - Pic #5 Views of 1.58" x 1.58" after installation. - Pic #6 Beam position on "catcher" dump plate. - Pic #7 View of tight clearance of beam into IFO_MEAS_B. DON'T DO THIS, JEFF.
Pics of Picomotor Quadrapus D25 Orientation Flip: This is of the Quadrapus D2500342, S2500513. - Pic #1 As I found the DB25 end in the Cable Table Bracket, having not been touched since Jim/Bram originally cabled it up on 2026-03-19. - Pic #2 After flipping the DB25 end in the CTB. - Pic #3 Same as Pic # but labeled.
Pics of MEAS IFO efficiency drift / changes over time Here's some photos showing the "drift" in efficiency I'm talking about. The first three photos: IFO BeatNote (400e-6 [sec/DIV]), InputPower, and NPRO Power. The second three photos show the same thing 15 minutes later, with no change to the system but the efficiency is restored to the ~72%: IFO BeatNote (400e-6 [sec/DIV]), InputPower, and NPRO Power The last three photos show the time-zoomed out 400 [sec] trends (40 [sec/DIV]) of the MEAS IFO efficiency as I was aligning the REF IFO, one at 10:56a and one at 11:19a PDT.
[Shoshana, Ryan S] Yesterday we began building the second set of CRSs sent over from LLO (mostly just putting in heli-coils). I (Shohana) will probably continue working on them today For some of the parts sent over from LLO (where they had already gone through clean and bake) we found some black residue in some of the aluminum foil wrappings and on the parts (specifically the cross beams [D2300102] and the solid supports [D2300144]) some of which would come off when wiped, but some of the residue would not. Pictures below
[Shoshana] Continued LLO CRS build One of the CRS Legs [D2300089 SN016] has a threaded hole on the side where the threads do not go deep enough for a helicoil to be fully inserted, and ends the helicoil up sticking out by ~1/8 inch, meaning half of one of the CRSs cannot be fully built right now unless the hole is tapped deeper a shorter helicoil is used. There were no other issues and 1.5 of the extra CRS supports are built The clean and bake team at Livingston says the residue is just aluminum oxide and not an issue
Which threaded hole is it ?
If the hole depth is correct, but we're just missing the threads on the bottom part of the hole we can tap it with a clean tool.
Alternatively we can also order a 1D helicoil.
The trends for the Kobelco air compressor oil temperatures can be viewed at 1day and 7day
They are also linked to the ndscope trends page
TITLE: 05/22 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
SEI_ENV state: MAINTENANCE
Wind: 7mph Gusts, 4mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.14 μm/s
QUICK SUMMARY:
Sounds like there is some work on gate valve 7 happening today. Gate valve 8 will also be shut which will be loud.
More BBSS work is very likely.
Purge Air is back on.
Jonathan, Dave:
The DAQ was restarted for three changes:
Add the new HEPI Pump Controller corner station channels and retire the old (ben box) channels.
Add the Kobelco compressor oil temperature channels
Expand EPICS LOAD MON to include the container IOC's service-host cluster machines (service-host[0,1,2])
This was an extended DAQ restart so we could backfill some of the new hpipumpctrl channels with the raw minute data from the old channels.
23 channels were effectively renamed, so the rawmin files with the old names were copied to the new names so the trend writer "continued where it left off" with these channels.
The DAQ restart sequence was:
Stop TW0, run the copy script
Stop TW1, run the copy script
Restart the 1-leg, immediately restart the EDC
Restart the 0-leg
The copy script which maps oldname to newname is:
cp 52/H1:HPI-PUMP_L0_BSC2SUP_PRESS ff/H1:HPI-PUMP_CS_BSC2SUP_PRESS_PSI
cp 56/H1:HPI-PUMP_L0_BSC2RET_PRESS f1/H1:HPI-PUMP_CS_BSC2RET_PRESS_PSI
cp 9e/H1:HPI-PUMP_L0_PS1_PRESS1 24/H1:HPI-PUMP_CS_PS1_PRESS1_PSI
cp 22/H1:HPI-PUMP_L0_PS1_PRESS3 a7/H1:HPI-PUMP_CS_PS1_PRESS3_PSI
cp a1/H1:HPI-PUMP_L0_PS1_PRESS4 f6/H1:HPI-PUMP_CS_PS1_PRESS4_PSI
cp 5b/H1:HPI-PUMP_L0_PS2_PRESS1 9c/H1:HPI-PUMP_CS_PS2_PRESS1_PSI
cp e7/H1:HPI-PUMP_L0_PS2_PRESS3 1f/H1:HPI-PUMP_CS_PS2_PRESS3_PSI
cp 64/H1:HPI-PUMP_L0_PS2_PRESS4 4e/H1:HPI-PUMP_CS_PS2_PRESS4_PSI
cp 18/H1:HPI-PUMP_L0_PS3_PRESS1 f4/H1:HPI-PUMP_CS_PS3_PRESS1_PSI
cp a4/H1:HPI-PUMP_L0_PS3_PRESS3 77/H1:HPI-PUMP_CS_PS3_PRESS3_PSI
cp 27/H1:HPI-PUMP_L0_PS3_PRESS4 26/H1:HPI-PUMP_CS_PS3_PRESS4_PSI
cp c8/H1:HPI-PUMP_L0_PS4_PRESS1 f5/H1:HPI-PUMP_CS_PS4_PRESS1_PSI
cp 74/H1:HPI-PUMP_L0_PS4_PRESS3 76/H1:HPI-PUMP_CS_PS4_PRESS3_PSI
cp f7/H1:HPI-PUMP_L0_PS4_PRESS4 27/H1:HPI-PUMP_CS_PS4_PRESS4_PSI
cp a4/H1:HPI-PUMP_L0_MAINSUPPLY_PRESS a/H1:HPI-PUMP_CS_MAINSUPPLY_PRESS_PSI
cp ca/H1:HPI-PUMP_L0_DIFF_PRESSURE 6d/H1:HPI-PUMP_CS_DIFF_PRESS_PSI
cp 39/H1:HPI-PUMP_L0_PRESSURE_OK cc/H1:HPI-PUMP_CS_PRESS_OK
cp a5/H1:HPI-PUMP_L0_PID 43/H1:HPI-PUMP_CS_DIFF_PRESS_PUMP_CTRL_SETPT
cp 64/H1:HPI-PUMP_L0_CONTROL_VOUT 20/H1:HPI-PUMP_CS_PUMP_CTRL_OUT_V
cp 10/H1:HPI-PUMP_L0_LEVEL_ALARM 39/H1:HPI-PUMP_CS_LEVEL_SENSOR
cp 18/H1:HPI-PUMP_L0_TWEAKSIZE f/H1:HPI-PUMP_CS_DIFF_PRESS_PUMP_CTRL_OUTPUT_TWEAK_SIZE
cp 74/H1:HPI-PUMP_L0_OUT_TWEAK 4/H1:HPI-PUMP_CS_DIFF_PRESS_PUMP_CTRL_OUTPUT_TWEAK_REQ
cp 9d/H1:HPI-PUMP_L0_MODE 60/H1:HPI-PUMP_CS_DIFF_PRESS_PUMP_CTRL_MODE
Richard, Gerardo, Jordan, Fil, Patrick, Jonathan, Dave
Fil, Gerardo, Richard, Jordan ran a line from the Kobelco compressor over to the vacmr rack and connected it to a spare Beckhoff ADC channel.
I wrote an EPICS IOC which reads the raw voltage from the Beckhoff terminal and converts it to DegC and DegF oil temperature.
The ioc is kobe_oiltp_ioc.py. It reads the raw voltage from H0:VAC-MR_TERM_M28_CHAN3_IN_VOLTS and converts this to temperature DegC using the simple formula
DegC = 30 * V
It also converts the temperature to DegF and, along with the raw voltage read via ezca, exports these in EPICS channels. The chan names are:
[H1:VAC-MR_KOBE_OILTP_VOLTS]
[H1:VAC-MR_KOBE_OILTP_DEGC]
[H1:VAC-MR_KOBE_OILTP_DEGF]
H1:VAC-MR_KOBE_OILTP_DEGF was added to the alarms system. Cell phone alarms will be sent to the vacuum group if the temperature exceeds 150F or falls below 100F.
These channels have been added to the Vacuum Overview MEDM (attached).
Currently the kobe_oiltp_ioc is running in a tmux on opslogin0. If it becomes a more permanent feature we will move it over to a container on the service-host cluster.
(Betsy, Jason, Oli)
Today Jason setup to see Pitch and Yaw of the BBS in the suspension cage on the cartridge. We were a ways off in Yaw and some Pitch. I spent a few hours walking YAW but the mechanics are rough. 5 bolts lock down the whole Top Blade assy and then you can use a push or a pull screw to pivot the whole Top Blade mechanism. Repeat for the second Top Stage blade assy. Of course when you pop the 5 locking screw the entire chain sags and grounds on stops yeilding confusing beams to look at. So a few iteration of this and that got us kinda no where. Part way thru I discovered that the push/pull thingy was totally out of range on both. No idea why. So back to starting over tomorrow and maybe trying to go around this "yaw" adjustment and just push the stages in the mounting slop or something.
Seems like I wrote this alog 10 years ago. Probably did since the mechanics from the BS are the same and we struggled with them at that time too. Will need to read back and also check how LLO faired with this.
Meanwhile, Oli and I also struggled to get Pit damping working so a few hours of parallel brain straining on that, swapping out the quad cable and it seems to be working. Weird tho because this is the same cable we used on the BS just a couple weeks earlier.
Yeah this yaw adjustment was no fun. Here at Livingston, it took us a decent part of a day but we think we got a good system going by the end.
We adjusted only one side at a time. We tried to keep the way we unlocked/torqued the 5 bolts of the top blade assembly consistent (see photo attached). When we unlocked we tried to only get the bolts barely loose and back them out as little as possible. Each time we locked the 5 bolts down, we found that the structure moved around 0-4 minutes in a consistent direction. By following the attached photo procedure, the yaw seemed to settle consistently 2ish arcminutes off of its unlocked value in the same direction each time. For example, unlocked we would set the BBSS at 45 degrees - 5 arcminutes, and when we locked it down we would get 45 degrees - 3 arcminutes. We repeated the process until we got lucky and the suspension locked in the right place. This took a lot of trial and error. There is some hysteresis in the push/pull screw adjustment. The yaw adjustment is not very good or repeatable.
To make matters worse, the LF and RT OSEM plates have the circular inset that houses the disk that the magnet flag of M1 sits on. This is a place where it is very easy to get subtle rubbing and it is hard to verify by eye. We did this alignment with the QOSEMs which was somewhat of a blessing because the Y direction readback of the QOSEM can act as a guide to tell you if you should start to be concerned about rubbing. It might be worth removing the LF and RT OSEM plates and see if you can to the alignment without roll or vertical damping to avoid this rubbing. If the suspension is moving too much to not have V and R damping, you must frequently adjust the LF and RT OSEMS to ensure that there is no rubbing at that location.
(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.)
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 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.
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.)
Attached are an example of beam position measurements (in this case MC1).
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.
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.)
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 |
TITLE: 05/21 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:
20:44 UTC the TSCX chiller's flow went to zero.
TJ turned the chillers back on and walked the lines to check for leaks.
Pressure and flow seems to be stable now.
VAC Alarms: Type Error while running test: VAC
GV1 is OPEN
GV5 is closed.
GV6 is closed.
Type Error cleared in VAC. I guess this is was caused by the CDS team.
DAQ restart happening at 22:28 UTC. Dave Says we are the DAQ restarts are done.
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 14:54 | VAC | Jordan | LVEA | N | Turning off the purge air. | 15:03 |
| 14:56 | VAC | Jordan & Contractor | Kobelco Pumps | N | working on VAC pumps. | 19:56 |
| 14:57 | NATR | Snake | LVEA Near PSL | N | Sneakin around looking for the mouse. | 16:27 |
| 14:58 | NATR | Mouse | LVEA Y-arm | N | Stuck in trap. | 16:27 |
| 15:16 | Safety | Richard | LVEA | N | Looking for wildlife. | 15:36 |
| 15:25 | VAC | Jordan | LVEA | N | Looking for wildlife. | 15:45 |
| 15:26 | NATR | Eric | LVEA | N | Looking for wildlife | 16:03 |
| 16:11 | EE | Fil | Mech Room | n | Working on HEPI | 18:11 |
| 16:38 | SEI | Jim, Ryan S, Shoshanna | Optics lab | N | cleaning optics | 17:36 |
| 16:42 | FAC | Kim | LVEA | N | Technical cleaning & resupply. | 17:07 |
| 16:44 | IAS | Jason | LVEA | N | Faro work on BBSS pitch and Yaw. | 19:08 |
| 17:05 | CDS | Patrick | Mech room | N | Searching for Fil | 17:14 |
| 17:08 | FAC | Randy | LVEA near BSC2 | n | taking measurements, NOT inside chamber. | 18:25 |
| 17:08 | FAC | Kim | EX | N | Technical cleaning & resupply | 19:08 |
| 17:15 | Safety | Main Gate | Main Gate | N | Main Gate is locked OPEN | 23:11 |
| 17:17 | BBSS | Betsy | LVEA | N | Driving the BBSS | 18:45 |
| 17:21 | TCS | Camilla & Madie | EY | Yes | Working with the ALS table | 18:03 |
| 17:22 | VAC | Travis | LVEA | N | Helping Besty with BBSS | 18:11 |
| 17:29 | BSC2 | TJ | LVEA BSC2 | N | Helping Randy with measurments | 17:52 |
| 18:17 | VAC | Gerardo | LVEA | N | Shutting off the Purge air valve In the LVEA | 18:45 |
| 19:06 | FAC | Randy | LVEA | N | BSC2 platform measurements. | 20:59 |
| 19:57 | BBSS | Betsy | LVEA | N | swapping osems. | 22:57 |
| 20:04 | SEI | Ryan & Shoshanna | LVEA H2 PSL | N | Building LLO CSRs | 23:03 |
| 20:15 | BBSS | Oli | LVEA | N | Helping Betsy | 00:13 |
| 20:39 | IAS | Jason | LVEA West bea | N | BBSS pitch and yaw measurements. | 23:38 |
| 20:54 | TSC | Camilla & Mitchel | Optics Lab | N | getting part? | 22:11 |
| 20:58 | CDS | Patrick | MER | N | talking with Fil | 21:02 |
| 21:03 | VAC | Fil & Jordan | MER | N | Workin on HEPI | 23:03 |
| 21:13 | TCS | TJ | LVEA | N | Checking on TCSX chiller flow rate. | 21:41 |
| 21:27 | EE | Fil | LVEA | N | Helping Betsy and Oli | 22:37 |
| 21:29 | FAC | Randy | LVEA Test stand | N | Taking more measurements. | 22:00 |
| 21:42 | SUS | Rahul | LVEA | N | Bag and Tag parts. | 22:22 |
| 22:22 | VAC | Travis | LVEA | N | Checking vac guages for glitches from the power fluxuation. | 22:26 |
| 22:40 | CDS | Dave | CUR | N | DAQ restarts to add new channels | 22:40 |
| 22:41 | CDS | Fil & Patrick | MER | N | Working on HEPI Beckhoff (Patrick \ | 00:25 |
| 22:51 | ALS | Madie Camilla | EY | YES | Measuring ALS beam | 23:51 |
Ibrahim, Oli
We ran a long overnight Bounce measurement on the BBSS. The BRDs weren't installed for this measurement. AOSEM flags were not installed, and we were 100g heavier at M1 than we are now (this measurements was taken before 90294).
With those settings in mind, our measurements show that our Bounce mode was at 19.80Hz. The last time these measurements were taken, back in the staging building (88141), the bounce mode with no BRDs was ~19.74Hz, so they're consistant.
The measurement file can be found in /ligo/svncommon/SusSVN/sus/trunk/BBSS/H1/BS/Common/Data/ 2026-05-19_2200_H1SUSBS_M1M2_BounceNoBRD_V_0p001to40Hz.xml as r13012.
Attached here is a zoomed in version of this file. The mode is indeed clearly visible in M2 UL, and the frequency is known well enough for proper BRD tuning. Thanks!
The Q of the mode seems to be about 3400. Maybe a higher excitation would be possible to get a better definition. Were you at the saturation limit to drive M1 V?