Displaying reports 161-180 of 89226.Go to page Start 5 6 7 8 9 10 11 12 13 End
Reports until 16:30, Friday 28 August 2026
LHO General
thomas.shaffer@LIGO.ORG - posted 16:30, Friday 28 August 2026 (91723)
Ops Day Shift End

TITLE: 08/28 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: Corey
SHIFT SUMMARY:

LOG:

Start Time System Name Location Lazer_Haz Task Time End
17:02 SEI, CC Mitch Ends n FAMIS HEPI checks and CC checks at EX 17:46
17:07 PEM Robert EX n Grounding investigation 18:13
22:36 PEM Robert EX n Grounding investigation 00:36
22:39 - Mike, Daniel, Tourist x2 LVEA Y Tour 00:09
22:52 SEI Jim, Shoshana CER y Checking on CRS damping signal 23:04
23:19 SUS Sheila, Mark EY n Checking on ESD 00:19
H1 SUS (ISC)
oli.patane@LIGO.ORG - posted 14:28, Friday 28 August 2026 (91728)
BBSS vs BSFM DOF noise measurements

I've made plots comparing the M1 stage BSFM BOSEM noise to the BBSS QOSEM noise to see how much better we are. This is similar to the plots TJ O made in 91466. During the time the BBSS data was taken from, we did have the LED sum current feedback switched on, but comparing our BBSS QOSEM noise to the two QOSEM noise floor plots (taken from G2501105 slide 29), it really looks like we are currently being limited by the constant LED current, as if we didn't have the feedback on at all.

We know the sum current feedback loops are doing something because when we first turned them on, they adjusted the sum counts on two of the osems that were reading too high of counts, but based on these plots it doesn't look like they're doing much? TJ O and I will talk with Tom to investigate more.

Results:
/ligo/svncommon/SusSVN/sus/trunk/BBSS/H1/BS/SAGM1/Results/2026-07_OLG_tfs_4_BSFMvsBBSS/allDampRegressCompare_H1SUSBSFMvsBBSS_M1_NoiseComparison_1435435038vs1469227619-1200.pdf
r13134

Loop suppression used to divide out:
BBSS: /ligo/svncommon/SusSVN/sus/trunk/BBSS/H1/BS/SAGM1/Data/Data/2026-07_OLG_tfs_4_BSFMvsBBSS/2026-07_H1SUSBS_M1_CDBIOState1_WhiteNoise_{L,T,V,R,P,Y}_0p02to50Hz_OLGTF.xml
BSFM: /ligo/svncommon/SusSVN/sus/trunk/BSFM/H1/BS/SAGM1/Data/2023-07-18_1740_H1SUSBS_M1_CDBIOState_1_OLDampingON_WhiteNoise_{L,T,V,R,P,Y}_0p01to50Hz_OpenLoopGainTF.xml

Non-image files attached to this report
H1 ISC
thomas.shaffer@LIGO.ORG - posted 14:12, Friday 28 August 2026 (91727)
Clipping scan with PR3 in single bounce

In an attempt to look for obvious clipping in the PRC, I scanned around +/-150 urads from our PR3 alignment while in single bounce and with SR2 following along to keep AS_C centered. This was a painfully slow process as I would move PR3 until SRC2 would near its limiters, wait for it to settle down, then move again. I ended up bumped the SRC2 gains way up to help speed this up, but it only helped a bit. 

I saw no signs of clipping in the +/-150 range, so I continued in yaw until AS_C nsum finally started to decrease. This didn't happen until +500urad in Y from our starting point. We stopped here to run some more pertinent tests. I reverted all alignments back to before this test.

Images attached to this report
H1 AOS
louis.dartez@LIGO.ORG - posted 13:00, Friday 28 August 2026 (91726)
PRM beam spot position
At Sheila's suggestion this morning I measured the beam spot position on PRM in PRMI. The drivealign gains that reduce the A2L coupling are P:0.38, Y:0.81. I used the same procedure as in 91701. This corresponds to an offset from center of 0.713 mm in PIT and 1.52 mm in YAW.

Images attached to this report
H1 AOS
louis.dartez@LIGO.ORG - posted 11:49, Friday 28 August 2026 (91724)
MICH and PRCL OLG in PRMI
Here are MICH and PRCL OLGs from today while in PRMI.
Images attached to this report
LHO General
thomas.shaffer@LIGO.ORG - posted 07:34, Friday 28 August 2026 (91720)
Ops Day Shift Start

