Displaying reports 1-20 of 88825.Go to page 1 2 3 4 5 6 7 8 9 10 End
Reports until 21:21, Monday 10 August 2026
H1 SQZ (AWC, SQZ)
sheila.dwyer@LIGO.ORG - posted 21:21, Monday 10 August 2026 (91471)
ZM4 psams adjustment today

Rahul, Ryan, Sheila

Today we think that we found a rapid way to iterate the psams preloading, and we made a couple of changes for ZM4.  

Frst Ryan and I measured the beam profile with ZM5 psams servo set to -8V, and ZM4 psams PZT votlage at 0V,  

Rahul can add the details of how he did this, but he added about 1/8 turn of torque to the ZM4 psams.  We then turned the laser back on, and took a beam profile measurement.  Unfortunately the profiler software got into a strange state where the beam waist seemed to be at a very different position and it would not calculate the original beam parameters.  We thought this was because the beam profile had changed dramatically, and Rahul backed off the preload by 1/8 of a turn.  As we were remeasuring the profile Ryan S noticed that the range of the translation stage displayed on the screen went only from 0-100mm, while it normally goes from 0-200mm.  The software would not allow Ryan to reset the measurement range parameter, until we powered the profiler off, exited the software, and started both up again.  

After this, we saw that indeed we had a reasonable q measurement, although not really an improved mode matching. It does seem promising to adjust ZM4 this way, as each iteration took about 30 minutes including our confusion about the beam profiler.  

Images attached to this report
H1 ISC
louis.dartez@LIGO.ORG - posted 19:37, Monday 10 August 2026 (91470)
PSL Green Beam aligned onto COMM PD on ISCT1
S. Dwyer, J. Oberling, L. Dartez

This afternoon we went to ISCT1 to align the green beam from the PSL Green PD, and ALS COMM PD. This is pre-peek prep so that by the time the peek takes place we don't need to worry about the beam alignment from the PSL.

We struggled a little bit to find an alignment that agreed with the crystal and the downstream PDs. We were able to get a beam onto the COMM PD. Sheila thinks that what we set up so far is more than enough to get a beatnote during the arm peek. We aligned the green beam onto the green PD but for some reason couldn't get see a readout signal that corroborated that the beam had made it onto the diode. We tried doing some troubleshooting, which included a local cable swap and adjusting the PD placement on the table. Neither were successful and, given the time of day, we opted to revisit at a later time. The important part thing is that the COMM PD _was_ seeing the beam. 
Images attached to this report
H1 CDS
jonathan.hanks@LIGO.ORG - posted 18:11, Monday 10 August 2026 (91469)
WP 13504 investigating higher rate of transport issues

As per WP 13504 we made some changes on h1daqdc0 to see if they would impact the error rate*.  We turned on the irqbalance daemon to see if that would help with IO load.  We are going to let this run a day or two and evaluate what things look like.  We are looking at other ideas (timing changes, network config changes, possible code changes to lock cores and network interrupts together better) but are going to hold off until the control room is ready.

* In the daqd, the CRC errors are a misnomer.  It really means late data, not corrupt data.

H1 SEI
jim.warner@LIGO.ORG - posted 17:58, Monday 10 August 2026 (91468)
Testing high voltage CPS on HAM8 ISI overnight

While Huyen is here, we've dug out the high voltage CPS that we got several years ago to try testing them on HAM8 again. We have a little preliminary data, that doesn't look good so far, but we will try to see if we can get any improvements over the next couple of days, while HAM8 is still isolated from the rest of the detector.

H1 SPI
jim.warner@LIGO.ORG - posted 17:48, Monday 10 August 2026 (91467)
No power on power mon pd in SPI laser chassis

Jennie and I were looking at the SPI with Sina during a call today and Sina pointed out there was no power on the first PDs on the SPI breadboard. She said there was a witness pd in there SPI laser chassis that could be checked with a multimeter next to the chamber, so I went and checked that this afternoon. I'm not totally sure what all of the labels meant, but I think there is no laser light on the pd in the interface chassis. The SPI_LP_M1_PD was at 0v, the other two, SPI_LPMON_M2_RFMEAS and SPI_LPMON_M3_RFREF were at ~.8v regardless of the state of the CDS control of the SPI pick off shutter, which I had Ryan toggling remotely. We've talked to Ryan and Jason about going into the PSL tomorrow to check the function of the SPI pick off shutter, I think we will also try to check the output of the fiber at the chassis with a laser card at least. Not sure how hard it would be to look with a power meter.

