Displaying reports 9981-10000 of 86439.Go to page Start 496 497 498 499 500 501 502 503 504 End
Reports until 14:34, Saturday 29 June 2024
H1 CAL
thomas.shaffer@LIGO.ORG - posted 14:34, Saturday 29 June 2024 - last comment - 18:27, Wednesday 03 July 2024(78746)
Calibration Sweep 2106 UTC

Calibration sweep taken today at 2106UTC in coordination with LLO and Virgo. This was delayed today since we were'nt thermalized at 1130PT.

Simulines start:

PDT: 2024-06-29 14:11:45.566107 PDT
UTC: 2024-06-29 21:11:45.566107 UTC
GPS: 1403730723.566107

End:

PDT: 2024-06-29 14:33:08.154689 PDT
UTC: 2024-06-29 21:33:08.154689 UTC
GPS: 1403732006.154689
 

I ran into the error below when I first started the simulines script, but it seemed to move on. I'm not sure if this frequently pops up and this is the first time I caught it.

Traceback (most recent call last):
 File "/var/opt/conda/base/envs/cds/lib/python3.10/multiprocessing/process.py", line 314, in _
bootstrap
   self.run()
 File "/var/opt/conda/base/envs/cds/lib/python3.10/multiprocessing/process.py", line 108, in r
un
   self._target(*self._args, **self._kwargs)
 File "/ligo/groups/cal/src/simulines/simulines/simuLines.py", line 427, in generateSignalInje
ction
   SignalInjection(tempObj, [frequency, Amp])
 File "/ligo/groups/cal/src/simulines/simulines/simuLines.py", line 484, in SignalInjection
   drive.start(ramptime=rampUp) #this is blocking, and starts on a GPS second.
 File "/var/opt/conda/base/envs/cds/lib/python3.10/site-packages/awg.py", line 122, in start
   self._get_slot()
 File "/var/opt/conda/base/envs/cds/lib/python3.10/site-packages/awg.py", line 106, in _get_sl
ot
   raise AWGError("can't set channel for " + self.chan)
awg.AWGError: can't set channel for H1:SUS-ETMX_L1_CAL_EXC
 

Images attached to this report
Comments related to this report
david.barker@LIGO.ORG - 09:48, Sunday 30 June 2024 (78757)

One item to note is that h1susex is running a different version of awgtpman since last Tuesday.

erik.vonreis@LIGO.ORG - 10:01, Monday 01 July 2024 (78777)

This almost certainly failed to start the excitation.

I tested a 0-amplitude excitation on the same channel using awggui with no issue.

There may be something wrong the environment the script is running in.

 

 

louis.dartez@LIGO.ORG - 13:48, Monday 01 July 2024 (78784)
We haven't made any changes to the environment that is used to run simulines. The only thing that seems to have changed is that a different version of awgtpman is running now on h1susex as Dave pointed out. 

Having said that, this failure has been seen before but rarely reappears when re-running simulines. So maybe this is not that big of an issue...unless it happens again.
louis.dartez@LIGO.ORG - 15:17, Wednesday 03 July 2024 (78842)
turns out i was wrong about the environment not changing. according to step 7 of the ops calib measurement instructions, simulines has been getting run in the base cds environment...which the calibration group does not control. That's probably worth changing. In the meantime, I'm unsure if that's the cause of last week's issues.
erik.vonreis@LIGO.ORG - 16:51, Wednesday 03 July 2024 (78846)

The CDS environment was stable between June 22 (last good run) and Jun 29.

 

There may have been another failure on June 27, which would make two failures and no successes since the upgrade.

 

The attached graph for June 27 shows an excitation at EY, but no associated excitation at EX during the same period.  Compare with the graph from June 22.

Images attached to this comment
erik.vonreis@LIGO.ORG - 18:27, Wednesday 03 July 2024 (78851)

On Jun 27 and Jun 28, H1:SUS-ETMX_L2_CAL_EXCMON was excited during the test.

H1 SQZ
andrei.danilin@LIGO.ORG - posted 11:21, Saturday 29 June 2024 - last comment - 11:21, Saturday 29 June 2024(78726)
Transfer Function from the FC control signal counts to displacement in μm

Andrei, Naoki, Sheila

For the upcoming measurement of the FC backscattering, we need to calibrate the length change of the FC. To do this, we calculated the transfer function from the GS_SL FC control signal [Hz] to FC2 displacement [μm]. We followed the steps in Diagram.png to get to result. The plot bode_all_datasets.png contains all the used datasets.

