Displaying reports 721-740 of 80463.Go to page Start 33 34 35 36 37 38 39 40 41 End
Reports until 16:03, Saturday 04 January 2025
H1 General
ryan.crouch@LIGO.ORG - posted 16:03, Saturday 04 January 2025 - last comment - 16:28, Saturday 04 January 2025(82115)
OPS Saturday EVE shift start

TITLE: 01/05 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.36 μm/s
QUICK SUMMARY:

Comments related to this report
ryan.crouch@LIGO.ORG - 16:28, Saturday 04 January 2025 (82118)SQZ

"pump fiber rej power in ham7 high, align fiber pol on sqt0" notification on SQZ_OPO_LR

H1 General (Lockloss)
oli.patane@LIGO.ORG - posted 14:51, Saturday 04 January 2025 - last comment - 16:48, Saturday 04 January 2025(82114)
Lockloss

Lockloss @ 01/04/25 22:50 UTC after 18.5 hours locked. Not sure of the cause yet.

Comments related to this report
ryan.crouch@LIGO.ORG - 16:48, Saturday 04 January 2025 (82120)

00:46 UTC Observing

H1 General
oli.patane@LIGO.ORG - posted 14:08, Saturday 04 January 2025 (82113)
Ops Day Midshift Update

Currently Observing at 161 Mpc and have been Locked for almost 18 hours. Nothing to note.

H1 CAL
oli.patane@LIGO.ORG - posted 12:05, Saturday 04 January 2025 (82112)
Calibration Measurements January 04, 2025

Calibration measurements taken during the regular Saturday calibration time. We had been locked for over 15 hours at the time of starting the measurements.

Calibration monitor screen

Broadband (01/04/2025 19:32:45 - 19:38:06 UTC)

../PCALY2DARM_BB/PCALY2DARM_BB_20250104T193245Z.xml

Simulines (01/04/2025 19:40:14 - 20:03:20 UTC)

../DARMOLG_SS/DARMOLG_SS_20250104T194014Z.hdf5
../PCALY2DARM_SS/PCALY2DARM_SS_20250104T194014Z.hdf5
../SUSETMX_L1_SS/SUSETMX_L1_SS_20250104T194014Z.hdf5
../SUSETMX_L2_SS/SUSETMX_L2_SS_20250104T194014Z.hdf5
../SUSETMX_L3_SS/SUSETMX_L3_SS_20250104T194014Z.hdf5

Images attached to this report
LHO VE
david.barker@LIGO.ORG - posted 10:25, Saturday 04 January 2025 (82111)
Sat CP1 Fill, manual cancel

Sat Jan 04 10:19:24 2025 ALERT: Fill done (errors) in 19min 20sec

TC-A started high again (+25C) and didn't quite reach the -60C trip, it flatlined at -58C, so I manually cancelled the fill. Discharge line pressure suggests it was a good fill.

OAT (-0.6C, 31F)

Trip has been increased to -50C for tomorrow's fill.

 

Images attached to this report
H1 General
oli.patane@LIGO.ORG - posted 07:39, Saturday 04 January 2025 - last comment - 07:42, Saturday 04 January 2025(82108)
Ops Day Shift Start

TITLE: 01/04 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 0mph Gusts, 0mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.43 μm/s
QUICK SUMMARY:

Currently Observing and have been Locked for 11.5 hours. Secondary microseism is high at the 90th percentile but holding steady, and wind is low. Super foggy and icy outside on the roads out here and there's snow on Laliik (Rattlesnake Mountain)!

Comments related to this report
oli.patane@LIGO.ORG - 07:39, Saturday 04 January 2025 (82109)

15:38 UTC Just dropped out of Observing due to the SQZer unlocking

oli.patane@LIGO.ORG - 07:42, Saturday 04 January 2025 (82110)

15:42 UTC Back to Observing - SQZer relocked by itself

H1 General (SEI)
ryan.crouch@LIGO.ORG - posted 22:00, Friday 03 January 2025 (82106)
OPS Friday EVE shift summary

TITLE: 01/04 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 162Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY: 1 lockloss from an earthquake, easy re-lock.
LOG: No log.