Images attached to this report
LHO General
corey.gray@LIGO.ORG - posted 16:33, Monday 10 August 2026 (91458)
Mon Day Ops Summary

TITLE: 08/10 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: Ryan S

SHIFT SUMMARY:

Input Align & ZM4 work continued today with LVEA being transitioned to HAZARD toward the end of the shift for checks at ISCT1.

Apollo on-site to begin work addressing a beam tube enclosure section which is failing by installing framework inside the beam tube enclosure (this section in question is part of X1 on the Xarm [near the bridge]).

VAC team has been preparing for the quick X-arm opening peek tomorrow.

 LOG:

H1 SUS (SUS)
timothy.ohanlon@LIGO.ORG - posted 15:29, Monday 10 August 2026 (91466)
QOSEM to BOSEM Performance Comparison

+ Valera

Now that we have the full 6x12 QOSEM to Euler matrix implemented at LLO, I have made a bunch of comparison plots looking at ITM BOSEMs and BBSS QOSEMS. Per sensor, we see about 2 to 3 times improvement but expected more like 10x. I made the comparison for L1 and H1. I also directly compared L1 v H1 BBSS QOSEM performance and compared the L1 6x6 v L1 6x12 OSEM to Euler Matrix.

L1 BS QOSEM vs L1 ITM BOSEM
H1 BS QOSEM vs L1 ITM BOSEM
L1 vs H1 QOSEM
L1 6x6 vs L1 6x12 OSEM to Euler Matrix 

Some things to note for the comparison plots

Non-image files attached to this report
H1 IOO (ISC)
louis.dartez@LIGO.ORG - posted 14:00, Monday 10 August 2026 - last comment - 15:18, Monday 10 August 2026(91463)
Morning input alignment work: better IR alignment to POP_X and LSC-POP
L.Dartez, S. Dwyer, M. Nakano

Continuing from alog 91450, I started using awg to raster the im4 alignment to find the IR beam on the ISCT1 REFL camera on Friday. This effort was paused at the end of the day without finding the beam. This morning, Masayuki and Sheila noticed that the AS AIR camera had a beam but it was off-center. They walked it back using PR2 and IM4 and adjusted PR3 and the BS to compensate. 

When I got in to the control room I adjusted IM4 further to center the beam on ASC-POP_A. ASC-POP_B is still off center but we're choosing to prefer that POP_A stays centered for now.

Later this morning, Masayuki and I decided to see if we could find a PR2 + PR3 + PM1 alignment that 1.) maximizes LSC-POP, 2.) maintains the beam centered on ASC-POP_X, and 3.) maintains the beam center on the ISCT1 REFL camera. Starting from the nominal position (e.g. the position it was already in before we started) we moved PR2 in each direction. Each trial move's procedure was as follows: 1.) move PR2, 2.) compensate with PR3 to recenter ISCT1 REFL camera, 3.) adjust PM1 to center onto POP_X, 4.) observe/record the LSC POP counts.

We currently have roughly 3.4 counts on ASC-POP_X NSUM and 2.7 counts on LSC POP with POP_X centered within about 0.15 and 0.1 counts for PIT and YAW, respectively.

The slider values for PM1 are in PM1_sliders.png and the sliders for PR2,PR3, and IM4 are in IFO_sliders.png.

This new alignment configuration should better position us for the arm peak taking place this week, since we can confirm that we have red beam down to the ISCT1 table and on POP_X. The next intermediate step here will be to lock PRMI...
Images attached to this report
Comments related to this report
louis.dartez@LIGO.ORG - 14:21, Monday 10 August 2026 (91464)
Masayuki and I aligned PRM. We aren't able to lock PRMI yet since there is no light on LSC POPAIR 18 right now.

Sliders for PRM are in PRM_sliders.png.
Images attached to this comment
louis.dartez@LIGO.ORG - 15:18, Monday 10 August 2026 (91465)
I briefly misaligned the PRM and BS to check the actuation range of the RMs with the DC centering loops engaged to make sure that we aren't at risk of railing them. All looks good.
H1 AOS (SEI)
wandaelisabeth.vossius@LIGO.ORG - posted 11:28, Monday 10 August 2026 (91462)
DAS Interrogators settings
Wanda V., Reinhardt R. 

