Derek noticed (via the summary pages) that there seems to potentially be an occasional discrepancy between CALIB_STRAIN_NOLINES and CALIB_STRAIN_CLEAN.

The NonSENS subtraction should be off.  The first attachment shows that indeed the noise estimate output by the front end NonSENS is zeros to the 1e-27 level (these are in the same strain units as GDS-CALIB, and I just didn't bother scrolling in more to see how 'zero' I can make the y-axis) during a time when the discrepancies are visible on the summary page. 

A next step is likely to try to zoom in on the time axis of the spectrograms from the summary page to see when these things are happening, and see what other things might be changing around those times (eg, are those the beginning of Observe segments or going in/out of NLN_CAL_MEAS?).  Since the output of the noise estimate from the front end is zeros, _NOLINES and _CLEAN *should* be identially the same. 

Gabriele updated the H1:LSC-MICHFF Channel and asked me to accept the SDF Diff.

TITLE: 07/20 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 8mph Gusts, 5mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.03 μm/s
QUICK SUMMARY:

Current State of of IFO : LOCKED in NOMINAL_LOW_NOISE and Observing for almost 11.5 hours with a nice bump in range!

TITLE: 07/20 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 145Mpc
SHIFT SUMMARY: Quiet shift, locked at low noise for the whole duration with some times out of observing for quick commissioning.

• Dropped observing from 13:44 to 13:54 for MICH measurement: alog 71538
• Dropped observing from 14:40 to 14:58 for implementation of new MICHFF filter: comment to alog 71538
  • Noticable increase in range of ~10Mpc!

While LLO was relocking this morning, I dropped observing from 13:44 to 13:54 UTC to run Gabriele's MICH FF template with 35 averages.

The measurement is saved in /ligo/home/ryan.short/MICH_excitation_2023_07_20.xml

The EX VEA appears to have been having a temperature fluctuation of 0.5 degF for ~12 hours the past two days (two day and one week trends attached). I don't believe we've seen impact of this on H1, but worth noting.

State of H1: Observing at 136Mpc

H1 has been locked for 7 hours. Quiet night so far.

TITLE: 07/20 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 138Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 4mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.04 μm/s
QUICK SUMMARY: Taking over from Austin. H1 has been locked for over 3 hours.

• All systems look good
• I'll keep an eye on the camera servos as Austin was reporting issues with them during his shift

TITLE: 07/19 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 138Mpc
SHIFT SUMMARY:

- 0:13 - inc 5.0 EQ from Alaska

- Lockloss @ 1:01 - cause unknown

- DRMI locking failed 2x at CHECK MICH FRINGES, so I will try running an initial alignment

• Most of the initial alignment went fine, but I still ran into the issue trying to get SRC to catch, despite having fairly good flashes,  so I am skipping and retrying ISC LOCK
• Relocking was unaided, waited at OMC WHITENING to damp violins

- Acquired NLN/OBSERVING @ 3:45 after accepting an OMC SDF diff leftover from yesterdays OM2 test - Tagging ISC

- 5:27 went into COMMISSIONING due to freezing of ETM cameras (which led to the CAMERA SERVO guardian failing), it fixed, then got stuck a few times before it fixed itself permanently, contacted Dave - scope attached

• It seems that all 3 camera servos, ETMX, ETMY, and BS failed at exactly the same time
• Dave did not see this issue on the IOC, indicating the the problem might be coming further upstream
• We looked at the CDS CA COPY guardian which sends data from the ioc/cameras into the ASC model - I ran a guardctrl log on CDS_CA_COPY during the first failure and saw no evidence of any issue in this guardian node
• The problem unfortunately reconciled itself and we were not able to replicate the problem, this might have to be looked at tomorrow

- Other than the camera hiccup, overall was a quiet night, leaving H1 to Ryan S. going on a 3 hour stretch

LOG:

No log for this shift.

Following a lockloss (caused by unknown reasons) and a subsequent intiial alignment, H1 is at OMC WHITENING waiting for violins to damp before going back to low noise.

Logging for Brina, who collected a bunch of relevant times to compare sqz vs. no-sqz at different OM2 settings. We aim to do some quantum noise budgeting with these times, to see whether/how much quantum noise is a contributor between 50-150 Hz, and to use the no-sqz data to look at ifo output losses for different OM2 settings. Looking at correlated noise budget from Craig recently, LHO:71333, hopefully we can understand what's going on with quantum noise ~30-200 Hz.. 

Lockloss @ 1:01 - DCPD saturation, can probably rule out an ASC ringup from the locklost tool, but there is potential suspicious LSC movement in PRCL, MICH, and SRCL.

Last night and this morning, we've turned the OM2 heater back on.  Our range didn't improve, however.  We still had in place the AS36Q yaw offset from last Thursday (alog 71309).  At the start of our Wed commissioning period, I turned that offset off.  This improved our range back to ~140 Mpc according to CAL-DELTAL on the wall, but our range is still not back to where it was the last time we had OM2 hot. We may need to think about more alignment changes / checks.

We conducted a study using data from the Fscan pipeline that shows when the violin modes are rung up, there is a dramatic increase in the number of narrow lines (of the type problematic for CW searches) in the regions around the violin modes and harmonics. This increase in the number of narrow lines is visible both in daily and weekly plots since June 29th when the violin modes and its harmonics are known to have rung up. 

Figure 1 shows how the number of lines jumped significantly in the 300-600Hz and 900-1200Hz bands from June 29th to June 30th, and again from July 9th to July 10th without much change in the other frequency bands. Figures 2 and 3 show the averaged spectrum for the 29th and 30th respectively, demonstrating just how dramatic the increase in the number of lines is. Figure 4 shows how visible and persistent the lines are in the weekly data. 

Figures 5, 6, and 7 show the max amplitude of the violin modes vs number of lines per the square root number of SFTs in three different frequency bands surrounding the violin modes and its harmonics. To remove the effect of the duty cycle on the number of lines counted, the total number of lines counted is divided by the square root of the number of SFTs produced in a day because the number of SFTs produced in a day is directly proportional to the amount of time spent observing on that particular day. From here on out, I will refer to the number of lines per square root of the number of SFTs as the number of lines.

Looking at all the O4 data so far, it is obvious that the number of lines increases with the max amplitude violin modes in the bands surrounding the violin modes and its harmonics. The most dramatic effect is visible in the 300-600Hz band (Figure 5) where the number of lines seems to increase approximately linearly with the max amplitude of the violin modes between amplitudes of 10^-20-10^-18 strain/√Hz. Between 10^-18-10^-17 strain/√Hz, the number of lines increases significantly with no clear pattern. Multiple days after the June 29th ring up appear in this region, showing that these long ring ups can greatly increase the number of lines and decrease CW data quality for a significant period of time. Around the 1000Hz (Figure 6) and 1500Hz (Figure 7) harmonics, the number of lines increases approximately linearly with the max amplitude of the violin modes without displaying the jump present in the 300-600Hz band. This might be because the amplitude of the violin modes has a much smaller range of 10^-19-10^-18 strain/√Hz during the ring up.