Ops Day Shift Start

TITLE: 06/25 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: MAINTENANCE
    Wind: 5mph Gusts, 3mph 5min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.08 μm/s
QUICK SUMMARY: We went down earlier to start our early maintanence day.

h1susex down for LIGO DAC install

WP11928

TJ, Marc, Dave, Erik

h1susex is currently powered down, we are installing the LIGO 28AO32 DAC card.

Lock ended 1340UTC

I ended the lock to start an early maintenance today in coordination with LLO. To prep for the EX CDS work I transitioned:

• SEI_ENV to Maintenance (verified CPS_DIFF was off)
• SEI_ETMX to ISI_DAMPED_HEPI_OFFLINE
• SUS_ETMX to SAFE

Dave was removing the link for the software watchdog as I was typing this. CDS team should be ready to go.

Ops Eve Shift Summary

TITLE: 06/25 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Quiet shift with H1 locked the whole time; current lock stretch is up to 11 hours.

• 23:04 - Dropped observing from BS camera (26) getting stuck; Dave restarted
• 23:10 - Resumed observing
• 23:42 - Dropped observing for short commissioning activities
  • SRCL FF (alog78632), no-SQZ time, improved SQZ angle
• 00:17 - Resumed observing

LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
18:36	SAF	-	LVEA	YES	LVEA is laser HAZARD	Ongoing
16:27	sqz	terry.KarMeng	optics lab	yes	shg work	23:33
18:05	PCAL	rick.tony.francisco	PCAL Lab	Yes	pcal work	23:28

Ops Eve Mid Shift Report

State of H1: Observing at 153Mpc; locked for almost 7 hours.

Dropped observing from 23:42 to 00:17 UTC to implement new SRCL FF (alog78632), get 12 minutes of no-SQZ time (from 23:52 to 00:04 UTC), and optimize SQZ angle with the SCAN_SQZANG Guardian state. Otherwise, it's been a quiet shift so far.

PSL 10-Day Trends

FAMIS 20703

There was an interesting jump down in NPRO output power at the same time as a jump up in AMP1 and AMP2 output powers earlier today. Pump currents and diode powers seem unchanged, so I'm not sure why a change in power like this would've happened.

PMC REFL is on the rise again, which seems to be bringing down PMC TRANS, ISS diffracted power, and RefCav transmitted power along with it. I can adjust the RefSignal to boost the diffracted power when we're next unlocked.

New SRCL FF in place

Jennie, Ryan S, Camilla

After Jennie's 78629 measurements, we fit the SRCL FF (not time for MICH). Possible we might add noise at 300Hz but this is FF looks overall better.