We've been locked for almost 2 hours, we lost the long lock to an earthquake.  Relocking was straight forward but took longer due to the high 2ndary motion.

Images attached to this report
H1 General (Lockloss)
ryan.crouch@LIGO.ORG - posted 18:16, Friday 03 January 2025 - last comment - 20:23, Friday 03 January 2025(82105)
02:15 UTC lockloss

02:15 UTC lockloss, likely due to a 5.8 from Ethiopia.

Comments related to this report
ryan.crouch@LIGO.ORG - 20:23, Friday 03 January 2025 (82107)

04:21 UTC Observing

H1 ISC
jim.warner@LIGO.ORG - posted 16:37, Friday 03 January 2025 (82103)
ETM glitch locklosses probably can't be fixed by adding ESD low pass

I have been trying to see if ETM glitches can be reduced by increasing the ~1khz roll off of the ESD, but it seems like this is no the route. I wasn't able to find a filter that would reduce the amplitude of some typical glitches and not adversely affect the phase of DARM at the UGF. The idea was to add a low pass at the output of the L3 drive, but it doesn't seem like this will work.

I got 3 seconds of ESD drive data for one of the locklosses which had several glitches shortly before the lockloss. I then looked at how the time series for those ESD glitches changed when I added various lowpasses using lsim in matlab. First attached bode plot shows 2 filters, red trace (filter2) is a way too aggressive filter, blue (filter1) is something that would probably allow DARM to stay stable but only maybe help a little.

Second plot is a timeseries showing the effects of the 2 filters on one of the glitches in the data I looked at. Yellow is the drive sent to one of the esd quadrants, red is the glitch after applying the unstable filter2 from the first plot, blue is with the less aggressive filter1. Even with the unstable filter the magnitude of the glitch isn't really reduced a ton. The phase margin at ~80hz for DARM is about 30 deg, the blue filter reduces this by about 6 degrees.

Sheila and I have talked about other approaches to make the IFO more robust to these glitches, we'll take a look at that next week.

Images attached to this report
H1 General
oli.patane@LIGO.ORG - posted 16:32, Friday 03 January 2025 (82104)
Ops Day Shift End

TITLE: 01/04 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Currently Observing and have been Locked for almost 45 hours. Nothing to note for today's shift.
LOG:

none

 

H1 General
ryan.crouch@LIGO.ORG - posted 16:03, Friday 03 January 2025 (82102)
OPS Friday EVE shift start

TITLE: 01/03 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 14mph Gusts, 8mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.43 μm/s
QUICK SUMMARY:

H1 SQZ
sheila.dwyer@LIGO.ORG - posted 14:37, Friday 03 January 2025 (82097)
Squeezer data set and comparison to quantum noise model

This is an update on the quantum noise compairson to models started in 80747.  Apoloiges for the large numer of plots.  The main message is that we have a decent model of the quantum noise from October (see this and this plot ) can get a fairly independent constraint on homodyne angle and SRC detunings from these squeezer data sets without the filter cavity, and some loose estimates for arm power based on squeezer losses.  There is a discrepancy between the model and the data in the traces taken near anti-squeezing without the filter cavity that is interesting, and I haven't tried to model mode mismatches yet.

Outline of how this model is made:

The first two attachments show data from mid October (80664), separated into two different plots (one with mid squeezing, one with +/-10 degrees from sqz and a sqz) to make it easier to read.  We can look at the mid and low frequencies to help us constrain the model for homodyne angle, SRC detuning, and maybe mode matching and FC parameters.  With the filter cavity, the traces that are +/- 10 degrees from squeezing and anti-squeezing don't provide much information, we can probably skip these in future data sets, but the ones +/-10 degrees from anti-squeezing without the filter cavity are interesting.

Arm power: We can get some constraints on arm power by assuming that all of our unknown loss is injection loss, or all readout loss, this gives us a range of 327kW-381kW with a homodyne angle of 10.8 degrees and no SRC detuning.  Attached are plots made for the high and lower power models, by clicking back and forth you can see that the lowest powers seem to disagree with the low frequency data, implying that some of our unknown losses truly are readout losses, but this isn't a very precise way to estimate arm power.

