Bruco Ran for 2023/12/07 01:07:00 UTC, MICH better with new FF

I ran a Bruco for yesterday after commissioning time ended: 2023/12/07 01:07:00 UTC  bruco_1385946438_STRAIN and the hour before commissioning period started: 2023/12/06 18:17:30 UTC bruco_1385921868_STRAIN The IFO had been locked since 2023/12/06 09:00UTC, so for 9 and 16 hours before measurements. 

MICH coherence looks much better  after compared to before the new FF was installed 74642. Can also compare to October's 73701 Bruco. There is still coherence around the 17Hz BS mode 74259, maybe this is expected.

Other ones to note: CHARD_Y, CHARD_P, PRCL, SRCL

Ran in LDAS using commad: python -m bruco --ifo=H1 --channel=GDS-CALIB_STRAIN_NOLINES --gpsb=1385921868  --length=3600 --outfs=1024 --fres=0.1 --dir=/home/camilla.compton/public_html/bruco_1385921868_STRAIN --top=100 --webtop=20 --plot=html --nproc=20 --xlim=1:1000 --excluded=/home/elenna.capote/bruco-excluded/lho_DARM_excluded.txt

h1sush7 single Dolphin IPC receive errors from h1lsc0

At 11:09:47 Thu 07 Dec 2023 all the Dolphin IPC receivers in the models h1susfc1 and h1sussqzin reported a single error from h1lsc0 senders.

This is a repeat of what was seen 16 days ago (05:22:13 Tue 21 Nov 2023). I have added today's issue to the already opened FRS29765

The main difference is that today's error occured while H1 was locked. It did not appear to cause any problems, these IPC receive channels would have repeated a value for one of the 16384 cycles in that second.

Turning off all HWS for DARM Comb test

TJ, Ansel, Dave, Camilla

After finding that 1Hz and 5Hz DARM combs were caused by HWS camera sync frequency in 74617, we've turned off all HWS at 21:00UTC so we can check that nothing else from HWS is effecting DARM.

Stopped all HWS code (ETMY was already off 73915). Tuned off all cameras and RCX CLinks. Turned off the ITM SLEDs, ETMX laser will still be on but was tested in 69648 not to effect DARM.

As long as the computers aren't restarted I think that the H1:TCS-E{OPTIC}_HWS_ channels will remain reading their last values, if not Dave might need to "green-up" the CDS overview.

Lock loss 2018 UTC

Earthquake from Mexico 5.8M.

Lock loss 2023-12-07_11:38:11Z

1385984310

This has that same feature seen ~100ms before lock loss in LSC-DARM, OMC DCPDs, and ETMX L3 master out. They all seem to be moving at the same time, so harder to differentiate, but maybe the ESD LVAMON chan, DRIVEALIGN L, and L3 master out channels start to deflect before LSC-DARM seen in attachment 2. So perhaps something with ETMX?

Observing 1847 UTC

Back after a lock loss and a large earthquake. Violin modes are quite high so we will be damping those for a while, but we are now in Observing.

Thu CP1 Fill

Thu Dec 07 10:12:35 2023 INFO: Fill completed in 12min 31secs

Travis confirmed a good fill curbside.

Ops Day Shift Start

TITLE: 12/07 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Earthquake
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: EARTHQUAKE
    Wind: 18mph Gusts, 13mph 5min avg
    Primary useism: 0.18 μm/s
    Secondary useism: 0.51 μm/s
QUICK SUMMARY: 7.1M earthquake from New Caldonia area killed a 26.5hour lock almost 3 hours ago. The SEI_ENV node just switched out of earthquake mode and has started relocking now.

 

Wed EVE Ops Summary

TITLE: 12/07 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:

H1 in Observing the entire shift (currently at 23hrs for the lock).  Microseism has slowly been decreasing.
LOG:

• 0515 nuc30's DARM spectra timed out.  Clicked Abort and then Start.  It was very slow, but it eventually re-started.  Then it timed out after only 17avgs
  • Contacted Dave and he mentioned this has happened before and was related to an issue with GDS.  A workaround until the GDS is addressed is that Dave ran a DARM .xml which uses NDS1 instead.  Email sent to Jonathan Hanks and John Zweizig regarding GDS issue.

Mid-Shift Status

H1's been locked for 19+hrs w/ a range around/just-under 155Mpc.  Microseism has slowly trended down to the 95th percentile level.  There was a M5.8 EQ off Chilean coast H1 (& L1) both coasted through no worse for wear.

Wed EVE Ops Transition

TITLE: 12/07 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 3mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.66 μm/s
QUICK SUMMARY:

H1's been locked 15.75+hrs with a range around 153Mpc.  

Handoffs from TJ:

• Keep an eye on CER temps
• ITMY Mode 5 violin mode has non-nominal gain of -0.01
• LVEA still laser HAZARD

looking at trends related to PRC cavity axis and LSC pop path

Jenne, TJ, Sheila, Naoki,

We looked at some trends together of what's been happening with H1's range, PRG, and various sensors related to the PRC over the last few months. 

The first screenshot here shows some of these trends, with the first horizontal cursor showing, Oct 24th a day when we had a particularly good BNS range just above 160 Mpc.  The vertical cursors are set to show a reference of what the various signals were on that good day.  Some things to notice:

