Wed Jun 12 10:12:30 2024 INFO: Fill completed in 12min 25secs

Gerardo confirmed a good fill curbside.

TITLE: 06/12 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 4mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.17 μm/s
QUICK SUMMARY: Locked for 11 hours, much quieter environment today. Just within the last 30 min the range seems to be going down. The 1-2kHz DARM BLRMS are moving up, but perhaps not appreciably. I'll keep an eye on this and run a few checks.

TITLE: 06/12 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
INCOMING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 13mph Gusts, 8mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.24 μm/s
SHIFT SUMMARY:

1:09 UTC got to PREP_DC_READOUT_TRANSITION
Noticed about about 15 minutes later that we were in this state for much longer than usual.

OMC should be trying to get to READY_W_NO_WHITENING but it is saying :

[SET_WHITENING.run] USERMSG 0: DCPD gains not equal after whitening switch -- yikes!
I tried poking it around to a few different states but it seemed to get stuck at the same state each time.

Ryan told me he had seen this before, I found Ryan's Alog and read through it.  I'm not sure if I have the right channels or not.
H1:OMC-DCPD_{A,B}0_GAIN Is what I scoped back to June 6th and saw that they were indeed changed that day.
Seeing as I couldnt find the full length of those channels on the OMC screen I did a caget and caput and was greeted with a failure to to write error.

CA.Client.Exception...............................................
    Warning: "Channel write request failed"
    Context: "op=1, channel=H1:OMC-DCPD_A0_GAIN, type=DBR_STRING, count=1, ctx="H1:OMC-DCPD_A0_GAIN""
    Source File: ../oldChannelNotify.cpp line 159
    Current Time: Tue Jun 11 2024 18:48:43.327036542

I'm not sure why that was but  Jenne D told me to try: 
cdsutils write CHANNEL_NAME SetPoint
cdsutils write  H1:OMC-DCPD_A0_GAIN 1  worked out well for both A and B Channels and got the OMC going again.

2:24 UTC Reached OMC_Whitening, Waiting for Violins to go Down.
Incoming EQ from northern East Pacific Rise
https://earthquake.usgs.gov/earthquakes/eventpage/us7000mrv4/executive

3:17 UTC Nominal_LOW_NOISE reached

made it to NLN but not in Observing because SQZ_MAN got stuck in FC_WAIT_FDS:
I requested SCAN_SQZANG, to see if that would allow it to cycle through the stages but it got stuck there again.

Naoki jumped on the chance to help the SQZ Manager make it to FDS
I saved some SUS Spot Gain SDFs And an LSC SDF.
4:02 UTC Obsering was reached!

H1 has been Locked and OBSERVING for 4 and a Half hours.

 

FAMIS Weekly In-Lock SUS Charge Measurement 28357

[Jenne, Sheila, Tony]

DRMI ASC had been pulling the SRC out of alignment for the last few days, from where initial alignment leaves things.  This is pretty clearly seen in POP90's rise when DRMI ASC is engaged.