SRC detuning: Without the filter cavity, the mid squeezing traces are most clearly sensitive to SRC detuning, shown in this attachment where the SRC detuning of 0.057 degrees is clearly too large. You can flip through these 5 SRC plots which suggests that our SRC detuning at the time of these measurements was between 0 and -0.057 degrees (I'll leave it at -0.029 degrees, or -1mrad in the model) . 

Homodyne angle: In 80747 we noticed that anti-squeezing without the filter cavity is very sensitive to the homodyne angle, and that we've been using the wrong sign for our modeling in O4.  Here are plots that reaffirm that the negative homodyne angle is wrong, with mid squeezing (as we did in 80747) and with squeezing angle +/-10degrees from squeezing and anti-squeezing, which also clearly shows the problem for those traces near anti-squeezing.  It's also nice to notice that the mid sqz traces aren't especially sensitive to homodyne angle in the mid frequency range taht we were using to set the SRC detuning, so this data set without the filter cavity can give us fairly independent constraints on SRC detuning and homodyne angle.  Here is a plot of the homodyne angle of 10.7 degrees (based on 71913), without the squeezing traces so that it's easier to see what's happening.  There is a large discrepancy between the model and FDAS -10 degrees, from 30-55Hz, and there is also a smaller discrepancy for FDAS+10 degrees in this frequency range. This discrepancy can be redcued a bit by making the homodyne angle larger, but that doesn't seem to be a good model of the data, so this discrepancy is probably due to something we aren't modeling correctly here.

Filter cavity detuning:  We have used -33Hz as the filter cavity detuning, but data from mid squeezing with the filter cavity suggests that the detuning in this data set closer to 27 Hz. Here is a series of plots to show how mid sqz is sensitive to FC detuning.

The last two plots are with the final model paramters, it is a reasonably good description of the data, with the main discrepancy remaining in the anti-squeezing without the filter cavity.  The scripts, parameters and data used to make these plots is in quantumnoisebudgeting commit 92f7e965.  The quantum noise paramters used are here.

Non-image files attached to this report
H1 General
oli.patane@LIGO.ORG - posted 12:03, Friday 03 January 2025 (82101)
Ops Day Midshift Update

Currently Observing at 155 Mpc and have been Locked for 40 hours now. Secondary microseism is high but not increasing any more and the wind has been going down the past few hours.

LHO VE
david.barker@LIGO.ORG - posted 10:50, Friday 03 January 2025 (82099)
Fri CP1 Fill

Fri Jan 03 10:10:00 2025 INFO: Fill completed in 9min 57secs

Gerardo confirmed a good fill curbside.

Images attached to this report
H1 ISC (Lockloss)
camilla.compton@LIGO.ORG - posted 09:35, Friday 03 January 2025 (82092)
Around 15%+ of NLN locklosses are tagged ETM_GLITCH

Oli, Camilla, Sheila.

We reran all lockloss events from 22nd November (PSL swap) with the improved ETM_GLITCH code MR#143. Oli has found that even with this improved tag, some locklosses with small glitches or a glitch just before the lockloss are being missed, e.g. 1419179528, 1419158677. It's possible that sometimes we loose lock on the first glitch so don't tag it.  Jim is looking into a filter that could reduce this: 81589.

We've had 73 locklosses from Observe, of these: 11 tagged ETM_GLITCH, 10 tagged EARTHQUAKE. 

H1 SQZ
sheila.dwyer@LIGO.ORG - posted 10:48, Thursday 02 January 2025 - last comment - 11:35, Friday 03 January 2025(82082)
running psams script

Ryan Short, Sheila

We've followed Camilla's suggestion to run the PSAMs scan script with a smaller step size.  814908

In userapps/sqz/h1/scripts/SCAN_PSAMS.py I've edited lines 267 and 269 so that     PSAM_ZM4_LIST = [5.6, 5.7, 5.8, 5.9, 6, 6.1, 6.2, 6.3, 6.4]     PSAMS_ZM5_LIST = [-0.7, -0.6, -0.5, -0.4, -0.3, -0.2, -0.1]  .  We will let this run until noon, and see how many points it gets. 

Comments related to this report
sheila.dwyer@LIGO.ORG - 11:51, Thursday 02 January 2025 (82086)

The script ran for a while then had an error, so we got some of this data (see attachment).  The error is probably due to the way I edited the lists.

Traceback (most recent call last):
  File "/opt/rtcds/userapps/trunk/sqz/h1/scripts/SCAN_PSAMS.py", line 415, in <module>
    PSAMS_scan(freq, cycle, amp_SQZANG, dT_ZM4, dT_ZM5, amp_sus)
  File "/opt/rtcds/userapps/trunk/sqz/h1/scripts/SCAN_PSAMS.py", line 361, in PSAMS_scan
    _best_sqz, sqz_angle = _sweep(ii,jj,fig,axs,dirname,zm4,zm5,'ZM4')
  File "/opt/rtcds/userapps/trunk/sqz/h1/scripts/SCAN_PSAMS.py", line 287, in _sweep
    best_sqz, min_sqz, sqz_angle, OMC_Q, ZM4_SV, ZM5_SV = sweep_SQZANG(freq, amp_SQZANG, cycle, axs[ii,jj],
IndexError: index -3 is out of bounds for axis 1 with size 2
ICE default IO error handler doing an exit(), pid = 70032, errno = 32

 

Images attached to this comment
camilla.compton@LIGO.ORG - 11:35, Friday 03 January 2025 (82100)

The plots created are attached and in /sqz/h1/scripts/PSAMS_data/PSAMS_SCAN/250102103351/ as SQZ_DB_fit.png and heatmap.png. No clear patterns seen when looking at plots of range/BLRMs data. From the heatmap,  ZM4 at 5.2V or 6.0V with ZM5 -0.6V is best. Current is 6.0V/-0.4V so the only suggested change would be to decrease ZM5 from -0.4V to -0.6V.

Comparing our SQZ_BD_fit to LLO's (LLO#72749) our BLRMS seem to oscillate when LLO's don't. Maybe we need to adjust our BLRMs filtering to improve our SQZ DB fits.

Images attached to this comment
H1 TCS
ryan.short@LIGO.ORG - posted 16:17, Wednesday 04 December 2024 - last comment - 10:42, Friday 03 January 2025(81622)
TCS Monthly Trends

FAMIS 28455, last checked in alog81106

Only things of note on these trends are that the ITMX spherical power has been dropping for the past week and a half, which Camilla agrees looks strange, and the ITMY SLED power has reached the lower limit of 1, so it will need replacing soon. Everything else looks normal compared to last check.

Images attached to this report
Comments related to this report
thomas.shaffer@LIGO.ORG - 07:50, Thursday 05 December 2024 (81625)

Two plots, one with the ITMX V, P, Y OSEMs in the same time frame as with Ryan's plots. This could make me believe that the spherical power is just from the normal ITMX movement. The second plot is a year+ trend and I'd say that it shows this is normal movement.

Images attached to this comment
thomas.shaffer@LIGO.ORG - 07:56, Thursday 05 December 2024 (81626)

What caught my eye with these plots is thst CO2Y power has increased in the last few weeks. We've that happen after it warms up and relocks, but this seems to be trending that way after a few relocks. Not sure how to explain that one.

Also, it looks like th flow for CO2X isn't as stable at Y, worth keeping an eye on.

Images attached to this comment
camilla.compton@LIGO.ORG - 10:42, Friday 03 January 2025 (82098)

Although ITMY POWERMON is below 1 (trend), the powermon seems to read lower than ITMX, see 73371 where they were last swapped in October 2023, both fibers had 2.5mW out but  SLEDPOWERMON recorded 5 vs 3. 

I checked that the data still makes sense and isn't considerably noisier: now vs after replacement. Maybe we can stretch out the life of the SLEDs for the end of O4 but should keep an eye on them.

You can see that the spherical power form ITMX is offset from zero so we should take new references soon.

Images attached to this comment
Displaying reports 721-740 of 80463.Go to page Start 33 34 35 36 37 38 39 40 41 End