Displaying reports 2221-2240 of 77273.Go to page Start 108 109 110 111 112 113 114 115 116 End
Reports until 23:58, Saturday 20 April 2024
H1 General
ryan.crouch@LIGO.ORG - posted 23:58, Saturday 20 April 2024 (77309)
OPS Saturday day shift summary

TITLE: 04/21 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 26Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: After relocking we stayed locked the whole shift, the wind started to pickup around 03:00 UTC.

05:30 UTC Superevent S240421ar

Lock#1

Relocking at green arms, went through prmi, chech_mich then prmi again before we could get DRMI

Lock#2

Strugged to get back up due to the wind knocking ALS out, the forecast has the winds calming down around 10:00UTC


LOG:

Start Time System Name Location Lazer_Haz Task Time End
23:17 CAL Francisco PCAL lab LOCAL Checks 23:24

 

H1 General (Lockloss)
ryan.crouch@LIGO.ORG - posted 23:06, Saturday 20 April 2024 (77310)
Lockloss at 06:03 UTC

Wind was gusting up to 40 mph around the time

https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1397714645

H1 General
ryan.crouch@LIGO.ORG - posted 20:01, Saturday 20 April 2024 (77308)
OPS Saturday eve shift update

We've been locked for almost 3 hours, range hovering around 160

LHO General
corey.gray@LIGO.ORG - posted 16:00, Saturday 20 April 2024 (77301)
Sat DAY Ops Summary

TITLE: 04/20 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:

Lockloss Sandwich:  Shift started with a lockloss during the first 30min and a lockloss near the last 30min of the shift.

Also posting  a spectrum of the HAM5 STS seismometer during Richland earthquake---mainly because when Robert walked in the Control Room he was surprised to not see anything on the low-frequency seismic plots on nuc5....but it's mainly because we don't have 1-3Hz up there.  The attached spectrum does show a big bump in that band for sure.  (along with lines at ~7Hz and around 32Hz.) 
LOG:

Images attached to this report
H1 General
ryan.crouch@LIGO.ORG - posted 15:57, Saturday 20 April 2024 - last comment - 17:10, Saturday 20 April 2024(77306)
OPS Saturday day shift start

TITLE: 04/20 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 2mph Gusts, 1mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.10 μm/s
QUICK SUMMARY:

 

Comments related to this report
ryan.crouch@LIGO.ORG - 17:10, Saturday 20 April 2024 (77307)

Back to Observing at 00:09 UTC

H1 CAL (CAL)
corey.gray@LIGO.ORG - posted 15:36, Saturday 20 April 2024 (77305)
Saturday H1 Calibration Measurement Run (broadband headless + simulines)

After coordinating with LLO & notifying Virgo, went with running the Saturday Calibration Measurements (broadband [~5min] + simullines [~25min]) at ~ 2200utc

LOCKLOSS (at 2225utc) During Measurement!!  Sadly, it looks like we had a lockloss toward the end of the Calibration.  Vlad said we should let Louis know so he could look at the script to see if the excitations are too strong toward the end of the Simulines measurement.

Images attached to this report
LHO General
corey.gray@LIGO.ORG - posted 13:22, Saturday 20 April 2024 (77304)
Belated Mid-Shift Report

Today is my first time being on shift to attempt a Saturday calibration  measurement, but have had a few wrinkles:

  1. h1 lockloss early in the shift; this is noteworthy because for the calib measurement you need to be thermalized (H1 has to be locked at high power for atleast 3hrs).
  2. When I was about 45min away from running the measurment, L1 had just recovered from their lockloss (so this resets the timers back to 3hrs again for L1 to thermalize).
  3. We are aiming to have a coordinated calibration measurement at 2200utc (3pm PDT).

No other notables for H1 from the shift

LHO VE
david.barker@LIGO.ORG - posted 10:34, Saturday 20 April 2024 (77303)
Sat CP1 Fill

Sat Apr 20 10:09:46 2024 INFO: Fill completed in 9min 42secs

For some reason none of us got texts for this fill, but subsequent test texts were getting through and fill emails were received as normal. I restarted the locklossalert service on cdslogin at 10:23 PDT. Tested it by sending test texts, we will see if this fixes our cp1 fill text issue tomorrow.

Images attached to this report
LHO General
corey.gray@LIGO.ORG - posted 08:21, Saturday 20 April 2024 - last comment - 08:55, Saturday 20 April 2024(77300)
Sat DAY Ops Transition

TITLE: 04/20 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 20mph Gusts, 18mph 5min avg
    Primary useism: 0.07 μm/s
    Secondary useism: 0.11 μm/s
QUICK SUMMARY:

H1 had a lockloss about 4.5hrs ago, but has been UP about 3hrs. 

