Displaying reports 1-20 of 89595.Go to page 1 2 3 4 5 6 7 8 9 10 End
Reports until 21:14, Friday 09 October 2026
H1 TCS
sophie.muusse@LIGO.ORG - posted 21:14, Friday 09 October 2026 (92270)
CHETA new unit 0970 profiling and alignment

Camilla, Sophie


We reprofiled the QCL unit 0970 because we were concerned the SNR was too low and effecting the profile of the beam (see alog 92242). The 99:1 BS placed in front of the QCL was replaced by the CO2 99:1 BS which at 4.6um acted effectively as a 70:30, with the 30% beam transmitted. We profiled the 30% beam at 1A and 25C over a 50cm range. 
The strange beamsize fluctuations around the waist were observed again so we concluded this was a not a measurement error and slightly non-gaussian behaviour of the beam.
The complex q parameter for the laser was found using a non linear fit to be:

--- Horizontal (A1) Fit ---

Data range: z = [97.0, 597.0] mm
Beam radii: [422.0, 1412.3] µm
Fit converged: w₀=411.4+/-9.2 µm, z₀=224.9+/-3.9 mm
q = -225+/-4 + 116+/-5i mm

--- Vertical (A2) Fit ---

Data range: z = [97.0, 597.0] mm
Beam radii: [413.6, 1183.7] µm
Fit converged: w₀=421.0+/-10.9 µm, z₀=293.7+/-3.9 mm
q = -294+/-4 + 121+/-6i mm
Note: Louis pointed out the plots of the fit have weird error bars which I will investigate in the QCL fitting code. 

The measured q-parameter is very similar to the Y-arm unit and a very similar telescope optimisation could be completed. This layout is listed in the git and has the following beamsize and astigmatisms. 

Beamsize at ITM
wx_ITM: 53.299 mm
wy_ITM: 52.042 mm
w_ITM_mean: 52.671 mm
w_ITM_astig: 1.257 mm

This is an improvement in astigmatism of approximately 7mm from the 0922 unit we swapped out.

We are currently aligning the table and the beam is aligned up to the PDBS. Unfortunately, many of the other optics had to move to ensure the PD intensity noise measurement optics would not be positioned in the waist so they do not get burnt.

Images attached to this report
H1 ISC
elenna.capote@LIGO.ORG - posted 20:19, Friday 09 October 2026 (92271)
Trouble getting back to resonance, is the recycling gain too low?

During the latter part of the day, Louis and I tried to get back to resonance, but have yet to get there. First, we had problems with TR carm (again), and then we struggled at the carm offset reduction.

For TR CARM, we thought the gain might be a bit low in start_tr_carm, so we upped the analog H1:LSC-REFL_SUM_A_IN1GAIN by 3 dB. This seems to help! Louis also increased the time in the servo to 10 seconds.

CARM_OFFSET_REDUCTION problems:

We had one lockloss at carm 5 pm after completing carm_offset_reduction by hand. Don't know why, but this was another state we sometimes had to carefully do by hand.

Want to reiterate that the IMC is still being fussy when relocking.

LHO General
ibrahim.abouelfettouh@LIGO.ORG - posted 20:00, Friday 09 October 2026 (92272)
OPS Eve Shift Summary

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

IFO is in at DARM_TO_RF

Elenna and Louis worked hard to get past IDLE_ALS, whioch is the state right before we lose lock. The current hypothesis is that the PR_Gain ramp up is wrong so they've been measuring and then stepping up the gain (more negative) slowly to see what is enough.

It turned out that the arm alignment was bad, and we successfully got past DHARD_WFS. Though the problem is still happening so Elenna is troubleshooting.

We've relocked fully automatically with DRMI over 10 times. 

LOG:

Start Time System Name Location Lazer_Haz Task Time End
15:12 FAC Chris MX, MY n FAMIS tasks 16:00
16:11 ISC Sheila LVEA YES Setting up measurement 16:23
17:15 EE Marc CER YES Checking signal for Richard 17:22
22:24 TCS Sophie CHETALab y(local) Aligning laser 00:14
23:15 ISC Keita, Alex LVEA Y Changing OMC measurement settings 23:23
H1 SEI
arnaud.pele@LIGO.ORG - posted 17:09, Friday 09 October 2026 (92263)
Testing new CRS_HAM3 guardian

