Displaying reports 1-20 of 87182.Go to page 1 2 3 4 5 6 7 8 9 10 End
Reports until 11:05, Thursday 02 April 2026
H1 SPI (CDS, SPI, SUS)
jeffrey.kissel@LIGO.ORG - posted 11:05, Thursday 02 April 2026 (89752)
Installed SPI ISIJ QPDA TIA
J. Kissel, S. Koehlenbeck
H1 SUS-R1 D0902810, S1301885
TIA D1002481-v3, S2500711

Finished with all required assembly and testing of the SPI pathfinder's in-vac ISIJ Reflector assembly (D2400102), we packed it up such that it's install ready. That means it's supporting QPD photodiode transimpedance amplifier, whose [V/A] impedance has been measured and tailored to suit a 10 [V_p] differential ADC input (see 89739) is no longer needed in the optics lab. As such -- we moved it from the optics lab to its final location in the LVEA -- in the U6 position of SUS-R1 by HAM2.

Pictures:
    BEFORE installation
    AFTER installation
    S-NUMBER and U-Height zoom for confirmation.

We have not cabled up any of its inputs or outputs, but will do -- per D2400111 -- so in the fullness of time.
Images attached to this report
LHO VE
david.barker@LIGO.ORG - posted 10:35, Thursday 02 April 2026 (89750)
Thu CP1 fill

Thu Apr 02 10:16:29 2026 INFO: Fill completed in 16min 25secs

 

Images attached to this report
LHO General
ryan.crouch@LIGO.ORG - posted 07:32, Thursday 02 April 2026 - last comment - 07:49, Thursday 02 April 2026(89747)
OPS Thursday day shift start

TITLE: 04/02 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: 4mph Gusts, 2mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.21 μm/s 
QUICK SUMMARY:

Comments related to this report
ryan.crouch@LIGO.ORG - 07:49, Thursday 02 April 2026 (89748)