TITLE: 08/28 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
CURRENT ENVIRONMENT:
    SEI_ENV state: MAINTENANCE
    Wind: 7mph Gusts, 3mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.10 μm/s 
QUICK SUMMARY: No alarms, calm environment. The EX VEA temperature has been moving around quite a bit the last few days. Looks like this was from the cleanroom being turned on.

Images attached to this report
LHO General
corey.gray@LIGO.ORG - posted 18:11, Thursday 27 August 2026 (91719)
Thurs EVE Ops Summary

TITLE: 08/27 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:

Commissoiners (Elenna, Louis, Camilla) were working on H1.  Once they were done, I let Jim know so he could run SPI injections on HAM2 & HAM3 over night.

LOG:

H1 AOS
louis.dartez@LIGO.ORG - posted 17:33, Thursday 27 August 2026 (91702)
pr2 spot move to determine how close we are to O4 beamspot position on PR2
[Elenna, Sheila, Louis, Keita, + input from others in CR]

This log is for work done yesterday August 26, 2026.

Yesterday we set out to move the beam spot position on PR2 with a dither line to determine whether the current beam spot position is the same as it was during O4. This test is part of the same line of investigation mentioned in 91701. The idea is that if the beam is still at the O4 spot position on PR2 then moving the beam in pit or yaw should result in higher A2L coupling than you would get at the nominal position. This test was done in PRMI. 

We had to pause midway and rethink the execution of this test because we kept losing PRMI lock. 

We used the guardian state PR2_SPOT_MOVE to move the beam spot position on PR2 while monitoring the A2L coupling using a dither on PR2's M3 DITHER bank (8.125 Hz, same as before). The guardian state lets us move the PR3 sliders and it will move IM4 and PR2 to compensate. 

Since this move has downstream effects in the POP path, Elenna held the output on POPAIR RF18_I, which provides the trigger signal for PRCL and MICH. We started off going in the +Yaw direction in steps of 0.3 urad using the PR3 slider. We noticed that each move would kick the MICH and PRCL loops. I was only able to move about 2 urad before losing PRMI. This was repeatable: I lost lock after moving 2.7 urad (yaw slider value -234.0) and later after only moving 2.4 urad (PR3 slider value -234.3). The nominal slider values for PR3 at the start of this test is Yaw: -236.7, Pit:-142.7. 

We considered that we could be falling off of the REFLAIR diode during these moves. REFLAIR_A_RF9_I and REFLAIR_A_RF45_Q are used as the input signals for PRCL and MICH, respectively. Interestingly, we noted that as we continued to move in the +yaw direction the demod diodes would see a small kick while the DC signal (REFLAIR_A_LF) was increasing (ndscope screenshot). This was repeatable and doesn't make sense to me right now. Meanwhile, we were losing power on POPAIR 18 and 90 (not surprising) and on POPX (not surprising). We turned off the DC centering for POPX because PM1 starts to rail pretty quickly if you don't. 

After losing lock a couple of times Elenna suspected that something weird might be happening with the MICH and/or PRCL loops. So she measured the OLGs while I moved the beam spot position on PR2. I've uploaded DTT screenshots of the MICH OLG and PRCL OLG. Both of these OLGs were taken after moving and pausing 2.1 urad away from the nominal position on the PR3 sliders (PR3 slider yaw: -234.6). 

The PRCL OLG looks to have experienced a loss in gain. We tried compensating by increasing the gain, but this didn't help avoid losing lock. The MICH OLG measurement showed some more egregious changes that are not fully understood at the moment. It is not immediately clear to us how moving the spot position on PR2 would result in the OLG changing like this. 