TJ, Jim, Arnaud

Implemented a new HAM3_CRS guardian. The purpose of this guardian is to :

1) monitor the state of the CRS on HAM3 (Laser status, 25mHz tilt amplitude, and readout noise (3_10Hz)
2) adjust the damping gain depending on the tilt amplitude, and
3) take it to "SAFE" (Damping OFF) when maintenance is necessary 

This morning, we tested the condition for a rung up CRS, see attached screenshot. The CRS was manually rung up, and we let the guardian take over. After the 1urad rms threshold was reached, guardian jumped to CRS_RUNG_UP state, changed the damping gain to 1 (from nominal 0.01), and went back to CRS_GOOD after the RMS threshold came back under threshold. The earthquake that happened later today also triggered the CRS_RUNG_UP state as expected, see second plot from this alog

Guardian logic description is written under: T2600479

Images attached to this report
H1 General
oli.patane@LIGO.ORG - posted 16:30, Friday 09 October 2026 (92268)
Ops DAY Shift End

TITLE: 10/09 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Earthquake
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: 

We are back to trying to relock after the big earthquake earlier today.

Locking notes:
Morning Initial Alignment
- Had to help XARM because it kept catching on wrong mode, but probably would've caught on its own eventually

Relocking
- Kept losing DRMI, mostly due to mode hopping - this was because the green arm references hadn't been sdf'd. After resetting the refs to what they were yesterday we were good
- Huge 7.6 earthquake come through and kept us down for multiple hours. It was in the BIG RED BUTTON zone, so I pressed the Big Red Button™.

LOG:                                                                                                                                                                                                                                                                                                                                 

Start Time System Name Location Lazer_Haz Task Time End
15:12 FAC Chris MX, MY n FAMIS tasks 16:00
16:11 ISC Sheila LVEA YES Setting up measurement 16:23
17:15 EE Marc CER YES Checking signal for Richard 17:22
22:24 TCS Sophie CHETALab y(local) Aligning laser ongoing
23:15 ISC Keita, Alex LVEA Y Changing OMC measurement settings 23:23
LHO General
ibrahim.abouelfettouh@LIGO.ORG - posted 16:10, Friday 09 October 2026 (92267)
OPS Eve Shift Start

TITLE: 10/09 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Earthquake
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 17mph Gusts, 12mph 3min avg
    Primary useism: 0.12 μm/s
    Secondary useism: 0.17 μm/s 
QUICK SUMMARY:

IFO is back to locking after Panam M7.7 (and 6.6 aftershock).

We're getting to DRMI.

 

H1 SEI
arnaud.pele@LIGO.ORG - posted 15:57, Friday 09 October 2026 (92266)
Thresholds for rung up CRS

Oli, TJ, Arnaud

We used the earthquake down time opportunity to evaluate safe IMC thresholds for a rung up, in loop CRS. A threshold of 1urad rms at 25mHz seems safe for alerting the seismic nodes to take the CRS out of loop. We will have to verify those thresholds are not too conservative, and that they still work with a full ifo. 

For this test :

HAM2-HAM3 were set to their nominal blends (no sensor correction), and the CRS was put in loop for HAM3. The CRS was rung up to 80 urad pp, 28 urad rms, by flipping the sign of the CRS damping gain. We monitored the IMC stayed locked throughout (fig1). The mode cleaner controls (on MC2) reached at most +/- 50e6 out of the +/- 134e6 limit (less than half the total dac range). In comparison, the Panama earthquake from this afternoon (or the change of ISI state) rung up the CRS to +/- 2.2 urad, 1.5 urad rms (fig2). 

Images attached to this report
H1 ISC (IOO, OpsInfo)
elenna.capote@LIGO.ORG - posted 11:42, Friday 09 October 2026 - last comment - 16:52, Friday 09 October 2026(92264)
Summary of morning locking- thwarted by massive earthquake

Louis and I started morning locking once Oli re-re-ran initial alignments with the "correct" green camera offsets (ones set by the baffle scripts).

