Displaying reports 181-200 of 88272.Go to page Start 6 7 8 9 10 11 12 13 14 End
Reports until 18:19, Monday 22 June 2026
H1 SUS
thomas.roocke@LIGO.ORG - posted 18:19, Monday 22 June 2026 (90697)
BBSS Pitch Yaw Coupling Investigation - Coil Driver Chain

[Tom, Ibrahim, Oli]

Summary: The yaw / pitch coupling seen on the BBSS is not due to the the coil driver chain.

As noted in LHO alog 90665, we are seeing strong pitch yaw coupling on the BBS, when actuating via the top stage QOSEM coils. When we try and adjust the optic yaw we see a 1:5 response in pitch and vice versa. This is seen in both the QOSEM readouts, and visually using an IR beamcard on the PSL beam bouncing off the optic. 

To investigate whether the cause was electronic in nature, we went into chamber to ensure that only the F2 and F3 QOSEM coils are being driven when requesting yaw drive. We used a multimeter to measure the voltage drop across the coils, to determine whether theyre being driven or not. As we expected, only the F2 and F3 coils are being driven, with equal and opposite magnitude, when trying to drive yaw. This suggests that this coupling is not coming from the coil electronics chain, or an issue in CDS.

H1 IOO
jennifer.wright@LIGO.ORG - posted 17:54, Monday 22 June 2026 (90700)
Aligned JAC wavefront sensors

I took an opportunity while the BSC team was in the control room and opened the light pipe and aligned the WFS on IOT1 while JAC was unlocked.

This was done at 200mW.

I used the manual adjustment knobs on the picomotor mounts as the IOT1 table is not hooked up to its pciomotor controller currently.

Got both WFS A and B as close as I could using this method. NB: pitch and yaw on QPD A are swapped as the manual pitch adjuster changes the yaw degree of freedom. I need to check this in the physical wiring for the QPDs.

Images attached to this report
H1 SQZ
camilla.compton@LIGO.ORG - posted 17:02, Monday 22 June 2026 (90698)
SQZT7 Beam profiles/alignment, no progress made.

Eric, Ryan S, Camilla

Went onto SQZT7 and checked on the M^2 profiler. It needed their alignment procedure ran but as we're aren't at a set alignment we did not do this yet.

In the control room we used the ASC set up in 88777 and had to adjust the H1:SQZ-ASC_TRIGGER_THRESH_ON/OFF, it worked well when we changed PSAMS but we then realized we needed a ZM4/5 ASC rather than a ZM5/6 ASC for SQZT7 profiles. Tried just changing the output matrix, did not work. 

Strangely, when I used the SQZ IFO ASC screen's "!graceful clear history", we now have outputs in the LOCK OUTPUTs but the beam looks a lot clearer on AS_AIR camera. We are now in a different alignment than we have been, but it's better on AS_AIR so we'll reassess tomorrow...

H1 General
ryan.crouch@LIGO.ORG - posted 16:32, Monday 22 June 2026 (90695)
OPS Monday Day shift summary

