Jennie W, Jeff K, Josh F, TJ S,
Summary: SPI interferometers aligned, shroud installed successfully. One stray beam and possible clipping on shroud to investigate/deal with but otherwise all problems were solved. Obligatory success photo taken by Josh.
Today we:
J. Freed
Found the problem discribed in 90644, as well as the strange sawtooth beat notes we have been finding in our IFOs. It was user error on our CDS system, the double mixer (which produces our REF RF signal for AOMs) requires a sin wave and cos wave 4096Hz signal. We were sending it 2x cos signals.
This also explains why our demod systems were not working as they use the same signals.
The sawtooth that Josh mentions was how the poorly phased analog versions of the 4096 Hz SIN and COS LO signals manifested on the digitized versions of the IFO PD voltage, reading out that beatnote. Here, I attach what it looked like on the o-scope (before discovering the issue of phasing the two SIN and COS versions of the LO).
I've been talking to Jeff about changes to the ISI and seiproc models for SPI and CRS integration. The ISI models are pretty much done, but today I added a parts to seiproc to take HAM2345 cps and gs13 cart channels and blend them to create cartesian differential supersensor channels. The idea being these will be good metrics for determing if SPI is actually improving the differential ISI motion. Plan is to use blend filters to combine the cps and gs13 pairs from each chamber to make supersensor channels, and then compare the differential supersensors for HAM2-3 to the differential supersensors at HAM45. I've checked that seiproc builds with these changes, but I now have some changes to make to the HAM45 models and some ipcs to make. And then a whole bunch of medm work.
Erik had to attach my screen shot, because firefox is not cooperating in the control room for me, but it shows a snippet of the flow in the ISI_DIFF block in seiproc and the channels I think Jeff wants to save. We didn't talk about data rate, so that's just a guess.
TITLE: 06/18 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY: BBS checks, SPI, and CRS work continued. (Covering the end of day for TJ).
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 20:18 | SAF | LVEA IS LASER HAZARD | LVEA | YES | LVEA IS LASER HAZARD | 12:18 |
| 15:44 | SPI | Jeff, Josh | LVEA | Y | SPI HAM3/2 work | 18:58 |
| 15:58 | SPI | Jennie | LVEA | Y | SPI HAM3/2 work | 18:58 |
| 16:01 | CRS | Betsy | LVEA | Y | Checking on chamberside test site for CRS | 16:26 |
| 16:26 | SEI | Jim, Randy, Shoshana | LVEA | Y | Crane and move CRS from H2 to next to HAM3 | 17:10 |
| 16:52 | VAC | Travis | LVEA | Y | Removing the old ISI oplev viewports on input and output arms | 19:01 |
| 16:58 | SUS | Ryan C | CR,EX,EY | n | SUS oplev charge measurements | 18:58 |
| 17:35 | SEI | Fil, Jason | LVEA | Y | Looking at the ISI oplev setup with Travis | 18:21 |
| 18:08 | SEI | Shoshana | LVEA | Y | CRS work near HAM3 | 20:25 |
| 18:37 | VAC | Gerardo | LVEA | Y | Helping removing viewport by HAM2 | 20:02 |
| 18:59 | SPI | Josh | LVEA | Y | SPI electronics racks | 20:36 |
| 19:15 | SUS | Betsy, Camilla | LVEA | Y | Going into HAM3, BSC2. Camilla out 20:45 | 21:38 |
| 20:14 | SUS | Sheila | LVEA | Y | Swap in for Camilla | 21:38 |
| 20:21 | SPI | Jennie | LVEA | Y | Looking for shroud parts | 22:32 |
| 20:21 | SPI | TJ | LVEA | Y | Installing shroud | Ongoing |
| 20:25 | SPI | Jeff | LVEA | Y | SPI work | 22:32 |
| 20:39 | SUS | Oli | LVEA | Y | HAM3/BSC2 checks | 21:38 |
| 20:52 | SUS | Tom | LVEA | Y | Join BBS team | 21:59 |
| 20:57 | SUS | Camilla | LVEA | Y | Grab stuff | 20:58 |
| 21:30 | FAC | Randy, Ibrahim | LVEA | Y | Move a scissor lift, find ameristat wrapper | 21:43 |
| 21:38 | EPO | Elenna, Deon, Matilda, Shrey, Khanh | LVEA | Y | Tour the LVEA | 22:34 |
| 21:42 | VAC | Travis | LVEA | Y | Viewport swap continued | 23:20 |
| 21:51 | VAC | Gerardo | LVEA | Y | CP1, check out pipes | 21:58 |
| 22:01 | SPI | Josh | LVEA | Y | SPI work at SUS R2 rack | Ongoing |
| 22:25 | SPI | Betsy | LVEA | Y | Check on SPI crew | 22:35 |
| 22:37 | SUS | Ibrahim, Tom, Deon, Oli | LVEA | Y | BSC2 cross coupling investigation and tour | 23:34 |
| 22:43 | SEI | Jim | LVEA/CR | Y | Diagnose HAM5 rack sensor signals | 23:25 |
Today Gerardo and I removed the unused HAM ISI Oplev viewports from the VP7 ports of both the -X input manifold and the +Y output manifold. The ports were blanked off with 10" CF blanks. I noted a series of 3 scratches on the angled flat of the flange, but the knife edge itself wasn't noticeably deformed. See pics.
Note to VAC: These will need to be leak checked during pumpdown.
Betsy said they couldn't isolate HAM5 while trying to find beam in the output arm. When I opened the overview, I saw that all of the corner 2 sensors were all 0. I went to the CER and found that the corner2 interface chassis was turned off. Turned that back on, HAM5 can isolate now. They tend to work better with all of their sensors.
At 15:03 Gerardo switched CP1 level control from manual to PID. We verified that the PID settings are still as they were when the LN2 level sensor stopped working on 5th August 2021.
I have added a ndscope trender which shows the pump level and the PID LLCV control value cp1_1_day_trend
CP1 pump level control alarms were restored to the alarms system, alarm level set to <= 85% and >=99%.
--- h0ve_configuration.xml (revision 7482)
+++ h0ve_configuration.xml (working copy)
@@ -9,30 +9,26 @@
<!-- CRYOPUMP ALARMS -->
<!-- Pump LN2 Levels -->
<!-- CP1 -->
-<!-- Indefinitely remove CP1 alarms due to long-term sensor failure. WP10156 06jan2022 D.Barker LHO -->
-<!-- -->
-<!-- <Channel name="H0:VAC-LY_CP1_LT100_PUMP_LEVEL_PCT" low="8.0e+01" high="9.9e+01" description="CP1 Pump LN2 Level"> -->
-<!-- <Contact address="5094380824@vtext.com" hot="15" cool="5" description="C:Richard McCarthy"></Contact> -->
-<!-- <Contact address="5094380826@vtext.com" hot="15" cool="5" description="C:David Barker"></Contact> -->
-<!-- <Contact address="5094380828@vtext.com" hot="15" cool="5" description="C:Gerardo Moreno"></Contact> -->
-<!-- <Contact address="2083011360@vtext.com" hot="15" cool="5" description="C:Travis Sadecki"></Contact> -->
-<!-- <Contact address="rjmcc@caltech.edu" hot="5" cool="2" description="E:Richard McCarthy"></Contact> -->
-<!-- <Contact address="dbarker3@caltech.edu" hot="5" cool="2" description="E:Dave Barker"></Contact> -->
-<!-- <Contact address="gmoreno@caltech.edu" hot="5" cool="2" description="E:Gerardo Moreno"></Contact> -->
-<!-- <Contact address="tsadecki@caltech.edu" hot="5" cool="2" description="E:Travis Sadecki"></Contact> -->
-<!-- </Channel> -->
-<!-- <Channel name="H0:VAC-LY_CP1_LT100_PUMP_LEVEL_PCT_ERROR" low="-5.0e-01" high="1.0e+00" description="CP1 Pump LN2 Level ERROR"> -->
-<!-- <Contact address="5094380824@vtext.com" hot="15" cool="5" description="C:Richard McCarthy"></Contact> -->
-<!-- <Contact address="5094380826@vtext.com" hot="15" cool="5" description="C:David Barker"></Contact> -->
-<!-- <Contact address="5094380828@vtext.com" hot="15" cool="5" description="C:Gerardo Moreno"></Contact> -->
-<!-- <Contact address="2083011360@vtext.com" hot="15" cool="5" description="C:Travis Sadecki"></Contact> -->
-<!-- <Contact address="rjmcc@caltech.edu" hot="5" cool="2" description="E:Richard McCarthy"></Contact> -->
-<!-- <Contact address="dbarker3@caltech.edu" hot="5" cool="2" description="E:Dave Barker"></Contact> -->
-<!-- <Contact address="gmoreno@caltech.edu" hot="5" cool="2" description="E:Gerardo Moreno"></Contact> -->
-<!-- <Contact address="tsadecki@caltech.edu" hot="5" cool="2" description="E:Travis Sadecki"></Contact> -->
-<!-- </Channel> -->
-<!-- -->
-<!-- End of WP10156 -->
+<Channel name="H0:VAC-LY_CP1_LT100_PUMP_LEVEL_PCT" low="8.5e+01" high="9.9e+01" description="CP1 Pump LN2 Level">
+ <Contact address="5094380824@vtext.com" hot="15" cool="5" description="C:Richard McCarthy"></Contact>
+ <Contact address="5094380826@vtext.com" hot="15" cool="5" description="C:David Barker"></Contact>
+ <Contact address="5094380828@vtext.com" hot="15" cool="5" description="C:Gerardo Moreno"></Contact>
+ <Contact address="2083011360@vtext.com" hot="15" cool="5" description="C:Travis Sadecki"></Contact>
+ <Contact address="rjmcc@caltech.edu" hot="5" cool="2" description="E:Richard McCarthy"></Contact>
+ <Contact address="dbarker3@caltech.edu" hot="5" cool="2" description="E:Dave Barker"></Contact>
+ <Contact address="gmoreno@caltech.edu" hot="5" cool="2" description="E:Gerardo Moreno"></Contact>
+ <Contact address="tsadecki@caltech.edu" hot="5" cool="2" description="E:Travis Sadecki"></Contact>
+</Channel>
+<Channel name="H0:VAC-LY_CP1_LT100_PUMP_LEVEL_PCT_ERROR" low="-5.0e-01" high="1.0e+00" description="CP1 Pump LN2 Level ERROR">
+ <Contact address="5094380824@vtext.com" hot="15" cool="5" description="C:Richard McCarthy"></Contact>
+ <Contact address="5094380826@vtext.com" hot="15" cool="5" description="C:David Barker"></Contact>
+ <Contact address="5094380828@vtext.com" hot="15" cool="5" description="C:Gerardo Moreno"></Contact>
+ <Contact address="2083011360@vtext.com" hot="15" cool="5" description="C:Travis Sadecki"></Contact>
+ <Contact address="rjmcc@caltech.edu" hot="5" cool="2" description="E:Richard McCarthy"></Contact>
+ <Contact address="dbarker3@caltech.edu" hot="5" cool="2" description="E:Dave Barker"></Contact>
+ <Contact address="gmoreno@caltech.edu" hot="5" cool="2" description="E:Gerardo Moreno"></Contact>
+ <Contact address="tsadecki@caltech.edu" hot="5" cool="2" description="E:Travis Sadecki"></Contact>
+</Channel>
J. Oberling, R. Crouch, J. Warner, B. Weaver, I. Abouelfettouh, O. Patane, S. Appert
And finally, here is the long-promised alog for our full set of measurements of the now-deinstalled aLIGO BS. I will give a brief overview of the WBSC2 support tube and BS in-chamber measurements we took, but the bulk of this alog will concern the various test stand measurements we took and how they tie in to the in-chamber and support tube measurements. As a reminder, our alignment tolerances for the aLIGO BS were:
Strap in folks, this is going to be a long one with a wall of text. But first, I demand... A shrub, errr, a summary!
Summary
Earlier this year we measured the location of the ends of the WBSC2 support tubes. They indicated a -X translation of the WBSC2 cartridge and a CCW yaw. But, since the support tube length wasn't a controlled dimension for support tube construction we can't use them to definitively inform us about the cartridge assembly in the chamber (we've measure 4 tubes so far, and all 4 have been different lengths by several mm). The -X translation was a little surprising because we translated the cartridge in the +X direction during our 2013 install, implying that the support tubes were already sitting too far in the -X direction. The CCW yaw wasn't surprising since we yawed the cartridge CCW back in 2013.
At first we thought the in-chamber alignment looked pretty good, it was only after the cartridge had been removed from the chamber that we realized the mode we had used to make the measurements had a high potential to disguise positional deviations and make the measured point look closer to nominal than it actually was (see the in-chamber section below for full details). The decision to use this mode was made during our planning for the alignment (it's in our alignment procedure), and was based on an incomplete understanding of how the underlying mode actually worked. Well, now we know better, but unfortunately the consequence is that we cannot say how well the BS was aligned to the IFO XYZ coordinate system. What we can say is that the BS was clearly yawed in the CW direction w.r.t. the SUS cage, by potentially several mrad, but have no insight into how it was yawed w.r.t. the IFO XYZ axes.
On the test stand, we found the BS SUS to be right on the edge of our position tolerances for the optic. We never measured the SUS cage back in 2013, so this was the first time we had looked at it. The optic itself was found to be within our position specs, but we did measure the position to be in a different place than we did in 2013. We traced this primarily to 2 things: The large +/- 2.0 mm error bar in the total station's distance measurement mode (used to set the optic's longitudinal position in 2013) and errors in the position of the test stand's brass monuments (used to place the alignment equipment in 2013). We were able to trace this using the FARO, using its much higher accuracy to measure both the BS longitudinal position and the test stand monuments. We did find that the pointing of the BS was well outside of our specs: pitch was ~200 µrad up while yaw was ~710 µrad CW. While the pitch being out of spec after the cartridge was craned was not surprising (looking back through my aLIGO install notes we never had a pitch alignment survive craning into a chamber), we were surprised at the yaw measurement. The mispositioning of the test stand monuments did not explain this yaw, and we could find no obvious cause.
WBSC2 Support Tubes
The WBSC2 support tube ends were surveyed with FARO earlier this year. From talks with Jim, my understanding is that support tube length was not a critical dimension for tube construction, and so far this is holding up. We've measured the support tube ends for WBSC2 and WBSC3 so far (more to come as we're able), and the lengths have not been constant (the WBSC3 support tubes measured short of their design length, and each one was a different length, while both WBSC2 support tubes measured longer than their design length). Because of this, we can't give any definitive numbers about the respective cartridges, but the info does offer some general guidance. For WBSC2 this is:
The important thing to note here, in my opinion, is the CCW yaw (again, the direction, not so much the exact number). This will be important later on, once we get to the test stand measurements.
aLIGO BS In-Chamber
We took a series of measurements on the BS while in the chamber in mid-April, see the alog for more detail. Some important takeaways, in my opinion:
Because we used the Build/Inspect mode with the automatic SMR radius compensation turned ON to measure the BS SUS position in-chamber, we unfortunately do not have a good idea of where the SUS was located within WBSC2 and by extension do not have a good idea of where the BS optic was positioned. Subsequent testing after the cartridge had been removed from the chamber showed that we did not have a good understanding of how the automatic SMR compensation worked. Short version: It's dumb. It simply compensates in the direction of the measurement object, regardless of where your measured point is. For example, you're measuring a point on the the underside of a horizontal plate with Build/Inspect mode. The SMR would sit below this plate in the -Z direction, so the SMR radius should be compensated in the +Z direction. The automatic compensation does not compensate in the +Z axis alone, it compensates directly towards the nominal point. This then can result in a measurement that looks dead on but in fact could be nowhere close; if the actual point is off several mm in the X and Y directions, the automatic compensation would make the resulting measurement look like it was dead on as it compensates towards the measurement object, removing the actual deviations in the process. The final attached picture is a drawing showing this behavior. We finally noticed this while testing the FARO test stand alignment procedure on an old HAM passive stack after the BS cartridge was removed, and then confirmed it while aligning the BBS SUS on the test stand; initial BBSS placement was done via Build/Inspect as a real time feedback, but we measured the points using a more involved method that tells PolyWorks what direction to compensate in instead of letting the software do it automatically. The measured points were several mm off of the Build/Inpsect points, and we confirmed the automatic compensation was the cause by turning it on and off (when automatic compensation was turned off, Build/Inspect reported deviations that matched our direct measurement of the alignment points).
aLIGO BS Test Stand
FARO Measurements
And now we come to the test stand meausurements. To start, we aligned the FARO to the ISI using 10 points on the ISI; these points and the resulting alignment are shown in the 1st attached picture, and show the FARO is well aligned to the ISI. Once the FARO was aligned to the ISI we then measured several points along the bottom of the SUS cage, as well as the center of both the HR and AR sides of the lower Figure 8 structure; this is shown in the 2nd attached picture. We did not measure the SUS cage position during aLIGO install, only the optic position, so it's good to see the cage is mostly in the neighborhood of the optic position tolerances. One note about the Z axis numbers shown here: The CAD model used here is the in-chamber model, which places the BS at its in-chamber Z axis coordinate of -82.9 mm. However, the BS SUS is the same length as the QUAD SUSs, so the BS is placed w.r.t. the ISI the same as the QUADs, i.e. at -80.0 mm; -82.9 mm was acheived in-chamber by lowering HEPI, but on the test stand the BS was aligned at -80.0 mm. This was never properly corrected for in the CAD model; I think the SUS cage itself and its components were lowered while the ISI was left at its nominal height, so all the Z axis measurements should show a deviation of around +2.9 mm (since they are physically higher than the CAD would indicate). This is seen most clearly with the HR and AR Figure 8 structure measurements. Both Z axis positions measured right around -80.0 mm as they should, while the CAD model claims they are too high. This has been corrected for in the BBS CAD model, so this is the only time we'll see this discrepancy.
The 3rd attached picture shows a set of lines created from the measurement points we took on the structure which show how the BS SUS cage is rotated w.r.t. the ISI; I also rotated the CAD model so that it matches the target yaw angle of the BS optic itself. The angles here are reported w.r.t. their respective positive axes (i.e. X Ang is the angle measured from the positive X axis). As can be seen, the SUS cage had a large CCW yaw w.r.t. the ISI. Averaging the various yaw deviations gives a yaw of the BS SUS w.r.t. the ISI of 0.2762°, or 4.82 mrad CCW. This explains the large CW yaw of the BS optic w.r.t. the SUS cage.
With those measurements done we then used the FARO to set a total station looking at the AR surface of the BS, set along the target AR surface normal so we can measure position deviations from nominal. Once we had these position deviations we moved the total station to the HR side of the BS, mounted a laser autocollimator (LAC) on top of it, set it along the target HR surface normal and offset by 150.0 mm (to avoid the test stand leg) to measure the pitch and yaw of the BS. The results were posted to the alog here, so the details follow below.
I should note here how we measured the longitudinal position of the BS AR surface. As noted above, we used the FARO to measure the circle that represents the AR side of the lower Figure 8 structure of the BS SUS; PolyWorks calculates the center of this circle, and is what is shown on the 2nd attachement with the label "BS_FIG8_AR". We also know the position of the total station, as we set that using the FARO. We then use PolyWorks to measure the distance between the total station and the BS AR Figure 8, as well as measure the target distance from the total station to the BS AR surface. We then measure the distance from the AR Figure 8 to the BS AR surface using a depth micrometer; this was done on the left, right, top and bottom of the Figure 8. These 4 measurements are averaged together to give us a distance from the Figure 8 to the BS AR surface, which is then added to the measured distance from the total station to the AR Figure 8. This final distance is compared to the target "total station to BS AR" distance to give us the longitudinal position deviation of the BS AR surface.
BS Position and Pointing
The original BS test stand alignment was completed in early February 2013. The below table gives the final position and pointing deviations we measured in 2013 and those we measured now; I've rotated the position deviations to the IFO XYZ axes for both. In 2013 we were on Test Stand #2 (currently disassembled due to filter cavity interference) and using pre-set brass monuments, and now we are on Test Stand #1 and using the FARO to precisely set the total station.
| 2013 Test Stand | 2026 Test Stand | Difference | |
| X | +0.1 mm | -1.8 mm | -1.9 mm |
| Y | +0.1 mm | +0.8 mm | +0.7 mm |
| Z | +0.3 mm | -0.8 mm | -1.1 mm |
| Pitch | -20 µrad (up) | -200 µrad (up) | -180 µrad |
| Yaw | -10 µrad (CW) | -710 µrad (CW) | -700 µrad |
That's, uh, quite the difference, yeah? A couple of things that should be noted here:
Despite the large difference in position deviations between 2013 and 2026, these are still within our set position specification. The pointing is decidedly not. While it's entirely possible that things have drifted in the 13 years since the BS was installed, there are 2 somewhat obvious things that would contribute to this difference: The total station's +/- 2.0 mm error bar for distance measurements and error in the placement of the test stand's brass monuments. We've already measured a difference in longitudinal position between 2013 and 2026 that is within the error bar of the total station's distance measurement, but what about the test stand monuments? Well, we used FARO to measure those.
Test Stand #2 Monuments
To measure the test stand monuments we first had to align the FARO to the test stand coordinate system. To do this, we used the set of monuments set along the XY axes of the stand and PolyWorks' Best-Fit Alignment routine (the same routine used to align the FARO to the ISI on the test stand); the test stand coordinate system was assumed to be flat along the floor and 2 dimensional (XY only), so I forced all of the Z axis nominals and measured to 0.0. The results of the alignment are shown in the 4th attachment. It's immediately apparent that our test stand monuments are not going to be where we thought they were, as the alignment routine was not able to fit a good alignment between the nominal and measured coordinates of the alignment monuments (the first attachment shows the results of the alignment routine when it can find a good fit between the nominal and measured data). We re-did this a couple times and got very similar results each time (to <0.1 mm), so the monuments are definitely not where we thought they were. We proceeded to use this alignment to measure the rest of the test stand monuments; those are shown in the 5th attachment. As expected, none of the monuments are well positioned, all show large errors. Well then. So now we have both an error in the longitudinal measurement (but within the error bar) and test stand monuments not where we thought they were. How could this have affected the 2013 BS XY alignment? To figure this out, I used PolyWorks to recreate our 2013 alignment setup, now with our mispositioned monuments and with our longitudinal position error. Since we had to rotate the cartridge to place it on the test stand, I created a new coordinate system that's rotated 90° CW, so the monuments are in the same coordinates as the BS would be once installed in-chamber (I was getting cross-eyed constantly flipping between the IFO and test stand coordinate systems, this made things much easier).
First I wanted to consider how these issues could have affected our 2013 XY position alignment, so I recreated the setup looking at the AR side of the BS. The 6th attachment shows this. There's a lot of info in this picture, so match the below numbered list with the red numbers in the picture. Also, "Theo" is my shorthand for theodolite, which is another name for a total station.
That's all well and good for X and Y, but what about the Z axis deviation between 2013 and 2026? Again, all I have to fall back on is 2013 equipment setup errors or things drifting over the course of the last 13 years. For equipment setup, we set optic height by setting the total station at a target distance down from the ISI, using a scale attached to a fixed-length rod, that matched the desired Z axis position of the BS. There could have been an issue with the scale/rod setup (such as a mistake in rod length (not likely) or the scale not mounted properly) or an issue with the total station setup (such as not well levelled or sighting the scale along a zenith angle other than 90°). While I'd like to think that 2013 me would not have made such obvious mistakes, 2026 me doesn't have perfect recall of events from over a decade ago so I cannot say for sure.
For pointing I made our HR test stand setup in PolyWorks, this is shown in the 7th attachment. This is much simpler as I'm only looking to see if the monument misposition caused a large yaw error back in 2013. Quick explanation, we set our total station/LAC combo over monument TS2-20 and sighted monument TS2-19 to set our 0° reference line. We then turned 44.9711° so we were sighting parallel to the HR surface normal of the BS; the gap between the 2 lines in the picture was handled by a Lateral Hollow Transfer Periscope, a device that horizontally translates the beam by ~400 mm while keeping the output beam parallel to the input beam by 1 arcsecond (0.0003°). For a 710 µrad CW yaw deviation in the BS to be caused by the monument mispositioning the deviation of the 0 Reference Line would have to be 0.0407° in the CW direction; this would be a measured X Angle of the line "Theodolite HR HA Ref" of 90.0407°. Clearly, this is not the case. In fact, the angle deviation caused by the monument misposition is only 0.0019°, or ~33 µrad, in the CCW direction. At this point, the only explanation I have for the difference in yaw between 2013 and 2026 is an equipment setup error in 2013 or things subtly shifting in the last 13 years. Keep in mind, we're not talking large shifts in the BS to cause this yaw. If we hold one side of the BS fixed in position and then yaw it by 710 µrad, the opposite side only moves by 0.26 mm (0.000710 * 370.0 = 0.263).
Wrapping Up
So, what does this all mean? Well, with the mistake in using the Build/Inspect automatic compensation mode we don't have any better of an idea where the BS was in the IFO XYZ coordinate system than we did before the cartridge was disassembled. The measurement looks good, but as I explained above I do not trust it. The support tube measurement indicates a -X shift from nominal and a CCW yaw, but these aren't good metrics since support tube length wasn't a critical dimension during tube construction (we've measured 4 so far and all 4 have been different by several mm). I wish I had better news to report here, but we didn't notice the mistake until after the cartridge had been removed from the WBSC2 chamber so there was no way to remeasure the in-chamber position.
The test stand measurements show that the BS SUS was on the edge of our positional tolerance for the optic, with a few points just outside of it. The optic itself, the object of primary importance and the only thing we actually measured in 2013, was within our positional tolerances but different from our 2013 measurements. The primary causes of this were found to be errors in the positions of the test stand brass monuments that we used to set our alignment equipment during the intial 2013 alignment, and the large error bar in the total station's distance measurement mode. The pointing was found to be well outside our tolerances, and I currently cannot explain the yaw deviation. Looking back through my old install notes we never had our test stand pitch alignment survive being craned into the chamber (ITMx shifted by over 2 mrad in pitch after being craned into the WBSC3 chamber), so the pitch being off wasn't really surprising. But the yaw was. Our measurements of the test stand monuments, despite the position deviations, did not show a large yaw deviation. The angle we turned the total station to measure the yaw was different between our 2013 alignment and 2026 measurements, but only by ~24 µrad so not enough to account for the 710 µrad CCW yaw we measured in 2026. We couldn't find any obvious cause of this, so all I can offer are guesses (procedure mistake, equipment setup mistake, small drifts over 13 years, etc.).
Sheila, Keita, Betsy, Elenna, Ibrahim, Oli, Tom, Camilla. Follow on from 90656
Summary: For BS alignment checks, we spent some time with the SQZ beam to check that we are happy with the SRC pointing. We could not find a beam using the BS sliders only. But we could see SQZ beam reflected off both ITMX and ITMY on the IR viewer paper at PR2. Beam splitter is being moved to overlap these SQZ beams.
With ITMY aligned, SR2, SRM mis-aligned, we expect 2.5 counts of AS_A and AS_B (1.25mW * 0.3 SRM * 0.5 BS * 0.5 BS * 0.3 SRM), we could get this on AS_A and AS_B after we reverted SR3 to O4 sliders and started with SR2 at O4 sliders but moved significantly to get light on AS_A and AS_B.
Once SRM was aligned, we could see a beam not centered on the camera. We then realized the ITMs were far off (for Oplev centering in 90443) and then started taking ITMY back towards sliders walking with SR2 (ZM6 didn't have enough range) to get a round beam more centered on AS_AIR camera. *Sheila was later unsure we should have moved ITMY like this.
After this we could see SRY fringes, there were +/-10 counts in size.
We then took ITMX to it's oplev positions last time we had DRMI lock (19 March 2025 18:02 UTC). The sliders/L2 WIT osems were still ~30urad off, think this is okay for this gross BS alignment.
Sheila put a large wobble on the BS while we had ITMX only aligned and we watched the AS_AIR camera and AS_A/AS_B. We could not find the beam off the BS at the HAM6 sensors.
Betsy then went into the chamber and could see the SQZ beam reflected off both ITMX and ITMY on the IR viewer paper clipped at the baffle in front of PR2. Sliders helped bring these beams together but was not enough. Beam splitter is being moved to overlap these SQZ beams...
Sheila, Oli and I worked on mechanically adjusting Pitch of the BBSS (BS) to bring the ITMs closer together in pitch as seen via their SQZ beams in front of PR2. In the end, I adjusted the BBSS PUM pitch adjuster ~2 full turns (after some more iterating) to get the ITM beams ~on top of each other (our better touching instead of inches apart). At some point it got harder to land the beams right on top of each other as I kept walking over the sweet spot so we moved over to using the sliders. I thought we had the slider values at ~1000 on each PIT and YAW when we left the chamber around 2:30pm PT. However now that we have moved back into the controlroom we have fallen down a few side quests and are a bit confused on what alignments are good and what aren't. So, I think we will need to revisit all of the alignment again starting next week.
Side Quest 1 - In order to refine our initial conditions alignment, Camilla and Elenna started looking closer at the ITM and SR2 slider values which were moved earlier in the day to get the SQZ correct on the AS_AIR. This was confusing since the ITM oplevs likely dropped off when we vented. Then, Anamaria pointed them ~Jun 2 90485 in order to monitor FC and baffle work, but then also they were different a month ago. These biases could be turned off to restore the "IFO pointing" but then we will be blind to the OPLEVs. So, this needs more study.
Side Quest 2 - I brought the HAM5 ISI state to Jims attention today - Jim found that HAM5 had some issues with some sensor electronics being off at the rack for the last 50 day (since April 29th) so fired that up and got the ISI back into the correct state. This moved the beam alignment Elenna and Camilla were in the middle of, so Camilla put the SR3 back to the oplev to restore the beam on the AS_AIR again.
Side Quest 3 - The BBSS sliders are badly cross-coupled in PIT and YAW - we see the beam move diagonally when moving them. LLO is newly reporting this as well. On the test stand there was no Tom, Oli and Ibrahim are looking into this - at the moment they are measuring which of the QOSEMs are firing up when requesting YAW and PIT, so the sliders are on the move. This needs more study.
So, the good news is that we have a process to view the IFO corner alignment in order to confirm/tweek the BBSS.
However because of the above and the factors which mean some SUSes have accurate OPLEVs and some don't, we will need to restart on Monday with repointing the ITMs and then revisit the SQZ beam at PR2.
SR2 - Use OPLEV pointing from THUR 5pm (when ISI came back on)
ITMs - Turn Anamaria biases off then restore to OSEMs from DRMI (?)
The pic of the beams is from before I started the mech pitch adjustment but had Yaw aligned via the slider.
The lead chiller at the corner station was changed from chiller 1 to 2. This is due to a condensing pressure fault that occurred overnight on chiller 1. The sequence is now chiller 2 - lead, chiller 1 - lag, chiller 3 - standby. Troubleshooting of chiller 1 will be done next week.
J. Kissel, J. Warner During SPI install we removed the following side-wall balance mass from the W9 side wall (see first bullet of LHO:90558): Plate Mass [lbs.] Mass [kg] QTY Total Mass [kg] D071200 Type 04 7.9 3.583 3 10.750 D071200 Type 01 1.1 0.499 1 0.499 D071200 Type 00 0.6 0.272 1 0.272 D071201 0.1 0.045 3 0.136 Total Mass 11.657 First attachment is a diagram to convey which side wall I'm talking about. This is inaccurate with the latest version of the ballast / balance mass inventory, D1000907-v7, which states that this side wall has only 1x Type 04 (3.583 [kg]) and a 1x Type 03 (2.041 [kg]), for a total of 5.625 [kg]; much less. Remember, from LHO:90504 that the total SPI mass is 12.599 [kg]. This *excludes* the mass of the lower ISI Shroud baffle (D2400106-v4) and the three upper HAM Table Baffles (D2600007) with all their bracketry and bolts, currently only represented only in e-drawings posted to D2400103-v6. After talking with Jim, he wants more mass in this -X / +Y corner of the table, because that's where all the new stuff is. So he wants this corner "over" or "heavy" (because the new stuff must be in a fixed position) so that he can adjust the *opposite* corner of ballast mass (which has more open table and side wall access and thus is adjustable). As such, he says "put all the at 11.657 [kg] back on the corner. So we will! Second attachment is a picture of the wall mass arrangement prior to us removing it taken on 2026-06-09.
I ran the OPLEV charge measurements this morning for the both of the ETMs.
For ETMX the charge is still trending towards zero on all DOF/quadrants, LR and UR have the highest charge around ~60-70 V but they're trending down.
For ETMY the charge seems stable at or just above +50 V on most DOF/quadrants. The error bars are pretty big for EY, but the measurements all had great coherences. In each individual measurement none of the errors look very large except for LR which is broken/not used.
(Jordan, Travis, Jake, Owen, Gerardo)
After taking some RGA scans of CP1, and pushing nitrogen gas through the cryotrap (we injected nitrogen gas at the top sensor line for about 10 minutes), then we started the cooldown, or did we? First, we opened the "bypass" valve (fully open) to measure the number of turns to guesstimate a less than 10% open valve, per procedure E960127. Then we opened the bottom draw valve to release LN2 out of the dewar. We opened both valves around 2:00 pm, bottom draw fully open and bypass valve only 10%, but by 7:40 pm local time we terminated the cooldown, we didn't want to risk for something to go array overnight.
We did not see a sign that the cryotrap was getting nitrogen, nothing on the exhaust (the exhaust pressure remained the same), nothing on the cryotrap level (remained at zero), pressure internal to the cryotrap remain level, and the consumption remained level at the dewar for CP1. We are going to look more into this Thursday.
(Jordan V., Travis S., Gerardo M.)
CP1 cooldown re-start, apparently one or both of the valves did not respond as they should have, either the "bottom draw" and the "bypass" valves did not open yesterday, or one of them did not open, do not know which.
This morning I opened the valves in a different manner, and paid close attention to their behavior, the "bottom draw" valve made a small pop as I opened it, so I closed the valve and then opened it again, I had to do that about 3 different times, the last time there was no pop, it seems as if the valve was letting go of the sealing component, on the third attempt I was able to hear the LN2 rush thru. Same for the "bypass" valve, opened it with care and paid attention to the sounds it made, no pops noted, but to make sure I opened and closed the valve 3 times, never opening it more than 1/2 turn. Then set it the same way as yesterday, the guestimate of 10% open, about 0.8 turns. Then I was able to hear the nitrogen gas out of the exhaust line. Left CP1 and went to check on the progress via MEDM screens and plots. Soon we had the first numbers on the pump level % full, we started with a very tiny number but little by little the cryotrap started to fill. Because of the experience of with the above mentioned valves I decided to actuate early the LLCV, but only opening it up to 2%, eventually with time and two cell phones I was able to note that the LLCV was indeed actuating good. Soon the 85% came along and it was time to hand over the controls to the PID, which it did not have any issues, well 1 issue, the 15% output low limit was to high, the PID railed, so I lowered it to 10%, this number will be assessed on the upcoming days to see if we leave it or not. We left the RGA scanning during and post the cryotrap cooldown.
Vacuum pressure in CP1 has dropped and currently we are at 3.8x10-09 Torr, from about 4.0x10-08 Torr this morning.
The consumption of LN2 was good, the dewar dropped about 2.24% to fill the cryotrap.
The turbo pump continues to pump on the system and it will until we reach at least 1.0x10-09 Torr or better.
We were adding a new filter module for annular CO2 heating to the TCS simulation model. Both filter modules are added to the substrate diopter calculation, but their inputs are switched using the CO2 mask. For now the same filter as for central heating has been loaded. This needs to be updated.
The calibration factors are -11uD/W and -13uD/W for ITMX and ITMY annular heating, respectively, see alog 66617.
We also noticed that the filter module name for H1:TCS-SIM_ITMX_SUB_DEFOCUS_FULL_SINGLE_PASS was too long and shortened it to H1:TCS-SIM_ITMX_SUB_DEFOCUS_FULL_SGL_PASS. However, we added the following EPICS channels H1:TCS-SIM_ITMX_SUB_DEFOCUS_FULL_SINGLE_PASS_OUTPUT and H1:TCS-SIM_ITMX_SUB_DEFOCUS_FULL_SINGLE_OUT16 back in so medm screens and trend will stay unchanged.
The following 2 lines have been added to the CDS_CA_COPY guardian list:
I used the CO2 profile measurement in aLOG 65382 to estimate the average radial CO2 intensity profile on the CP. The spatial scale on the CP was determined by using the 16 axial nodes in the HWS measurement in aLOG 65436 as fiducials to estimate the diameter on the CP.
From this, I ended up with an average radial profile for intensity for the annular CO2 laser - which, when normalized to deliver 1W, looks like the following.

I put this into a 2D axially symmetric model of the coupled ITM+CP system in COMSOL and worked out the transient response for the defocus. The response looks like the following:

From this response, we estimate the steady-state defocus and can fit a weighted sum of exponential decays to the normalized response. The fitted time constants, tau, correspond to the poles in the transient response function, where the poles are 1/(tau*2*pi).
The COMSOL model predicts peak after about 2-3 hours and a slow decrease over 24 hours to settle around -9uD/W.
Steady state defocus = -8.91uD/W
amplitude = [-1.571, -0.846, 1.417]
tau = [798.6s, 7756.6s, 26491.9s]
poles = [199.30uHz, 20.52uHz, 6.01uHz]
Normalized response = 1 + sum[ amp(ii)*exp(-t/tau(ii) ) ]
The transient output of the annulus can be estimate by a weighted sum three single-pole LPF, where the weighting for each pole is just the "a" values given in the previous aLOG.
These are single-pass values.
Attaching the analysis used.
Note on the absolute power level for this simulation: it's a little unclear how to normalize the amount of power in the CO2 intensity profile. There is the power on the thermopile to consider, the aperture of the CP to consider (some power is lost as it falls off the edge of the CP) and the missing bits of the intensity on the paper on the camera. This will result in a calibration error in the magnitude in the simulation - the time constants should be relatively unaffected though.
Translated this into the following filter function: zpk([2.837e-05;2.691e-06],[6.01e-06;0.0001993;2.052e-05],1,"n")
Attached is the filter step response as given by foton in blue (red is the previsouly loaded filter.
New filters loaded into H1:TCS-SIM_ITMX_SUB_DEFOCUS_CO2_AN and H1:TCS-SIM_ITMY_SUB_DEFOCUS_CO2_AN at FM6.
TJ, Camilla, Evan
With some difficulty I was able to extract the annular mask design data from D1201477. One can piece together that the CO2 beam size at the mask is nominally 10 mm and is more or less at a waist (LHO:76715), which is consistent with some crude finesse beam propagation based on T2200035, although one has to fudge the location of the 1.2 mm beam waist out of the CO2 laser. Aidan measured 10 mm at Livingston, too (LLO:14419).
The first attachment is a simulation of the intensity pattern immediately after the mask, with the nominal 22.5° horizontal angle applied to the mask. The in-air CO2X table is supposed to image the mask onto the CP with about a 23× magnification factor, so the aperture (imaged to the same plane of the mask) is indicated too.
The second attachment computes the radial intensity function and projects it to the CP, with the CP aperture again indicated. This plot is vaguely similar to Aidan's inferred intensity plot above (his horizontal units are presumably supposed to be meters, not millimeters). These intensity patterns are very different from the final design document and from the TCS overview paper from 2016, where the goal there was to cut off the intensity above 10 cm or so at the CP.