Displaying reports 741-760 of 83117.Go to page Start 34 35 36 37 38 39 40 41 42 End
Reports until 10:33, Thursday 05 June 2025
LHO VE
david.barker@LIGO.ORG - posted 10:33, Thursday 05 June 2025 - last comment - 15:10, Thursday 05 June 2025(84814)
Thu CP1 Fill

Thu Jun 05 10:09:05 2025 INFO: Fill completed in 9min 2secs

 

Images attached to this report
Comments related to this report
david.barker@LIGO.ORG - 15:10, Thursday 05 June 2025 (84831)

TC-A stayed cold (<-80C) after the fill. I knocked an ice ball off the end of the discharge line which seems to have done the trick.

H1 SEI
anthony.sanchez@LIGO.ORG - posted 08:30, Thursday 05 June 2025 (84813)
H1 ISI CPS Noise Spectra Check - Weekly

FAMIS H1 ISI CPS Sensor Noise Spectra Check - Weekly 26045
This CPS noise check doesn't include HAM1 yet.

 

Non-image files attached to this report
LHO General
ibrahim.abouelfettouh@LIGO.ORG - posted 07:46, Thursday 05 June 2025 (84812)
OPS Day Shift Start

TITLE: 06/05 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 11mph Gusts, 6mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.13 μm/s
QUICK SUMMARY:

IFO is in DOWN and PLANNED ENGINEERING

This morning we have vacuum going into the LVEA to find out which annulus on the HAM1 doors is leaking (WP 12591). TJ is transitioning LVEA to laser safe for this (WP 12590). Commissioning will then resume.

H1 General (ISC)
oli.patane@LIGO.ORG - posted 22:18, Wednesday 04 June 2025 - last comment - 13:46, Thursday 05 June 2025(84811)
Ops Eve Shift End

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

Just put the IFO in DOWN for the night after losing lock from ENGAGE_ASC_FOR_FULL_IFO. I was having trouble all evening getting DRMI to stay locked - we kept losing lock from the 16.2 Hz oscillation that Craig and Elenna had found yesterday (84769). I have no idea why it's only been appearing in the evenings - yesterday evening we had these issues, then this morning no issues at all, and then this evening issues again!! I would lose lock from it anytime after ENGAGE_DRMI_ASC, but even just in DRMI_LOCKED_PREP_ASC, the oscillation was there, just not ringing up.

One of the times I was able to get DRMI to lock, I stayed in DRMI_LOCKED_PREP_ASC and took MICH, PRCL, and SRCL OLG measurements. Later on, Sheila called and figured out it must be due to the MICH gain being too high, so I lowered MICH2 gain, originally at 1, by 30% to 0.7. After doing that, the 16 Hz oscillation went away (diaggui) and we were able to get through DRMI. Sheila said we probably needed that gain back to 1 for DRMI_TO_POP, so I paused at RESONANCE, reset the MICH2 gain to 1, and then continued. We lost lock during ENGAGE_ASC_FOR_FULL_IFO.

So the MICH2 gain is currently at its original gain of 1.

Evening task progress for today:

LOG:

23:30 Sitting in NOMINAL_LOW_NOISE while tests are being run
00:32 Started BB calibration measurement
00:37 BB measurement done
00:38 Lockloss due to earthquake
    - started a manual initial alignment
        - tried to leave SCAN_ALIGNMENT for UNLOCKED and got a Guardian node error about the time being in the past - had to manual before reloading to get out of it (txt)
    - After the initial alignment was done, I relocked SRY and left it there for a while while Vicky and Kevin worked on SQZ stuff
    02:24 Lockloss from ENGAGE_DRMI_ASC due to the 16.2 Hz oscillation (84769)
    02:37 Lockloss from TURN_ON_BS_STAGE2 due to the 16.2 Hz oscillation
        - I paused in DRMI_LOCKED_PREP_ASC and adjusted SRM to make POP look better, then went into ENGAGED_DRMI_ASC. We had an oscillatoni start, but we were able to survive it. Then I went into TURN_ON_BS_STAGE2 and we immediately lost lock
    03:24 Lockloss from ACQUIRE_DRMI_1F while trying to acquire. We had gotten it earlier and I stayed in DRMI_LOCKED_PREP_ASC and took MICH, PRCL, and SRCL OLG measurements, but we lost DRMI when I aborted the SRCL measurement and we weren't able to grab it again
    03:40 Lockloss from ACQUIRE_DRMI_1F
    - Ran another initial alignment
    04:20 Lockloss from TURN_ON_BS_STAGE2 due to the 16.2 Hz oscillation
    04:31 Lockloss from ENGAGE_DRMI_ASC due to the 16.2 Hz oscillation
    - Sheila called, I lowered MICH2 gain (originally at 1) by 30% to 0.7, then the 16 Hz oscillation went away and we were able to get through DRMI
    - Paused at RESONANCE, reset the MICH2 gain to 1, and then continued
    04:58 Lockloss from ENGAGE_ASC_FOR_FULL_IFO