TITLE: 06/22 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY: CRS, SPI at HAM3, BS / input alignment work, and a little bit of beam profiling at HAM7 continued today.
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
14:41 FAC Kim LVEA Y Tech Clean 15:50
15:34 VAC Jordan LVEA Y CP1 checks 15:43
15:53 SPI Jennie LVEA Y Unshutter SPI laser 15:56
16:10 FAC Kim LVEA Y Tech clean 17:01
16:22 SUS Jennie LVEA Y Open light pipe, IOT1 work, light pipe closed at 1700 17:00
16:40 SEI Jim, Arnaud LVEA Y BSC2 cabling, 1 person in-chamber 18:29
17:00 SPI Shoshana LVEA Y H2 enclosure to HAM3 parts shuffle 18:09
17:06 PEM Robert EndX N Grounding study 18:20
17:13 SUS Ibrahim, Betsy LVEA Y BS pitch adjustment in-chamber, by HAM3 checks, Betsy out 1830 18:49
17:24 SUS Oli, Camila LVEA Y Help alignment team by HAM3 18:46
17:33 OPS RyanS LVEA Y Bring Dust monitor to BSC2 crew 17:50
17:57 VAC Gerardo LVEA Y Inspect viewports, input/output tube 18:20
18:00 ISC Keita LVEA Y Talk to HAM3 crew 18:42
19:02 SUS Oli LVEA Y Move a chassis 19:10
19:48 PEM Carlos, Shrey Site Y Huddle test at vertex 20:54
19:49 PEM Robert Site N Searching for a seismometer 20:54
20:00 CDS Patrick Ends N Check on Beckhoff computers 20:22
20:13 SPI Jeff, Jim Optics lab, LVEA Y SPI work, optics lab then HAM3 at 21 UTC, Jim in at 2100, Jeff out at 2259 23:22
20:33 PSL Betsy LVEA Y Shutter PSL laser 20:40
20:35 VAC Jordan, Gerardo LVEA Y CP1 RGA scans and checks 22:55
20:40 SPI Jennie LVEA Y Search for a laptop 20:53
20:55 PEM Robert, Carlos, Shrey EndY N Retrieve seismometer 22:49
20:59 SPI TJ LVEA Y Join Jeff at HAM3 for SPI work 22:05
21:00 ISC Betsy LVEA Y Progress checks 21:26
21:05 SUS Oli, Fil LVEA Y Plug in chassis for BS 21:28
21:22 CRS Shoshana, Michael LVEA Y CRS  work by HAM3 Ongoing
22:04 SQZ Camilla, Eric, RyanS+1 LVEA Y Beam profiling at HAM7, RyanS out at 23:10 23:15
22:05 CRS Arnaud LVEA Y Join CRS team Ongoing
22:09 SUS Oli, Ibrahim LVEA Y BS work Ongoing
22:14 SEI RyanC Ends N Reset VFD panels for HEPIs, EY then EX 23:04
22:28 SAF CRS LVEA YES CRS laser ON near HAM3 Ongoing
23:32 IAS Jason LVEA Y FARO auto OFF/ON 23:37
23:34 ISC Betsy, Robert LVEA Y Checks Ongoing
H1 SEI
arnaud.pele@LIGO.ORG - posted 14:45, Monday 22 June 2026 (90696)
BS CPS replugged

Jim, Arnaud

The x12 in-vac BSC2 / BS ISI CPS sensors were replugged to their feedthrough as per D1003079. Jim worked from the platform, verifying the signals were live with a cds laptop while I was plugging them in from the chamber.  Before starting this work we turned on the interface chassis and had to power cycle corner 3 a couple of times before getting the -18V LED from the back panel to turn on.

Images attached to this report
H1 AOS
michael.ross@LIGO.ORG - posted 14:04, Monday 22 June 2026 (90693)
BRS Thresholds Changed

I increased both BRS damping threshold defaults to stop the ringing behavior that we've seen after Beckhoff restarts. The defaults are hard coded into the BRS Beckhoff control under the follow lines:

H1_ISI_GND_BRS_ETMY_LOWTHRESHOLD: INT:=2000;(*~ (OPC : 1 : visible for OPC-Server)
                                        (OPC_PROP[0005] :3: read/write)
                                        (OPC_PROP[0101] :Lower Damping Threshold: DESC)*)
H1_ISI_GND_BRS_ETMY_HIGHTHRESHOLD: INT:=4000;(*~ (OPC : 1 : visible for OPC-Server)
                                        (OPC_PROP[0005] :3: read/write)
                                        (OPC_PROP[0101] :Upper Damping Threshold: DESC)*)

 

I changed the LowThreshold from 800 to 2000 and the HighThreshold from 2000 to 4000.

