I was able to request and transition to the new DARM state without issue. ETMX still saw a pretty large kick. I'll have to circle back re: how large compared to previous attempts. We will also want to take a look at any effects moving the integrator on L2 LOCK L had. Note: We do get a few SUS_PI warnings shortly after transitioning to this state. Quiet time to monitor for non-stationarity: Start GPS: 1394344327 Stop GPS: 1394346169 Turned off cal lines at GPS 1394346770.39 Elenna started a Bruco after the cal lines were turned off. here is a screenshot of DARM in the new configuration. 20-90Hz looks high and below 15Hz looks low. It's hard to tell how much of this is real until CAL-CS is calibrated & that calibration is propagated to the DTT template. I started an L2 LOCK IN1/IN2 injection using noise recorder at 1394347034.426. We used a tuned broadband measurement that Craig and I put together. Apparently it was too strong because we lost lock from this injection. It also tripped EX. I requested DOWN and the EX trip alarm reset.
Bruco is here: https://ldas-jobs.ligo-wa.caltech.edu/~elenna.capote/brucos/New_DARM/
Just from first glance looks like some residual LSC coherence, but not enough to explain the strange shape of New DARM.
Here are plots comparing the MASTER OUTS on ETMX during Louis's quiet time here with L3 offloaded, vs Gabriele's quiet time in alog 76278 during Nominal DARM. We are concerned only with the filter changes that Louis and Sheila made to offload more of L3's length actuation onto L2. Because L2 is used to control both length and angular degrees of freedom, it can be easy to ask too much of L2. This lock seems to indicate that this configuration is fairly stable. I looked at the UL MASTER OUTs for the L1, L2, L3 on ETMX. 1) RMS on L3 drives is halved. There is much less L3 drive from 1 to 6 Hz, which dominates the RMS. 2) L2 drives are largely unchanged. 3) L1 drives are changed, but the RMS remains similar. There is much less HF content in the L1 drive with L3 offloaded, and the shape of the resonances around 3 and 6 Hz is altered. Overall it's hard to tell which stage is picking up L3's slack from these PSDs. I believe the intention was to offload to L2, but we don't see any obvious change in what control signal is being sent to the L2 stage. This could simply mean that the angular controls are relatively stronger in the L2 controllers. We'll look at the DRIVEALIGN signals to try and figure that one out quantitatively.
The new DARM loop configuration reduces the DARM noise non-stationary at low frequency.
First plot compares the ESD drive with the Old DARM and the New DARM, confirming that the RMS is significantly reduced, especially at the relevant frequencies.
Second and third plots are spectrograms and whitened spectrograms of GDS-CALIB_STRAIN in the two configuration. Despire GDS-CALIB_STRAIN being wrongly calibrated with the New DARM, it is clear that the low frequency non stationarity is gone in New DARM.
Last two plots are the bicoherence of DARM with the ESD drives, showing that in the Old DARM there is still some bicoherence for noise in the 10-30 Hz region, while in the New DARM this is gone.
These transitions last night were made with a different L2 LOCK filter (which is in L2 LOCK L FM6, replacing the filter used in earlier new DARM configurations that was at FM2). The attached screenshot shows the filter change, I replaced the poles at zero with poles at 0.03 Hz to get rid of the integrator here without changing the phase at the crossover much. This was done with the guardian version 27211
Plots of the actuators during the transitions are attached, here and here, they can be compared to the one that Louis posted where we used L2 LOCK FM2. This suggests that the change to these poles didn't help to reduce the transient during the transition.
Today we tried another change to the transition, this time Evan and I moved the poles in L2 LOCK L from 0.03 Hz to 0.1 Hz, and changed the ramp time for the transition to 10 seconds (from 5). The model is shown in the attached PDF where the new filter is in place in the transition traces. This transition wasn't smoother than the others, see here.
The new UGF is 70 Hz with 20° of phase margin. The crossover between L2 and L3 is at 18 Hz with probably about 40° of phase margin (low coherence due to interference with calibration lines). We have not measured the L1 to L2 crossover yet.
S. Dwyer, E. Capote, E. Hall, S. Pandey, L. Dartez
Here are some notes from our efforts to measure IN1/IN2 at the L1 LOCK L input.
- Sheila adjusted UIM measurement template for new darm config. This template is at /opt/rtcds/userapps/release/lsc/h1/templates/DARM/UIM_crossover.xml
.
- Evan ran the template initially and saw that the UGF is near 1Hz. He adjusted the excitation amplitude along the way to improve coherence for the next time we run this measurement.
- Evan added a high pass filter in the L3 DRIVEALIGN bank with a cutoff frequency at at 5Hz
- first filter attempt was at 8Hz; possibly caused a roll mode to excite near 13.75Hz
- second filter attempt was at 5Hz; this seemed to improve the roll mode excitation
We ended up losing lock a shortly after the injection finished due to PRC activity.
Comparison of DARM ESD drive from end of O4a versus a few days ago. The microseism was about 0.2 µm/s in both cases. The rms DAC drive from 0.1 Hz to 0.3 Hz is about 400 ct, so even in cases of exceptionally high microseism it will be subdominant to the 7000 ct rms that is accumulated above 1 Hz.
I tried a new DHARD Y filter that should reduce the noise injected from DHARD Y between 10-30 Hz. It's about 6 dB improvement. I ran 10 minutes quiet DARM after the test starting Mar 13 4:36 UTC (Mar12 21:36 local). No apparent change in the low frequency noise in DARM.
The filter engagement works, so I added it to the "LOWNOISE ASC" state of the guardian. It's in FM8 and engages with other DHARD Y boosts.
Gabriele ran a bruco for me, looks like this was an improvement-
[Gabriele, Elenna]
Since we saw high coherence betwen DHARD_Y and DARM, we tried to improve the A2L. In summary, the current value of 1.65 is the best for angular coupling at ~30 Hz, so we didn't change it.
To do the measurement, we injected two lines, one at 15.1 Hz and one at 30.3 Hz, and used a python script to demodulate the lines in DARM. The lowest coupling at 15.1 Hz is obtained for a larger value around -2.4, but this makes the coupling at 30.3 Hz larger. The initial value is the best for minmize the coupling at 30 Hz, where DHARD is limitign DARM.
As a part of several suggestions to address the clipping on IM4 trans and the ISS QPD, Keita suggested I check the POP QPDs to see if things have changed there since the vent. Here are two ndscopes comparing the PIT, YAW and NSUM channels of both POP A and POP B QPDs. The two screenshots show the last lock in January and the recent lock yesterday. It appears that the overall power on the QPDs is about the same, but the alignment on POP B in particular has changed significantly in pitch, close to -1 and probably to falling off.
We servo on POP A during DRMI lock, but do not use POP B for any control (to my knowledge).
[Evan, Gabriele, Louis, Georgia]
We struggled to properly align the IFO. We saw low flashes in the y arm during ALS locking and had to move the beamsplitter to increase the flashes. Then, after completion of initial alignment, the ALS Y arm alignment would be poor again. After some trial and error and fighting with the "increase flashes" guardian state, Evan saw that PR3 has drifted in yaw 0.4 microradians. When he moved PR3, it significantly improved the Y arm flashes and the input alignment. We don't know why PR3 drifted and it had so much effect on the Y arm but not necessarily the X arm. Our third initial alignment succeeded and locking is proceeding well.
Attached are some trends of PR3 witness sensors.
The hepi and ISI position sensors say that those are not drifting. The oplev yaw was restored by the move described above; the top mass osem doesn't see any drift except for the move of the slider to restore the optical lever.
General Compute work successful and complete. Split the fibre optic pair that was a single pair - 2 strand connection to ESNet and split the fiber to 2 single strand full duplex circuits to ESNet. We now have BGP Peer redundancy and Seattle route as preference. We are using BiDi connectors now over standard SFP+. One route to Boise and one route to Seattle. Seattle preferred due to latency, Boise is redundant. Duration of total outage was approximately 30 minutes, and duration to full restoration was about one hour. 1500: Work Started 15:15 Internet connection cut 15:45 Initial restoration achieved, but not the Seattle link. 16:15 Seattle link is restored when fiber patch found incorrectly connected. This was corrected and full circuit restoration was seen. 16:30 All secure from this evolution. Hands off all systems check shows complete operation, BGP peering to Seattle that is established, and IP Flows are in the Seattle route destinations.
TITLE: 03/12 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
INCOMING OPERATOR: None
SHIFT SUMMARY: Tuesday maintenance today, mostly a lot of VAC and CDS work. We has issues getting ETM and TMS model working(76305), but we were finally able to get them up and are currently working on locking green arms.
LOG:
15:00UTC Starting Tuesday maintenance
15:38 Turned sensor correction off
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
15:15 | ISC | TJ, Georgia, Matt, Trent | LVEA - ISCT1 | yes(local) | Realigning green beatnote - TJ out 15:50 | 16:01 |
15:15 | FAC | Karen | EY | n | Tech clean | 15:53 |
15:16 | FAC | Kim | EX | n | Tech clean | 16:20 |
15:24 | HWS | Camilla, Graeme, TJ | EX | YES | HWS table work | 18:20 |
15:28 | FAC | Mitchell | LVEA - West bay | n | Labelling things | 17:47 |
15:30 | EE | Fil | H2 | n | Looking at humidity sensors | 16:23 |
15:38 | VAC | Gerardo, Jordan | Bier Garten | n | Purge air, Jordan out 17:07, Travis out 18:40, Janos out 18:49 | 19:00 |
16:01 | CDS | Dave | remote | n | WP11766 New h1iopsusey model | 20:23 |
16:02 | SUS/ISI | Oli, Jeff,Dave | CR | n | WP11743 New SUS & ISI models ETMX, ETMY | 20:23 |
16:03 | DMT | Dan | MSR | n | WP11765 Reboot DMT servers | 18:46 |
16:03 | DAQ | Dave | remote | n | Reboot DAQ for SUS/ISI model changes | 20:23 |
16:08 | FAC | Karen, Kim | HAM Shack | n | Tech clean | 16:35 |
16:09 | CDS | Jonathan | office | n | WP11761 Upgrade FCES network switch | 17:23 |
16:14 | CDS | Jonathan | remote | n | Upgrading FCES switch firmware | 16:55 |
16:34 | Richard | LVEA - GV2 | n | Meeting up with Fil | 16:55 | |
16:36 | IAS | Ryan C | LVEA - Beer garden | n | Measuring with FARO | 18:29 |
16:45 | SQZ | Daniel, Nutsinee | HAM7 | n | Measuring SQZ rack electronics | 18:19 |
17:02 | FAC | Kim | High Bay | n | Tech clean | 18:48 |
17:04 | FAC | Karen | OptLab, VacPrep, LVEA | n | Tech clean | 18:16 |
17:07 | VAC | Jordan, Eric | EX | YES | Hooking up RGA | 18:07 |
17:25 | EE | Marc, Fernando | LVEA | n | Helping Gerardo | 18:35 |
18:36 | TCS | Camilla, Fernando | LVEA | n | Looking at TCS controls | 19:01 |
20:00 | FAC | Bubba | EY | n | Checking water tank | 20:24 |
20:13 | - | Gabriele | EX,EY | n | Becoming healthier | 22:13 |
20:56 | - | Janos, Graeme, Craig | MX | n | tour | 21:56 |
21:01 | EE | Gerardo, Jordan | EY,ex | n | replacing batteries for solar panels | 22:01 |
22:21 | SQZ | Nutsinee | LVEA - SQZT0 | n | Taking measurements | 22:26 |
22:22 | VAC | Travis | MX | n | Turn off turbo pump | 22:52 |
22:35 | SQZ | Nutsinee | LVEA - SQZT0 | n | More measurements | 23:05 |
J. Kissel, O. Patane, D. Barker ECR E1700387 IIET Ticket 9392 WP 11743 More details to follow in the comments, but today started the campaign of SUS / SEI watchdog improvements. This required us to restart the h1susetmx h1susetmy h1sustmsx h1sustmsy h1susetmxpi h1susetmypi h1isietmx h1isietmy front-end models. The update makes the following changes: (1) Establish a sensible band-limited RMS user watchdog trigger (where it had been some old broken RMS code prior), where the OSEM trigger signals are now calibrated into microns (um_RMS), and the threshold has been adjusted to match it. (2) Entirely removed the USER DACKILLs from the SUS, so we no longer AND together the output triggers for any stages' user watchdog and shut down the output of DAC. In other words, we'll no longer kill damping and offsets if we drive the L2 stage too hard with ISC control. (3) Entirely removed the connection between the ETM and TMS DACKILLs to the ISI and PI models, and replaced the input to the ISI's PAYLOAD flag with "always good" constants. As originally promised in ECR and IIET ticket -- this drastically reduces the unnecessary complexity and redundancy of the watchdog system, it now behaves in a much less trigger-happy fashion, and delightfully, we now can answer the question "how much motion trips the watchdog?" I've accepted the threshold at 25 um_RMS over the 0.1 to 10 Hz band. We can and should adjust this threshold as we gather more experience. All changes to settings have been accepted in the corresponding SUS safe.snap such that the work in calibrating the OSEM trigger signal won't disappear with the ISC_LOCK guardian's SDF_REVERT state.
WP11766 Shorten SWWD SUS-EY trip time
Dave:
The h1iopsusey model was changed to reduce the SWWD SUS timer from 900s to 600s. This means that the SUS DACKILL time to trip is shortened from 20mins to 15mins and is no longer coincident with the HWWD tripping.
This IOP restart required the restart of all the models on h1susey, and was done in conjuction with the restart of h1susetmy.
After all the models had been running again for a few minutes, h1susey locked up. It was not on the network (no ping, ssh). We fenced it from Dolphin and power cycled it via its IPMI management port.
WP11743 SUS DACKILL Removal
Jeff, Oli, Jim, Dave:
Today we removed the SUS DACKILL from the end station models h1susetmx and h1susetmy. The dolphin ipc receiving models h1isietmx, h1isietmy were modified to replicate a good ipc receiver.
In addition the h1susetmxpi and h1susetmypi models also needed replicated receivers.
Unfortunately I got the ERR replication value incorrect, it should be 0 and not 1. The receiver models were restarted with the correct values.
The first round of restarts required a DAQ restart, the subsequent changes only needed model restarts.
The TMS models were modified later, requiring a second DAQ restart.
WP11761 sw-fces-cds0 Firmware Upgrade
Jonathan:
The firmware on the FCES switch sw-fces-cds0 was upgraded.
WP11765 DMT Upgrade and Reboots
Dan:
This action was canceled for today and will be scheduled for a later maintenance period.
DAQ Restart
Jonathan, Erik, Dave:
The DAQ was restarted partially once, completely twice for the above model changes.
The first restart (partial 0-leg only) at 12:30 highlighted that the PI models were showing IPC Rx errors due to a removed SUS SHMEM channel.
The second full restart at 13:06/13:12 was in support of the SUS-ETM, SUS-ETM-PI and ISI-ETM model changes.
the third full restart at 14:47/14:52 was in support of the SUS-TMS model changes.
There were no major issues with the DAQ restarts, just the usual GDS second restarts for channel
list synchronization.
Restart/Reboot Log
Tue12Mar2024
LOC TIME HOSTNAME MODEL/REBOOT
12:14:27 h1seiex h1isietmx <<< SUS-ETM and ISI-ETM model restarts
12:14:58 h1susex h1susetmx
12:15:32 h1seiey h1isietmy
12:16:47 h1susey h1iopsusey <<< EY IOP and all Models restarts
12:17:04 h1susey h1susetmy
12:17:18 h1susey h1sustmsy
12:17:32 h1susey h1susetmypi
12:24:21 h1susey ***REBOOT*** <<< h1susey locked up, needed a reboot
12:26:25 h1susey h1iopsusey
12:26:38 h1susey h1susetmy
12:26:51 h1susey h1sustmsy
12:27:04 h1susey h1susetmypi
12:30:40 h1daqdc0 [DAQ] <<< Partial 0-leg restart
12:30:49 h1daqfw0 [DAQ]
12:30:49 h1daqtw0 [DAQ]
12:30:50 h1daqnds0 [DAQ]
12:30:58 h1daqgds0 [DAQ]
12:34:33 h1daqgds0 [DAQ]
12:50:53 h1susex h1susetmxpi <<< PI model change, remove IPC Rx
12:55:45 h1susey h1susetmypi
13:06:50 h1daqdc0 [DAQ] <<< Full DAQ restart for susetm, susetmpi, isietm models
13:07:01 h1daqfw0 [DAQ]
13:07:01 h1daqtw0 [DAQ]
13:07:02 h1daqnds0 [DAQ]
13:07:10 h1daqgds0 [DAQ]
13:08:42 h1susey h1susetmypi <<< Problem is etmypi build (install too quick), rebuild and install.
13:12:08 h1daqdc1 [DAQ]
13:12:20 h1daqfw1 [DAQ]
13:12:20 h1daqtw1 [DAQ]
13:12:22 h1daqnds1 [DAQ]
13:12:30 h1daqgds1 [DAQ]
13:12:56 h1daqgds1 [DAQ]
13:49:38 h1seiex h1isietmx << Fix the replicated IPC ERR=0
13:55:49 h1seiey h1isietmy
13:58:35 h1susex h1susetmxpi
14:01:46 h1susey h1susetmypi
14:43:40 h1susex h1sustmsx <<< New TMS models
14:44:06 h1susey h1sustmsy
14:47:04 h1daqdc0 [DAQ] <<< DAQ restart for TMS model changes
14:47:15 h1daqfw0 [DAQ]
14:47:16 h1daqnds0 [DAQ]
14:47:16 h1daqtw0 [DAQ]
14:47:24 h1daqgds0 [DAQ]
14:47:50 h1daqgds0 [DAQ]
14:52:21 h1daqdc1 [DAQ]
14:52:33 h1daqfw1 [DAQ]
14:52:33 h1daqtw1 [DAQ]
14:52:34 h1daqnds1 [DAQ]
14:52:42 h1daqgds1 [DAQ]
Sheila, Camilla, Jennie W, Keita remote
Stefan and Daniel suspect that our excess noise around 100 Hz might be due to intensity noise, and we did have a large shift in alignment of the beam transmitted through IM4 (76291) 76241. I moved pico 1, first to center the beam on the ISS QPD, which made the power on the ISS array PDs drop, and didn't improve the spectrum of the ISS Sum inner or outer channels (we did this with the loop open). We reverted this, then looked at the QPD position in O4a when we had 60W input power, went to 60W input power and pico'd to bring the beam to the same location as O4a. This also didn't improve the spectrum, so we brought the pico back to where we started.
Sheila asked me to compare the ISS second loop outputs with from our recent NLN lock last night to that during O4a. The spectra doesn't show much difference in the noise (top left plot shows Jan 14th lock in cyan and yellow, last night's one in pink and brown).
The other three plots shows the coherence of ISS output with all three GS13s on the HAM2 optical table. There only seems to be coherence at the power lines.
So maybe the ISS is not causing intensity noise to couple into DARM differently pre and post vent.
Images 2 and 3 attached shows the ndscope fro all channels I used around the two times I took spectra.
Time 1 = 2024-01-14 22:05:27 UTC
Time 2 = 2024-03-12 12:53:24 UTC
Channels for ISS:
H1:PSL-ISS_SECONDLOOP_PDSUMINNER_OUT_DQ
H1:PSL-ISS_SECONDLOOP_PDSUMOUTER_OUT_DQ
Channels for GS13s:
H1:ISI-HAM2_BLND_GS13X_IN1_DQ
H1:ISI-HAM2_BLND_GS13Y_IN1_DQ
H1:ISI-HAM2_BLND_GS13Z_IN1_DQ
I looked at the pointing of the IMs and MCs from the start of a lock 16th Janary to now. As previously found, nothing seems to have changed much, IM1 P changed by ~100 counts, more than the other IMs, but it's unclear what these counts are calibrated to.
Daniel, Naoki, Nutsinee
We installed a new VCO that allows us to increase the gain in the CLF loop (was 4kHz with 20 degree phase margin with the old VCXO). The box sits in the left SQZ rack U35. Below is the old VCO. CLF is now running at ~13kHz UGF with 40 degree phase margin. VCXO interface isn't working quite right but that doesn't stop us from locking the CLF. The "ON" switch is the excitation switch at the moment. The VCO control currently has a wrong sign and can't be turned on but it can be tuned by hand. CLF common mode board is now operating at -16dB common path gain with all three boosts on (no compensation). All relevant changes has been accepted in the SDF.
A quick look at the CLF noise (QMON) at 10 kHz tells us that we are now a factor of 5 better than last year. The Vpp calibration is 5V/rad.
Unrelated to this work we commented out OPO common gain in the guardian and have SDF take care of the gain value instead. We also accepted the PMC trans nominal value.
I updated the CPS cal filters for all of the ISIs this morning. This was to fix a slight, long standing error in the filters, as described in FRS 30428. Shouldn't really have any impact on the IFO. LLO was done a while ago, we can close the ticket.
A new VCO for the CLF was installed. This VCO has a higher modulation bandwidth compared to the previous VCXO at the cost of more low frequency phase noise.
The SSB phase noise according to the data sheets:
Frequency | New VCO | Old VCXO |
---|---|---|
100Hz | -103 dBc | |
1kHz | -110 dBc | -133 dBc |
10kHz | -132 dBc | -148 dBc |
100kHz | -150 dBc | -158 dBc |
Sorry I made a duplicate alog. More details here
Lights turned off.
Noting but left alone as commissioning work is still ongoing :
Quiet time between
PDT: 2024-03-11 19:11:02.319941 PDT
UTC: 2024-03-12 02:11:02.319941 UTC
GPS: 1394244680.319941
and
PDT: 2024-03-11 19:21:42.276196 PDT
UTC: 2024-03-12 02:21:42.276196 UTC
GPS: 1394245320.276196
Used this time to run BruCo: https://ldas-jobs.ligo-wa.caltech.edu/~gabriele.vajente/bruco_1394244680_STRAIN_CLEAN/
Notable coherences:
OMC-REFL_A_LF shows low-ish but broadband coherence with DARM above 30 Hz, and this is suggestive of the excess noise we see now w.r.t. O4a. Evan suggests that this could be 45 MHz sidebands amplitude noise, that dominates the OMC reflection, and has a small transmission through the OMC
comparing OMC_REFL with CLF to now
Atttached is a plot of the power spectrum of OMC-REFL during:
-- blue: REFL 45 O4a ( Janurary 15th 02:25 UTC )
--green: REFL 45 now (March 12th 12:30 UTC )
--brown: REFL 45 with CLF closed ( March 12th 00:24 UTC )
--red: REFL 45 with CLF open (March 12th 01:54 UTC )
Clearly, during O4a, the noise in OMC-REFL 45 was better compared to now. It seems from this is that the noise level does not change with the modulation depth (only looking at a 2 minute stretch); however, the source of the noise difference between CLF open and closed is not known. The noise level also seems to vary over the recent locks, which we cannot explain yet.
I ran a quick bruco on the OMC-REFL_A_LF channel itself, https://ldas-jobs.ligo-wa.caltech.edu/~elenna.capote/brucos/OMC_REFL/
J. Kissel, L. Dartez Jeff ran the calibration measurement suite. We processed it according to the instructions here. I then updated theCAL_DELTAL_EXTERNAL
calibration using the new report at/ligo/groups/cal/H1/reports/20240311T214031Z
.
Attaching the cal report. Optical gain: 2024-03-12: 3.322e+06 [DARM ERROR counts / meter] 2023-10-27: 3.34e+06 [DARM ERROR counts / meter] KappaC at the end of O4a: 1.006 Optical gain at end of O4a: 3.336e6 [DARM ERROR counts / meter] So the current optical gain is differs from what we had at the end of O4a by about 0.4%.
The calibration from this report has now been added to the LDAS cluster archive such that it shows up in the official infrastructure. It's location is https://ldas-jobs.ligo-wa.caltech.edu/~cal/?report=20240311T214031Z It was tagged as "valid" and "exported" as follows: On a local control room workstation (or on whichever computer system the report was created) $ cd /ligo/groups/cal/H1/reports $ touch 20240311T214031Z/tags/exported $ touch 20240311T214031Z/tags/tags $ arx commit 20240311T214031Z