• The PR3 yaw moves from Friday (74535) and Monday (74578) seem to have restored our PRG to nearly 50, with a similar stability to what we had in late October.  These moves improved our range and glitch rate, but the range is still lower than our best times in October and early November.
• The top mass osems aren't a reliable way to track PR3 yaw (neither is the optical lever): We had previously seen that PR3's optical lever wasn't tracking long term drifts well at all, (70008) so on Nov 7th we used the top mass osems to reset PR3 yaw to previous times (74065), as marked by the red arrow.  You can see that from this time forward the PRG dropped, became more noisy, and seems to drift more.  So it seems that this move started to introduce clipping probably in the LSC POP path.
• The POP QPDs also can't be used to track this shift:   POP A is the QPD used in DRMI ASC, which has large offsets applied.  Both POP A and POP B yaw would indicate that our recent moves Friday and Monday went in the wrong direction, but we observe that these moves reduced clipping in the POP LSC path (74586 and 74582).  Also, looking at their trends over the last few months they don't seem related to changes in PRG, (for example, POP A YAW was the same as at the good time in our worst PRG times 14-7 days ago). 
• Jenne suggested looking at trends of IM1-3, which are uncontrolled and could be drifting.  The second attachment shows their trends, they seem to be drfiting in a way that might correlate with outdoor temp, like many things do.  I believe these are fairly small shifts of the IMs (I'm not sure that these are calibrated into urad, for historical reasons some channels which are calibrated on other suspensions aren't calibrated in the same way on the IMs). I'm not sure that we can tell without taking some steps on some of these if they are responsible for the PRG change. 

 

New MICH FF installed

We installed the new MICHFF FM8 filter that Gabriele fit 74602, 74595. This looks to do a great job suppressing the MICH excitation, see pink trace attached. A little less suppression 150-200Hz so we'll want to run some coherences with NLN data to see if we care about MICH in this region. Saved in safe and observe sdf and ISC_LOCK.

Left the MICHFF off for 5 minutes 22:05:45 to 22:10:45UTC.

Tagging CAL, this may have an effect on the 17.6Hz line 74259

Un-damped spectra results of suspensions for diagnosing mechanical problems

I took un-damped spectra (amplitude spectra density) of all the suspensions today to check for rubbing or mechanical/electrical issues. The latest results (orange trace) have been compared with the ones taken in 2020 (blue trace, LHO alog 56019 which were judged healthy) and the dotted line is the bosem sensor noise. Given below are the results for some of them (while I am still processing others):-

For now I have just glanced through the plots and will look into the details later.

Quads - ETMX, ETMY, ITMX, ITMY :  They look healthy to me, although I need to cross check the tall peaks of ETMX (for F1, F2, F3 sensors).

HSTS - MC1, MC2, MC3, PR2, PRM, SR2, SRM :

MC1 RT BOSEM (also L and Y dof) looks to be a bit worse than previous measurements- see page 5 on MC1. Later, I requested Oli to take a transfer function measurements on MC1 and they looks healthy. He will post the plots later. Perhaps RT bosem on MC1 is degrading with time.

On MC2, sensor T3 (MC2 page 3) shows a broad peak at 15Hz approximately (this also needs to be cross checked)

HLTS - PR3, SR3 : the results look better than the ones taken in 2020, however I still need to cross check the resonant peaks.

The results for the other remaining suspensions will posted after processing them.

Having looked through all the un-damped SUS spectra of most concern is the MC1 M1 stage RT channel BOSEM. I would suspect a fault in the read-back electronics chain (e.g. the ADC, AA-chassis or Satellite Box) rather than a fault in-chamber with the BOSEM. If this elevated noise has not been observed in subsequent measurements, then it could be intermittent and therefore tricky to track down. So I would recommend monitoring the MC1 M1 stage RT channel for elevated noise.

ITM HWS Camera Sync Frequencies Adjusted to 7Hz for DARM Comb Search

Ansel, Camilla

This morning we found that the 0.98Hz DARM comb was related the the ITMX HWS camera 1Hz sync frequency, see alog 74614 where I adjusted ITMX from 1Hz to 5Hz at 20:10UTC. This was a past issue with an expected fix in place 44847 FRS4559.

Ansel then suggested that the 4.98Hz DARM comb 68261 could also be from HWS as we have nominally used a 5Hz sync frequency on the ITM HWSs during O4. At 22:25UTC I adjusted both ITMX and ITMY camera sync frequencies from 5Hz to 7Hz (instructions).

In May we had the ETM HWS and camera off for 1 week 69648, but I didn't repeat the test with the ITMs, ETMY is currently off, ETMX has 15Hz camera frequency.

Another nice find! This is good news to clean up more of the H1 spectrum. I hope this one can also be turned off in observing. Any others? Potentially there might be one at 9.5 Hz since we're also seeing a problematic 9.48 Hz comb.

Mezanine Power Supply Labels Installed

M. Pirello, F. Mera

We completed the install of the new magnetic labels to the Kepco supplies on the Mezanine today.

While placing one of the labels, the power on the HAM-6 PZT driver was unintentionally interrupted.  We contacted the control room and they verified that this glitch did not affect anyone and we could turn this power back on.

One side note, the supply in H1-VDC-C6 slot 26 LHS which supplies HI-ISC R3 & R5 (HAM-6 +18V supply) is nearly maxed out at 20V 17A in the Mezannine, see attached photo.  The two supplies below it are the old squeezer +/- 18V.  These are currently unused, disconnected at the racks, but still on (not sure why we keep these supplies on).  We could alleviate the load by splitting up R3 and R5 with respect to +/-18V and using this +/- 18V for either R3 or R5.