In any case, we think we want to be able to continue moving the spot by moving PR3 in +yaw because the A2L coupling was getting better as we did (dtt_pr2_spot_a2l.png. So it would be nice to be able to repeat this and move further without losing PRMI. 

The DTT used for the A2L coupling measurement lives in my home directory under Templates/pr2_spot_move_a2l.xml. The 8.125 Hz line was injected using awggui.
Images attached to this report
H1 General (OpsInfo)
anthony.sanchez@LIGO.ORG - posted 16:56, Thursday 27 August 2026 (91712)
Thurday Day OPS Report & Manual Initial Alignment Notes.

TITLE: 08/27 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: Corey
SHIFT SUMMARY:

Elenna's current Manual Initial Alignment steps: 
Get ALS Gaurdians for Y arm to ETMS WFS OFFLOADED [13], (except X arm is messed up so only for Y arm currently). ETMX was left in Locking [-23] and ETMX and TMSX were touched up to maximixe the ALS-C_TRX. 
Then once they are locked and stable. unlock them.
COMM Beatnote was 6.5 
DIFF was -9 ish
Then use ALIGN_IFO to start a manual Initial alignment. But we cannot use ASC at all because the diodes need to be "rephased" something about the sidebands are all different now.
This means we take ALign IFO to  AQUIRE_XARM_IR[11]. Once that is done.
We go to Aquire PRX.  Moved PRM to to maximize ASC-AS_A_DC_NSUM.
Then went to Prep_for_mitch[41] > mitch dark locked and moved the beam splitter while watching the AS Air cam for maximum darkness and a ring around a center dot.
SR2 Align[58] was ran and automatically worked. Which uses a QPD and does not need sidebands.
Moving SRM while in SRY_LOCKED[62] to maximize ASC_AS_A_DC_NSUM. 
AS_CENTERING[77] also ran with out intervention.
Then take the power back down to 2 watts.
We are ready to try locking!!!

The Verbal Alrams did a weird thing today. The VAC Alarms sounded off for PT-134  , PT152, and PT-180... 
I called Travis over to come check it out and he said everything looks fine. 
PT-134 is tripped due to someone's phone tripped it a while ago.
PT-152 is correctly telling us the pressure because that sensor is indeed at atmospheric pressure between HAM 5 and 7.
And PT-180 was replaced on tuesday but it's new channel name is PT-180_MOD2 now instead of MOD1.
Which brings up the great point that the Verbal's VAC alarm channels need to be updated.

PEM note: 
A garbage truck slammed a garbage dumpster on the ground around 22:49 UTC today. It was felt in the ground by multiple staff's highly calibrated foot seismometer.

Craning over X arm never happened because they ran out of time. Even if it is mentioned in the Reservation system table below.


LOG: 

Start Time System Name Location Lazer_Haz Task Time End
14:39 FAC Kim OpticsLab N Technical cleaning 14:52
14:53 FAC Kim End X N Technical cleaning & Resupply 16:06
15:59 EE Fil LVEA HAM6 yes Checking out a chassis. 16:22
16:08 EE Richard LVEA HAM6 yes Helping Fil hold his tools. 16:22
16:19 ISC Sheila & Elenna LVEA ISCT1 yes Alignment of PD's on ISCT1 17:09
17:21 EE Fil & Sheila LVEA HAM3 y Checking HAM3 Flange cabling 17:51
17:31 DetEngr Betsy LVEA HAM3 y Checking flange cabling for pico motor 17:50
17:36 PEM Robert End X No Working on grounding. 20:11
17:38 TCS Camilla CHeTA Lab N Grabbing parts 17:51
18:12 ISC Sheila, Elenna LVEA Y ISCT1 19:00
18:15 FAC Kim LVEA - Garb checks 19:15
19:05 VAC Jordan Travis LVEA X arm y Craning  19:51
19:06 CDS Dave Remote n DAQ restarts. Now Waiting on the FWs to agree ~21:00 UTC 21:08
20:55 ISC Camilla & Mitchel LVEA Arms YES Replacing Viewport covers with boxes on the Arms need Gatevalves. Mitchel out first. 22:25
20:56 ISC Ryan  & Sheila LVEA ISCT1 yes ISCT1 alignment. 21:36
21:10 Safety Richard LVEA y Taking measurements. 21:25
23:06 PEM Robert EX - Grounding studies 02:06

 

 

H1 TCS
camilla.compton@LIGO.ORG - posted 16:52, Thursday 27 August 2026 (91716)
Fit Check of Modified CHETA camera steering mirror assembly D2500166

Mitch, Camilla, WP#13559

Tyler modified the D2500166 as it was too wide to sit next to the Oplev laser enclosure. Tyler modified: D1300702 and D1300703 so that the box is now ~0.75" offset of the center. Will add more deatils to these modifications in the DCC. 

At the X-arm adapter plate this technically fits but is close to interfering with the  op-lev laser enclosure. The 10-32 bolt next to it will want to be replaced with a button or countersunk bolt.  Photos attached: side view, below view, ruler.

At the Y-arm adapter plate this fits well. Photo attached: side view, below view, ruler.

Images attached to this report
H1 SPI
jennifer.wright@LIGO.ORG - posted 15:03, Thursday 27 August 2026 (91707)
QPDB went down in pitch slowly starting on August 17th

Jennie W, Jeff K, Jim Warner

Jeff noted the QPD B pitch alignment is off. 

As part of checking this I did some checks on the QPD alignments since Jeff re-aligned both QPDs on the 23rd July.

 

Between the 23rd and 27th July (when the shutter was closed unknowingly for a period after swapping in the permament shutter controller) QPD A was well-algined and QPD B drifted slowly down in pitch, showing some oscillation (maybe diurnal).

For context the M_M1 (located on HAM3 ISIK assembly) controls are on the left. This picomotor aligns the beam onto QPDA which sits on the HAM2 ISIJ assembly. The picomotor motor X and Y position channels H1:SYS-MOTION_C_PICO_G_MOTOR_5_X_POSITION and H1:SYS-MOTION_C_PICO_G_MOTOR_5_Y_POSITION give the relative change in the X and Y position of the mirror. Similarly on the right are the pitch and yaw of QPD B which is located on ISIK assembly in HAM3 and can be aligned using the M_C1 pico controlled mirror located in the ISIJ assembly in HAM2. This has the X and Y position readouts H1:SYS-MOTION_C_PICO_B_MOTOR_7_X_POSITION and H1:SYS-MOTION_C_PICO_B_MOTOR_7_Y_POSITION.

 

The channels in the image show we did not re-align the picomotors in this period (I also checked the M_B4 and M_M2 picomotors on ISIK). The temperature does not seem to change appreciably during this time and the HAM2/3 ISI and HEPI stayed isolated during this period also.

 

The vacuum pressure gauge I chose maybe could correlate with the beam position going down so maybe this was some bouyancy effect?

Seems unlikely though since by July 23rd the gauge was already at 6e-7 torr which is well within high vacuum pressure region.


I also took a trend of the time during which the shutter was closed here. This can be used for dark noise measurements.


Looking at the trend between when we unshuttered the laser on August 11th and today, There was some kind of drop in QPD B pitch from -0.1 to -0.4 that seemed to start on August 17th. Not sure why this happened as doesn't seem to correlate with ISIs, HEPI or picomotor changes.

We will probably need to retake any measurements we did of HAM2 after August 11th.


I have now recentred both QPD A and B using M_M1 and M_C1 respectively.

Images attached to this report
H1 ISC
sheila.dwyer@LIGO.ORG - posted 14:57, Thursday 27 August 2026 (91715)
ISCT1 POP + REFL periscope moved

Sheila, Ryan Short, Camilla

We moved the periscope on ISCT1, about 1 inch in the +X direction.   This leaves the refl beam on the -Y side of it's top periscope mirror, and the POP beam on the +X side, but neither of them should be clipping.  The beam is not well centered on the refl bottom periscope mirror, but we did not fix this, as we'd have to move everything in the refl air path to fix it.  

Periscope position before we moved it

POP beam on top periscope mirror

REFL beam on top periscope mirror

 Note, we moved the pop top periscope mirror in the +X direction in 91481, Keita put some photos of how the beams were left after in chamber work 89761

Images attached to this report
H1 ISC
elenna.capote@LIGO.ORG - posted 13:23, Thursday 27 August 2026 - last comment - 16:15, Thursday 27 August 2026(91696)
PRMI buildup

Comparing the buildup of H1:LSC-POPAIR_B_RF18_I_ERR_DQ between Nov 2025, at GPS time 1447346785, POPAIR RF18 I has a maximum of 168 counts. Today, while locked at PRMI with the buildups maximized, the same channel has a maximum of 62. This means that we are missing more than 70% of the power along this path.

We have previous trends from Ryan S and Ryan C, but they might have trended a normalized channel, which is confusing because the input power and the way we power normalize these channels has changed. Comparing the ERR channels is more straightforward.

POP A LF maximum was about 88 and now it is about 32.

Referencing these alogs: 9162291528

Keita has also confirmed that the whitening gains and digital gains of POPAIR RF18 and the modulation depth settings are all as they should be between these two times.

***

I also looked up a MICH dark time since we are getting very confused about what power we actually are or are not missing. Here is a table summary:

MICH DARK: 1432426657, ALIGN IFO STATE 43, May 28 2025

Channel Value Units Notes Value Now Ratio Now/Then
IMC-IM4_TRANS_NSUM_OUT16 9.42 W   9.22 W 0.98
LSC-POP_A_LF_OUT16 4.5 (max) uW maximum power, BS was being moved by hand during this time (checked aligment sliders) 3.83 uW 0.85
LSC-POPAIR_B_LF_OUT16 1.04 ct   0.65 ct 0.63
ASC-POP_X_DC_NSUM_OUT16 0.28 ct I multipled by the normalization factor of 407 so this value is comparable to now, no PM1 centering engaged I think, but segments look well-balanced so the beam was close to center of diode 3.02 ct 10.8

Here is a table summary of the PRMI time:

PRMI locked: 1447346762, ISC_LOCK state 52, Nov 16 2025

Channel Value Units Notes Value Now Ratio Now/Then
IMC-IM4_TRANS_NSUM_OUT16 1.84 W   1.83 W 0.99
LSC-POP_A_LF_OUT16 88 uW   30 uW 0.34
LSC-POPAIR_B_LF_OUT16 17.8 ct average value 5.5 ct 0.30
ASC-POP_X_DC_NSUM_OUT16 35.4 ct I multipled by the normalization factor of 407 so this value is comparable to now, PM1 centering was engaged 129 ct 3.6
LSC-POPAIR_B_RF18_I_ER_DQ 167 ct average value 52 ct 0.31

Conclusion:

Sheila and I think that the MICH dark numbers actually hang together. This is further bolstered by the fact that we can only make marginal improvements to the alignment onto POP diodes with picoing the HAM3 pico. We think the larger discrepancy in the popair diode in MICH DARK can be accounted for by the fact that the beam is close to the edge of the periscope mirror. We also manage to make the ALS alignment worse with the pico. Therefore, we think the pico alignment is fine.

However, the PRMI numbers clearly indicate a problem, but this points to PRC clipping instead.

Images attached to this report
Comments related to this report
camilla.compton@LIGO.ORG - 16:15, Thursday 27 August 2026 (91717)

Adding two more columns and a row to Elenna's table showing that on July 23rd afternoon, we were at MICH DARK locked with LSC-POP_A_LF_OUT16 at 7uW, plot. 

Channel Value O4 May 28 2025 00:15UTC plot Units Value Now plot

Ratio Now/O4

Value 23 July 2026 23:45UTC plot Ratio July/O4
IMC-IM4_TRANS_NSUM_OUT16 9.42 W 9.22 W 0.98 8.68 W 0.92
LSC-POP_A_LF_OUT16 4.5 (max) uW 3.83 uW 0.85 7.2 (max) 1.6
LSC-POPAIR_B_LF_OUT_DQ 1.04 ct 0.65 ct 0.63 0.84 ct 0.80
LSC-POPAIR_A_LF_OUT_DQ 1.85       0  

 Interesting to note that the May time we were still recovering from the HAM1 vent. e.g. 84648

Images attached to this comment
H1 CDS
david.barker@LIGO.ORG - posted 12:48, Thursday 27 August 2026 (91710)
Restart of h1spih23 model and DAQ

WP13564 SPI Added QPD Filter modules and DQ chans

Jeff, Jennie, Jonathan, Dave:

We installed the new h1spih23 model at 12:15. The DAQ was restarted soon afterwards. 0-leg 12:16 and 1-leg 12:20.

 

H1 SPI
jeffrey.kissel@LIGO.ORG - posted 12:16, Thursday 27 August 2026 (91709)
Fixed links to SPI_LIBRARY in h1spih23 model; hetdemod.mdl now integrated into SPI_LIBRARY and correctly referenced in HET_IFO_SPD
J. Kissel, J. Wright, D. Barker

Dave tried compiling the h1spih23 model in prep to install my changes described in LHO:91705, and found there were no changes. Upon close inspection, the top-level model,
    /opt/rtcds/userapps/release/spi/h1/models/
        h1spih23.mdl
had it's link to the primary library "HJK" block in the 
    /opt/rtcds/userapps/release/spi/common/models/
        SPI_LIBRARY.mdl
and the link to Jennie's 
    /opt/rtcds/userapps/release/spi/common/models/
        hetdemod2.mdl
library part was also broken in the "HET_IFO_SPD" block of the SPI_LIBRARY. 

We believe these links got busted up when Jennie created and installed the hetdemod2.mdl part which flipped the assignment of SIN / COS to I / Q and removed the phase rotator block on Friday Aug 14 2026 (LHO:91543).

I've 
   (1) moved the block that was inside the hetdemod2.mdl file in to the SPI library, breaking the link to the hetdemod2.mdl library in the process so it's it's own fresh new library block solely within SPI_LIBRARY.mdl.
   (2) deleted the broken link to the hetdemod2.mdl version of the demod block in the HET_IFO_SPD block, and replaced it with the version now in the SPI_LIBRARY.mdl
   (3) deleted the instantiation of the top level library block HJK from the top level h1spih23 model, and then brought in a fresh copy from the SPI_LIBRARY.mdl (renaming it to H23 of course).
   (4) removed hetdemod.mdl from the svn so there's no longer any confusion as to where this block comes from, and the SPI_LIBRARY.mdl returns to being self-contained.
i.e. I resolved all of these broken links, and committed everything anew to the svn with all links resolved, so it should have no functional change to the demodulation fix. 

Here's the svn commit log:

Committed SPI_LIBRARY fix with HETDEMOD correctly linked to HET_IFO_SPD, so that it's all self-contained and functional.
    /opt/rtcds/userapps/release/spi/common/models/
        SPI_LIBRARY.mdl
        r35942.

Deleted hetdemod.mdl, since it's now in the SPI_LIBRARY.
        [[no longer in the svn]]
        r35943.

Commited new top level model with the H23 block newly refreshed as a link to the HJK block in the SPI_LIBRARY.mdl.
    /opt/rtcds/userapps/release/spi/h1/models/
        h1spih23.mdl
        r35944.

Committed bug fix to DAQ Channel list in SPI_LIBRARY found during test compile (that wasn't found earlier because the library link to the HJK block was broken).
    /opt/rtcds/userapps/release/spi/common/models/
        SPI_LIBRARY.mdl
        35945.

Screenshot #1 shows how/where the HETDEMOD block now is integrated into the SPI_LIBRARY structure.
Screenshot #2 shows that the link to the SPI_LIBRARY HJK part is now alive and well in the h1spih23.mdl
Images attached to this report
H1 ISC (SUS)
elenna.capote@LIGO.ORG - posted 12:10, Wednesday 19 August 2026 - last comment - 14:36, Thursday 27 August 2026(91602)
Successful commission of BS M3 feedback for MICH

Louis and I immediately started where we left off yesterday with BS M3 commissioning. Louis copied over the LLO filter design that sets up the BS feedback with a 7 Hz crossover between M2 and M3, 82200 (thanks LLO for doing the heavy lifting here!).

I copied these filters into my matlab model so we could confirm we understand what it is doing. This plot shows the modeled feedback with the locking and drivealign filters applied. The LLO design is applied to M2 and M3, such that the crossover is roughly 7 Hz as expected. I applied our current M1 offloading scheme, and the M1/M2 crossover is still 30 mHz.

This looks good to us, so we proceeded to copy over the filters to the BS sus banks. I first locked MICH dark using the old feedback design without the lowpass filters so we had much more phase. This provides a reference for us to make sure we do the switchover correctly.

Louis and I engaged the correct filters in ISCINF M3 L, M3 lock L, M3 drivealign L2L and M2 lock L. Here is a screenshot of the old M2 filter design, and here is a screenshot of the settings we used to test the new feedback. I want to note that one difference is I found that we need a gain of -1 overall in BS M3 drivealign to get the phase correct.

I did touch up the MICH alignment before locking, since the arm team is working on aligning the arms now that gate valves are open (spoiler alert).

We successfully locked MICH dark, no issues! I measured the MICH olg again, and saw that we were almost exactly where we wanted to be in the gain, and the phase is a little different but not drastically so.

Masayuki noted in a previous alog that the MICH gain is a bit low, it would be better to have a 10 Hz UGF. Therefore, I bumped up the gain by a factor of 3 and remeasured. Looks good! This plot compares all three MICH dark olgs.

Louis has updated the ALIGN_IFO guardian with these new settings and is working through ISC_DRMI. In addition to the filters in the BS sus, we are updated the MICH dark and MICH bright gains to be 3x higher (so plus/minus 7200 instead of 2400).

As a note, ALIGN IFO does not use M1 feedback, we expect to test this when we lock PRMI/DRMI. However, I don't predict any issues, as the crossover should still be the same.

I have accepted new settings in the SDF as well, screenshot.

Below are the foton strings that we copied over:

BS_M2_LOCK_L

FM1: zpk([-4.398229715026552+i*5.654866777052986;-4.398229715026552-i*5.654866777052986], [-344.8589087698574+i*562.4185982606715;-344.8589087698574-i*562.4185982606715; -2513.274122871833],21314144.89497595)

FM2: zpk([0+i*754.0107241782374;0-i*754.0107241782374], [-114.2660735869546+i*205.9572881820654;-114.2660735869546-i*205.9572881820654], 0.09757621338967941)

FM4: zpk([],[-50.26548245743591],50.2654824574367)

BS_M3_DRIVEALIGN

FM1: zpk([],[],298.5382618917961)

FM2: zpk([0],[-50.26548245743591],1.003192)

FM3: zpk([0+i*1.232546515546514;0-i*1.232546515546514;0+i*2.235392999096904;0-i*2.235392999096904], [-0.1284339970099986+i*2.497529352797497;-0.1284339970099986-i*2.497529352797497; -1.722920509773179+i*2.801700651589354;-1.722920509773179-i*2.801700651589354], 0.9928357135551715)

FM10: zpk([0+i*2021.046153045786;0-i*2021.046153045786;0+i*4405.443648178848;0-i*4405.443648178848], [-457.9243327239894+i*601.6182012226579;-457.9243327239894-i*601.6182012226579; -132.3004333168722-i*1248.734723957288;-132.300433316874+i*1248.734723957288], 0.01013394010636035)

Images attached to this report
Comments related to this report
elenna.capote@LIGO.ORG - 14:36, Thursday 27 August 2026 (91713)

I measured the M2/M3 crossover while locking MICH. Looks like it's about 6 Hz. with 37 deg of phase.

Images attached to this comment
H1 ISC
sheila.dwyer@LIGO.ORG - posted 12:41, Thursday 23 July 2026 - last comment - 15:56, Thursday 27 August 2026(91211)
PRMI checks
  POP A LF POPAIR B LF REFLAIR A LF MICH IN1 (REFLAIR A 45 Q) PRCL IN1 (REFLAIR A 9I) POPAIR B RF18
PRMI O4 200-400 200 2-10 +/-6000 +/-600 80-100
PRMI now 100 6 2.5-4 +/-20 +/-100 5
PRX O4 0.5          
PRX now 0.5          
Images attached to this report
Comments related to this report
elenna.capote@LIGO.ORG - 16:52, Thursday 23 July 2026 (91224)

In order to fix this alignment issue, Sheila, Keita, and I had some different ideas, and it was hard to determine the best path.

Here is the one we tried:

  • Sheila found the alignment slider positions from O4, and noticed that PR3 and ITMX pitch are bother very different now versus then. So is ITMX yaw.
  • I suggested we use PR2 spot move to move the PR3-PR2 axis, and see if we can follow with PM1 to better align the beam onto POP LF. Then, we can adjust ITMX and beamsplitter.
  • Moving PR3 pitch to the O4 alignment causes the beam to fall off POP X, and it does not go back onto POP A LF. I tried moving the PM1 slider to the "good for POP A LF" setting above, but that does not bring the beam back.
  • When in the "good for POP X" setting, PM1 saturates both LL and UR, so it is not obvious if the problem is pitch or yaw.
  • I tried moving ITMX around, and PR3 as well, but ITMX moves cause us to fall off ISCT1 refl camera, and PR3 moves do not bring us back on that camera.
  • Overall, Keita and I agree that we need to think more about this.

This is the state of the alignment as I am leaving it tonight:

  • PM1 is in the "good for POP A LF" state, which means it is not saturating, and there is no beam on POP X
  • PR3 alignment (as well as the corresponding IM4, PR2 and PRM alignment)  is reverted to where it was before I started this particular adventurew
  • ITMX alignment and BS alignment are also reverted.

Screenshot attached of all these settings.

Earlier we did some OMC scans and got weird results. We tracked this down to an incorrect DCPD whitening setting. Keita fixed it, and we reran the scans, the carrier peak heights are now correct compared to the blue reference.

Oli tracked down the problem with MC2. All crossovers are fine now and the mode cleaner locks with normal gain settings. They will alog the details.

Images attached to this comment
elenna.capote@LIGO.ORG - 12:44, Thursday 23 July 2026 (91216)

Centering on POP X DC with PM1 pulls beam off POP A LF

Right now we have an alignment that can bring the beam to both POP A in vac and to the POPAIR diodes on ISCT1 in a PRMI, or with either PRX or MICH locked.

However, the beam was very far off of POP X WFS DC, suggesting PM1 is not well-aligned. I spent a bunch of time trying to move PM1 while keeping the beam on POP A LF and improving the POP X alignment while we are locked on MICH DARK, which brings a lot of light to the POP port.

I gave up on keeping the beam on POP A and instead did much larger moves of PM1, which brought the beam to all four segments of POP X DC and increased the POP X sum. I finally got the beam well enough aligned that I could engage the DC6 centering loop, which aligns PM1 to POP X.

We are now well centered on POP X, but have lost the beam on POP A. PM1 is also unfortunately close to saturation at this alignment.

Here are the PM1 slider values that put the beam on POP X:

P: -868.5, Y: -2076.5

Here are the PM1 slider values that put the beam on POP A LF:

P: 213.5, Y: -258.5

Assuming the sliders have a decent calibration to urad, this is a 1 mrad difference in pitch and 1.8 mrad difference in yaw.

Images attached to this comment
camilla.compton@LIGO.ORG - 15:56, Thursday 27 August 2026 (91718)

The afternoon of this alog, we had H1:LSC-POP_A_LF_OUT_DQ at 7uW, see attached plot.

Images attached to this comment
H1 SEI (SEI)
shoshana.apple@LIGO.ORG - posted 18:31, Wednesday 01 July 2026 - last comment - 09:24, Friday 28 August 2026(90851)
CRS Installed on HAM3

[Jim, Shoshana]

Yesterday when I went to put the cover on the CRS to get it ready to move to the clean area right next to HAM3, I noticed one of the flexures (SN 15) was broken [picture attached]. It's unclear how this flexure broke as it had been locked since last Wednesday (?), and it is strange that only one flexure broke.

We decided that it would be better to install a new pair of flexures and re-suspend next to the chamber rather than in the temporary clean room to reduce the risk of them breaking again. So today we wheeled the table the CRS is on to the space next to HAM3 and I re-suspended the CRS there and roughly balanced it.

Following the procedure outlined in E2600210 and work permit 13356,  we moved the CRS to the table and lined everything up so that the CRS baseplate can be bolted directly to the table in one spot.

We installed the fiber feedthrough, and dealt with all the cabling (fiber and DB25) that required Jim to be physically inside the chamber and we'll install the rest of the cable clamps which we can reach from outside the chamber tomorrow and finish connecting all the cables and dog clamping the CRS down (hopefully)

Comments related to this report
shoshana.apple@LIGO.ORG - 09:25, Thursday 02 July 2026 (90874)

Attaching pictures (which I forgot to do last night)

Images attached to this comment
brian.lantz@LIGO.ORG - 09:10, Friday 03 July 2026 (90892)EPO

Congratulations on getting the CRS onto HAM3! I'm tagging EPO

Looking forward to seeing it running

shoshana.apple@LIGO.ORG - 09:24, Friday 28 August 2026 (91721)
Images attached to this comment
H1 PEM (DetChar, PEM)
samantha.callos@LIGO.ORG - posted 17:10, Thursday 16 April 2026 - last comment - 14:40, Thursday 27 August 2026(89929)
PEM November 2025 Injection Coupling Analysis Complete

Samantha Callos, Genevieve Connolly, Robert Schofield, Ryan Short, Carlos Campos

The detchar presentation summarizing the injection analysis can be found on the DCC at: https://dcc.ligo.org/LIGO-G2600768

A PDF of this report has also been attached to this alog along with a spreadsheet of the injections.

Non-image files attached to this report
Comments related to this report
samantha.callos@LIGO.ORG - 14:40, Thursday 27 August 2026 (91714)

Updated presentation to reflect the mislabeled accelerometers presented in alog 91537.

 

Non-image files attached to this comment
Displaying reports 161-180 of 89226.Go to page Start 5 6 7 8 9 10 11 12 13 End