Start Time System Name Location Lazer_Haz Task Time End
00:44 VAC Gerardo LVEA YES Moving a ladder by HAM4 01:21
Images attached to this report
Comments related to this report
oli.patane@LIGO.ORG - 13:46, Thursday 05 June 2025 (84821)GRD

I forgot to actually attach the text file for the ALS_XARM error I got last night, so here it is

Non-image files attached to this comment
H1 General
oli.patane@LIGO.ORG - posted 19:23, Wednesday 04 June 2025 (84810)
Ops EVE Midshift Update

After losing lock earlier due to an earthquake, we went through an initial alignment. After that had finished, I put the ifo back into SRY so that they could calibrate the ADF. They finished that a bit ago, and after touching up SRC1 and rerunning the SRC alignment, we are now starting to relock.

H1 CAL
oli.patane@LIGO.ORG - posted 18:12, Wednesday 04 June 2025 - last comment - 10:44, Friday 06 June 2025(84808)
(Incomplete) Calibration Measurements June 5th, 2025

I was only able to take the broadband measurement due to an earthquake that knocked us out of lock a minute later. We had been at full power for around 5 hours at the time this measurement was run. Unfortunately since we weren't able to take the Simulines measurements, I am not able to run the report.

Broadband:

Start time: 1433118749 (2025-06-05 00:32:11 UTC)

End time: 1433093874 (2025-06-05 00:37:36 UTC)

Data found in: /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250605T003226Z.xml

Images attached to this report
Comments related to this report
elenna.capote@LIGO.ORG - 11:01, Thursday 05 June 2025 (84815)

Attached the screenshot of the broadband measurement as a quick reference for us before we have a chance to take the full measurements.

Images attached to this comment
elenna.capote@LIGO.ORG - 10:44, Friday 06 June 2025 (84862)

I added GDS CALIB to this plot from the same time.

Images attached to this comment
H1 ISC
matthewrichard.todd@LIGO.ORG - posted 17:42, Wednesday 04 June 2025 - last comment - 11:09, Thursday 05 June 2025(84809)
IMC refl-trans-wfs comparisons before and after vent

M. Todd, C. Cahillane, G. Mansell


We're curious if any of the IMC WFS channels (DC and RF) are seeing some of the peaks we witness in DARM. Most of the sensors seem dominated by phase noise due to being in air; IMC-TRANS seems the best witness. Not sure if there is anything meaningfull from these, indicating coherence with the DARM peaks.

List of Figures: references are from March 12th, 2025 -- lives are from June 4th, 2025

1. IMC REFL and TRANS PSD estimate comparison before (March 12, 2025) and after vent (June 4, 2025)
2. IMC WFS A/B DC/RF-I PITCH
3. IMC WFS A/B DC/RF-I YAW

 

The template to measure these again is found at /ligo/home/matthewrichard.todd/Templates/imc/imc_wfs_comparison.xml

Images attached to this report
Comments related to this report
craig.cahillane@LIGO.ORG - 11:09, Thursday 05 June 2025 (84816)
It seems like the summary of this is "input beam jitter was never good, but is worse now than in March 2025", especially at 500 Hz in IMC_REFL and IMC_WFS_DC.

H1 ISC
elenna.capote@LIGO.ORG - posted 17:16, Wednesday 04 June 2025 (84807)
LSC feedforward updated

I ran an iterative tuning of the LSC feedforward today. The feedforward was already decent, but there was some room for improvement. The two attached screenshots compare injections from the new feedforward fit and the old fit. The only place to pay attention to moving forward is the high frequency coupling of SRCL, which may be effected by the large SRCL offset measured (and potentially corrected) today. If we see any >100 Hz noise coupling from the LSC, maybe we can do another iterative fit. I also injected in PRCL and the noise coupling has not changed, so the previous feedforward is just fine.