Old SRCLFF was FM2 with gain 1.18 (didn't account fort this is code but should have changed this to 1 for best iterative fitting). New FF is FM4 gain 1.18. Plot attached. SDF saved and ISC_LOCK edited and loaded.

Mon DAY Ops Summary

TITLE: 06/24 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
INCOMING OPERATOR: RyanS
SHIFT SUMMARY:

Today there was a 3hr Commissioning Period, but down time extended a couple of hours after that due to a lockloss (which also had a very misaligned BS & SR2 and SRM).  There was a retracted superevent.  And during the handoff a few minutes ago, H1 was dropped from observing due to the Camera26 (Beamsplitter); Dave restarted it to get us back to Observing.  There is high frequency noise for H1 even after 2.5hrs of thermalizing.  Ryan and Camilla chatted about dropping H1 out of OBSERVING to run the SQZ ANG and also try a feed forward set-up within this hour.
LOG:

• 1522-1553 Optics/VacPrep lab cleaning (karen)
  • 1616-1718 MY cleaning (karen)
  • 1625-1719 MX cleaning (kim)
• 1530 Mon Commissioning
  • 1545 Moving magnetometer (preet, sheila)
  • 1617-1649 Feedforward measurement (jenny)
  • 1658 CPS diff test (jim)
  • 1659 Squeezer script running (sheila)
• 1625 SHG work (terry, kar meng)
  • 1737 Kar Meng out
  • 2033 Kar Meng & Terry return for the afternoon
• 1630-1655 Grabbing tools at EY (chris)
• 1804-1831 PCal lab work (tony.francisco)
• 1817 Lockloss
  • RECOVERY:  Something was really off:  CHECK MICH FRINGES & MICH BRIGHT OFF were really bad (and SRC had issues). 
  • 1851utc  Because of CHECK MICH FRINGES issues, moved on to an INITIAL ALIGNMENT, but the Bright Michelson would not lock. 
  • 1915 MANUAL INITIAL ALIGNMENT and worked on the badly misaligned BS & SR2 & SRM.
  • Centered the BS to get better spot
  • Finally MICH BRIGHT OFFLOADED
  • needed to move SR2 a bit in pitch and yaw to center on ASC_AS_C PD
  • then moved SRM for good fringes
  • 2000 Finally SRC OFFLOADED, and returned to locking
  • CONCLUSION:  Something really misaligned the BS & SRC during commissioning.
• 1819-1823 LVEA check (janos...and he heard a locust out there!)
• 1939 Received automated call for Siren testing on Hanford site
• 2033, and2150 Pcal lab work (rick)
  • 2230 Francisco, Tony joining
  • 2328 All out
• 2139 Superevent S240624cd (later retracted)
• 2304 Bumped out of Observing due to stuck Camera Servo.  This happened on Jun16th (#78472) & also (#77499).  The culprit was once again Camera #26 (BS).  Asked Dave to take care of the camera to bring it back for us. 

Ops Eve Shift Start

TITLE: 06/24 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 19mph Gusts, 8mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.15 μm/s
QUICK SUMMARY: H1 has been locked and observing for 2 hours. High frequency range doesn't seem great, but there's a plan from commissioners to take no-SQZ time and try a new SRCL FF this evening.

• Wind and microseism are low
• All other systems nominal

Measured Feedfoward after heating OM2

I followed Camilla's instructions at

I requested the ISC_LOCK guardian go to NLN CAL MEAS.

Ran SRCL_excitation.xml in /opt/rtcds/userapps/release/lsc/h1/scripts/feedforward/

The FF filtersd are at sitemap->LSC->OVerview -> IFO_FF

Set the gain of SRCLFF1 filter bank to 0, turned off ff and input, cleared history, turned gain back to 1

Ran SRCLFF_excitation_ETMYpum.xml

Ramped the gain to 0, turned on ff filter and input, turned gain back to 1 on SRCLFF1 block.

Accidentally ranthe wrong template (MICHFF_excitation.xml) so I aborted the measurement and ran the correct template

MICH_excitation.xml instead.

Ramped the gain of MICH FF block to 0, turned off ff and input, cleared history, then turned gain back to 1.

Ran MICHFF_excitation_ETMYpum.xml

Finished FF measure at 16:49:19 UTC

Fitting to come...

Although after discussion at the commissioning meeting earlier we think the thermal transient OM2 causes will not settle to a steady state till two days time so this measurement may need to be redone if the output mode-matching of the interferometer changes.

Committed versions of the MICH and SRCL FF measurements today all with the suffix _OM2_heating, I didn't want to commit the modified templates that don't have this suffix in case I had saved over anything so made these copies.

OMC Alignment Tests this morning

Jennie W, Sheila

 

At the start of the commissioning period we did some OMC Alignment tests to see if this improved our optical gain.

First Sheila turned off injection of squeezing.

15:32:50 UTC Started OM1 and OM3 dithers at 15:32 UTC roughly from OMC control screen. sitemap -> OMC -> OMC Control then push slider shown in this image to on.

15:32:50 UTC started low frequency OMC ASC dither lines via template at /ligo/home/jennifer.wright/Documents/OMC_Alignment/20240419_OMC_Alignment_EXC.xml
Stopped OMC ASC lines at 16:03:07 UTC.

The lines effect on the OMC ASC degrees of freedom and kappa C (optical gain) can be seen here.

Then we re-injected freq dep squeezing.

OM1 and OM3 dither lines were turned off at 16:03 UTC.

After these tests we proceeded to run A2L optimisation recorded here.

---

To analyse the date I used a version of Gabriele's method where we demodulate OMC DCPD SUM at the OMC ASC dither frequencies and then the 410Hz PCAL line, to see what combination of QPD alignment offsets gives the highest optical gain.

The notebook is  at /ligo/home/jennifer.wright/Documents/OMC_Alignment/OMC_Alignment_2024_06_24.ipynb

and can be ran using:

jupyter notebook OMC_Alignment_2024_06_24.ipynb

and then opening the provided link in your browser.

The time series of the QPD offsets being changed are in this image. The right-hand plots show the cleaned DARM time series for different BLRMs regions. It can be seen that the first three have large glitches in the time series, but the 410 Hz one on the bottom right does not and so this frequency should be good for analysis.

The same plot but using data from the OMC DCPDs in the same frequency regions on the right is here. Again, there are glitches in the other BLRMS frequencies, but the 410 Hz one looks clear.

The final plot shows the BLRMS at 410Hz after the double demodulation against the QPD offsets, the red lines are set to be the proposed change in QPD offset. For three it does not look like changing ther QPD offset will improve the optical gain. For the bottom right (H1:OMC-ASC_QPD_B_YAW_OUTPUT) the correct offset change could be 0 or it could be +0.1.

It was decided not to change any of the ASC alignment offsets therefore.

SRM M1 LOCK offload boost filter

A few weeks back Oli put in an alog about IMC and SRM M3 saturations during earthquake lock losses. In April of 2023 Gabriele had redesigned the M1-M3 offload, reducing the gain of the offload somewhat to get rid of 3-ish hz instabilities in the corner cavities. This may have contributed to the SRM saturations that Oli found, so we want to try adding some low frequency gain back into the SRM offloading.

Sheila wrote out the math for me for the stability of both the SRCL loop and the stability of the M1-M3 crossover, so I have been looking at ways to increase the low frequency gain without affecting the stability above 1hz. The open look gain for SRCL looks like :

SRCL_OLG =  SRCL_sens * SRCL_FIlter * (SRM_M3_PLANT+SRM_M1_LOCK_FILTER * SRM_M1_PLANT);

The SRM M1-M3 offloading looks like:

SRM_OFFLOAD_OLG = SRM_M1_LOCK_FILTER * SRM_M1_PLANT * SRCL_sens * SRCL_Filter / (1-SRM_M3_PLANT * SRCL_sens * SRCL_FILTER);

Both of these are (or behave like) open loop gains (g), so the suppression/gain peaking can be show by looking at the 1/(1-g) for each.

I made a 50mhz boost filter for this and tried it during the commissioning window this morning. Bode plots for the boost (red), boost *m1 lock filters(blue) and the nominal M1 lock filter(green) are shown in the first image).  The affect on M3 drives and SRCL are shown in the second image asds, live traces are with the new boost, refs are without. There is good reduction below 100mhz, but there is gain peaking from the M1-M3 offloading at .2-.4hz. which might bleed into the secondary microseism during the winter. I'm working on a filter with similar gain, but less gain peaking in a region that won't affect the overall rms of the m3 drive as much. I will try installing and testing during maintenance tomorrow.

Ran A2l, accepted new values in OBSERVE.snap

Jennie, TJ

 

I ran TJ's script to measure and set all the A2L gains for the quads.

16:05 UTC ran script in userapps/isc/h1/scripts/a2l
 

python a2l_min_multi.py -a
 

*************************************************
RESULTS
*************************************************
          ETMX P
Initial:  3.26
Final:    3.19
Diff:     -0.07

 

          ETMX Y
Initial:  4.89
Final:    4.81
Diff:     -0.08

 

          ETMY P
Initial:  4.35
Final:    4.39
Diff:     0.04

 

          ETMY Y
Initial:  1.06
Final:    1.13
Diff:     0.07

 

          ITMX P
Initial:  -1.0
Final:    -1.02
Diff:     -0.02

 

          ITMX Y
Initial:  2.8
Final:    2.73
Diff:     -0.07

 

          ITMY P
Initial:  -0.38
Final:    -0.41
Diff:     -0.03

 

          ITMY Y
Initial:  -2.41
Final:    -2.28
Diff:     0.13

16:14 UTCscript finished.

TJ added these to lscparams.py and so they were loaded when Corey re-locked after the commissioning period (around 20:50 UTC).

I accepted these in OBSERVE.snap, see attached photos.

Updated Jitter cleaning for hot OM2

Since we've got OM2 warm now, I've updated the jitter cleaning coefficients.  It seems to have added one or two Mpc to the new SENSMON2 calculated sensitivity [Notes on new SENSMON2 below].

The first plot shows the SENSMON2 range, as well as an indicator of when the cleaning was changed (bottom panel, when there's a spike up, that's the changeover).

The second plot shows the effect in spectra form.  The pink circle is at roughly the same frequencies in all 3 panels.  The reference channels are data taken before the jitter cleaning was updated (so, coefficients we've been using for many months, trained on cold OM2 data), and the live traces are with newly trained jitter coeffs today.

• Top left is a comparison of old vs. new _CLEAN, showing that the blue trace is a little lower than red around one of our main jitter peaks.
• Top right is a comparison of pre-cleaning (blue _NOLINES) vs. cleaned (red _CLEAN) , for the updated coefficients.  Here you can see that the cleaning is improving that jitter peak.
• Bottom right is a comparison of pre-cleaning (blue _NOLINES) vs. cleaned (red _CLEAN) , for the old coefficients.  Here you can see that the cleaning isn't really doing much.
• Bottom left is a comparison of the estimated noise due to jitter.  With OM2 hot, we seem to have less jitter noise.

I've saved the previous OBSERVE.snap file in /ligo/gitcommon/NoiseCleaning_O4/Frontend_NonSENS/lho-online-cleaning/Jitter/CoeffFilesToWriteToEPICS/h1oaf_OBSERVE_valuesInPlaceAsOf_24June2024_haveBeenLongTime_TraintedOM2cold.snap , so that is the file we should revert Jitter Coeffs to if we turn off the OM2 heater.

---

Notes on SENSMON2, which was installed last Tuesday:

• SENSMON2 has different overlap parameters than 'normal' SENSMON that we're used to, so the absolute value is lower.  From JohnZ: Classic Sensemon calculated the noise psd with non-overlapping hann windows. Sensemon2 gives many options for the psd calculation but because the non-overlapping windows would miss loud glitches when they landed near a 4s boundary, I chose to use the 50% overlap. This affects the leakage of low frequency noise but I haven't quantified this effect.
• SENSMON2 is calculating range based on the GDS-CALIB_STRAIN_CLEAN channel.  It does not have an equivalent calculation for other versions (eg pre-cleaning) CALIB_STRAIN channels.
• The nice thing about SENSMON2 is that it is calculated more of the time.  Previous SENSMON would only calculate range from GDS channels when the IFO guardian node was OK (i.e. we were in NomLowNoise and had no SDF diffs), which made it challenging to use during commissioning.  Now SENSMON2 should be calculated any time the ISC_LOCK guardian state is above some value (chosen, I think, to be roughly when we've got 2W full IFO locked).

New DARM BLRMS ndscope FOM

I added a new version of the DARM BLRMS FOM based off of Minyo's template (alog77815). The top two plots are the inverted BLRMS, so positive changes seen on these should correlate to positive changes in the range. The units of the top plots should be close to Mpcs, so it is important to look for changes in the top plot since the scale is so much larger.

Using this in conjunction with the low range checks should help us diagnose what is changing our range around lately.

10 minutes of no sqz time before OM2 heating test

10 minutes of no squeezing time started at 12:18 UTC June 24th, back to squeezing at ~12:29.  This is so we have a comparison without squeezing before OM2 starts heating up 78573. 

Unmonitored the OM2 heater channel when the script changed it, now we are back in observing while OM2 heats up.

SQZ Laser is Glitchy since May 20th, CLF ISS gltihcy since O4b start.

Vicky, Begum, Camilla: Vicky and Begum noted that the CLF ISS and SQZ laser is glitchy.

Vicky's plot shows CLF ISS glitches started with O4b, attached.

Timeline below shows SQZ laser glitches started May 20th and aren't related to TTFSS swaps. DetChar - Request : Do you see these gltiches in DARM since May 20th?

ETMX bias sweep gives significantly different minimum in electronics ground noise coupling after charge change: from 150 V to new value of 58 V (1.5 bias offset)

Sheila, Camilla, Robert

A change in the ETMX measured charge over the O4a-O4b break (e.g. 78114 ) suggested that there might be a change in electronics ground fluctuation coupling. This is because the hypothesized mechanism for ground fluctuation coupling depends on the test mass being charged so that, as the potential of electronics (such as the ring heater and the ESD itself) near the test mass fluctuate with electronics ground potential, there is a fluctuating force on the test mass.

We swept the bias (see figure) and found that the minimum in coupling had changed from an ESD bias of about 150 V in August of 2023 ( 72118 ) to 58 V now, with the coupling difference between the two setting a factor of about ten (in other words, if we stuck with the old setting the coupling would be nearly ten times worse).  Between January of 2023 and August of 2023, the minimum coupling changed from about 130 V to about 150 V, with the coupling difference between the two settings being less than a factor of two. The second page of the figure is from this August alog, showing the difference in the coupling between then and now. I checked the differences across the break for ETMY, ITMY and ITMX and the coupling differences across the break were not much more than a factor of two, so the change in ETMX, about a factor of ten, seems particularly large, as might be expected for a significant charge change.