For the Alarm Handlers there was a "Not Connected Error" window up (and WHITE alarm for dust monitors) at 2:23amlocal which cleared up in 3 seconds.

For those who felt it (or heard) there was a M2.8 earthquake in Richland last night (at 9:18pm Local).  H1 rode right through it and it was only seen on our seismometer DMTs for the 3-10 & 10-30Hz bands (it's the orange EX x-axis line at about 11hrs --see attached-- (I happened to look at it last night after my sister texted me about it while she was working at the Emerald; she (and I) didn't feel it.)  :)

Calibration measurement scheduled for 11:30amLocal /1830utc.

Images attached to this report
Comments related to this report
corey.gray@LIGO.ORG - 08:55, Saturday 20 April 2024 (77302)SEI

Here's a zoom-in of the Richland EQ (circled in red) as seen from the Control Room FOMs.

https://earthquake.usgs.gov/earthquakes/eventpage/uw61998221/executive

Images attached to this comment
H1 General
ryan.crouch@LIGO.ORG - posted 00:00, Saturday 20 April 2024 (77299)
OPS Friday eve shift summary

TITLE: 04/20 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: We stayed locked the whole shift, 1 small local EQ. The range hovered around 155-165
 

Bit of local motion that was reported as a 2.7 EQ in Richland, WA on USGS and EMSC at 04:19UTC

Virgo went down later in the evening (around 06:00UTC) and wasn't able to relock from their green ALS laser needing to be fixed (new amplifier) Valog 64030

LOG:                                                                                                                                                                                                                                                                                                                                                                                                                        

Start Time System Name Location Lazer_Haz Task Time End
20:52 pcal tony pcal.lab y PCal Work 23:22
23:33 CAL Tony PCAL lab LOCAL PCAL work 01:33
23:41 CAL Francisco PCAL lab LOCAL Help Tony 23:59
Images attached to this report
H1 General
ryan.crouch@LIGO.ORG - posted 20:02, Friday 19 April 2024 (77298)
OPS Friday Eve shift update

We've been locked for about 4 hours. The range has been just over 160.

LHO General
corey.gray@LIGO.ORG - posted 16:02, Friday 19 April 2024 (77283)
Fri Ops DAY Shift Summary

TITLE: 04/19 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:

Commissioning time from 1900-2200utc but there was a lockloss at the end---H1 currently at 60W so almost back up.

Picket Fence froze earlier in the shift.
LOG:

H1 General
ryan.crouch@LIGO.ORG - posted 15:59, Friday 19 April 2024 - last comment - 16:16, Friday 19 April 2024(77296)
OPS Friday eve shift start

TITLE: 04/19 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 12mph Gusts, 9mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.12 μm/s
QUICK SUMMARY:

Comments related to this report
ryan.crouch@LIGO.ORG - 16:16, Friday 19 April 2024 (77297)

Back into NLN at 23:06 UTC and we returned to OBSERVING at 23:15 UTC after Robert took apart his PEM setup/EXC

H1 ISC
sheila.dwyer@LIGO.ORG - posted 15:05, Friday 19 April 2024 (77289)
PRCL to SRCL input matrix element, phasing of POP45

Sheila, Gabriele, Camilla, Jennie

The other day I used Elenna's template to make a PRCL excitation: 77252

We can use this to check on our PRCL to SRCL feedforward element in the LSC input matrix, where we add some of the POP A 9I signal (PRCL) to the POP A 45I signal (SRCL) to cancel the POP45 sensitivity to PRCL.

When the PRCL excitation is on, the transfer function of POP45I/POP9I is -0.028716 cnts/cnt

We want to set out input matrix such that:

5_1 = -5_3 * POP41/POP9I tf (with PRCL excitation on) to cancel the PRCL contribution to the SRCL error signal.  This means that now, our POP 9I to SRCL ERR matrix element should be 0.107 but it is now 0.06. 

EDITING to Add:

Today I re did this measurement and saw that POP45/POP9I is -0.02551 cnts/cnt, meaning that the input matrix should be 0.0946. Updating the input matrix to this did improve the PRCL to SRCL decoupling, as shown in the second attachment. 

I also tried moving the PRCL offset, this did not seem to change the POP45I/POP9I ratio much, so the PRCL to SRCL decoupling doesn't seem to need retuning each time the PRCL offset changes. 

The third screenshot shows the PRCL to DARM coupling, there are small changes (2-3dB change) with these changes in PRCL offset and PRCL to SRCL decoupling.  So this suggests that the main coupling of PRCL to DARM isn't through SRCL.  (And that the PRCL offset sn't helping much). 