H1 ISC
camilla.compton@LIGO.ORG - posted 12:38, Monday 22 June 2026 - last comment - 14:15, Monday 22 June 2026(90691)
BS alignment, could see SQZ beam off ITMX fly-bys at AS Port
Betsy, Ibrahim, Oli, Keita, Camilla. Follow from 90665 where we left ITMY and SR2 in a strange location. 
Summary: With ITMs back to top mass osems and BS at  (P 1000, Y 1290), we have seen fly-by of SQZ beam of ITMX at AS port. Expect BS is moving to much to get steady beam. SR2 alignment very different than March/O4 (+500urad P, +150urad Y).
 
 
9am. We started by putting ITMs, SRM, SR2, SR3 back to March DRMI time sliders (11:02 PDT 19 March 2026), attached sliders. We did not like that ITM PIT top mass osem sensors were far from the March time (-30urad for ITMX, +220urad ITMY).
We tried adding -170 to the ITMY Pitch slider as per 90551, this still took us very far form the osem sensors. 
 
9:33am We took ITMs, SRM, SR2, SR3 back back to the sensors (top mass osems) in March DRMI time (11:02 PDT 19 March 2026), attached sliders of this.
 
We then misaligned SRM but did not get our SQZ beam back on AS_A,B or AS_AIR camera off ITMY. We then went back to the time Thursday we had the beam on the camera at the current ITMY pitch pointing, moved according to osems for SR2 and oplev for SR3 (as HAM5 moved Thursday late afternoon 90671). Got the SQZ beam from ITMY back on the camera as per last Thursday, but this time we are happy with out ITM pointing.
We started the /ligo/home/sheila.dwyer/SUS/BS/BS_raster.xml but still could not see sign of SQZ beam off ITMX. BS was at (P 1000, Y 1000)
 
10:15am Went into HAM4 and moved BS sliders to get SQZ beams on top of each other:  (P 1000, Y 1290). This is encouraging that even with a different ITMY position, the BS pointing is very similar to last week. Sliders attached. 
 
On AS_A and AS_B we could see intermittent flashes of the SQZ beam off ITMX as it hit the sensors, we could also see it "fly-by" on the AS_AIR camera. We moved BS in a few 100's of counts and ITMX in ~100urad counts to try to improve this, it was intermittent (more flashes when there was more activity in the changer and when BS was not damped) but we did not improve it. Our best fly-bys are attached, typical good flashes also attached,  amplitude of flashes as are expected. We'd later like to go back to this alignment.
 
We tried using SR2 to center ITMY SQZ beam on AS_AIR camera but the beam quality got worse we we reverted. Expect there’s a better SRC alignment could find, currently SR2 slider is ~ 500urad different than March! 
Images attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 13:44, Monday 22 June 2026 (90692)

Found the ITMX alignment that sends IMC flashs all the way to AS camera AND the SQZ beam all the way to ISCT1

But, as of now, IMC flashes don't come back to ISCT1 at all, and SQZ beam only comes back to AS camera via ITMY reflection. PRM is misalilgned.

The ITMX alignment is very different from where I started but this is expected as we have moved PR3 by a large amount when we tried to center the IMC flashes on  ITMX.

sqz -> SR chain -> BS-> ITMX -> BS -> PR-chain -> ISCT1

  before/after
H1:SUS-ITMX_M0_OPTICALIGN_P_OFFSET -96/-125
H1:SUS-ITMX_M0_OPTICALIGN_Y_OFFSET 104/-331

In the attached video (PXL_20260622_203143545TS~2.mp4), ITMY is misaligned and only ITMX reflection reaches two cameras. In the ISCT1 REFL camera you can see a big bright beam which is from SQZ, while in the AS camera you can see IMC flashes.

What we should do is to refine ITMX alignment such that we can see ITMX reflection of IMC flashes in ISCT1. After that, if the IMC flashes arestill visible in AS camera, scan BS alignment to find ITMY reflection of IMC flashes in ISCT1. If the flashes are not visible in AS camera, we need to do some math.

 