The new filters are in FM7 for both MICHFF and SRCLFF, and I updated the guardian.

Images attached to this report
H1 SQZ
camilla.compton@LIGO.ORG - posted 17:06, Wednesday 04 June 2025 - last comment - 13:42, Thursday 05 June 2025(84794)
SQZ FIS SRC Detuning Dataset

Vicky, Sheila, Kevin, Camilla

Followed plan outlined in 84762 apart from after each SRCL offset change we moved sqz angle roughly close to max sqz to allow SCAN_SQZANG_KHZ enough range to optimize sqz.
After each 3 minutes of data, Kevin and Vicky took a ADF scan.

Increased NLG (needed to adjust SHG waveplate) by taking OPO trans setpoint from 95uW up to 120uW. Measured NLG = 49 (numbers below) following 76542.

Sheila's fitting found that the SRCL  offset (H1:LSC-SRCL1_OFFSET) needed to get a zero degree SRC detuning is -455 counts. Have not accepted in sdf, Sheila added to ISC_LOCK.
Finally we went to FDS and adjusted FC detuning from -34 to -24.

Data attached and saved at /ligo/home/camilla.compton/Documents/sqz/templates/dtt/20250607_SRCdetuning.xml

Type Time (UTC) SRCL Angle DTT Ref
No SQZ 21:37:00 - 21:43:00 N/A N/A ref 0
FIS 22:17:30 - 22:30:30 -191 (CLF-) 242 ref1
FIS 22:35:00 - 22:38:00 -90 (CLF+) 120 ref2
FIS 22:49:30 - 22:52:30 0 (CLF+) 172 ref3
FIS 23:17:00 - 23:20:00 -390 (CLF-) 161 ref4
FIS 23:45:00 - 23:48:00 -455 (CLF-) 143 ref5
FDS ~ 00:00:30 -455 (CLF-) 143 ref6

Note that I left the OPO servo gain at -8, but we have previously left it there (83569) or used -12dB for 120uW OPO trans (83370)

opo_grTrans_ setpoint_uW Amplified Max Amplified Min UnAmp Dark NLG (usual) OPO Gain
120 0.018035 0.000119507 0.000316548 -2e-5 48.9 -8
Images attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 13:42, Thursday 05 June 2025 (84806)

Here are the plots of this dataset, showing that our SRCL detuning (in gwinc) would be 50 mrad with no digital offset in the SRCL loop.  Kevin tells us that this is a double passed SRCL detuning, so it's really 25 mrad, 1.4 degrees of SRCL detuning. 

Edited to add the last point (and have the correct plots).

Images attached to this comment
LHO General
ibrahim.abouelfettouh@LIGO.ORG - posted 16:39, Wednesday 04 June 2025 (84804)
OPS Day Shift Summary

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

IFO is in NLN_CAL_MEAS and PLANNED ENGINEERING

Extremely productive day in which we got to Nominal Low Noise for the first time in two months!

Very briefly, here's what we did today:

Relevant alogs:

alog 84800: low range coherence checks

alog 84798: a2l optimized pre-NLN

alog 84796: IM4 and MC2 TRANS

There are undoubtedly more in-progress alogs about work done today.

LOG:

Start Time System Name Location Lazer_Haz Task Time End
15:30 LASER LASER HAZARD LVEA LASER HAZARD LVEA IS LASER HAZARD (\u2310\u25a0_\u25a0) 07:26
14:39 FAC Herc Lift Lift MX N Lifting a lift 15:05
17:11 FAC Randy MX N Inventory 20:10
17:29 VAC Travis MY N Checking storage space 17:44
20:54 AOS Jeff, Jordan Optics Lab Local SPI Collimator 21:06
20:55 VAC Travis MY N Inventory 20:55
H1 General
oli.patane@LIGO.ORG - posted 16:19, Wednesday 04 June 2025 (84801)
Ops Eve Shift Start

TITLE: 06/04 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 19mph Gusts, 10mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.14 μm/s
QUICK SUMMARY:

Currently we are sitting in NOMINAL_LOW_NOISE and people are working on measuring and updating various things.

