PSL Weekly Status Report FAMIS 26358
Laser Status:
NPRO output power is 1.857W
AMP1 output power is 70.47W
AMP2 output power is 139.8W
NPRO watchdog is GREEN
AMP1 watchdog is GREEN
AMP2 watchdog is GREEN
PDWD watchdog is GREEN
PMC:
It has been locked 26 days, 3 hr 51 minutes
Reflected power = 22.27W
Transmitted power = 106.0W
PowerSum = 128.3W
FSS:
It has been locked for 0 days 0 hr and 18 min
TPD[V] = 0.7976V
ISS:
The diffracted power is around 4.0%
Last saturation event was 0 days 0 hours and 18 minutes ago
Possible Issues: None reported
Sun Mar 02 10:14:17 2025 Fill completed in 14min 14secs
Trying out a new colour scheme with the delta channels to distinguish between 30S, 60S and 120S chans.
TITLE: 03/02 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 0mph Gusts, 0mph 3min avg
Primary useism: 0.04 μm/s (yesterday 0.11 μm/s)
Secondary useism: 0.47 μm/s (yesterday 0.81 μm/s)
QUICK SUMMARY:
H1's had a great night with a current 8+hr lock. Secondary microseism AND Primary microseism have both been trending down over the last 18-24hrs (see attached).
LVEA Wifi continues to come up as "ON" in Verbal (but it's been in the INVALID state since 1008amPST on Maintenance Day, see attached).
TITLE: 03/02 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Microseism
INCOMING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 11mph Gusts, 8mph 3min avg
Primary useism: 0.05 μm/s
Secondary useism: 0.59 μm/s
QUICK SUMMARY:
Locking has been very difficult this evening. Getting past ALS and DRMI has been challenging. Possibly due to the Microseism.
I was able to get ISC_LOCK up to Low_Noise_ETMX before a lockloss.
H1 current status:
I have taken ISC_LOCK to Initial_Alignment again to see if H1 will get past DRMI and actually get locked.
It does seem like the microseism is falling so hopefully we can get locked on the OWL shift via H1 Manager.
TITLE: 03/02 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 12mph Gusts, 8mph 3min avg
Primary useism: 0.08 μm/s
Secondary useism: 0.67 μm/s
QUICK SUMMARY:
H1 is currently Locking DRMI_1F after receiving an Initial Alignment.
H1 has apparently been difficult to lock all day.
I'm not entirely sure why that is the case.
The secondary useism isn't that high, though yesterday there was a noticeable increase in primary microseism with out the aide of earthquakes.
Also I have a Stand Down query failure on my OPS_Overview screen, which can be seen on screen shots.
TITLE: 03/01 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Aligning
INCOMING OPERATOR: Tony
SHIFT SUMMARY:
It's a been a rough day on the locking front.
Microseism is high (the 2hrs when H1 was OBSERVING, you could definitely see alot of 0.12 - 0.15 Hz oscillations in many LSC, ASC, & SUS signals ndscopes).
DRMI has not looked great (even after fresh alignments). Not seeing many triggers for it and the flashes are as high as they have been. Hoping this is also microseism-related.
Also had a return of the SRC noise during OFFLOAD DRMI ASC earlier in the day, but then it went away.
LOG:
Managed to get 1.75hrs of OBSERVING this morning, but then had a lockloss. Acquisition is no easy either. DRMI & PRMI have not looked great after Initial Alignments (like they usually had been). BUT, there is high secondary AND primary microseism for H1. Will keep battling. Did not get to run the Saturday Calibration, because H1 was not thermalized this morning (in the last 13hrs we have not had a thermalized H1).
Have had some PRMI offloading which has taken as long as 4-5min (don't recall it taking that long...with that said, this current lock offloaded PRMI in under 2min).
H1 struggled last night/this morning--H1 was down close to 6hrs (NOTE: µseism is elevated).
Since there hadn't been an alignment, thought this would do the trick since one hadn't been run a few hours into relocking. Unfortunately, DRMI & PRMI didn't look great post-IA. CHECK MICH FRINGES helped. Then continued with locking with various locklosses. During locking I happened to notice a RETURN of the SRC noise during OFFLOAD_DRMI_ASC (noted: alog83080, alog82997). This is post-SRC2_Pitch gain reduction a couple days ago (alog83092, alog83078).
This noise issue definitely looks ugly and continues to exhibit SRM/SR2 Saturations heard via Verbal and for the one for this current lock it eventually calmed down on its own after a few minutes (this was around 1732utc). While waiting for H1 to get to OBSERVING, looked to see if we if there were other instances of this noise returning (atleast for the last 1.5 days). Here were the times when it occurred with the lower SRC2_P gain of 40 for ISC_LOCK state -111 (w/ notes for each one; also see attachments):
Perhaps it's getting worse? Also only had the one lockloss from looking at these for the last 1.5 days.
Sat Mar 01 10:12:29 2025 INFO: Fill completed in 12min 26secs
Delta time channels now continue post-fill showing the max-delta values attained, which for today is about 85C with the trip set to 50C. The Delta values are absolute, so the rise in TC temps appears as a second hump in the 30S lookback channels.
TITLE: 03/01 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 5mph Gusts, 3mph 3min avg
Primary useism: 0.11 μm/s
Secondary useism: 0.81 μm/s
QUICK SUMMARY:
Walked in to see H1 down, after figuring out what was going on (ISC_LOCK was stalled due to H1 Manager), and seeing that H1 hasn't had an alignment for a few hours, started an alignment a few minuts ago (feels like H1 has been requiring an alignment after locklosses the last few weeks). Alignment is almost done.
Primary microseism took a small quick stepup betwen 21-1utc, and secondary microseism returned to being above the 95th percentile since about 7utc. Winds are calm.
H1 is trying to lock but things seem shaky. The primary useism has grown quite a bit in the last 12 hours and the secondary is peaking above1um/s. We've had a few higher state lock losses, not in the same place, and we've made it to NLN recently, so I think I'll just let it keep trying for now.
TITLE: 03/01 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
INCOMING OPERATOR: TJ
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 9mph Gusts, 5mph 3min avg
Primary useism: 0.12 μm/s
Secondary useism: 0.52 μm/s
SHIFT SUMMARY:
H1 has been locked for 8 hours and 14 minutes and Observing all shift. I expect the Owl shift should be peaceful.
Everything seems to be running smoothly.
LOG:
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
22:14 | isc | keita.siva | optics.lab | - | iss pd array | 01:03 |
22:24 | ISC | Matt, Mayank | OpticsLab | n | ISS array | 01:03 |
TITLE: 02/28 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 143Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY:
Decent shift with only one lockloss (whose recovery was straightforward but an initial alignment was needed due to usual ALSy shenanigans). Also had a tour from a group from the VIT plant.
LOG:
The digital camera MEDM main window now indicates which cameras are copied by the CDS_CA_COPY Guardian node and written to front end models. These are denoted by a blue tick at the left edge.
The camera.yaml file has been expanded to add how the camera is powered and which network-switch and switch-port the camera is connected to.
TITLE: 03/01 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 7mph Gusts, 3mph 3min avg
Primary useism: 0.08 μm/s
Secondary useism: 0.37 μm/s
QUICK SUMMARY:
LHO H1 has been locked for 2.5 hours.
The IFO seems to be running smoothly, with decent range.
The plan is to continue to Observe for the rest of the Evening & night,
At 12:17:36 PST we had a sensor glitch on the BSC3 gauge, causing a VACSTAT alarm. This was another of the periodic glitches, the pressure stepped up from 3.2e-08 to 4.9e-08 for 4 seconds and then immediately stepped back.
vacstat_ioc.service was restarted at 12:26.
I replaced the bad pump seal on the one of the chiller pumps at the End X chiller yard on 2/27.
Fri Feb 28 10:06:02 2025 INFO: Fill completed in 5min 59secs
New code did not post-fill the ROC channels, I tracked this to a "calculated ROCs but didn't write to PVs" bug. Will test again tomorrow.
We tested a replacement in-vac WFS for 9MHz/45MHz (ICS ASSY load D1102002-001, S1301248) in preparation for the upcoming HAM1 vent (E2200228).
Rich will write about the details, but in short we have tested that the DC power supply current was good, DC responded as expected, and RF outputs made sense for 9MHz and 45MHz. We used screw-on type ISC AM laser head for this test.
Attached show the LOW (9MHz) and HIGH (45MHz) results measured using the network analyzer. In these pictures, reference trace (green) is Q3 and the live (yellow) is either Q2, Q1 or Q4. All in all these look good in that there's no reason to suspect that they aren't working as intended.
Minor detail is that there are differences not just in overall level because the beam is not centered on the diode and the beam is not circular either, but sometimes in the shape of the traces (for example look at the Q2 HIGH at around the shoulder of 45MHz peak). We've confirmed that both the level and the shape changed when Rich rotated the AM laser head. Don't know why the shape changes but Rich mentioned that the modulation might not uniform across the beam, or maybe we're somehow saturating something (but it didn't change much when we reduced the modulation current by 10dB w/o rotating the head).
Adding to what Keita and Jordan put in yesterday:
1. We looked at the data from the S1301248 WFS that's going to be the replacement device to be installed into HAM1. This was the original manufacturing data from when the head was built in 2014.
2. We checked that the quiescent current draw was the same as that described in the data sheet for this part. Saw 170mA and 240mA on positive and negative 18V rails respectively
3. We verified that each DC path responded both to ambient light (in terms of magnitude and polarity), and the photocurrent produced by the laser calibrator head we use to check the response of ISC photodetectors. The magnitude and polarity of the observed DC response was reasonable and confirms what Keita mentioned that the beam pattern coming out of the calibrator head is elliptic and offset slightly from the center of the four quadrants of the photodiode. Rotating the calibrator head allows the user to verify all quadrants behave similarly.
4. Using the calibrator head and a network analyzer, we were able to take the transfer function of each quadrant both 9.1 and 45.5MHz. Each quadrant's response was reasonable when compared to identical functions of other quadrants. We took the first quadrant we happened to measure and stored this to a reference trace on the network analyzer. The remaining quadrants were then superimposed onto the reference trace to make a comparison. While there are differences in the absolute amplitude of each trace (due to the elliptic nature of the calibrator head beam pattern), the overall shape of each trace was reasonable when compared to the other quadrants.
For the new WFSA noted above (D1102004-V6 S/N 005 S1301248), I wanted to update the ICS Assy Load to make more sense. So the ICS Assembly Load link above no longer works, but the new one is now this:
Just a note on these in-vac WFS: The Body for these assemblies is D1102004 and it has its own s/n stamped on it from when it was machined. However when a WFS Assy has its electronics installed, thus determining its operating frequency, and it is locked at this frequency because the WFS is then welded shut for in-vacuum install. When this happens, the WFS (assembly really) is then assigned a new s/n (such as the DCC-generated serial number for the electrical innards of this WFS---S1301248 in this case). I did not know this when I made this Assy Load, so I just picked a random s/n of 001---using the DCC s/n is a better and cleaner way to identify an installed-WFS assy.
I am working on the Noisebudget Model these days and made a summary of the WFS in use with calibrations:
WFS |
Serial No. |
RF Trans. [Ω = V/A] |
Responsivity [A/W] |
Demod. Gain [dB] |
Whit. Gain [dB] (40W) |
ADC [cts/V] |
Digital Gain |
Cal [cts/W] |
|||||
Freq. |
Q1 |
Q2 |
Q3 |
Q4 |
AVE |
||||||||
REFL_A |
S1301242 |
9 MHz |
894 |
894 |
1069 |
974 |
958 |
0.85 |
21 |
21 |
1638 |
1 |
1.7E8 |
45 MHz |
642 |
662 |
657 |
634 |
649 |
21 |
1 |
1.14E8 |
|||||
REFL_B |
S1301243 |
9 MHz |
822 |
873 |
742 |
861 |
824.5 |
0.85 |
21 |
21 |
1638 |
1 |
1.44E8 |
45 MHz |
678 |
644 |
635 |
648 |
651 |
21 |
1 |
1.14E8 |
|||||
AS_A |
S1300635 |
36 MHz |
810 |
828 |
872 |
891 |
850 |
0.85 |
21 |
12 |
1638 |
1 |
5.3E7 |
45 MHz |
707 |
718 |
732 |
766 |
731 |
3 |
1 |
1.6E7 |
|||||
AS_B |
S1300634 |
36 MHz |
846 |
904 |
826 |
832 |
852 |
0.85 |
21 |
15 |
1638 |
1 |
7.5E7 |
45 MHz |
644 |
711 |
719 |
691 |
691 |
3 |
1 |
1.5E7 |
Calibration (from W to cts) = RF Trans. * ADC * Responsivity * Digital Gain * 10^(Demod. Gain + Whit. Gain)/20
Just a note for ASC WFS REFL_A: S1301242 was swapped out in 2022 for S1301248. See alog #63544.