Since the AS72 offsets have been working well in EngageASCforFullIFO and bringing POP90 back down, I have put the same AS72 offsets into DRMI ASC.  This has worked well twice now (although we're not getting all the way to DC readout, likely because of the high wind).  I've also moved where in EngageASCforFullIFO the AS72 offsets come on, so that it's using those offsets all the time (rather than how I had it in alog 78333 where the offset came on later).

- The EX GV20 AIP was not functional since Sunday (for details, see aLog https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=78339). The controller was replaced, and since the pump lost functionality, the pressure in the Annulus system built up, so it was pumped out with a Pfeiffer aux cart. After reaching ~2E-5 Torr, the pump came alive again. The pumping cart was switched off, disconnected, and the AIP was able to hold and decrease the pressure further.
- The HAM2 AIP seemingly was not functional since last Wednesday (06/05). It was found that the issue was with the communication cable. The cable was disconnected, then reconnected, and the signal came back.

I tried the FF filters Gabriele put in  78307: the new SRCL filter was on at 17:36, (while Jennie W was adjusting the A2L) the new MICH feedforward was on at 17:45 with quiet time from 17:45- 18:10.  In this configuration the SRCL coherence was high, so I switched it back to the old SRCL FF (with a gain of 1, rather than 1.14) at 18:12, and this is how we've been observing.

The PRCL coherence is the highest of the LSC coherences, with MICH and SRCL lower than PRCL but still large from 15-25Hz. 

The attached screenshot shows that we still have large ASC coherences with DARM, as well as jitter coherences. 

Edit: Adding a second screenshot that shows the coherence of SRCL, MICH and PRCL with DARM at 17:45 UTC, when the new SRCL FF was on with a gain of 1 (and also the new MICHFF). 

One potential explanation for what happened is that something happened last Tuesday that means we need an offset in AS72 now, but we were running with SRM misaligned last week before we realized this, which changed the feedforward.  Now that we have a hadn tuned offset in AS72, the SRCL and MICH couplings are more similar to what they were before last week, so we better off with the old feedforward filters in.

WP11914, WP11918 Install ADC in h1iscex for h1pemex readout

Fil, Marc, Erik, Jonathan, Dave

In preparation for testing the new LIGO DAC card in h1susex, an ADC was installed in h1iscex which will read the new DAC's signals.

This ADC belongs to PEM, it was purchased to expand the number of accelerometers.

The ADC, its ribbon cable and interface card were installed in the h1iscex IO Chassis (see drawing). A PEM AA-Chassis was installed and connected to the ADC.

Two models were changed:

h1iopiscex: add 5th ADC

h1pemmx: readout the 5th ADC, route all 32 channels into filter modules with the names H1:PEM-EX_ADC_4_CHAN_n where n=0-31

DAQ restart was needed.

Add WAP channels to DAQ

Erik, Dave:

We took the DAQ restart as an opportunity to use the latest H1EPICS_WAP.ini which adds the missing corner station WAPs. EDC and DAQ restart needed.

Add IRIG-B signals back to end station CAL models

Keita, Fil:

The CNS-II Clock GPS receivers independent IRIG-B signals were reattached to the h1isc[ex,ey] AA chassis.

DAQ Restart

Dave, Jonathan:

The DAQ was restarted for the above model and EDC changes. There were several issues:

gds0 needed a second restart

FW1 spontaneously restarted itself after 728 seconds.

TITLE: 06/11 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Wind
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 30mph Gusts, 20mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.19 μm/s
QUICK SUMMARY:

H1 is currently trying to lock in Windy conditions.... It would be nice is the Wind would calm down.

TITLE: 06/11 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Wind
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Longer maintenance day today, with activities wrapping up an hour or two ago. We've made it through initial alignment but there was no green light in the arms when Oli and I first started locking. We ran the baffle align scripts for the TMS and ITMs but ended up finding the arms by hand. The rest of initial alignment was hands off. The wind has increased and ALS is now having a rough time staying locked, so we'll see how the rest of locking goes.
LOG:

A consequence of WP 11919 today is that we should be able to see the range calculation (eg on the control room wall) for the GDS-CALIB_STRAIN-type channels for more of the time.  Now, rather than needing the overall IFO to be ready for Observing (i.e. at NomLowNoise and no SDF diffs), there should be a range calc (for, eg, the thick red line on the range plot on the control room wall) thorughout much of the locking sequence, just like the range that is calculated from Cal-DELTAL_EXTERNAL (the thin line on the control room wall range plot).

No other configurations have changed, but this will be something that looks different from how it had been, so it's worth noting in the alog.

FranciscoL, [Remote: RickS]

After one week of having the inner beam centered (alog 78247), on June 11, we moved the beam by 5 mm on the Rx sensor.

The Rx side cover was compromised due to work being done by the vacuum team (images attached for reference.) Fortunately, the back cover was accessible and the measurements were done accessing the Rx input aperture through there. There might be a minor uncertainty on the alignment of the target - it was done by "projecting" the front of the power sensor by using the front camera of my phone; instead of the usual alignment by eye. Since the procedure had a regular/similar flow as the movements done on previous weeks, uncertainty of the target alignment should not be problematic for our measurements.

Attachment 'AlignedTarget' shows the alignment with the beam height gauge. Attachment 'BothBeamsBefore' shows the beams before making any changes. The pdf 'EndStationLog.pdf' lists the voltage values after each significant step of procedure T2400163. The steps represent writing down a voltage value after a particular change to the beam position. Some steps were recorded multiple times after minor changes.

• (2) Only inner beam at Rx detector. (see image 'InnerBeamBefore')
  • The beam voltage was maximized before making a move. The first two values are before attempting to move. The third value comes from making a horizontal move. There was an increase of about 0.014 V (1.6%) from this move. There was no increase from moving vertically.
• (3) Finalized beam movement. (see image 'InnerBeamAfter')
  • Signal is significantly higher, ~ 4.1%, than the centered beam.
• (8) Target off. The measurement was recorded after placing the pcal enclosures.

The 'Initial' measurement is *equal* to the last voltage measurement from the previous movement, done on May 21 (alog 78247). The initial and final voltage measurement during today procedure remained the same despite the increase of the inner beam with the target.

We expect this movement to be symmetric (equal in magnitude, opposite in sign) to alog 77840

J. Kissel
TIA D2000592: S/N S2100832_SN02
Whitening Chassis D2200215: S/N S2300003
Accessory Box D1900068: S/N S1900266
SR785: S/N 77429

I've finally got a high quality, trustworthy, no-nonsense measurement of the OMC DCPD transimpedance amplifiers frequency response. For those who haven't seen the saga leading up to today, see the 4 month long story in LHO:77735, LHO:78090, and LHO:78165.

For those who want to move on with their lives, like me: I attach a collection plots showing the following for each DCPD:
Page 1 (DCPDA) and Page 2 (DCPDB)
    - 2023-03-10: The original data set of the previous OMC DCPD's via the same transimpedance amplifier 
    - 2024-05-28: The last, most recent data set before this, where I *thought* that is was good, even though the measurement setup was bonkers, 
    - 2024-06-11: Today's data
Page 3 (the Measurement Setup)
    - The ratio of the measurement setup from 2023-03-10 to 2024-06-11.

With this good data set, we see that
    - there's NO change between the 2023-03-10 and 2024-06-11 data sets at high frequencies, which matches the conclusions from the remote DAC driven measurements (LHO:78112) and
    - there *is* a 0.3% level change in the frequency response at low frequency, which also matches the conclusions from the remote DAC driven measurements. 

Very refreshing to finally have agreement between these two methods.

OK -- so -- what's next? Now we can return to the mission of fixing the front-end compensation and balance matrix such that we can 
   - reduce the impact on the overall systematic error in the calibration, and 
   - reduce the frequency dependent imbalance
that were each discovered in Feb 2024 (see LHO:76232).

Here's the step-by-step:
- Send the data to Louis for fitting.
- Create/install new V2A filters for A0 / B0 bank
- Switch over to these filters and accept in SDF
- Update pydarm parameter file with new super-Nyquist poles and zeros.
- Measure compensation performance with remote DAC driven measurement of TIA*Wh*AntiWh*V2A
	confirm bitterness / flatness

Once IFO is back up, running, (does it need to be thermalized?)
- Measure balance matrix, 
	Remember -- SQZ OFF
	confirm better-ness / flatness
- Install new balance matrix
- Accept Balance Matrix in SDF

Once IFO is thermalized
- grab a new sensing function.
- push a new updated calibration

FAMIS tasks 24852 and 24876, WP 11915

Procedure checklist for both stations completed.  No issues were identified at this time.

MX: Scroll pump hours: 218.0

       Turbo pump hours: 128

       Crash bearings: 100%

EX: Scroll pump hours: 7146.0

       Turbo pump hours: 1097

       Crash bearings: 100%

On Friday 06/07/2024 Dave Barker sent an email to the vacuum group noting 3 spikes on the pressure of the main vacuum envelope, I took a closer look at the 3 different events and noticed that the events correlated to the IFO losing lock.  I contacted Dave, and together we contacted the operator, Corey, who made others aware of our findings.

The pressure "spikes" were noted by different components integral to the vacuum envelope.  Gauges noted the sudden rise on pressure, and almost at the same time ion pumps reacted to the rise on pressure.  The outgassing was noted on all stations, very noticeable a the mid stations, and with less effect at both end stations, and for both with a delay.

The largest spike for all 3 events is noted at HAM6 gauge, we do not have a gauge at HAM5 or HAM4.  The one near HAM6 is the one on the relay tube that joins HAM5/7 (PT152), with the restriction of the relay tube, then the next gauge is at BSC2 (PT120), however the spike is not as "high" as the one noted on HAM6 gauge.

A list of aLOGs made by others related to the pressure anomalies and their findings:
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=78308
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=78320
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=78323
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=78343

Note: the oscillation visible on the plot of the outer stations (Mids and Ends) is the diurnal cycle, nominal behavior.

Naoki, Sheila

To investigate the origin of whistles and rms increase in FC IR signal as reported in 78263 and 78344, we turned off the FC green VCO lock after FC IR transition.

In TRANSITION_IR_LOCKING state of SQZ_FC guardian, the FC CMB servo is disabled after FC IR transition. Since we use the green QPD at FC trans for beam spot control, we also turned off the beam spot control. The SDF is accepted as shown in the attachment.

P. Baxi , J. Kissel 

Finished characterizing (Channels 1 to 4) of the new 524KHz Analog OMC Anti-Alias Chassis - S2300162

• Bode plot for the system include the Transfer function and Phase of each individual Channels (1 to 4) and their (Channel 2 to 4) respective ratio with Channel 1 for comparision. The system was characterised from Start Frequency of 1KHz to a Stop Frequency of 102.4KHz with 100 steps.

                       BodePlot_Channel_1_4_freq_start_102.4KHz_Freq_stop_1KHz_Steps_100.pdf  (raw data - available in DCC S2300162)

              - We see the frequency response has minimal phase impact in the gravitational wave band, with deg of phase loss at 1000 Hz.

• Noise Measurements for Channels 1 to 4 with reference to the noise of SR785 is shown in the plots below. To achieve the maximum frequency range we incorporate and merge three frequency spans: 4Hz to 3.2 KHz, 32 Hz to 25.6 KHz, and 128Hz to 102.4KHz.

                       ASD_SR785_Channel_1_4_Freq_span_4to32K_32to256K_128to1024K.pdf  (raw data - available in DCC S2300162)

              - We see the noise of each of these 4 representative ADC channels is around ~20 nV/rtHz

• Python scripts to regenrate the plots. (Bode plot and ASD plots) 
• Measurement notes to reproduce the above raw data.  (Bode plot and ASD plots)