Images attached to this comment
Non-image files attached to this comment
camilla.compton@LIGO.ORG - 14:15, Monday 22 June 2026 (90694)

Ryan S and I went back to the ITMX and BS alignment of the best ITMX SQZ beam "fly-bys", we did not see them or any flashes again. 

H1 CDS
david.barker@LIGO.ORG - posted 10:00, Monday 22 June 2026 (90689)
h1crsproc model running on h1seih23

WP13318 h1crsproc model install

Shoshana, Arnaud, Jim, Jonathan, Erik, EJ, Ryan C, Dave:

We installed the first version of the h1crsproc model on h1seih23 at 09:27 Mon22jun2026PDT. Because this took one of the two spare cores on this W2245 machine, this required a reboot to force the exception to this rule. We will upgrade this machine to a W3323 before the RGC/IPC upgrade.

A DAQ+EDC restart was needed, no major issues were found.

H1 SEI (SEI)
shoshana.apple@LIGO.ORG - posted 09:54, Monday 22 June 2026 (90652)
CRS Transport to Chamber Side and Other Updates

[Shoshana]

Craned the CRS over to the temporary clean room over by HAM3 on 6/18. Unfortunately the flexures (SN13,SN20) broke during the transport process. It seemed like a clean break that was potentially caused by the proof mass jolting upwards crushing the flexures (photos attached), and the locks remained in place.

CRS was re-suspended chamber side HAM3 with flexures SN15/SN19, which is the last of the approved flexures of the first batch, but the other batch is ready for pickup. Suspension was painless as the locks kept the proof mass centered even after the break. The CRS CoM was balanced by eye.

There isn't an easily accessible outlet near the temporary clean room, so I was unable to get a resonance frequency measurement on Thursday. The hope is that because the proof mass remained locked when the flexures broke, the HoQI should hopefully still be mostly aligned with the CRS and only need small adjustments which will be done this week.

Images attached to this report
LHO VE (VE)
jordan.vanosky@LIGO.ORG - posted 09:20, Monday 22 June 2026 (90687)
Purge Air Dewpoint Check (6/19/26)

Late entry from Friday night.

Jordan, Gerardo (remote), Betsy (remote)

On Friday night (6/19) Gerardo noticed the purge air dewpoint had risen above our -40C requirement and continued to rise. Out of precaution, I came on to the site to check the purge air status and see if any HAM/BSC door covers had blown off the flange.

All door covers were in place, so no issue there. I then isolated the purge air from the lvea for ~30 minutes, therefore dropping the demand/duty cycle of the air comporessor, to see if the dewpoint changed. It slowly began to drop and I took local dewpoint measurements at the sample port just past the filters on the purge air skid. There was no significant difference in dewpoint when the drying towers cycled, the dewpoint remained around -38C regardless of which tower was drying. 

After ~30 minutes, the dewpoint had dropped to -43C and so I reopened the purge air to the lvea, then reduced the flow at the purge air port on the output tube. It seems there was just too much demand on the compressor.

As of this morning, the dewpoint has returned to normal -51C at the drying towers. 

Images attached to this report
H1 General
ryan.crouch@LIGO.ORG - posted 07:34, Monday 22 June 2026 (90686)
OPS Monday Day shift start

TITLE: 06/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: 17mph Gusts, 10mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.09 μm/s 
QUICK SUMMARY:

H1 CDS
david.barker@LIGO.ORG - posted 07:37, Friday 19 June 2026 - last comment - 07:14, Monday 22 June 2026(90683)
PID control of CP1 pump LN2 level looking good

Using the same settings as 2021 the PID control of CP1's level is maintaining the 92% setpoint nicely.

Images attached to this report
Comments related to this report
david.barker@LIGO.ORG - 07:14, Monday 22 June 2026 (90685)

Here is the last two days trends, CP1 LN2 level is holding at 92.00 +/- 0.05 %