We got to DRMI ASC, and the SRC P error signals looked close to zero, so I tried engaging SRC1 and SRC2 P. However, we saw slow large oscillations that went away when the SRC P loops were turned off. I also saw that the alignment wasn't brought to the best buildups- I had to move SRM pitch more to maximize. I also reset the POP A offsets (SDF attached), which is a minor change but we have the best buildup now (ignoring the >200 buildup from last Friday)- POP18 is 167 and POP90 is 20. As an aside, I think we need to pico onto the POP QPD sled. The POP A offset required is very large, about 0.98 in both pitch and yaw. We're probably close to or falling off of POP A and the same is true for POP B. Perhaps we can lock DRMI, close PRC1 with the current offsets, let it converge, open the loop, turn off the offsets, and pico to bring the beam closer to the center of the QPDs.

I have now created separate "use DRMI ASC" flags for SRC1 and SRC2 pitch and yaw. The yaw flags are set to TRUE, and the pitch are set to FALSE. The ISC_DRMI guardian will now separately engage these loops in ENGAGE_DRMI_ASC. This means that only SRM and maybe SR2 pitch will need to be hand-adjusted for buildups in DRMI ASC. Tagging opsinfo.

Louis and I tried to go through TR CARM four times:

We're holding in down while this large earthquake passes.

I want to re-emphasize that we are still having trouble relocking the IMC after lockloss. The IMC will acquire lock, and the boost will kill it. This can get intense enough that the boost kicks the FSS which then kicks JAC. The only way around it is to either wait a really long time, or to hold the IMC guardian in acquire, wait a minute, and then engage boost. Doesn't always work, but can be faster than just waiting forever. Tagging IOO, someone needs to look into this boost.

 

Images attached to this report
Comments related to this report
elenna.capote@LIGO.ORG - 16:52, Friday 09 October 2026 (92269)

In the late afternoon, we returned to locking, and the guardian errored at DRMI locked check ASC, because the loop convergence checker uses the loops named in the use DRMI list, and due to my edit above it tried to check the convergence of "SRC1_P_Y". I don't know a good way around having a true/false bit for the p/y dofs of a particular dof, so my short term solution is to just have SRC1 and SRC2 set to TRUE, and I commented out the engagement of SRC1 P and SRC2 P in the engage DRMI ASC state, so only the yaw loops will come on.

H1 General
oli.patane@LIGO.ORG - posted 07:36, Friday 09 October 2026 - last comment - 09:05, Friday 09 October 2026(92260)
Ops DAY Shift Start

TITLE: 10/09 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    SEI_ENV state: SEISMON_ALERT
    Wind: 7mph Gusts, 4mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.16 μm/s 
QUICK SUMMARY:

Starting an initial alignment as requested

Comments related to this report
elenna.capote@LIGO.ORG - 09:05, Friday 09 October 2026 (92261)

When I came in this morning, Oli was having trouble locking DRMI even after the morning initial alignment, so I check what the green references actually were. They had not actually been reverted last night (92256, maybe they were reverted but not SDFed) so I did that. SDFs are attached. I have a feeling we're going to be doing green references multiple times today, so the file names are dated with an "_1".

Oli is now rerunning another initial alignment.

Images attached to this comment
LHO General
ibrahim.abouelfettouh@LIGO.ORG - posted 20:09, Thursday 08 October 2026 (92257)
OPS Eve Shift Summary

TITLE: 10/09 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: None
SHIFT SUMMARY:

IFO is in COMMISSIONING and FIND_IR

Overall a good shift where Louis and Elenna outlined the steps that worked to get to RESONANCE - alog 92254.

Instructions after they left were to run an initial alignment, which I did. I had some initial troubles with MICH_DARK since my first adjustment of the BS was not enough. After figuring that out, I was able to get all the way through. By this time, Louis came back on at around ENGAGE_DRMI_ASC and took over.