Gabriele remembered that the PRCL to DARM coupling could also be through MICH, indeed the third screenshot shows that the PRCL signal is a factor of 10 smaller in POP45 Q than in I. In 66151 Anamaria tuned the phasing so that the PRCL signal in 45Q was a factor of 100 smaller than in I, so we can try to improve this by rephasing POP45.

Edited again:

Camilla and I moved the POP45 phase from 8 to 11, this reduced the PRCL to POP45Q transfer function to be about a factor of 100 below PRCL to POP45I (last screenshot blue references show the improvement from a phase of 8 to 11).  We then remeasured the SRCL to PRCL input matrix element, which should be 0.087.  This made the SRCL coherence in DARM rather bad, although the PRCL to MICH and PRCL to SRCL couplings were improved.  We decided to revert these, and wait for next week to make the changes at a time when we could immediately retune FF.  As I stepped the phase back I accidentaly moved us from 11 to 6 in one step, which unlocked the IFO. 

 

Images attached to this report
H1 ISC
gabriele.vajente@LIGO.ORG - posted 14:54, Friday 19 April 2024 - last comment - 15:14, Friday 19 April 2024(77294)
OMC alignment

[Jennie, Sheila, Gabriele]

Low frequency OMC alignement lines were injected between 20:19 UTC and 21:16 UTC, following a similar method to what described in 76462.

Using the code attached, I looked at how the noise in DARM and the amplitude of the 410.x Hz calibration line changes with respect to the OMC QPD signals.

One can see from a spectrogram that the noise in GDS-CALIB_STRAIN_NOLINES is strongly modulated by the OMC angular lines. The spectrogram shows GDS-CALIB_STRAIN_NOLINES normalized to the median over time.

Then one can compute BLRMS as several bands of GDS-CALIB_STRAIN_NOLINES to see how the noise changes, and of OMC-DCPD_SUM at 410-411 Hz to monitor the amplitude of the DARM calibration line, that is a proxy to optical gain. Time series are shown in the attached figure, where the OMC-DCPD_SUM BLRMS time series are comapred with the OMC QPD signals.

Finally, I plotted the 410-411 Hz BLRMS of OMC-DCPD_SUM (optical gain) in a scatter plot vs all four QPD. This allows me to select a value of the QPD signals that maximize the optical gain. The negative of those values is the offset that should be added to the OMC QPD on top of the existing offset.

Signal Aditional offset
(to be added to the existing value)
H1:OMC-ASC_QPD_A_PIT -0.05
H1:OMC-ASC_QPD_A_YAW +0.12
H1:OMC-ASC_QPD_B_PIT +0.00
H1:OMC-ASC_QPD_B_YAW -0.12

CAVEAT: However, looking at the noise in GDS-CALIB_STRAIN_NOLINES between 800 and 900 Hz (that should be shot noise) one see that it is minimum for the current OMC offsets. Maybe this is an indication that the SQZ is aligned with the current OMC, but the current OMC is not well aligned to the IFO. I suspect that using the offsets above will increase the optical gain, but make SQZ worse

 

Images attached to this report
Non-image files attached to this report
Comments related to this report
jennifer.wright@LIGO.ORG - 15:14, Friday 19 April 2024 (77295)

The template we used to run these lines is saved in /ligo/home/jennifer.wright/Documents/OMC_Alignment/20240419_OMC_ALignment_EXC.xml

The lines ran from 1397593158 to 1397596597 GPS in parallel with Robert's PEM measurements.

H1 SQZ (DetChar)
naoki.aritomi@LIGO.ORG - posted 14:50, Friday 19 April 2024 (77292)
ADF line at 322Hz

Naoki, Camilla, Sheila

We did 5+5 minutes ON/OFF test of ADF line at 322 Hz. While the ADF is ON, we changed the ADF demod phase to make the ADF SQZ angle around 0 so that we can use the ADF servo with 322 Hz ADF line. 

The script to change the ADF frequency is in (userapps)/sqz/h1/scripts/ADF/setADF.py. The command is as follows.

python setADF.py -f 322

1st cycle
ON (5 min)
UTC: 2024/04/19 19:02:10 UTC
GPS: 1397588548

OFF (5 min)
UTC: 2024/04/19 19:07:21 UTC
GPS: 1397588859

2nd cycle
ON (5 min)
UTC: 2024/04/19 20:02:52 UTC
GPS: 1397592190

OFF (5 min)
UTC: 2024/04/19 20:08:00 UTC
GPS: 1397592498

3rd cycle
ON (5 min)
UTC: 2024/04/19 20:13:16 UTC
GPS: 1397592814

OFF (5 min)
UTC: 2024/04/19 20:18:35 UTC
GPS: 1397593133

Images attached to this report
Displaying reports 2221-2240 of 77273.Go to page Start 108 109 110 111 112 113 114 115 116 End