H1 ISC
ibrahim.abouelfettouh@LIGO.ORG - posted 16:17, Wednesday 04 June 2025 (84800)
Low Range Coherence Check

Ibrahim

Ran a low range coherence check to better understand H1 range and its effects right before NLN. Screenshot of result attached.

Images attached to this report
H1 ISC
ibrahim.abouelfettouh@LIGO.ORG - posted 16:16, Wednesday 04 June 2025 (84798)
A2L All Run

Camilla, Ibrahim

Ran A2L before NLN to maxmimize range.

We had to run the a2l script a few times for all QUADs. The first two times, there was no change in gain because the required change vin gain was too much for the script to apply (a safety feature I'm sure). Camilla and I then stepped the gain in the right direction until we were sure that it would be within the adjustability of the script. It took two more runs in order to finally get the range maximized. This improved the range by about 20 MPc. Screenshots attached (the screenshot named initial is before manual stepping).

Images attached to this report
H1 ISC
matthewrichard.todd@LIGO.ORG - posted 16:13, Wednesday 04 June 2025 (84797)
Looking at LSC-REFL_A_RIN at different thermal states

M. Todd, C. Cahillane


We are looking at the RIN in LSC-REFL_A to try and understand if there are some cavity dynamics that can give an estimate of the power recycling cavity mode-matching to the arms (for some more background, see Daniel's alog 70985)

I've made a plot that shows some interesting changes in the REFL_RIN asd as a function of thermal state. In particular I've looked at the asd at 4 different times as we thermalize after locking and stabilize the ISS.

There's some very interesting dynamics around 5-50 Hz. For the HF dynamics, I've also plotted the shot-noise limit based on that time's DC REFL_A_LF power; which I think is the limit in that frequency regime.

I've put both the dtt plot as well as my own plot that used quick_psd.


Next, I would like to model what RIN we would expect in that frequency band and compare to these measurements, specifically if this is intensity noise coupling changes due to mode mismatch changes during thermalization.

Images attached to this report
Non-image files attached to this report
H1 AOS
craig.cahillane@LIGO.ORG - posted 16:00, Wednesday 04 June 2025 - last comment - 17:39, Wednesday 04 June 2025(84796)
IM4 and MC2 TRANS now
Looking at IM4 and MC2 trans, we see that the amount of power on MC2_TRANS and IM4_TRANS has decreased by around 1%.
The plot shows a time in March 12, 2025, with white dashed lines where those values are now on June 04, 2025.
The IM4_TRANS calibration was fixed after the HAM1 work in alog 82260.

The PRG is around 3% higher now, going from 52.2 to 53.9.
The PRG calculation already incorporates this apparent 1% fall in IM4_TRANS.
Matt Todd checked the PRG at 2W in alog 84668.

As far as alignment, MC2_TRANS is servoed to zero by the input PZT using IMC ASC DOF3, so that is "unchanged".
IM4_TRANS has drifted only a small amount, from 0.1 to 0.2 in PITCH, and -0.04 to -0.10 in YAW.

This is all loosely consistent with the small changes in input pointing we've seen in the ISS array pointing seen in alog 84728.
Keita noticed that the SEG3 on the ISS QPD is totally saturated at -32768 cts due to the misalignment onto that PD, so it becomes even harder to trust the ISS QPD reference.

We have not yet closed the ISS secondloop as a part of the locking sequence, so we don't know if the beam jitter coupling to DARM problem will get worse when we close this loop.
I reckon there is a very high likelihood that it will.

Keita had more suggestions, including
1) injecting into the IMC and checking coherence between IMC WFS and the ISS array and DARM (Mr. Todd has already started this analysis alog 84775).
2) moving the input pointing into the array in PITCH and YAW and checking the PHASE between each individual array diode, maybe via line injection, to see if there is any cancellation happening, or if some diodes are more susceptible to misalignments
3) far future: change around plugs for INNER and OUTER so that the INNER diodes are the most stable, best-aligned ones.  This could improve our overall beam jitter coupling, if we think it's coupling via the intensity loop.
Images attached to this report
Non-image files attached to this report
Comments related to this report
elenna.capote@LIGO.ORG - 16:26, Wednesday 04 June 2025 (84803)

Trending back to a recent 2W lock, our PRG is a bit too high, nearing 60 when Matt has recently measured it to be 55.6. I added a gain correction factor to the PRG bank of 0.93 to account for this, in FM4. This makes our current 60 W locked PRG about 50!

