We measured the TTFSS OLG, I didn't save the data but will attach several photos here. There is a feature that looks like it could be unstable at 1.68MHz, there are about 3 untiy gain crossings around 500 kHz. The FSS has a gain between the test points that mean that unity gain is at -10dB in this measurement.
67253 Craig mentions that the FSS OLG was 350kHz, we'd need to reduce the gain by 3dB to get back to a 350 kHz ugf.
Fri Nov 01 10:10:11 2024 INFO: Fill completed in 10min 8secs
Jordan confirmed a good fill curbside.
We lost lock at some higher states in the relocking process due to the laser glitching* issue that we have been having. At this point we decided to pause locking for now to run some tests that were discussed during a meeting yesterday. The current plan is to hold at 2W with the ISS, FSS, and IMC locked. If this configuration is found to be unstable or we see excessive glitching still, then we will start to remove just the ISS or FSS, etc to narrow down the problem.
During this time, other, approved, light maintenance activities can take place.
*The issue may not be the laser itself, but I'm unsure what else to call this at the moment.
We sat in this configuration from 15:34:37 UTC Nov 1 until the IMC lost lock at 16:45:34, 1 hour and 10 minutes. The attached screenshot shows some channels at the time of the IMC lockloss, FSS fast mon and PC mon show some growing oscialltion until the time that the reference cavity transmission drops, the ISS sees a jump, and the IMC unlocks.
We've been sitting with the IMC in offline (MC2 is misaligned so the IMC won't flash), with the PMC, FSS and ISS locked since 17:09 UTC.
Summary of today's tests:
Another BSC3 PT132 gauge glitch caused a VACSTAT false alarm at 00:28:26 this morning. I captured the MEDM (attached) and restarted the service at 07:02.
As in previous PT132 glitches, it is the detaP channel which triggered, just exceeding its trip value of 1.0e-08 Torr
Code is being worked on to mitigate this issue.
TITLE: 11/01 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 14mph Gusts, 11mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.52 μm/s
QUICK SUMMARY: Relocking, powering up right now. useism is starting to trend down.
TITLE: 11/01 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY:
IFO is in NLN and OBSERVING since 02:36 UTC
Mostly a quiet and uneventful shift, with the exception of the squeezer failing to lock for abbout 50 mins (until we lost lock - Lockloss Alog 80985). Vicky reverted some changes to SQZ that were made today (comment alog 80984) I accepted those SDF changes (attached).
Microseism is still high and rising, but doesn't seem to be too much of an issue.
LOG:
None
Lockloss while troubleshooting SQZer not locking (before going into OBSERVING). No IMC tags on the Lockloss Tool.
[Jenne and Betsy in PSL enclosure; Jason logged in remotely; Marc, Fil, Rick, Fernando as EE support; consults with Daniel]
At today's commissioning meeting, we decided that one candidate thing to try to help mitigate the lockloss-causing glitches would be to swap in one of the spare TTFSS boxes. We also noted that if it was going to happen, it had to happen today, or wait until Mon/Tues next week. So, we tried swapping in a new FSS box. We were unable to lock the RefCav with either spare without significant oscillations, so ended up putting back in the original box, and that's how we'll leave things at least for the weekend.
Each time we changed out a box, we followed the steps 1-5 of our work permit 12182 (listed also below). In particular, before unplugging the 37 pin connector on the back, we had one of the support folks turn off the high voltage in the mezzanine of the CER (I think it is a pair of Kepcos, one +150V, one -150V). Then, once we had the 37 pin connector secured in the new box, one of the support folks went back to the mezzanine and turned back on the high voltage.
For both spares, the autolocker was able to find a ref cav resonance and hold it there. However, even with both the FAST and COMMON gain sliders set to the minimum values of -10dB we saw significant oscillation of the loop. An idea I had later (have not yet checked with anyone else to see if it's crazy or not) is to try one of the spare boxes, but with an attenuator on one of the cables, to see if it really is just a loop gain thing, or if there is something else going on. This could potentially be tried next week.
We first tried the 'blue box' spare, since it is supposed to be the same (including form factor) as the in-service unit. We noted that this box has had trouble in the past, but Marc said he'd taken a look and made some fixes, so it should work. Since that one caused oscillations and had previously been known to be challenging to work with, we tried also the 'silver box' spare, which I think has also been referred to as 'Rev-C'.
The silver box spare is a different form factor and different front/back panel than the blue box style, but it's supposed to be a drop-in replacement. There is no space to mount the water-cooled cold block, so if we had left the silver box TTFSS in place, we were just going to leave the cold block hanging around on top of the box, but not mounted to anything. Also, on the blue boxes, there is a SLOW output on the back panel that goes to a RAMP IN on the front panel. However, on the silver box that SLOW output is on the front panel, and it needs to be connected to the FAST OUT2 also on the front panel. Finally, the spigot labeled "PC" on the blue boxes is labeled "EOM" on the silver box. To install the silver box, you'll also need 2 adapters to go from TNC (on the silver box) to BNC (what the cables are, and what the blue box is), so bring those into the PSL enclosure with you.
Steps from the work permit submitted by Jason:
1)Unlock FSS RefCav.
2)Turn off High Voltage power supply in CER mezzanine.
3)Enter PSL enclosure and disconnect in-service TTFSS box.
4)Install spare TTFSS, hooking the same cables to the same ports on the TTFSS box; turn HV supply back ON.
5)Try to lock RefCav.
If it locks:
6)Measure TF to set common gain for ~500kHz UGF.
7)Measure crossover (use SR785, take a spectrum of IN1 port, crossover is at ~20kHz), set Fast gain to minimize hump in spectrum.
If it will not lock, then follow the same steps above to re-install the in-service TTFSS box.
TITLE: 10/31 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: Currently relocking and at DARM_TO_RF. Spent most of the day unlocked, with two locklosses and multiple hours of downtime while trying to figure out the FSS issues. Relocking since that work finished has gone great so far.
A couple minutes after Jenne and Betsy left the PSL laser room(and maybe also antetroom), we did notice the FSS PZT have the huge oscillations for about two minutes(attachment), similar to those we had been seeing on the backup FSS boxes(probably alog to come). Jenne is not sure what that means in the case of this FSS box, but mentioned that it might have been due to turning off the air conditioning or something else related to them being in there.
LOG:
14:30 Close to end of an initial alignment
14:40 Initial alignment done, relocking
15:25 NOMINAL_LOW_NOISE
15:32 Observing
16:01 Dropping Observing for Commissioning
16:22 Lockloss
17:17 Took to DOWN and started manual initial alignment due to DRMI being bad and PRMI ASC having trouble
17:31 manual IA done, started relocking
18:13 NOMINAL_LOW_NOISE
18:35 Lockloss from little earthquake+low CARM gain actuation range
18:38 Started an initial alignment
FSS unlocked due to measurement cable being plugged in and was unlocked for an hour
20:05 FSS relocked, started manual initial alignment for PRC, MICH, SRC
20:21 Left manual initial alignment for IDLE for PSL FSS box swap
22:59 PSL incursion done, started an initial alignment
23:17 Initial alignment done, relocking
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
15:28 | FAC | Karen | OptLab/VacPrep | n | Tech clean | 15:50 |
16:02 | PEM | Robert | LVEA | n | Setting up for injections | 16:20 |
16:28 | PSL | Sheila, Vicky | LVEA | n | Setting up for measurements | 16:37 |
17:01 | FAC | Karen | WoodShop | n | Tech clean | 18:02 |
18:41 | PSL | Jenne, Sheila, Vicky | LVEA | n | Connecting cable for FSS transfer functions | 18:59 |
20:02 | ISI | Jim | HAM Shack | n | Move measurement equipment | 20:40 |
20:36 | PSL | Betsy, Jenne | PSL Encl | y(local) | Swapping FSS box | 22:58 |
20:39 | EE | Fil, Rick, Daniel, Fernando | CER, LVEA | n | Turning off HV, looking at PSL rack layout (Fil out 21:13), Rick out | 22:12 |
20:59 | Richard | LVEA | n | Looking at PSL light pipes | 21:15 | |
21:03 | FAC | Tyler | CER | n | Investigating burning smell | 21:07 |
21:16 | EE | Fil | LVEA | n | Looking at SQZ racks | 21:56 |
21:22 | EE | Rick, Fil | CER | n | Turn HV back on | 21:25 |
21:48 | EE | Fil | LVEA | n | Taking other FSS box out to PSL | 22:29 |
21:58 | EE | Marc | LVEA | n | Helping with FSS box | 22:14 |
21:58 | Rick | CER | n | Turning off high voltage | 22:12 | |
22:16 | EE | Rick, Marc | CER | n | Turning HV back on | 22:21 |
22:35 | EE | Rick, Fil | CER | n | Turnign off HV | 22:54 |
TITLE: 10/31 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 18mph Gusts, 14mph 3min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.80 μm/s
QUICK SUMMARY:
IFO is LOCKING and recovering from CORRECTIVE MAINTENANCE.
To solve some of the PSL/IMC issues, IFO went into maintenance in order to swap out the FSS box. Unfortunately, both spares had PZT oscillations so we had to revert the swap. Attempting to get observing through the weekend until further potential action.
Vicky was concerned that the SQZ_SHG stays trying and failing to lock even when the IMC is unlocked. Driving the PZTs unnecessarily and maybe injecting excess light into the fibers.
We edited ISC_LOCK's DOWN to now take SQZ_MANAGER to DOWN and then ISC_LOCK's READY (had to main a main state) to take SQZ_MANAGER to FDS_READY_IFO in. Previously requested SQZ_MANAGER to FDS_READY_IFO in DOWN.
Also edited SQZ_MANGER's DOWN to take SQZ_SHG and SQZ_PMC to DOWN. Reloaded all guardian. Previously didn't touch them.
Vicky and I plugged in the 785 to the IMC common mode board. The first attachment was taken while Oli was trying to lock DRMI, with 10W into the IMC for CHECK_MICH_FRINGES, ugf just over 4kHz. The second attachment was taken at full lock, nominal low noise, a nearly 80kHz UGF. This is somewhat higher than in March 76753
Detector is currently in IDLE while the FSS box gets swapped in an effort to solve our PSL/FSS issues.
Lockloss @ 10/31 18:35UTC due to small earthquake, high microseism, and low CARM actuation range(80969)
We re-enabled FC beam spot control, by enabling inputs to the H1:SQZ-FC_ASC_INJ_ANG_{P,Y} filter banks. Seemed to just work (see attached screenshot) - moves ZM3 to control the spot on the green QPD in filter cavity transmission (SQZ-FC_TRANS_A on SQZT8). Have not yet checked the centering, last done in May 2024 (see 77942 , 69276 , 69374 , 73777).
QPD offsets are set in the FC_ASC_INMATRIX filter banks, last column and row.
I set the flag in sqzparams.py (use_fc_beamspot_control = True), and reloaded SQZ_FC guardian so it will be used in the next locks.
Disabled FC beam spot control (use_fc_beamspot_control = False) and loaded SQZ_FC guardian. We can try that again later, beam should be closer to centered now.
FC had a hard time locking in this past lock (ending ~0100 UTC), so that lock didn't have squeezing injected. We first used sliders to set ZMs2-3 and FC1-2 back according to M1_DAMP_{P/Y}_INMONs, to a time during the last lock. FC alignment was still bad with slides set back (bad green tem00 trans, green vco not catching the lock stably).
Then see the attached scope for the QPD alignment that worked. Overall what we should have done: 1) bringing SQZ_MANAGER through DOWN first (I think that fixed something). 2) Setting ZM3+FC1 according to RLF QPDs in HAM7, then set FC2 according to green trans QPD (FC_QPD_TRANS_A) on SQZT8. Biggest move was moving FC2 Y by about +20 on the slider, which is a really big change for this one. With setting SUS back based on top mass osems, then green FC_REFL looked bad, and FC couldn't hand off the IR lock successfully. With the alignment looking good on all QPD's, the FC alignment looks stable (both FC_GR_TRANS and FC_GR_REFL), and I think FC should lock next time.
Reran all O4b locklosses on the locklost tool with the most up to date code, which includes the "IMC" tag.
I used the lockloss tool data since the emergency OFI vent (back online ~23rd August) until today and did some excel wizardry (attached) to make the two attached plots, showing the number of locklosses per day tagged with IMC and without tag IMC. I made this plots for just locklosses from Observing and all NLN locklosses (can include commissioning/maintenance times), including:
Attaching plots from zooming in on a few locklosses:
Time | Tags | Zoom Plot | Wide Plot |
2024-10-31 12:12:26.993164 UTC (IMC) | OBSERVE IMC REFINED | annotated plot | plot |
2024-10-30 12:16:33.504883 UTC (IMC) | OBSERVE IMC REFINED | annotated plot | plot |
2024-10-30 16:09:21.548828 UTC (Normal) | OBSERVE REFINED OMC_DCPD | N/A | annotated plot |
The 10-31 zoom plot notes the framerates of the channels: ASC, REFL and NPRO_PWR are 2kHz and GS13 is 4kHz, the others are 16kHz.
Since September 18th we've had 21 locklosses from NLN tagged as FSS_OSCILLATION, of these 20 also had the IMC tag. Since September 12th, we've had 49 locklosses from NLN tagged IMC, so roughly 40% of these IMC locklosses have the FSS oscillation tag, since the NPRO was swapped we don't have any tagged with FSS_OSCILLATION.
(Reminder, the FSS_OSCILLATION tag is an old tag, intended for a different problem, but it tags times where the FSS fast mon goes above a treshold.)
Updated plot attached of NLN locklosses tagged with and without the IMC tag.
Continuing on from Jenne's observation that there are still glitches in the new NPRO, I've tried to make a plot we can use to compare the glitch rate in the new and old NPROs, using the NPRO_PWR channel instead of the FSS channel which isn't available for the new NPRO.
I've used a 3 hour stretch of observing time for the old NPRO, and a three hour stretch before the time when Jenne made a plot in 80837. The ISS is not on for the new NPRO time, which is probably why the intensity is flcutuating and making it harder to see the small steps in power that are the glitches we are looking for. In the second panel, I've plotted the data high passed with a 0.05 Hz butterworth, this helps to show the glitches, although not perfectly (in either case). Based on this, the glitches look to be happening at a roughly similar rate, although somewhat less with the new NPRO.
This script in in sheila.dwyer/DutyCycle)4/dutycycleplots/PSL_glitches.py
Attaching another plot, showing that comparing our old NPRO to LLO during an observing stretch that started at midnight UTC time on Oct7th, LLO has no similar glitches.
Here's the same plot, but using a time from last night when the PSL environmental controls were off. There are still gltiches, but fewer.
These plot tiles show runs of Sheila's code looking for PSL power glitches on several days before / after the suspect date around Sept 12.
There's not a clear correlation between the glitches and locklosses. While maybe there's more glitches after Sept 12 (bottom row), the glitches don't consistently correlate with locklosses? Sept 14 is a good example of this: lots of glitches, the IFO stays locked through many of them.
2nd plot here shows overnight again with the swapped new laser. There are still glitches (though potentially less).
The PSL-PWR_NPRO_OUT_DQ channel seems to not be connected at LLO, which explains why the comparison plot a few comments above makes it look like L1 PSL is so much quieter than H1.
Adding screenshot of the NPRO power glitches over the past day. There are still glitches with the new laser -- not all glitches correspond to locklosses, but some do.
Sheila, Vicky, Camilla
We have turned back on the SQZ angle servo using the ADF at 322Hz. Last briefly tried while testing ADS alignment in ADS in 80194. Turned on ADF and used 'python setADF.py -f 322'. Then set H1:SQZ-ADF_OMC_TRANS_PHASE to get H1:SQZ-ADF_OMC_TRANS_SQZ_ANG close to zero and checked by stepping the SQZ angle that there is a zero crossing in the ADF measured SQZ angle, plot attached.
The servo adjusts the SQZ angle (H1:SQZ-CLF_REFL_RF6_PHASE_PHASEDEG) via keeping the ADF measured angle (H1:SQZ-ADF_OMC_TRANS_SQZ_ANG) at zero. Setpoint can be adjusted using the ADF phase (H1:SQZ-ADF_OMC_TRANS_PHASE).
Tagging Detchar: ADF is now on at 322Hz. It was turned all the way off in 79573 by Alan. We can adjust the frequency 50-500Hz if there is a better place for a line.
Note to operators: if you want to run SCAN_SQZANG, the ADF servo will now overwrite the sqz angle. So BEFORE going back to FREQ_DEP_SQZ you'll want to tweak H1:SQZ-ADF_OMC_TRANS_PHASE (via sqz overview > ADF) to make H1:SQZ-ADF_OMC_TRANS_SQZ_ANG close to zero. Or you can tweak H1:SQZ-ADF_OMC_TRANS_PHASE (via sqz overview > ADF) until the SQZ BLRMs/ DARM is best.
Trends of the ADF servo stabilizing the SQZ angle overnight. Looks good: the ADF SQZ ANGLE servo can hold the maximum squeezing level throughout the lock! Last night was running with the ADF SQZ angle servo + SQZ-IFO AS42 ASC together.
In the first lock of the screenshot, the ADF SQZ ANGLE servo is not yet running, and the squeezing level drifts quite a bit (~0.5-1 dB in ~2 hours, and ends up un-optimal). In the last 2 locks, the ADF SQZ ANGLE servo is running and successfully stabilizes the SQZ angle, though the 2 locks from last night stabilize at different SQZ angles (weird?). Note SQZ ASC is running in both of these locks, so it seems like ASC + ADF SQZ ANG servo work well when used together.
Naoki looked at sqz trends with/without the ADF servo before in LHO:75000. Looking at sqz trends for yesterday, the ADF servo stabilized the SQZ angle in the first ~25 minutes. Then over the first ~2 hours, the ADF servo needed to move the CLF_RF6 demod phase by 5-10 degrees to hold the SQZ angle stable. This implies something like, the optimal injected squeezing angle changed by about 2-5 degrees during IFO thermalization.
Also noting a reference to LHO:77292, where Naoki does an On/Off test with the ADF line at 322 Hz.
Checked against the 68139 list, can see that 322Hz is a good frequency for CW. We will look at trying to add this ADF line to the _CLEAN or _NOLINES subtractions.
Scans from the FSS after reducing gain.
In Marc's files above the A one should be magnitude for 100kHz to a few MHz frequency span, B should be phase for that measurement. C should be magntiude zoomed in on the 1.7MHz region, D should be phase for that measurement.