Images attached to this comment
H1 SPI (SEI)
jennifer.wright@LIGO.ORG - posted 18:39, Thursday 18 June 2026 - last comment - 09:40, Friday 03 July 2026(90676)
SPI install update - day 6

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:

 

Images attached to this report
Comments related to this report
thomas.shaffer@LIGO.ORG - 10:08, Monday 22 June 2026 (90690)

More details regarding the baffle installation:

When placing the below table baffle brackets, there was a ballast mass baffle (D1700262) that was blocking the angle bracket for the furthest -Y bracket. The bracket could not slide under the ballast mass baffle (bmb), so we decided to move the bmb in the +Y direction a few inches and I had to loosen the baffle panel within the feet to slide it up a few mm and then reclamp. This allowed the bracket to slide under the baffle just to the side of the feet, but the move partially exposed a corner of the shiny ballast mass stack.

The lower baffle shroud that covers the breadboard needed the fiber spools to be moved. We moved them over one set of bolt holes, but they are quite close to chamber edge, I'd guess around 1/2". Jeff then centered the two aperatures to the SPI beam, and we called it good. We still need to B&K the whole area.

Images attached to this comment
jennifer.wright@LIGO.ORG - 17:46, Monday 22 June 2026 (90699)

Just did an 8 hour trend of the fiber power monitor channels for REF and MEAS channels (left two plots) and the optical lever QPDs (right two plots) to check whether we expect variations on the order of ~2V on the QPDslike we saw on Thursday before and after baffle installation.

From this trend the power appears to drift more than this for two hours after unshuttering the laser (around 15:56 UTC), but once it reaches a steady state both QPDs were only drifting by 1V and the fiber power input monitor PDs by 1V or less.

Conclusion: I think we would have seen a dramatic power drop on Thursday when we installed the shroud, that I would expeact to have been much larger than the trends I saw today.

Images attached to this comment
jeffrey.kissel@LIGO.ORG - 13:47, Tuesday 23 June 2026 (90713)
Note mentioned in the summary of activities in the main entry -- per LHO:90667, we re-installed all the ballast or balance mass discussed during this 2026-06-18 day's session. See attached "after" picture.
Images attached to this comment
brian.lantz@LIGO.ORG - 09:40, Friday 03 July 2026 (90893)EPO

Here's another picture of the SPI breadboard on HAM3 prior to the baffle installation. Photo credit is ?? maybe Jeff?

Images attached to this comment
H1 SPI
joshua.freed@LIGO.ORG - posted 18:10, Thursday 18 June 2026 - last comment - 19:51, Thursday 18 June 2026(90680)
SPI, Pathfinder Install, REF Beam error found

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.


CDS_Sin_and_Cos.jpg Shows that they were the same signal
 
REF_RF_Before.jpg   REF_RF_After.jpg Shows the REF signal before and after. The before had a 4096Hz beat note inside itself
 
MEAS_IFO_BEAT_After.jpg Shows the corrected beat note on the Meas IFO after the correction. Note: There is some noise here which is partly caused by 16kHz signal that is ~13dB less than the main signal. The double mixer produces this as a byproduct and SPI is insensitive to this noise.
Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 19:51, Thursday 18 June 2026 (90682)
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).
Images attached to this comment
H1 ISC (SQZ)
camilla.compton@LIGO.ORG - posted 14:39, Thursday 18 June 2026 - last comment - 09:46, Monday 22 June 2026(90665)
Using SQZ to check BS alignment

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. 

Details:
Injecting 1.25mW on SRM from SQZ seed (75mW SEED), expect 0.875mW on AS_A, get 0.77mW (fine).  

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...

Comments related to this report
betsy.weaver@LIGO.ORG - 17:25, Thursday 18 June 2026 (90679)

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 (?)

 

betsy.weaver@LIGO.ORG - 18:46, Thursday 18 June 2026 (90681)