The resulting transfer function is presented here: Tranfer_func.png (where Result curve is the transfer function). The result was exported to frequency/magnitude/phase dataset and can be found in result_data.txt. The remaining .txt files contain all the used datasets for this calculation.

Assuming that the frequency of the FC resonance shift Δf equal to c/2L corresponds to the FC length change ΔL equal to λ/2. (λ = 532 nm, L = 300 m), then Δf/ΔL = c/(L * λ) = 1.88*1012  [Hz/m] = 1.88*106  [Hz/μm]. Multiplying Transfer function by this coefficient will get us the open loop unity gain frequency of 39.4 Hz. Open-loop gain plot (after multiplication) can be found in the following figure: openloop_gain.png.

Images attached to this report
Non-image files attached to this report
Comments related to this report
naoki.aritomi@LIGO.ORG - 13:17, Friday 28 June 2024 (78728)

For FC2 suspension plant, we used sus_um in H1:CAL-CS_SUM_PRCL_PRM filter bank. The sus_um is the PRM suspension plant in the unit of um/count. Although the FC2 and PRM are the same HSTS suspensions, FC2/PRM M2 and M3 actuation strength is different by 0.326/2.83 according to the suspensions control design summary table on the door of control room as shown in the attachment (TACQ for FC2, TACQ*** for PRM). So we added this factor for FC2 M3 path.

Images attached to this comment
H1 ISC
thomas.shaffer@LIGO.ORG - posted 11:00, Saturday 29 June 2024 (78744)
Changed TMSX Opticalign tramp from 20->2

The long ramp time was confusing me while I was trying to adjust the TMS to speed up locking, so I looked into what needed such a long ramp. I thought it was the TMS servo, but it seems to only use the TEST bank. I couldn't find another place in ISC_LOCK or the ALS guardians that specifically referenced this bank, so I changed it to 2sec like for TMSY and then accepted it in SDF safe and observe. We made it through this acquisition at 2sec so maybe we're OK.

Images attached to this report
LHO VE
david.barker@LIGO.ORG - posted 10:22, Saturday 29 June 2024 (78743)
Sat CP1 Fill

Sat Jun 29 10:09:48 2024 INFO: Fill completed in 9min 45secs

Images attached to this report
H1 General
thomas.shaffer@LIGO.ORG - posted 10:08, Saturday 29 June 2024 - last comment - 11:03, Saturday 29 June 2024(78742)
Lock loss 1655 UTC

Lockloss 1403715367

There was ground motion from an earthquake just after the lock loss, but the lock loss itself seemed to be quite sudden. ETMX sees those usual wiggles that we often see.

Robert had just started running HVAC shutdown tests, but this seems very unlikely to be the cause.

Images attached to this report
Comments related to this report
thomas.shaffer@LIGO.ORG - 11:03, Saturday 29 June 2024 (78745)

Back to Observing at 1800UTC

I touched up TMSX P, PRM Y, and a bit pf BS P to speed of acquisition and avoid an initial alignment.

Our ALSX PLL beatnote seems to have gone quite bad ~10 hours ago, getting < -30 dBm. It recovered during this acquisition but I worry we will have more issues with this.

Images attached to this comment
LHO General
thomas.shaffer@LIGO.ORG - posted 07:32, Saturday 29 June 2024 (78740)
Ops Day Shift Start

TITLE: 06/29 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 4mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY: Locked for 8 hours, calm environment after the earthquake settled down.

LHO General (SEI)
ryan.short@LIGO.ORG - posted 01:07, Saturday 29 June 2024 (78739)
Ops Eve Shift Summary

TITLE: 06/29 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Two locklosses this shift and recovery was straightforward in both cases. Earthquakes at the end of the shift shook things up, but ultimately H1 rode through. H1 has now been locked and observing for almost 2 hours.

LOG: No log for this shift.

H1 General (Lockloss)
ryan.short@LIGO.ORG - posted 23:29, Friday 28 June 2024 - last comment - 23:30, Friday 28 June 2024(78737)
Lockloss @ 05:35 UTC

Lockloss @ 05:35 UTC - link to lockloss tool

End of short lock, no obvious cause. I don't see the same ETMX motion as in the previous lockloss.

Comments related to this report
ryan.short@LIGO.ORG - 23:30, Friday 28 June 2024 (78738)

H1 back to observing at 06:29 UTC, fully automatic relock.

H1 General (Lockloss)
ryan.short@LIGO.ORG - posted 20:24, Friday 28 June 2024 - last comment - 21:17, Friday 28 June 2024(78735)
Lockloss @ 03:06 UTC

Lockloss @ 03:06 UTC - link to lockloss tool

