FAMIS 31052
No major events of note this week. PMC reflected power seems to be holding mostly steady now, like we started to see last week.
Related detchar request: #172
Key points
11.9 Hz comb is present in some ASC, IMC and ISI-HAM5 channels:
Fscan data on 2024-04-08 was analyzed with a 2-week duration. 11.9 Hz comb is common at both observatories. The 1st and 3rd harmonics (11.9hz and 35.7hz) are the strongest peaks to study.
Details
*The method is adapted from #77990.
The stamp-pem-comparison tool was used first to pick out possible witnesses from low-resolution STAMP-PEM data. The result of 2024-06 -- 2024-08 is shown in Figure 1. I then followed up the analysis with week-long Fscan data on 2024-04-08. This date was chosen because the comb appeared strong then, according to alog 72866. Figures 2-7 are the coherence plots for the witness channels listed above. The interactive plots for some more auxiliary channels, plots of data from June, speclong data and data spanning 2 weeks can be found under https://ldas-jobs.ligo-wa.caltech.edu/~zhiyu.zhang/11.9Hz_appearance/. These other plots confirm the same channels. The comb is not visible in one day in these auxiliary channels.
The results of this analysis only apply to LHO for now, but the same method can be applied to LLO data.
Sheila and I are still trying to determine if the a2l script can be helpful, or made helpful, and understand our coupling from these changes to DHARD and CHARD. We ran it today with both C&D HARD showing higher coherences with our current lock (attachment from Ryan C's alog80244). After running the script the largest change was to ITMY Y gain (-0.28 diff). This helped out DHARD from 15-35Hz, but made CHARD worse in 10-21Hz. We were then going to try and tune common by hand to see if we could make any difference, but we lost lock.
We decided to update the gains with the script results since this did help out our DHARD. Perhaps an acceptable trade off for now. Values for the Y gains have been updated in lscparams and SDF, but P was close enough that I left them alone.
We had the chance to try one ITM common step by hand before running out of time, but it seemed to help out CHARD in the lower frequencies that we care about and and not affect DHARD.
Final gains +0.1 ITMY=-2.43 ITMX=3.05
We are starting planned commissioning at 15:30 UTC. Some of the tasks to be worked on are:
Lockloss 15:45 UTC from a HEPI HAM1 trip
Back into Observing at 18:39 UTC, high freq SQZing doesn't look good now?
Mon Sep 23 08:11:39 2024 INFO: Fill completed in 11min 35secs
Jordan confirmed a good fill curbside.
TITLE: 09/23 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 3mph Gusts, 1mph 3min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.15 μm/s
QUICK SUMMARY:
Running the low range check, low freq PRCL, CHARD_Y (and at high freq), DHARD_Y coherence
TITLE: 09/23 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Two locklosses this shift, one from a PI ringup and another from an earthquake. Otherwise a quiet shift and lock acquisition has been straightforward.
Lockloss @ 03:22 UTC - link to lockloss tool
I originally thought this lockloss was from a M5.4 EQ from Chile that was predicted to hit at this time, but now that the USGS site has updated and looking at how sudden and hard-hitting the lockloss was, I now suspect this was from a M3.2 EQ from Desert Aire, WA, a mere 20 miles northwest of the site.
Since this quake was so close, ground motion calmed down quickly and I've started the relocking process.
H1 back to observing at 04:45 UTC. Fully automated relock after waiting for ground motion to calm.
Lockloss @ 00:18 UTC - link to lockloss tool
PI mode 24 rung up 90 minutes into the lock stretch and caused this lockloss. I tried manually damping after seeing Guardian be unsuccessful, but I also wasn't able to find a phase which brought this mode down at all before losing lock (I did not get to trying different gains).
H1 back to observing at 01:18 UTC. Fully automated relock.
TITLE: 09/22 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 136Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: The range has peaked at 164 Mpc in the first 2 locks of the day. 2 locklosses this shift, the range isn't so great this current lock, high freq SQZing looks bad.
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 23:58 | SAF | H1 | LVEA | YES | LVEA is laser HAZARD | 18:24 |
| 19:36 | PE | Robert | EndY | N | CEX PEM investigations | 23:08 |
TITLE: 09/22 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 15mph Gusts, 9mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.13 μm/s
QUICK SUMMARY: H1 just got back to observing about 15 minutes ago. High frequency noise looks particularly bad this lock, so once H1 is thermalized I may try some SQZ alignment to improve it.
20:53 UTC lockloss
There were HAM3 CPS glitches on verbal before the LL, and PRM was the first saturating suspension from the LL tool.
Another CPS glitch tripped the HAM3 ISI
All of the glitches are on the H2 & V2 sensor, which I believe have their own rack, corner 1 & 3 are on the other rack. I've asked Ryan to go and power cycle the CPS electronics are the rack in the CER. We'll see if that fixes the issue.
I called Jim who advised I go to the CER and power cycle the HAM3 ISI interace chassic CPS power as we were seeing the glitches in H2 and V2, I did this which has fixed the issue (for now at least).
22:46 UTC Observing