The pic of the beams is from before I started the mech pitch adjustment but had Yaw aligned via the slider.

Images attached to this comment
betsy.weaver@LIGO.ORG - 09:46, Monday 22 June 2026 (90688)

This was supposed to say

SR3 - Use OPLEV pointing from THUR 5pm (when ISI came back on)

H1 ISC (IOO)
jennifer.wright@LIGO.ORG - posted 17:07, Thursday 30 April 2026 - last comment - 23:30, Sunday 21 June 2026(90081)
Measurement of jitter with IMC WFS at 10W

Summary: Since I had trouble seeing a noticeable improvement in jitter by looking at the IMC WFS in this alog #89988 where the PSL output power was 2W, I looked at times when we were at 10W PSL output power to see if we were limited by shot noise. The measurements at 10W show that we might have decreased jitter but I checked the QPD sum values for the measurements after JAC was installed vs. before and we are near the edge of the QPDs.


I took reference times, when our input power was 10W to see if this gave a better measurement of jitter

Time 1: 2025/11/17 16:13:17 UTC during initial alignment. Without JAC.

Time 2:2026/03/19 15:31:23 UTC during commissioning when HAM1 was at vacuum.

Image one shows the yaw measurement, there is again a difference in the value at DC of the QPD ASDs. It looks like the peaks seen between 40 and 1000 Hz are slightly better with JAC than without JAC but it is only obvious on WFS A and B QPDs (top left plot comparing green and purple lines for WFS A and red and yellow lines for WFS B).

Image two shows the pitch measurement, there is again a difference in the value at DC of the QPD ASDs. It looks like the peaks between 40 and 1000 Hz are slightly better with JAC than without JAC but it is only obvious on WFS A QPD (top left plot comparing green and purple lines).


I also checked that the QPD sum values changed between my reference times during O4 and after JAC installation. See these four images.

1. 2W reference time during run. A and B QPD SUMs were arpund 0.03 counts.

2. 2W reference time after JAC installation. A and B QPD SUMs were arpund 0.002 counts. Maybe we are now nearer the edge of the diode?

3. 10W reference time during run. A and B QPD SUMs were around 0.16 and 0.13 respectively.

4. 10W reference time after JAC installation. A and B QPD SUMs were around 0.009 and 0.008 respectively. Maybe we are now nearer the edge of the diode?

Images attached to this report
Comments related to this report
jennifer.wright@LIGO.ORG - 23:30, Sunday 21 June 2026 (90684)

Just adding a note with the comparison I used for my GWADW talk on May 19th so its in the alog.

I did an injection into the yaw DOF of the PZT mirror in the PSL and measured the response on the IMC REFL QPD DC when locked, since this was used to do jitter injections to produce noise plots during O4 I could compare to a time when we did this measurement during NLN without JAC, and locked at 10W with JAC.

The power difference shouldn't matter since I am doing a transfer function, but unfortunately the injection I did was not high enough to see coherence in the IMC REFL WFS QPDs and I ran out of time to repeat the measurement in March due to corner re-alignment efforts.

The two times I chose were:

60W lock without JAC: 07-08-2025 21:47:59 UTC - approx 16 minutes.

2W lock with JAC: 18-03-2026 22:28:12 UTC - approx. 16 minutes.

The graph which compares WFS B QPD with old measurement in blue and new in orange can be used to put a lower limit on the suppression of JAC. It gives a minimum jitter reduction of 0.15 at 10Hz.

I would like to redo this once we pump down the corner sufficiently to do some measurements with the main laser.

The txml measurement files that contain the data I used for this are in /ligo.home/jennfioer.wright/git/2026/JAC/JAC_PZT_Y_inj.xml for the new measurement and the same folder but the file 20250807_IMC_WFS_PZT_Y.xml for the older measurement.

Images attached to this comment
Displaying reports 181-200 of 88272.Go to page Start 6 7 8 9 10 11 12 13 14 End