JAC has been trying and failing to lock overnight (since 5pm PST // 00 UTC yesterday), the SCAN keeps timing out "Check trigger level or Laser power". Bringing it to DOWN for now.

H1 TCS
sophie.muusse@LIGO.ORG - posted 18:06, Wednesday 01 April 2026 (89746)
CHETA 0922 unit installed

S. Muusse, G. Bolingbroke, C. Compton


The new QCL laser 0922 was installed in the setup to replace the broken 0920 unit and has been turned on and its working. Thermal paste got on the output lens during storage/transport and but we cleaned off using tissue and isopropanol. The main path alignment has been completed but the pickoff paths havent been checked and lenses havent been replaced. The new unit requires a slightly different lens position described in the yaml file which will hopefully be installed tomorrow. 

H1 ISC (INS, ISC)
keita.kawabe@LIGO.ORG - posted 17:38, Wednesday 01 April 2026 (89745)
Peeking down the X arm, Pico-ing HAM3 POP steering mirror, using dichroic to center ASC POP_X, using pico mirror in HAM1 to center LSC POP_A (Camilla, Jennie, Sheila, Jenne, Betsy, Keita)

After opening the X arm,  Jenne used the baffle PD script to roughly align the X arm.

We've found that the green beam was too high, hitting the aluminum part of the top periscope mirror mount. But it was off in YAW, too. We moved the PR3 to see what happens, but we ended up reverting it and moved pico steering mirror for POP path in HAM3.

In PIT, green beam was brought to a place where it's higher than the middle of the top periscope mirror because centering that beam in PIT the IR beam will be clipped.

The IR beam was still very close to the +X-Y edge of the dichroic and also the 90:10 to split in-air and in-vac beams, so pico-ed in YAW too.

At this point there was a HUGE pit offset on POP-X, the beam was hitting the top of the QPD case, and large (but not huge) yaw offset. We couldn't center the beam using PM1, so we used the dichroic.

We had to set the DC gain of the WFS DC interface on the front panel to HIGH to be able to see any meaningful DC signal from POPX, but anyway we managed to roughly center the beam in that H1:ASC-POP_X_DC_PIT_OUT and H1:ASC-POP_X_DC_YAW_OUT go both positive and negative as the beam fluctuates.

We didn't see anything on LSC POP_A at this point. We scanned PM1 and found that the beam is not that far and off mostly in PIT. We used a pico-ed splitter to split ASC and LSC POP to steer the beam on POP_A. We scanned the PICO to roughly put the beam at the center of the plateau. I say "roughly" because we used PRX beam which was freely flashing, so it was hard to go precise, but we can always do it after pumping down.

I say that the in-vac alignment is done (in that we can fine-tune after pumping down using picos and suspensions in HAM1 and also using pico in HAM3 if necessary).

Since we changed the HAM3 pico and made a large adjustment of the dichroic, the in-air POP beam as well as the green beam should have been affected. We'll put the table by HAM1 and see how they land on the periscope, and will adjust the steering mirrors in HAM1 if needed.

H1 CDS (PEM)
jonathan.hanks@LIGO.ORG - posted 17:24, Wednesday 01 April 2026 (89744)
WP 13137 Testing running the MX weather station IOC in a container

To test out new infrastructure for running IOCs and other services in CDS I put the MX weather station into a podman container and started it on our new service-host cluster (a high availbility cluster for services).

As part of this I created a generic container that should work for the other weather stations and the dust monitors (until those are migrated to beckhoff).

This work is part of an effort to improve our infrastructure, including how we track, monitor, and manage our IOCs.  There should not be any user visible change with this, other than the IP address that the IOC responds from is different.

Notes:

 * We run these older IOCs in the background with screen as they are iocsh shells and want a terminal.  For this setup I no longer need to run with screen, we just tell the container system (podman) to run the container with a tty in interactive mode in the background.

 

 

 

H1 ISC (SUS)
elenna.capote@LIGO.ORG - posted 16:43, Wednesday 01 April 2026 (89741)
Beam aligned to both OMCs!

[Georgia B, Elenna, Oli]

Last Friday I reported that the alignment to OMCA was decent, 89674. However, I had aligned OMCA with an HR and then removed it to align OMCB. On Monday, I tried placing a beamsplitter at the same location so I could simultaneously align OMCA and OMCB, but then I didn't have enough power for both. I then tried to fix the upstream fiber, which at first went horribly, but now we are getting 50 mW to align with, so overall things have improved.

Today, Oli and I began to realign the beams to the OMCs, since so much changed upstream. Georgia then later tagged in to help me. For alignment, we have about 33 mW to align OMCB and about 17 mW to align OMCA. This enough to see flashes on the card at the DCPDs.

Summary: we see flashes at the DCPDs of OMCA and OMCB. These flashes look pretty good overall. The beam is not modematched to the OMCs, so the flashes look mostly like mode mismatch.

We used the IR sensitive camera to take long exposure shots of the DCPDs to capture a long average of the flashes.

Here is a picture of both DCPDs of OMCA. There are some blobs that indicate the alignment could be a bit better, but overall it looks pretty good.

Here is a picture of DCPDA of OMCB. This mostly looks like mode mismatch, so again, decent alignment overall.

I have also attached videes of the OMCs flashes on an IR card.

Images attached to this report
Non-image files attached to this report
LHO General
corey.gray@LIGO.ORG - posted 16:30, Wednesday 01 April 2026 - last comment - 17:03, Wednesday 01 April 2026(89726)
Wed DAY Ops Summary

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

HAM1 & SQZ alignment work continued with focus on HAM1  GV7 was opened for a check down the X-arm for HAM1 work.  Team is still out at HAM1 and GV7 will be open overnight.  Would like to have ISCT1 rolled into place in the morning.

LOG:

Comments related to this report
ryan.crouch@LIGO.ORG - 17:03, Wednesday 01 April 2026 (89743)

Zone4s' temperature has dropped rapidly over the past half hour. Minute trends look like it may be rebounding but I can't tell yet.

Images attached to this comment
H1 SPI (SPI)
sina.koehlenbeck@LIGO.ORG - posted 16:19, Wednesday 01 April 2026 (89739)
LIGO-SPI Photodetector Chassis: CDS Range Maximization and TIA Output Settings

Sina, Jeff

The photodetector chassis of the LIGO-SPI pathfinder has been modified to maximize the CDS range. The TIA is designed to put out 0V - 10V on the positive leg of the differential output. The power monitoring PDs are set to get close to 5V, the interferometer PDs a mean of 2.5V, and the QPD quadrants 3.5V each. The whitening filters for the heterodyne-interferometer photodiodes are bypassed. The details of the installed capacitor and resistors are listed in the following table:

Detector R4 Resistor value now (kohm) Design value of pole frequency (Hz) C5 capacitor value calculated (F) C5 capacitor value now (pF) Resulting pole frequency (Hz) Chassis Variant Channel Mean power at PD (mW) measured with S121C Mean voltage at PD positive leg (V) Sum of mean voltage of TIA positive leg (mV) PD calibration (mW/V)
PD POW: FBR_PWRIN_MEAS (SIG) 53 1.00E+04 3.00E-10 220 13,650 3 1 0.9 3.9 3.9 0.23
PD POW: FBR_PWRIN_REF (LO) 53 1.00E+04 3.00E-10 220 13,650 3 2 1 4.25 4.25 0.24
                       
QPDB               9.9 13.5 13.5 0.73
QPDB Q1 3 1.00E+04 5.31E-09 1,000 53,052 2 5   2.9 2.9  
QPDB Q2 3 1.00E+04 5.31E-09 1,000 53,052 2 6   3 3  
QPDB Q3 3 1.00E+04 5.31E-09 1,000 53,052 2 7   3.9 3.9  
QPDB Q4 3 1.00E+04 5.31E-09 1,000 53,052 2 8   3.7 3.7  
                       
PD IFO: IFO_MEAS_A (LO)               3.3 0.9    
PD IFO: IFO_MEAS_A (SIG) 3 5.00E+04 1.06E-09 1,000 53,052 2 3 4.8 1.29 2.19 3.7
PD IFO: IFO_MEAS_B (LO)               3.1 0.9    
PD IFO: IFO_MEAS_B (SIG) 3 5.00E+04 1.06E-09 1,000 53,052 2 4 4.8 1.36 2.26 3.5
                       
PD IFO: IFO_REF_A (LO)               2.6 1.16    
PD IFO: IFO_REF_A (SIG) 4.99 5.00E+04 6.38E-10 560 56,955 2 1 2.9 1.24 2.4 2.29
PD IFO: IFO_REF_B (LO)               2.6 1.08    
PD IFO: IFO_REF_B (SIG) 4.99 5.00E+04 6.38E-10 560 56,955 2 2 2.9 1.22 2.3 2.39
                       
QPDA 1.5 10000 1.06E-08         18.5 9 9 2.06
QPDA Q1 1.5 10000 1.06E-08 2000 53,052 1 1   1.9 1.9  
QPDA Q2 1.5 10000 1.06E-08 2000 53,052 1 2   2.6 2.6  
QPDA Q3 1.5 10000 1.06E-08 2000 53,052 1 3   2.2 2.2  
QPDA Q4 1.5 10000 1.06E-08 2000 53,052 1 4   2.3 2.3  

 

The capacitor for the QPDs might be changed to result in a low-pass frequency of 10 kHz at a later date.

H1 SPI (SPI)
sina.koehlenbeck@LIGO.ORG - posted 13:47, Wednesday 01 April 2026 (89740)
LIGO-SPI Pathfinder ISIK/ISIJ Picomotor Test: All Motors Operational

Sina, Jim

We tested the functioning of the picomotors in the LIGO-SPI Pathfinder ISIK and ISIJ assemblies. All motors are working (see attached video).

Non-image files attached to this report
H1 ISC
jenne.driggers@LIGO.ORG - posted 12:27, Wednesday 01 April 2026 (89737)
ITMX alignment set with green baffle PD script

After the vacuum team opened up GV7 so that we can have a peek down the arm, I ran the green baffle PD scripts for the Xarm.

I did the usual misalign ITMX and ETMX, and ran the script for TMSX.  I then realigned ITMX, and ran the script for ITMX.  I then realigned ETMX and ran the script for ETMX.  

I looked at H1:ALS-X_REFL_A_DC_POWER and moved ETMX a bit to try to get some refl dips, which indicate that there are some flashes in the Xarm.  ETMX is not at all optimized, and I haven't touched TMSX since running the baffle align script on it. 

The baffle align script moved ITMX 5 or 6 urad "down" in yaw, and very little in pitch.  The attached screenshots shows times before, during, and after the baffle align script, for the ITMX sliders, top mass osems, and oplev.  The only difference between screenshots is whether cursors are included for convenience.

Images attached to this report
H1 SQZ
camilla.compton@LIGO.ORG - posted 12:08, Wednesday 01 April 2026 (89736)
ZM3 moves for FC alignment

Sheila,  Camilla 

Yesterday, Sheila moved ZM3 in steps of +10urad in PIT on the sliders (towards the diorection we know we need to be for SQZT7 light). She then compensated with FC1 and FC2 to maximize FC green flashes each time. And then measured the amount ZM3 needed to be moved to get light on SQZT7, ZM3 needed to be moved less each time to get light on SQZT7 IR PD (good) however, the flashes could not be brought back to thier maximum (bad). Plot attached.

Today, I moved ZM3 in steps of -10urad in PIT on the sliders (away from the diorection we know we need to be for SQZT7 light). Then compensated with FC1 and FC2 to maximize FC green flashes each time. And then measured the amount ZM3 needed to be moved to get light on SQZT7, ZM3 needed to be moved slightly more each time to get light on SQZT7 IR PD (bad), but the flashes could be brought back to thier maximum and mayeb even got slighly better (good). Plot attached

Images attached to this report
H1 IOO
sheila.dwyer@LIGO.ORG - posted 10:57, Wednesday 01 April 2026 - last comment - 12:27, Wednesday 01 April 2026(89733)
Two PRX alignments

For the HAM1 work today, here are two screenshots showing PRX alignments with two different PR3 values.  

PR3 yaw slider at -233.7 urad is here, since HAM2 HEPI is locked 3.7 urad positive RY compared to it's usual location (89701), this corresponds to -230 urad our yaw alignment from O4 (and from the March 14th PRMI/DRMI locking).  

PR3 yaw slider at -240, here, is the alignment for which in the in chamber crew found the beam on the edge of the ASC POP X diode.  

Images attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 12:27, Wednesday 01 April 2026 (89738)

Redoing these screenshots after Jenne Driggers ran the baffle PD script to point ITMX down the X arm.  

O4 PR3 pointing here

yesterday's PR3 pointing that put beam close to POP X here

Images attached to this comment
H1 SUS
jenne.driggers@LIGO.ORG - posted 10:37, Wednesday 01 April 2026 - last comment - 11:47, Wednesday 01 April 2026(89732)
JM3 overdamped for HAM1 work

[Keita, Oli, Jenne]

To make relocking the IMC easier during the HAM1 work, JM3's damping has been significantly increased.  Oli did mention that the JM3 damping loops haven't seen much real tuning yet, so even when we discontinue this overdamping, we may want to spend some time on them.

Attached are screenshots of JM3's damping loops before we tuned anything, as well as how we're leaving JM3 overdamping for now

The spectra show JM3 damping, but with gains of -2 in each of the Pit and Yaw loops as the references (so, a little more damped than they were yesterday), and then the live traces are with the overdamped situation.  

As a comparison, Oli pointed me to this old alog 62672 with a similar suspension's damping loops measured. 

Images attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 11:47, Wednesday 01 April 2026 (89734)

Tried the same thing for JM1, but the LL and UR coils rail once in a while because the alignment slider offsets are larger for JM1. Even without any damping/feedback, the DAC output for JM1 LL and UR are ~96 million counts (they rail at 134 million).

I decreased the gain by a factor of 2 for JM1.

[H1:SUS-JM1_M1_DAMP_P_GAIN, H1:SUS-JM1_M1_DAMP_Y_GAIN]=[-10, -20], [H1:SUS-JM3_M1_DAMP_P_GAIN, H1:SUS-JM3_M1_DAMP_Y_GAIN]=[-20, -40].

Elliptic lowpass as well as YAW "boost" were disabled for both.

Images attached to this comment
LHO VE (VE)
gerardo.moreno@LIGO.ORG - posted 18:32, Tuesday 31 March 2026 - last comment - 16:54, Wednesday 01 April 2026(89723)
GV7 Pneumatic Pressure System

(Jordan V., Travis S., Gerardo M.)

We removed and replaced the broken pressure regulator for GV7, we haven't tested the new regulator yet (open or try to hard close GV7), but hope to do so soon. During the regulator replacement we installed an isolation valve on the line that feeds GV7, this for upcoming work on this system.
While doing the replacement of the regulator for GV7, we discovered that the pressure regulator for GV8 pneumatic system is broken too, currently it is reporting a max pressure of 100 psi and a low pressure of 80 psi, it rides the instrument air compressor behavior (high and lows).  We tried to lower the pressure but the regulator is non-responsive.  We'll replace the pressure regulator at the next opportunity.  Also, it turns out that the pressure regulators attached to the different pneumatic gate valves are not the same model.

Images attached to this report
Comments related to this report
gerardo.moreno@LIGO.ORG - 16:54, Wednesday 01 April 2026 (89742)VE

(Travis, Jordan, Dave, Gerardo)

We finally got a chance to actuate GV7, but to the open position, and it took about 40 psi to start moving, it opened without any issues, current pressure to keep it open is 55 psi.  Opening the gate valve generated a few alarms, nothing out of what we expected, Dave took care of them.
GV7 will remain open until work at HAM1 is done, then we can attempt to hard close this gate valve, then after a start a vent of the corner.
A very smooth working pressure regulator, it did its job with ease.

H1 IOO (IOO, OpsInfo)
sheila.dwyer@LIGO.ORG - posted 12:27, Tuesday 31 March 2026 - last comment - 11:40, Wednesday 01 April 2026(89718)
JAC refl shutter trigger level, can lock JAC (and sometimes IMC) at 20W input power

Sheila, Keita, Jennie W, Jenne D, Georgia B.

We want to be able to power up to 20W in JAC to check the POP beam.  

We were loosing lock with about 8W into JAC because the REFL shutter was closing.  Jennie Wright measured 6mW on the REFL diode with 2W input to HAM1 and JAC unlocked yesterday.  This corresponds to 0.58V on the shutter trigger diode.  The threshold cannot be set above 2V, which means we would unlock when 21mW hit the diode.  Jennie Wright added a ND05A into the path before the refl diode, and another ND05A in front of the shutter diode.  

Now, with 2W input to HAM1 and JAC unlocked, we should have 2mW on the REFL diode, and the shutter diode votlage is 0.18V.  The threshold of 2V now will shut the shutter with 22mW on it. 

Gaurdian changes:

The JAC error signals are normalized by the PSL input power if we use the laser power guardian to change the input power, so we shouldn't need a power scaling like 89708.  People have been using the rotation stage instead of the guardian to adjust the power because the laser power guardian would go into fault if the power was below 1W (people have been going below 1W while HAM1 is vented.)   Jenne Driggers adjusted the fault in LASER_POWER and added a 200mW state to the laser power guardian, so now we should use this guardian whenever we want to change powers, even below 1W. 

We also hard coded the gain used for locking JAC in the down state, although this could be reverted to allow the power normalization to work again, once that has been updated to take into account the new ND filters.  Once this was done, we could lock JAC at a variety of powers and also change the requested power after it was locked. 

Georgia B and I also had a look at the IMC guardian, which has not generally been able to lock the IMC except at 2W.  There was some code in the down state of IMC LOCK that was supposed to adjsut settings for lcokign at different power levels, these were unused except for the IN1 gain setting used for acquisition.  Georgia and I adjusted some of these numbers and watched if the IMC would lock, we didn't take much time to test it but we did once twice see the IMC lock with 10W + input power, so that is promising. 

Comments related to this report
jenne.driggers@LIGO.ORG - 11:40, Wednesday 01 April 2026 (89735)

At Elennas' good suggestion, I added the IMC_power_adjust_func() to the IMC_LOCK's ACQUIRE state, so that it will adjust the IMC's FASTGAIN, so that the fast gain won't be wildly high when trying to acquire at higher powers.  

I did modify the function, so that if we're in ACQUIRE, it uses a FASTGAIN 5dB lower than the operating nominal gain.  This makes it match the 2W acquisition situation, where the fastgain was always acquiring at 0dB, and then for a 2W IMC lock would increase during the BOOST state to 5 dB.  

The IMC will lock at 10W, but it takes a long time.  It's a little happier at 8W.  It's still perfectly happy at 2W (which makes sense, since none of the 2W settings have changed).

I'm pausing any further testing, since the Xarm is open for our green peek.

Displaying reports 1-20 of 87182.Go to page 1 2 3 4 5 6 7 8 9 10 End