craig.cahillane@LIGO.ORG - 17:39, Wednesday 04 June 2025 (84805)
I checked out the individual diodes on the array to see if they have different responses to beam jitter.
It seems like Keita's intuition was correct.

ISS array PDs 2, 3, 5, and 7 have significantly higher intensity noise at 3.5 Hz, 2.0 Hz, 1.1 Hz, and 0.15 Hz.
These frequencies correspond to some HSTS suspension resonances for YAW in particular.
Most likely is we are clipping somewhere on the path to the ISS array for only a few of these diodes.

There is also some improvement in the diode noise at around 330 Hz, 380 Hz, and 960 Hz.  

PDs 1, 4, 6, and 8 are better performing.  Out of those, we still see some beam jitter, just significantly reduced.
PDs 1, 4, 6, and 8 are better for both low and high frequency motion, which is consistent with clipping.

Jennie Wright will post a picture of the ISS array itself, but she believes the diodes are arrayed like

5 6 7 8
-   - 
1 2 3 4
  - - 
 
when looking from the back of the array where the cables are coming out.
The underlined diodes are the "bad" diodes.  
Seems to not be totally sensible as an overall DC YAW adjustment, which is consistent with our attempts to align onto this array. 

To reproduce this PSD plot, run
quick_psd H1:PSL-ISS_SECONDLOOP_PD?_OUT_DQ -t1 1433112446 -d 3600 -b 0.01 

on a CDS machine.
Non-image files attached to this comment
H1 ISC
matthewrichard.todd@LIGO.ORG - posted 10:44, Friday 30 May 2025 - last comment - 16:21, Wednesday 04 June 2025(84668)
PRG Estimation 2025-05-30

M. Todd, C. Cahillane, S. Dwyer


I ran another estimate of the PRG, following Craig's method in alog  58327, and estimate it to be around 54.2 W/W.


I compared the TRX power to Input Power ratio during the FIND_IR state versus the PREP_ASC_FOR_FULL_IFO state, with the PRM transmission as a normalization factor.

                       TRX_POWER_FULL_IFO  /  INPUT_POWER_FULL_IFO
PRG   =    -------------------------------------------------------------------------------------
                     TRX_POWER_FIND_IR   /  (Tp  * INPUT_POWER_FIND_IR)

I've attached the quick script I've used for the interesed reader.

Non-image files attached to this report
Comments related to this report
matthewrichard.todd@LIGO.ORG - 12:25, Sunday 01 June 2025 (84700)

I reran this measurement during DARM_TO_DC_READOUT (GRD-ISC = 501, input power = 2W), comparing the input and TR-X powers during the previous FIND_IR state (GRD-ISC = 16, input power = 2W). And I got a post vent PRG of  55.6 W/W. (post-vent)

I reran this estimate for the same states, before the vent (FIND_IR = 1427488687, DARM_TO_DC_READOUT =1427490018) and got a PRG of 55.7 W/W. (pre-vent)

It's interesting that we estimate almost the exact same PRG pre and post vent, though we may be able to improve this post vent value (probably not drastically) with some ASC improvements. We wanted to get this estimate to just check that everything is in general order in HAM1 after the vent.

Non-image files attached to this comment
elenna.capote@LIGO.ORG - 16:16, Wednesday 04 June 2025 (84799)

I think our PRG channel calibration needs updating. Matt's measurement agrees with mine: that the PRG is about 54 when we are at 2 W of power. However, at 2 W it is currently reading 60, which is wrong, possibly due to slightly less power on IM4 trans. I will add a correction factor in FM4 of our "LSC_PR_GAIN" bank, 55.6/59.8 = 0.93.

matthewrichard.todd@LIGO.ORG - 16:21, Wednesday 04 June 2025 (84802)

I checked what the PRG was according to the calibration channel H1:LSC-PR_GAIN_OUT16 during the same time that I used for my measurement of the post-vent PRG (1432694134) and it is off by roughly a factor of 8%.

The calibration channel reports a PRG of roughly 59.9; I've measured it to be 55.5. We may benefit from some re-calibration.

Images attached to this comment
Displaying reports 741-760 of 83117.Go to page Start 34 35 36 37 38 39 40 41 42 End