ETMX saw a small hit about a half second before the lockloss.

Images attached to this report
Comments related to this report
ryan.short@LIGO.ORG - 21:17, Friday 28 June 2024 (78736)

H1 back to observing at 04:14 UTC. Automatic relock except BS and PRM needed adjusting to lock DRMI.

H1 AOS
robert.schofield@LIGO.ORG - posted 18:47, Friday 28 June 2024 (78734)
Slow changes of ITMY ESD bias during observation

I made slow (ramp time = 120s) changes of the ITMY ESD bias today during observation mode in order to find a minimum in electronics ground noise coupling, using coherence between DARM and a current clamp on a grounding cable as the figure of merit. This project will continue, but I am done for the day and wanted to get today's times into the alog.

 

Start of change (GPS)

End of change (GPS)

ITMX bias at start (V)

ITMX bias at end (V)

ITMY bias at start (V)

ITMY bias at end (V)

1403651100

1403651220

0

0

0

-39

1403653448

1403653569

0

0

-39

170

1403655679

1403655799

0

0

170

-222

1403657640

1403657760

0

0

-222

0

 

 

 

 

 

 

H1 SEI
ryan.short@LIGO.ORG - posted 18:01, Friday 28 June 2024 (78733)
BRS Drift Trends - Monthly

FAMIS 26444, last checked in alog78167

Both BRSs look good. The slight motion of BRS-Y looks to line up with small temperature changes.

Images attached to this report
LHO FMCS (PEM)
ryan.short@LIGO.ORG - posted 17:37, Friday 28 June 2024 (78732)
HVAC Fan Vibrometers Check - Weekly

FAMIS 26313, last checked in alog78597

CS fan 5 had a slight jump up in noise about a week ago, still well within range.

All other fans largely unchanged from last check and within range.

Images attached to this report
LHO General
thomas.shaffer@LIGO.ORG - posted 16:08, Friday 28 June 2024 (78720)
Ops Day Shift End

TITLE: 06/28 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: Two lock reacquisitions, both automated. Robert has been changing some ITM L3 biases while in observing, as approved.
LOG:

LHO General
ryan.short@LIGO.ORG - posted 16:00, Friday 28 June 2024 (78731)
Ops Eve Shift Start

TITLE: 06/28 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 8mph Gusts, 5mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY: H1 has been locked and observing for over 4 hours.

H1 OpsInfo
thomas.shaffer@LIGO.ORG - posted 15:08, Friday 28 June 2024 (78729)
Temporarily unmonitored some SDF settings for ITM L3 BIAS

For Robert's tests of changing the ITM L3 bias, I unmonitored a few things to allow him to make changes while we are in observing as approved. These will need to be remonitored at the end of teh weekend. I made the changes while in observing, which didn't knock us out of observing, but I failed to notice that the offset switch was monitored and when Robert changed it we did go out of Observing. Good to know that we can unmonitor channels while in observing.

Unmonitored:

H1:SUS-{ITMX, ITMY}_L3_LOCK_BIAS_{GAIN, TRAMP, OFFSET}

H1:SUS-{ITMX, ITMY}_L3_LOCK_INBIAS

Images attached to this report
H1 ISC
jennifer.wright@LIGO.ORG - posted 14:25, Thursday 06 June 2024 - last comment - 15:30, Friday 28 June 2024(78282)
Measured OMC Scan before Moving spot in OFI Today

At the start of commissioning today, before we got to NLN and were having trouble locking the OMC, I took an OMC mode scan when we were locked at 10W.

We manually move the OMC_PZT2_OFFSET to its lowest slider value then run the template which does two 100s ramps of this PZT.

Posting for posterity.

Time of Scan = 15:23:43 UTC

200s length. See template in /ligo/home/jennifer.wright/Documents/OMC_scan/2024_06_06_OMC_Scan_15-23UTC.xml

Images attached to this report
Comments related to this report
jennifer.wright@LIGO.ORG - 15:30, Friday 28 June 2024 (78730)

Analysed mode scan and C02 mode for this full-lock scan but since we have mainly been doing single bounce to look at losses and all the sidebands were on, just posting it here for posterity. The mode-matching calculation has to take into account all the sidebands I think.

Analysis code is In OMCscan_nosidebands13.py and fit_two_peaks_no_sidebands13.py in /gitcommon/labutils/omc_scan/figures/2024-06-06 on the /dev branch (ie. it will not be on the workstation branch as this is the master branch).

Non-image files attached to this comment
Displaying reports 9981-10000 of 86439.Go to page Start 496 497 498 499 500 501 502 503 504 End