One weird thing is that the power would auto-jump to 10W after SRC_ALIGN was being offloaded. I may have clicked the LOWER_POWER guardian when we were stuck at 10W after MICH to see if it would go down to 2W (instead of going to the LASER_PWR guardian, but it doesn't seem to have worked and may have fudged the state ordering). Either way, SRC did actually offload. So after that, I set PWR back to 2W and started locking. This was fully auto.

LOG:

Start Time System Name Location Lazer_Haz Task Time End
15:39 TCS Camilla LVEA YES Looking for optic 15:55
16:02   Camilla LVEA YES Looking for phone 16:06
17:54 TCS Camilla, Sophie CHETAPrepLab y(local) CHETA work 19:26
18:03 VAC Gerardo, Jordan VACPrepLab n Looking for viewports 18:23
20:16 CDS Dave CER YES Looking for channels 20:40
20:39 TCS Camilla, Sophie CHETAPrepLab y(local) CHETA work 22:05
21:36   Richard EX,EY n Looking for phone numbers 22:07
22:08 OMC Keita, Alex LVEA YES OMC measurements 22:18
23:05 TCS Camilla, Sophie LVEA YES Turning on CHETA laser 23:55
23:06 PCAL Tony PCalLab y(local) Setting up PCAL measurement 23:59
H1 ISC (OpsInfo)
elenna.capote@LIGO.ORG - posted 16:58, Thursday 08 October 2026 - last comment - 21:56, Thursday 08 October 2026(92254)
Resonance achieved, some notes

We have achieved resonance, and could probably make it to carm analog. Unfortunately, the steps are not fully automated just yet. Here is a summary of how we are doing this:

I know Sheila had her own alog documenting our work for most of the day, but I don't see her post just yet.

I'm attaching the green camera SDF, and also the rephasing of RF36 that Louis and I did earlier.

Images attached to this report
Comments related to this report
louis.dartez@LIGO.ORG - 21:56, Thursday 08 October 2026 (92256)OpsInfo

notes on continuing to get back through to CARM_TO_ANALOG: 

- first try: lost lock at CARM_TO_TR
- I asked Ibrahim to run initial alignment for green
- asked Ibrahim to actually go ahead w/ full initial alignment while I moved to home office
- second try (first after running initial alignment): lost lock shortly after getting to CARM_OFFSET_REDUCTION before I was able to take a look at whether I should walk DHARD. 
- third try: lost in CARM_TO_TR
- fourth try: went to START_TR_CARM and lost it before getting a chance to take TR_CARM OLG measurement
- fifth: went to prmi_asc then back to ENGAGE_DRMI_ASC
- Sheila joins online
- also added oplev damping to guardian in ISC_LOCK.py:OFFLOAD_DRMI_ASC

 

- paused in DRMI 1F to adjust alignment, checked MICH OLG, OLG looked bad ... in the way that it often does when there are mode hopping problems. I didn't get a screenshot unfortunately.
- mode hopping problems are back. alignment is not great. we reverted the alignment back 4PM PDT using the restore button on IFO ALIGN Compact screen. This reverted the alignment for all the optics on the COMPACT IFO ALIGN medm screen I think.
- I reset the green camera references to what they were before Elenna updated them this afternoon. We're not sure what is wrong but suspect that the alignment got worse in the evening. 

 

Morning operator: We are leaving the IFO in DOWN. please run a full initial alignment when you get in.

 

 

sheila.dwyer@LIGO.ORG - 21:08, Thursday 08 October 2026 (92258)

Sheila, Elenna, Louis, Oli

This morning Elenna and Louis looked using AS36 for BS ASC.

I added a guardian state called SERVO_COMM offset, which looks at the TR_CARM inmon and servos the ALS COMM VCO tune offset to bring it close to 0.5.  I'm hoping this will help make the TR_CARM transition more reliable by making sure we start closer to the correct offset, it has worked (5 out of 6 times), we will see. 

We had several more locking attempts, stepping up the CARM offset reduction. 

Elenna engaged DHARD WFS by hand partway through the CARM offset reduction state, TR offset -12 I think.  We stepped up the REFFL BIAS gain in steps at TR_CARM of 40, rather than waiting for 52 as the guardian would have.  We lost lock going to TR_CARM of 50, although it looked like we had enough gain margin in TR_CARM.  

Next lock: Let guardian take us to DHARD WFS automatically.  PRCL ugf was about 30 Hz, we changed the input matrix to 4.12 to get the ugf to 52 Hz. stepped TR_CARM offset to -47, increased TR_CARM gain to 1.3 (guardian would have done -52 offset and 2.1 gain).  

Next lock:  Stepped TR_CARM offset to -48, increasing gain to 1.5 in steps as we increased.  We could then see that we were in range of the TR_REFL error signal, and measured the transfer function using the TR_CARM template.  We were able then to run through the CARM_TO_REFL and RESONANCE guardian states as written, but lost lock after 1 minute at resonance.  

Later this evening we've had difficulty, seemingly related to being in a different alignment (both mode hopping issues and trouble with TR_CARM).  

H1 DetChar (DetChar, EPO, VE)
keita.kawabe@LIGO.ORG - posted 16:52, Thursday 08 October 2026 - last comment - 09:38, Friday 09 October 2026(92253)
Return of ice-pecking raven

I was walking the overpath and heard hammering noise, and there it was, an ice-pecking raven. You can hear the sound as the guy pecks in the attached video (PXL_20261008_233238334TS~2.mp4, use headphone). I was shooting from the middle of the overpath slope, so it was kind of far but the noise was very much audible.

Thick layer of ice formed around the LN2 pipe, see picture (PXL_20261008_233616363MP.jpg).

Images attached to this report
Non-image files attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 17:09, Thursday 08 October 2026 (92255)

For those who have not seen it, please look back to alog 37646 for Andy's seminal poem on this topic.

jeffrey.kissel@LIGO.ORG - 09:38, Friday 09 October 2026 (92262)PEM
Tagging the PEM team, whom had originally discovered the issue.
H1 General
oli.patane@LIGO.ORG - posted 16:44, Thursday 08 October 2026 (92252)
Ops DAY Shift End

TITLE: 10/08 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: Commissioners have done a great job getting us up to RESONANCE. 

I had some issues in the morning with ALS but we didn't have any issues after that. Relocking has been really fast and smooth.
LOG:                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              

Start Time System Name Location Lazer_Haz Task Time End
15:39 TCS Camilla LVEA YES Looking for optic 15:55
16:02   Camilla LVEA YES Looking for phone 16:06
17:54 TCS Camilla, Sophie CHETAPrepLab y(local) CHETA work 19:26
18:03 VAC Gerardo, Jordan VACPrepLab n Looking for viewports 18:23
20:16 CDS Dave CER YES Looking for channels 20:40
20:39 TCS Camilla, Sophie CHETAPrepLab y(local) CHETA work 22:05
21:36   Richard EX,EY n Looking for phone numbers 22:07
22:08 OMC Keita, Alex LVEA YES OMC measurements 22:18
23:05 TCS Camilla, Sophie LVEA YES Turning on CHETA laser 00:05
23:06 PCAL Tony PCalLab y(local) Setting up PCAL measurement 00:06
H1 ISC
camilla.compton@LIGO.ORG - posted 10:43, Thursday 08 October 2026 - last comment - 05:39, Friday 09 October 2026(92245)
WIP Table of Buildups before and after BS swap, with and without arms.

Sheila, Louis, Elenna, Camilla. Follow on from 92167. 

Louis made this Googledoc. It incudes a table of Powers before and after BS swap, with and without arms. It shows that we now have a higher ratio of powers on POP ports with the arms that without the arms that we used to have in O4. 

There’s still work done on this and finding better comparism times, but see attached table for arms vs no arms ratios. 

Images attached to this report
Comments related to this report
evan.hall@LIGO.ORG - 05:39, Friday 09 October 2026 (92259)MDL/SIM

Focusing only on measurements from O4 till now (ignoring everything before 2023) and only on POPAIR B:

  • The observed power ratios RF18 / LF and RF90 / LF in each configuration don't actually show any change from O4 till now. For PRMI, RF18 / LF ~ 10 and RF90 / LF ~ 8–9. For DRMI, RF18 / LF ~ 17. For DRMI with antiresonant arms, RF90 / LF ~ 2.5. (The single measurement of DRMI without arms has RF90 / LF ~ 2.0.)
  • For PRMI, switching from no arms to antiresonant arms should raise both the carrier power and the 9 MHz power by a factor of 2.2, theoretically (91738). It seems hard to explain the observed factor of 4 just due to a change in the cavity configuration, rather than something like POP path clipping.

I ignored the 2019 and 2020 measurements, which aren't consistent with the later ones, including having very different ratios of RF90 / RF18 (some configuration/electronics change?).

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