On Friday (08/07) we connected both fibres which measure the arms to the Febus interrogator, with the X arm on Ch1 and the Y arm on Ch2. This frees up the Sintela interrogator for Reinhardts experiments. 

The Febus interrogator is now measuring at 2500 Hz with a downsample factor of 10 before saving, coming to a recorded sampling rate of 250 Hz. The gauge length was 6m. In case there is a crash or the measurement needs to be restarted, the pipleline to load is LIGO_20260807_DS_SR_Writer_both250hz_v2. Filesize is ca 50 MB/min/channel

Monday August 10th: 
We measured at 10 m gaugelength over the weekend and it was changed to 6m at 11:00 am (PST) on Monday. 

The filesize is roughly 100 MB/min for the 6m gaugelength (so 200 MB/min for both channels) and roughly 60 MB/min per channel for 10m GL. If this measurement should be restarted, the pipeline is LIGO_20260807_DS_SR_Writer_both250hz_v3. 

In principle, the interrogator can now run "as is" through IR1, but we are still free to change any of the settings. 

LHO General
tyler.guidry@LIGO.ORG - posted 08:29, Monday 10 August 2026 (91459)
Well Pump Failure
On the morning of Monday, 8/3 I noticed that the well tank was quite low. Given the sporadic re-routing of well water supply to CEBEX this was not immediately concerning. Because the well tank can call for the pump to run, it sometimes calls but never satisfies because of the possible configuration of valves at MY. This confuses the FMCS logic, and will cause it to no longer function as designed. That said, when I attempted to manually command the well pump remotely, it alarmed out. At that point, Eric, Bubba and Richard did some lite electrical troubleshooting. The most obvious issue at the time was that the IR contactor refused to pull in despite the cabinet being in hand and being told to run.

At this point, I called Ohmco to see if they were able to shift their schedule around to put eyes on the well cabinet ASAP. They arrived within ~2 hours and began their troubleshooting. After hours of poking around, their assessment was that the soft start motor control was likely faulty. Unfortunately, despite the soft start readout being largely shielded from the sun, it was not operable so no apparent faults could be documented.

A soft start (P/N ATS480D88Y) was ordered on Monday and arrived Friday. Ohmco arrived that day, swapped the motor control's, set the appropriate parameters according to our pump HP and we verified rotation. This fixed the issue and operation of the wellhead returned to normal.

A second, identical soft start motor control has been ordered and is expected to arrive today. This will serve as a backup in the event this issue arises again. It will be clearly labeled and stored in the carpenter shop.

B. Gateley E. Otterman R. McCarthy T. Guidry 
Images attached to this report
LHO General
corey.gray@LIGO.ORG - posted 07:37, Monday 10 August 2026 - last comment - 10:45, Monday 10 August 2026(91456)
Mon Day Ops Transition

TITLE: 08/10 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: EARTHQUAKE
    Wind: 7mph Gusts, 4mph 3min avg
    Primary useism: 0.58 μm/s
    Secondary useism: 0.09 μm/s 
QUICK SUMMARY:

NOTE:  Both Ops work stations had troubles logging in  (I could enter my username, but then the computer would freeze...for both computers).  So I'm back here at cdsws27.  It worked, but it was a little slow.

We had a M7.4 earthquake in Bogota (sort of in between Cali/Medellin/Bogota) that rolled in here about 2hrs ago.  Looks like this has mainly tripped mostly LVEA HAMs.  Picket Fence is lighting up in yellow also.

