TITLE: 12/08 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
OUTGOING OPERATOR: Austin
CURRENT ENVIRONMENT:
SEI_ENV state: SEISMON_ALERT
Wind: 9mph Gusts, 8mph 5min avg
Primary useism: 0.06 μm/s
Secondary useism: 0.58 μm/s
QUICK SUMMARY:
TITLE: 12/08 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
INCOMING OPERATOR: Austin
SHIFT SUMMARY:
Decent evening shift even with several earthquakes rolling through (there is another M5.6 New Caledonia eq about 10min away now!). L1 has been down for most of this shift due to a power outtage.
LOG:
Have had (2) south Pacific earthquakes the first half of the shift, lockloss from the first one (M5.8, Solomon Islands) and rode through the 2nd one (M5.4, Tonga).
LLO is currently recovering from a power outtage.
TITLE: 12/08 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 16mph Gusts, 11mph 5min avg
Primary useism: 0.05 μm/s
Secondary useism: 0.45 μm/s
QUICK SUMMARY:
H1's been locked almost 3hrs. Violins are a little rung up (have the IY5 gain at -0.01). Microseism is lower than it was 24hrs ago and it looks like the day's wind storm have calmed---TJ took SEI_CONF to WINDY after being in USEISM for the last couple weeks.
Robert is currently making adjustments to CER AC units.
One of the ACs in the CER is again running at the 13.1 Hz frequency of the MC baffle near HAM3, producing broad harmonics in DARM. I shut it down at 0:34 UTC and will turn it on in a couple of hours to see if this moves the peak away from 13.1 Hz.
TITLE: 12/08 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Currently observing for 2 hours. We've had two lock acquisitions for this shift from a fast lock loss and and earthquake that immediately followed it, then another earthquake later. The first acquistion I had some odd X arm transmission issues (see alog 74655) , but the second was automated.
LOG:
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
16:15 | PEM | Robert | LVEA | yes | Mounting accelerometers | 18:15 |
16:55 | FAC | Randy | VPW,high bay | n | Move equipment from VPW to high bay with forklift | 17:27 |
17:11 | FAC | Eric | EX | n | Mech room check | 17:47 |
18:11 | FAC | Eric | MX | n | Check on temperature dip | 18:53 |
18:47 | FAC | Eric | MX | n | Fixing heater element | 20:53 |
22:57 | VAC | Jordan, Mitchell | MX | n | Parts hunt | 23:29 |
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
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.
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.
I temporarily took out the DIAG_MAIN notifications for all HWS. We will have to remember to put them back in though when we are done turning them on and off.
Unfortunately the 7 Hz comb is still present in DARM (figure 1) and in the magnetometer channel where we were tracking it (figure 2).
Extra: just to check that this really is a 7 Hz comb that started after the camera sync frequencies were moved to 7 Hz on Dec 5 (74617), and not something pre-existing, I re-plotted the magnetometer data for the time period when both were set to 5 Hz. This time period avoids any obscuring effects of the 1 Hz comb in magnetometer data. (The 1 Hz comb is much weaker than 7 Hz in DARM so it shouldn't really be an issue, but in the magnetometer data both are clear and there's a little more ambiguity there-- and anyway it's easy to check.) Indeed, no sign of 7 Hz during that hour except at frequencies that are also 5 Hz multiples (figure 3).
I put modified HWS() notifications back into DIAG_MAIN now Dave has a running script that turns the HWS camera/code off within 60 seconds of ISC_LOCK reaching state 580 and on within 60s of IFO being DOWN 74951. DIAG_MAIN may give the warning 'HWS code stopped for ITMX / HWS code stopped for ITMY' as soon as we loose lock for up to 60s, if this is annoying, we can make DIAG_MAIN cleverer. svn link
Earthquake from Mexico 5.8M.
Back to Observing 2157 UTC
I accepted the HWS SDF diffs that were related to alog 74658
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?
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.
A few notes on relocking.
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:
I do not believe we have any sensors that are more stable than just relying on the mechanical stability of the suspensions themselves. In the past, all our attempts to stabilize the uncontrolled dof in the IMC have produced worse results than relying on the stability of its suspensions.
Naoki, Sheila
We looked at some spectra comparisons. In both attached screenshots the references are the 160+ mpc time from Oct 24th. The first one shows the good time from Oct 24th compared to a time when the DARM noise was high due to clipping from Nov 29th. This shows features that have been aloged else where, the yaw ASC loops have excess noise 74502, the coherence of LSC and ASC POP is high and the ASC pop signals have extra noise (74580). There isn't as dramatic a difference in the LSC signals, which are measured in the path that was clipped, which is interesting.
The second attachment is a comparison to after our recent PR3 moves, motived by wondering if some small amount of remaining clipping could explain why our sensitivity isn't as good as it was in October. The noise of the POP sensors and the coherence of LSC and ASC POP are similar now to the time of our best range, so there isn't any obvious indication here that we are still clipping.
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
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.
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.
Yep, as hypothesized:
Plots attached.
More precise comb spacings for future reference / searchability: 0.996785 Hz, 4.98425 Hz, 6.97794 Hz.
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.
This change does also affect the comb in DARM, as expected. Yesterday's (Dec 6) daily spectrum shows that the near-5Hz comb has been replaced by a near-7Hz comb. (Figure attached, see points marked with blue squares.)
Two combs being related to the HWS of course raises suspicion that there could be more, so I'll also mention a couple of things I checked that are probably *not* due to HWS.
nuc26 (upper camera-fom machine) froze up at 22:54 Thu 07dec2023 PST, resulting in an EDC disconnected chan count of 12. TJ rebooted this machine and all is good now.
ITMY mode8 is damping down very nicely with FM1+FM5+FM10 G=+0.3 but for ITMY modes 5/6, 6 is damping but 5 seems to be slowly rising using FM6+FM8+FM10 G= -0.01 based on the narrow and broad monitors, but on DTT they both appear to be rising.