Oh and Rattlesnake Mountain finally returns (after missing quite a bit last week due to a smoky week).  AQI for Richland (closest sensor on AirNow) is at a YELLOW 71.  Only active fire in Benton Franklin counties is far away up near Kahlotus (Nunamaker Road Fire with 20k+ acres.

Also, the GWANW (Gravitational Wave Astronomy North West) meeting will be hosted here at LHO today and tomorrow.

Post NOTE:  Looks like BOTH ops workstations have now moved to the password for the login, so I will try to move back there.

Comments related to this report
corey.gray@LIGO.ORG - 07:47, Monday 10 August 2026 (91457)SEI

Untripped HAMs 1-5+8 After the Colombia EQ tripped them at 1245utc (545amPDT).

corey.gray@LIGO.ORG - 10:45, Monday 10 August 2026 (91461)

Whoops...apparently I did NOT un-trip HAM8 ISI.  But that's ok since SEI group is working on CPS for HAM8 this morning.

H1 General
anthony.sanchez@LIGO.ORG - posted 16:29, Friday 07 August 2026 (91452)
Friday Ops shift report.

TITLE: 08/07 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:
Dust levels for H1:PEM-CS_DUST_LAB1_300NM_PCF is climbing up to 70,000 counts today. I imagine that the Dust level is goign to continues to rise with the wind this weekend. 

Input Alignment team has a PLAN, which is a simple matter of just walking the mirrors.  

Output  Arm team has been looking for MAXIMUM_POWER through their straws in HAM7, Note: Removed yellow View Port cover and left a guillotine in place on HAM6  & Misaliging SR2 & SR3.  

VAC team reports:  "Cryo Traps are open to the Beam Tubes." &  "The Corner station is still isolated from the Beam tubes." 

End Station Y had it's PCAL Integrating sphere returned today after it was stolen for some lab measurements last night. 

LOG:

Start Time System Name Location Lazer_Haz Task Time End
14:53 FAC Kim LVEA n Technical cleaning. 15:35
15:30 VAC Jordan LVEA n Taking pics of GV6 status 16:00
17:12 SQZ Sheila & Ryan S LVEA YES Power measurements In HAM7 19:42
18:29 VAC Jordan & Mitchel LVEA y/n opening ION pumps in the LVEA 19:14
19:49 PCAL Tony, Cory PCalLab, EY YES Taking Ey's PCAL Sphere back to EY's Laser Enclosure. 21:05
20:01 FAC Tyler +1 EY - Wellhead work 22:01
20:24 CDS Marc, Caroline CER - Swapping ISC power supply 21:04
20:26 PEM Carlos, Shrey, Miranda Overpass - Seismometer tests 22:26
20:37 VAC Jordan LVEA - Opening/closing GVs 22:25
21:08 SQZ Sheila & Ryan LVEA HAM7 YES Power Budget measurments & Beam Profiling 23:08
22:09 CDS Dave CER N Looking at the accelerometer.... Specifically Not Touching it 22:25
22:35 CDS Dave Miranda CER N Checking on more accelerometer chassis cabling 23:15
22:43 VAC Jordan LVEA HAM6 yes Isolating turbo pumps, and turning on the ION pump in HAM6 22:54
H1 SQZ
sheila.dwyer@LIGO.ORG - posted 16:12, Friday 07 August 2026 - last comment - 15:30, Saturday 08 August 2026(91444)
HAM7 power budget repeat

Ryan S, Sheila

In summary, after removal of the A:L2 apperture stop we still see about 4% extra losses in HAM7.  We searched for the rejected beam from SFI1 in both directions with lights out, IR card, and viewer.  To explain a few % loss we should expect to have 10-20urad in this beam, which should be visible with lights out an a viewer.  We also noticed that the beam is off in yaw at the location where we had an iris after ZM1.  

Since Ryan and Camilla aligned the beam onto the SQZT7 PD yesterday, we are noting the power on that PD here after each measurement so we can use that to account for fluctuations in power out of the OPO.  

From the control room, we dithered ZM2 + ZM3 and tried to reduce the fluctuations in the SQZT7 IR PD, we were able to recover a 4% of power this way, with fairly small adjustments (+9urad ZM2 P, +19 urad ZM2 yaw, 5 urad ZM3 yaw).  

One more round of power measurements: 

 

Images attached to this report
Comments related to this report
ryan.short@LIGO.ORG - 17:19, Friday 07 August 2026 (91454)SQZ

After all of this power budgeting, OPOS rebalancing, ZM4 PSAM preloading adjustments, and alignment, this afternoon I took another (possibly the last?) ZM4/5 PSAM M^2 grid on SQZT7. Data files attached. I used different strain gauge values for ZM4 than in the past since they've shifted with the preloading change, but this still covers pretty much the whole PZT range.

This was a 26-point grid using the following PSAM strain gauge settings:

ZM4 PSAMS = [-2.6, -1.0, 1.0, 4.0]

ZM5 PSAMS = [-8.0, -6.75, -5.5, -4.5, -3.3, -1.0]

Non-image files attached to this comment
sheila.dwyer@LIGO.ORG - 15:30, Saturday 08 August 2026 (91455)

The attached plot shows the qs measured on SQZT7 propagated to SRM, with three different ZM4 preloads. Camilla has summarized the history of our ZM4 + ZM5 preloading in 91404

 

Clickable Image

The blue points here are with 75 in lbs on ZM4, as adjusted in 75677.  The teal points were after an attempt to lower the pre-load to 65 in lbs, which Rahul and Camilla later rechecked with the torque wrench and thought that it went to something between 40-60 in lbs. ( 91416)

On Wensday, Rahul and Camilla believed that they applied more torque to the psams (91416), but somehow the beam profiles that Ryan took show that the preload was reduced instead.  

We did not repeat the OMC scans at this preload.  The M^2 range is similar to previous measurements, but the astigmatism is a little better here.  

Images attached to this comment
H1 IOO (IOO)
khanh.vu@LIGO.ORG - posted 14:32, Tuesday 04 August 2026 - last comment - 00:43, Tuesday 11 August 2026(91386)
IOT1 Table Work
Jennie Wright, Masayuki Nakano, Khanh Vu

This morning we worked on several tasks on the IOT1 table, including installing the camera and shutter, profiling the beam, and calibrating the DC power.

We identified a new location for the camera using the beam transmitted through JACR_M5. During this process, Masayuki noticed that the beam was being clipped by the shutter. We suspect that the beam may have been clipped for some time. We then installed the camera in its new location, and Masayuki aligned the shutter on the table.

Next, we profiled the beam for the wavefront sensors. We found that the Gouy phase separation between the two WFSs is approximately 70 degrees. We decided to leave the current configuration as it is since the separation is good enough. Masayuki will make a plot and perform a more detailed calculation later.

We also maximized the laser power in the REFL path by optimizing the waveplate angle. When JAC is unlocked, the measured power on the RFPD is 5.1 mW, and the trigger PD voltage is 0.28 V. When JAC is locked, the measured power decreases to 0.4 mW, and the trigger PD voltage is 0.02 V. Since the beam is split evenly, each WFS receives approximately 2.55 mW of optical power.

Finally, we calibrated the DC readout of RFPD by converting counts to mW. Before performing the calibration, Masayuki checked the alignment and recentered the RFPD. He then recorded two sets of measurements, each averaged over 10 seconds:

Measurement #1

* JAC_REFL_A_LF_INMON: 1072.3966186523437 counts
* DC power: 4.4 mW

Measurement #2

* JAC_REFL_A_LF_INMON: 1073.5228637 counts
* DC power: 4.5 mW

After the calibration, we updated filter number 10 with the new coefficients.
Comments related to this report
masayuki.nakano@LIGO.ORG - 14:56, Tuesday 04 August 2026 (91388)

The beam profile between the beamsplitter and the JAC WFS  was measured. Here I fit a Gaussian beam to those measured beam sizes and convert the WFS locations into Gouy phase.

Fit

The measured beam diameters were fit independently in x and y with the standard Gaussian beam model, w(z) = w0 * sqrt(1 + ((z - z0)/zR)^2) with zR = pi * w0^2 / lambda and lambda = 1064 nm:

  w0 [um] z0 [m from JACR_BS4] zR [cm]
x 141.2 0.377 5.89
y 151.9 0.370 6.81

The beam is slightly astigmatic, so x and y are treated separately throughout.

WFS positions and Gouy phase

The positions of WFS A and WFS B were measured with a ruler from the same reference as the profile scan: WFS A at z = 0.325 m, WFS B at z = 0.410 m. The corresponding Gouy phases, psi(z) = arctan((z - z0)/zR), are:

  WFS A [deg] WFS B [deg] Separation [deg]
x -41.3 +29.5 70.8
y -33.5 +30.4 63.9

Assessment

The separation is 71 deg in x and 64 deg in y, not the optimal 90 deg. This is not optimal, but it is not terrible either: the two WFS remain well separated in Gouy phase and the sensing matrix would not be close to degenerate. Given the time available we did not optimize the layout.

If we want to optimize it later, the fix is straightforward: moving WFS A upstream (toward the BS) by about 5 cm in x / 7 cm in y, i.e. from z = 0.325 m to roughly z = 0.27 m, brings the separation to 90 deg. WFS B does not need to move. 

Images attached to this comment
khanh.vu@LIGO.ORG - 09:38, Wednesday 05 August 2026 (91405)
Additional context for the work described above: The motivation for the table work came from the difficulties we had with the sensing and input matrices of the JAC ASC loops. In pitch, the PZT and JM1 signals are well separated, but their responses in yaw are too similar. This is problematic because we need the two wavefront sensors to distinguish between the motions of the two actuators.

While identifying a new location for the camera, Masayuki noticed that the shutter was clipping approximately half of the beam on the left side. We suspect that the beam may have been clipped for some time and that this may be related to the yaw issue, since the clipping affects yaw more strongly than pitch.
masayuki.nakano@LIGO.ORG - 00:43, Tuesday 11 August 2026 (91472)IOO

Summary

Today we installed the iris to block the ghost beam on the JAC REFL path with an iris, and to re-measure the beam profile with it in place. The ghost beam was produced by the laser window which picks off the partial power of the JAC reflection beam (~0.4%). Since this laser window doesn't have the wedge on it, the AR reflection is not well separated. We observed this interference during the original beam profile measurement in this thread. 

And now, the iris dumps the ghost beam, and we made a new the beam profile measurement. I made a good JAC REFL optical model which obtained by the fitting the beam profile measurement. We will use this model for the WFS signal calibration.


Iris installation

An iris was placed on the REFL path, between the first pick-off mirror and the first lens. To position it, the beam profiler was set just after the beam shutter, and the iris was closed while watching the profile, until the ghost was blocked and the main beam was left untouched. Actually, Since the ghost beam is very close, the main beam is partially blocked as shown in the attached pics. We will see if it would have any effect on our WFS signals.


Beam profile measurement after the change

1/e2 diameters along the REFL path, with JACR_MB4 as the origin:

z [inch from JACR_MB4] -21 3.5 5.5 7.5 9.5 11.5
horizontal [μm] 4440 1360 1140 895 696 500
vertical [μm] 4540 1360 1111 873 661 461

On-table distances were also measured: JACR_L1 to JACR_MB4 = 24", JACR_MB4 to WFS A = 12.5", JACR_MB4 to WFS B = 15.5".


New propagation model

I made a model of the beam propagation of the JAC REFL path from PSL to JAC and IOT1. This model was fitted to the new profile, with the PMC waist as origin.

Taken as known. The positions of lenses in PSL (IO_MB_L1/L2/L3) and of the JAC waist are the design values, i.e. the PSL bench to HAM1 relative distance is trusted.

Taken as unknown. The design placed the IOT1 table only loosely, and the periscope that matches the HAM1 beam height to the table height was estimated roughly. The distance from the JAC input to the IOT1 table is therefore the principal free parameter, allowed ±30 cm; it enters the calculation as the position of JACR_L1 measured from the PMC waist. The profile measurement was referenced to JACR_MB4, which carries its own error, so the JACR_MB4-JACR_L1 distance is a second free parameter.

The profile carries astigmatism, so a yaw tilt was allowed on each of the four lenses (three on the PSL bench, one on IOT1). This is deliberately over-parameterised: the individual tilts should not be read as physical alignment errors.  However, the aim of this analysis is not to measure how each lens sits but a model accurate enough for the following calculation. So as long as the aquired prameters are physically reasonable, we can use these numbers as the following calculations.

One note:
The HAM1 periscope (JAC_M1/JAC_M2) rotates the beam 90 degrees about its axis, so the transverse planes swap on the way to JAC: bench x (YAW) descends from the upstream sagittal channel and bench y (PIT) from the tangential one. A tilt therefore gives astigmatism of opposite sign depending on which side of the periscope the lens sits. This is the reason why the x/y beam size flipped at periscope in the attached plot.


Result

parameter fitted vs design
JACR_L1 position from PMC waist 11.4768 m -21.5 cm
JACR_MB4 to JACR_L1 0.6004 m -0.36"
yaw tilt, IO_MB_L1 / L2 / L3 -16.9° / -7.1° / -1.8° -
yaw tilt, JACR_L1 -3.2° -

The fitted path from the JAC input to the IOT1 table comes out about 21.5 cm shorter than design, which is the scale of looseness that was expected there.


Astigmatism at the WFS planes

Expressed as the difference in accumulated Gouy phase between the two transverse axes:

  model from the measured profile alone
WFS A -4.10° -4.96°
WFS B -10.61° -10.32°

Sanity check: mode matching into JAC

Taking the cavity eigenmode as the reference, the fitted injection-lens tilts imply a mismatch of 0.48 % (tangential) and 0.43 % (sagittal), 0.91 % combined. Small enough not to conflict with the measured mode matching (~1%).


Model parameters

PMC eigen mode

axis w0 [μm] zR [mm]
tangential (u) 546.312 881.232
sagittal (v) 549.028 890.016

The waist sits at z = 0 in both axes. Downstream of the periscope the tangential channel becomes bench y (PIT) and the sagittal channel bench x (YAW).

Elements

z is given from the PMC waist (the model's own origin) and from JACR_MB4 (the origin the bench profile was measured against).

element z from PMC waist [m] yaw tilt [deg] source
PMC waist 0.000000 - origin
IO_MB_L1 0.900000 -16.86 design / tilt fitted
IO_MB_L2 0.960000 -7.12 design / tilt fitted
IO_MB_M4 (PZT) 2.812000 - design
IO_MB_L3 2.900000 -1.75 design / tilt fitted
HAM1 periscope (JAC_M2) 7.040000 - design; x/y swap
JM1 7.268000 - design
JAC input mirror 7.576000 - design
JAC waist 7.826000 - design
JACR_L1 11.476799 -3.15 fitted
JACR_MB4 12.077174 - fitted (via JACR_L1 distance)
WFS A 12.394674 - measured from JACR_MB4
WFS B 12.470874 - measured from JACR_MB4

What was fitted, and what was not

parameter fitted value design allowed range
JACR_L1 from PMC waist 11.476799 m 11.691967 m ±30 cm
JACR_L1 to JACR_MB4 0.600375 m 0.609600 m ±1"
yaw tilt, IO_MB_L1 -16.8588° 0 ±20°
yaw tilt, IO_MB_L2 -7.1210° 0 ±20°
yaw tilt, IO_MB_L3 -1.7534° 0 ±20°
yaw tilt, JACR_L1 -3.1527° 0 ±20°
Images attached to this comment
LHO VE (VE)
jordan.vanosky@LIGO.ORG - posted 17:10, Wednesday 29 July 2026 - last comment - 10:50, Monday 10 August 2026(91314)
Seal Replacement on GV6 Air Cylinder

Travis, Gerardo, Jordan

During the closing of GV6 back in May, we noticed that there was some blow-by in the pneumatic system when trying to hard close the valve, see alog 90093

We were able to hard close the valve eventually but as preventative maintenance we wanted to replace the air cylinder seals, similar to GV7.

Prior to disassembly we measured the locations of the reed switches from the top surface of the bottom plate to the bottom surface of the reed switches:

Bottom Switch: 1 1/8"

Top Switch: 49 1/4"

We then disassembled the air cylinder and replaced the seals following procedure/notes collected during the GV7 repair. During cleaning of the old grease on the piston head, we noticed there were two burrs on the top of the piston, we did not notice any damage to the inside of the cylinder, but as a precaution we used a small flat file to remove the burrs. We also chased the threads on the four threaded rods with a die to aid with reinstallation. After cleaning and inspection of the cylinder tube, we found no issues or damage so we decided to continue to use that cylinder and keep the new one as a spare.

No other issues encountered, we removed the old seals, cleaned the grooves, added copious amounts of the supplied grease to the o-rings, seals and the inside of the air cylinder, and then re-assembled the cylinder tube. Pictures posted below and a final procedure is in progress and will be posted to the DCC.

We did not get a chance to cycle the valve after the seal replacement, so we will continue tomorrow with cycling the valve.

 

Images attached to this report
Comments related to this report
jordan.vanosky@LIGO.ORG - 16:04, Thursday 30 July 2026 (91333)

We were unable to fully open GV6 today after the cylinder repair. We heard the clunk of the gate camming over at 45 psi, but it did not start to raise until 55 psi, at which point we could hear air blow-by at the solenoid manifold, and up at the cylinder itself.

So we stopped trying to open the valve any further and slowly reduced the regulator output in order to bleed out the accumulated pressure on the bottom side of the piston. This lowered the gate back down and we heard the gate touch down indicating it is soft closed.

We will have to disassemble to air cylinder again and see what may be the issue. We still have 4 sets of replacement seals and one brand new air cylinder on hand if needed.

The valve remains soft closed until we are able to troubleshoot and repair the cylinder.

jordan.vanosky@LIGO.ORG - 17:45, Monday 03 August 2026 (91378)

8/3/2026

Travis, Gerardo, Jordan

Today we again disassembled the GV6 air cylinder with the valve soft closed to try and see what may have been causing the air blow-by which prevented us from fully opening the valve last week.

We did not find anything immediately obvious such as a seal that had jumped out of the groove, so we measured the ID of the original air cylinder, which was re-used, and found that it was ~0.01" larger than the ID of the spare cylinder (original ID ~8.015", spare ID ~8.005"). We then elected to use the spare cylinder instead to make sure there is good sealing contact with the cylinder wall, so we re-distributed the grease on the new cylinder and attempted to install over the piston, but the tube seemed to be slightly out of round and would not fit over the piston. So we flipped the tube 180 degrees and measured that side of the tube and found it was better. We again added grease to that side of the cylinder and installed it over the piston, ensuring the seals and wear band stayed in place, Then we re-installed the threaded rods, torqued the nuts, installed the reed switches and installed the air lines.

To verify all the new joints/connections were ok, we put ~10 psi to the top of the cylinder and then to the bottom to see if there were any leaks. There were none so we started to open the valve by increasing air pressure at the regulator, once we got to ~25 psi we could hear and feel air coming out of the bottom plate/adapter flange below the cylinder assembly, see picture below the area where air is coming out of is circled in red, at which point we stopped trying to open the valve and closed the quarter turn isolation valve to the air line.

We spoke with a GNB rep who advised we try to to open at a higher pressure and see if the bottom seals, so we then tried to open the valve again. This time we started at 20 psi and followed our normal opening procedure with the exception of increasing by 5 psi instead of 10 and waiting 3 minutes between increases. At ~35 psi, air stopped leaking out of the bottom flange, there was no air blow-by in the cylinder and we could hear the carriage starting to move. The gate fully opened at ~48 psi and Gerardo was able to take a video where you can hear the piston incrementally move up the cylinder. We increased the holding pressure to 58 psi and verified the MEDM screen showed the valve status as green.

Images attached to this comment
jordan.vanosky@LIGO.ORG - 17:10, Thursday 06 August 2026 (91437)

8/6/2026

This morning we wanted to soft close GV6 to see if the scraping/squeaking sound continued, or if grease just need to be distributed in the cylinder. Following our normal soft close procedure,we still heard the same noise as the piston moved down. 

We decide to swap the cylinder one last time to the spare cylinder which removed from GV7 back in May. This cylinder had an ID of 8.004" on both ends. 

During the removal of the "sticky" cylinder, we saw there were some small metal shavings on top of the piston, so we decided to remove the seals and install new ones to make sure there is no damage or debris that could cause sealing issues. We added grease to the new seals/o-rings, and the inside of the cylinder, then re-assembled the cylinder/threaded rods/nuts. 

An updated cylinder repair procedure in the works at E2600176.

Once we were done with the cylinder assembly we opened the gate valve to test functionality, and see if there were any leaks in the cylinder. We again heard air coming out of the bottom flange, same as the entry above, but once we got to 35-40 psi the leak stopped and we could hear the carriage moving up. This time there was no excess noise or dragging, and the valve fully opened at 48 psi. After of ~10 minutes with the valve open, and we confirmed there were no leaks in any of the newly assembled joints, we soft closed the valve, again there was no excess noise or dragging of the piston. This is what we typically see/hear when actuating the pneumatic valves.

GV6 remains soft closed for now, closing WP 13471

melina.fuentes-garcia@LIGO.ORG - 10:50, Monday 10 August 2026 (91460)

Videos related to alog 91378 above (original .mov files compressed to be able to upload in alog)

Non-image files attached to this comment
Displaying reports 1-20 of 88825.Go to page 1 2 3 4 5 6 7 8 9 10 End