Jennie W, Ryan C,
Ryan noticed that DIAG_MAIN was complaining about the anti-whitening and whitening filters for the two JAC WFS not matching. The fix was to go on sitemap->JAC OVERVIEW NEW->WFS->WFSA/WFSB->I Filters screen and toggle the switch for STAGE 1 on and off and on.
The CS_ISC model shows we expect the first stage of whitening to be on.
I trended back and it looks like the all four filters were switched off on 16th Sept at 11:04:26 UTC and then just the anit-whitening filters were switched on 6 hours later.
After we reset the whitening filters we checked there were no diffs on ASCIMC, CS_IMC and that the messages on diag_main had gone.
We received a new CRS HOQI TIA chassis this week, which includes a new amplifier for the capacitive dampers. Marc helped me set up an SR785 to test the new chassis and it looks like everything is as expected, though not exactly as laid out in the test procedure, T2600330.
For the PD TIAs in the first attached plot, we did a 10mV p2p tf from 100khz down to .1 hz. Input was single leg, with a 10kohm resistor on the + input. Output was differential. Overall gain was 30db, and shape matched what is shown in the procedure.
For the capacitive damper amp in the second attached plot, we did a 1V p2p tf from 100khz down to .1 hz. Input was differential and output was differential. Overall gain was 3.5db, but the test procedure says should be 9.5, however, I think this is known issue. The shape matches what is shown in the procedure.
TITLE: 09/25 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: Quite a lot of environmental noise today, high microseism (it turned around after touching the 90th percentile and is decreasing), a wind storm with sustained 40+ mph winds, and a large earthquake. The main focus of commissioning today was SQZer and OMC. CDS_OVERVIEW shows lock loss alert is down, disconnected channels.
* There's currently a fire south of Benton City by Horse Heaven Hills, anyone driving to or through Benton City should take care.*
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 14:42 | FAC | Kim | Optics lab | N | Tech clean | 14:59 |
| 15:19 | FAC | Randy | Yarm | N | Beam tube enclosure repairs, crack sealing | 18:18 |
| 15:46 | FAC | Kim, Dawn | EndX | N | Clean up garbage at recieving | 16:59 |
| 16:00 | EPO | Corey | YARM | N | Photography | 16:30 |
| 16:09 | TCS | Camilla | Vac prep lab | N | Inspect viewports | 16:52 |
| 16:49 | ISC | Mitch | MidY | N | Look for cables | 17:11 |
| 17:20 | SUS | Oli | CR | N | BS + ETMX transfer functions | 19:36 |
| 17:30 | PSL | Jason | CR | N | Ref cav alignment | 17:47 |
| 17:37 | VAC | Travis | LVEA | N | Check on gate valves | 17:44 |
| 17:45 | VAC | Travis | EndX | N | Take picures of GV20 area | 18:01 |
| 19:08 | VAC | Gerardo | LVEA | N | Look for parts, Nbay | 20:08 |
| 19:13 | CDS | Dave, Erik | EndX | N | EX hardware swap | 20:05 |
| 19:55 | EPO | Robert, Miranda, Caroline, Rachel, Oli, James | LVEA | N | LVEA tour | 21:05 |
| 20:49 | ISC | Mitch | FCES | N | Checking out inventory | 21:15 |
| 21:07 | SQZ | RyanS, Camilla | CR | N | OMC scan | 21:37 |
| 21:15 | ISC | Mitch | LVEA | N | Inventory | 21:24 |
| 21:27 | FAC | Richard, Gerardo | LVEA | N | Safety checks | 21:48 |
| 21:30 | EPO | Robert+fellows | Roof | N | Taking a look outside | 21:34 |
| 22:00 | ISC | Camilla, Marc | MidY | N | Electronics parts search | 22:31 |
| 23:05 | TCS | Camilla | Prep Lab | - | Inspecting viewports | Ongoing |
Jonathan, EJ, Erik, Dave:
WP13653 h1seiex computer replacement
Last night's crash of h1seiex was different from the two previous that day in that dmesg logged ECC RAM error correction issues. We opened WP13563 to replace the computer rather than just the memory DIMMs so we could test this computer offline in the DTS.
Erik and I replaced the W2245 computer with one from the spare pool, which had been running in production as h1sush2a until it was removed in Dec 2025 during the IFO upgrade. Since the replacement computer already had 4 Adnaco cards installed, we just moved the Mellanox GigE card from the old to the new computer.
| Removed computer (W2245) | SN 200601707 |
| Installed computer (W2245) | SN 200601708 |
Erik changed the BIOS to enable PERR/SERR reporting and changed the IPMI IP address.
We took the opportunity to remove the long-range-dolphin-ethernet test machine which had been left at EX at the end of that testing. We also removed the old h1cdsrfm's adnaco expansion tower enclosure (and the shelf it was sitting on) which is no longer needed.
Ryan S, Camilla. Followed 90783.
ZM4 and ZM5 PSAMS were set at 100V, strain gauges for ZM4 0.4V and ZM5 -4.5V. I turned on the servos.
Dither locked the OPO with 75mW SEED power. Had 1.1mW on SQZT7 IR PD.
Set ASC back to settings as in 90742.
When we opened the beam diverter, we could not see the SQZ beam, tried moving SRM back to alignment as in vent. Turned out Travis still needed to open a Relay tube GV, after the gate value was opened, we saw the SQZ beam and reverted SRM to nominal.
Needed to reduce H1:SQZ-ASC_TRIGGER_THRESH_ON to get the sQZ ASC to turn on. Turning on SQZ ASC dropped all powers, attached, so we must be clipping. Turned off ASC and cleared SUS histories.
Ryan then did a walk of ZM5 for AS_C and ZM6 for AS_A. Once we were closer, we turned on the SQZ ASC and it worked. We put in the H1:OMC-ASC_QPD_A/B_PIT/YAW_OFFSET we had in 91371. The OMC ASC went to these values when turned on.
We then turned off ASCs and ran /sqz/h1/Templates/dtt/OMC_SCANS/Sept25_2026_OMC_scan.xml (after taking H1:OMC-PZT2_OFFSET to -50). We got 00 peaks of max height 0.5V whereas before Sheila got 0.6V 90783, we are not sure why, the SEED power injected is the same. Initially had asymmetric peaks, checked whitening as in 90612, adjusted H1:OMC-DCPD_{A,B}_GAINSET to be HIGH. Peaks were then symmetric, we followed 91371 to lock OMC and tweak OM3 and OMC to slightly improve TEM00 mode. Our misalignment peak to was then ~1%, plot.
Ryan checked the ZM4 and ZM5 strain gauge ranges (from 5V to 195V avoiding 0 and 200V edges):
| Strain Gauge Reading | ||
| 5V on PZT | 195V on PZT | |
| ZM4 | -3.9V | 3.2V |
| ZM5 | -9.5V | -1.2V |
Ryan then adjusted 4x4 grid of PSAMS settings and ran: /ligo/gitcommon/squeezing/sqzutils/omc_scans_psams/ham7_psams_sweeo_QPD_centering.py
The data looked good with misalignments <1.5% and the best mismatch <1%. Plot attached. The analysis may need some tweaking by Sheila, the misalignment peak was not identified in all scans so I did not include it in the total of some to give us the mismatch values, edit attached.
We reran the OMC scans, zoomed in around our best area, results attached.
Because it's gotten quite windy outside, I've put the HAM3 CRS in-loop for RY. I don't expect this to cause any issues, but if the IMC starts showing a ~40 second oscillation, the CRS is a likely culprit. Doing a " caput H1:ISI-HAM3_BLND_RY_NEXT_CHAN 4 " in a terminal should revert HAM3 to nominal if there are any issues. Also since this is not a state set by any of the nominal guardians, any environment transion from SEI_ENV will also revert this.
I tweaked up the beam alignment into the FSS RefCav this morning; the ISS was ON for this tweak and the IMC was unlocked. Starting TPD was ~0.391 V, and current TPD ~0.498 V.
I also adjusted the ISS RefSignal, as the diffracted power % was ~3.5%. The new RefSignal is -1.97, changed from -1.98, and the diffracted power % is now hovering around the 4.0% target.
Sheila, Ryan S, Camilla.
First we used the SEED beam to see if we were getting 00 flashes on the FCES IR camera (CLF is too dim). We did a mode scan with GR_SUS_LOCKED and a 'z step' as below on the VCO, as attached. We think that with the higher order modes a lot of the beam is clipping the edge of the FC2 AR coating and making the sizes of the peaks in the scan not representative of real powers.
z step H1:SQZ-FC_VCO_TUNEOFS '+0.01,1200' -s 0.5
Better Centering beam on FC1
We then, with the FC locked on green, used the template naoki.aritomi/Desktop/FC2_dither and adjusted the P2L and Y2L gains. With our inital sliders P2L was 8.0 and Y2L was 1.0 to minimize the injected peaks. We then stepped ZM3 in negative Pitch and then compensated with FC1 FC2 to get green FC power back up. These moves did increase power on SQZT7 IR PD from 0.3 to ~0.5. Ending sliders attached with P2L was 0.5 and Y2L was 1.5. So not completely centered, but close. O4 values were 0.8 and -1.6. See template here. We do not need to completely center green now as if we need to pico this will need to be redone.
SQZT8 Checks
Expect:
To get a IR mode scan where we can see the tops of the peaks, we turned down SEED to ~ 0.5mW, I changed line 789 in SQZ_OPO_LR.py to have a 1.2 fudge factor so that I could lock with a seed dither lock with these low powers.
Our starting scan shows a lot of mis-alignment plot and extra peaks where we think the misalignment mode beams were outside the FC2 AR coating so showing up as bright hourglass shapes across the camera. We watched the camera to see what all peaks were as attached. We then manually put the VCO on a 00 IR mode with H1:SQZ-FC_VCO_TUNEOFS and then maximized this with FC1 and FC2 sliders, we ended with much better alignment plot and importantly, when the SEED power was turned back up to 75mW, had our expected ~1.1mW on the SQZT7 IR diode. This is great news we have a IR beam with okay alignment/mode-matching in the FC that makes it back though the OPO to SQZT7!
I tried stepping ZM3 and then adjusting FC1 and FC2 to try to improve IR 00 mode, but the green power was getting lower which was causing frequent green lock losses so I stopped.
Next steps are to adjust FC green to be co-aligned with IR (plan to do next week) and then can continue to improve FC IR alignment to measure mode matching.
TITLE: 09/25 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 18mph Gusts, 12mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.27 μm/s
QUICK SUMMARY:
Toward optimizing the JAC injection mode-match at 62 W, the 2 W LDWFS data (LIGO-P2600491) taken before the EOM swap, after it, and after the IO_MB_L2 move were re-analyzed with a full Finesse model of the injection and REFL paths. Mode mismatch power at 2 W: 1.8 % → 5.8 % → 4.5 % for the three states, consistent with the REFL PD lock/unlock ratio (1.9 / 5.7 / 4.9 %), which didn't enters the fit. The current lens position did not improve as much as predicted earlier because that prediction used the symplified model, which misses the near-resonance of the RF sideband's first-order modes in this cavity. The Finesse model includes it and now reproduces all three states. The 62 W analysis and the lens solution derived from it come next.
The table gives the fitted injected beam as a deviation from the cavity eigenmode, both taken at the output of IO_MB_L3. The eigenmode there has a waist of 545 µm (YAW) / 551 µm (PIT) located 4.93 m downstream of L3. dw is how much larger the injected waist is than that; dz is the position of the injected waist relative to the cavity waist, positive toward the cavity (downstream), so the negative values below mean the injected beam focuses before the cavity waist. Values come from the joint fit over the three data sets; the errors are statistical.
| YAW dw [µm] | YAW dz [mm] | PIT dw [µm] | PIT dz [mm] | |c20| / |c02| | mismatch (Finesse) | REFL lock/unlock | |
|---|---|---|---|---|---|---|---|
| before EOM swap (09/14) | +87 ± 6 | -94 ± 18 | +48 ± 4 | -138 ± 22 | 0.108 / 0.076 | 1.8 % | 1.87 % |
| after EOM swap (09/15) | +136 ± 6 | -511 ± 36 | +65 ± 4 | -143 ± 25 | 0.212 / 0.090 | 5.8 % | 5.73 % |
| after L2 move (09/16) | +100 ± 5 | -449 ± 28 | +30 ± 3 | -234 ± 21 | 0.183 / 0.092 | 4.5 % | 4.93 % |
Three data sets were taken at 2 W input, one per state of the injection path: before the EOM swap, after the EOM swap, and after the IO_MB_L2 move. Each set is a series of 30 s records (24 records, 12 for the last one).
Two angular actuators are dithered, each in both planes, at separate frequencies: JM1 at 9.7 Hz (PIT) and 11.3 Hz (YAW), the injection PZT mirror at 13.1 Hz (PIT) and 14.9 Hz (YAW). A length dither is applied to the JAC PZT at 809 Hz. In addition, during each record one pico motor sweeps the beam spot on one WFS head along one axis with a slow triangle wave (fundamental about 1.5 Hz), cycling through the four head/axis combinations over the series.
The recorded channels are the WFS quadrant I/Q outputs of both heads (H1:JAC-WFS_{A,B}_{I,Q}{1-4}_ERR_DQ). Offline, the amplitude of each angular line is read in the WFS signal (RF) and in the WFS signal demodulated once more at 809 Hz (DD: double demodulation), each normalized by the head's DD sum: 2 actuators × 2 planes × 2 heads × (RF, DD) = 16 line observables per data set.
The pico sweep adds, for each head/axis combination, the ratio RF/DD of the head's response to the spot motion. Being a ratio it needs no pico calibration, and it is a direct mode-mismatch observable: it measures the c2 content (together with the detuning x0) as seen at that head (4 observables). Each data set thus contributes 20 observables.
| before EOM swap | after EOM swap | after L2 move | |
|---|---|---|---|
| head Gouy phase, WFS A / B, PIT (shared) | 124.8 ± 0.7° / 189.1 ± 0.9° | ||
| head Gouy phase, WFS A / B, YAW (shared) | 112.7 ± 0.7° / 173.9 ± 1.1° | ||
| mismatch power (Finesse) | 1.8 % | 5.8 % | 4.5 % |
All parameters, errors and the per-record fits are in the detailed analysis note (to be posted).
Only IO_MB_L2 (and IO_MB_L1 by 3 mm) was moved between the 09-15 and 09-16 sets. Back-propagating the fitted 09-15 beam through the injection telescope and asking which L2 displacement reproduces the fitted 09-16 beam gives 18 ± 3 mm toward L1. The survey gives the L1–L2 spacing as 60 mm before and 26.5 mm after, i.e. an L2 move of 33.5 mm, so the error is ~1.5cm. This error is bigger comparing to the quoted error, which is statistical only (from the fit χ2); lens focal-length tolerances, the optic positions (even between PSL and HAM1) and any thermal lensing are not included.
Figures
Figure 1: Beam radius along the injection path from the IO_MB_L3 output to the cavity, YAW (left) and PIT (right). Black: the cavity eigenmode (waist 545 / 551 µm, 4.93 m from L3). Colored: the injected beams from the joint fit for the three states. In every state the injected beam focuses before the cavity waist with a larger waist, and the two planes differ.
Figure 2: The 16 line observables per data set — RF (top) and DD (bottom) amplitudes of the four angular lines on WFS A (blue) and WFS B (orange), normalized by the DD sum — for the three states. Bars: data with 1 σ errors; black marks: the joint-fit model (one shared WFS layout, per-state injected beam and x0).
At 19:39:56 PDT all the models on h1seiex stopped running after h1iopseiex detected an ADC timeout on the first ADC.
PCI bus scans can see all of the IO Cards.
Uptime of this crash was only 3hr 26mins suggesting a restart at 16:16 this afternoon. Trending the IOP CPU usage also shows an anomaly between 14:15 and 14:29
We will diagnose the issue and restart first thing in the morning.
2026-09-24T19:39:58-07:00 h1seiex.cds.ligo-wa.caltech.edu kernel: h1iopseiex: ERROR - An ADC timeout error has been detected on ADC 0, waiting for an exit signal.
2026-09-24T19:39:58-07:00 h1seiex.cds.ligo-wa.caltech.edu kernel: ligo_roce_mcast: ERROR - ib_poll_cq() - returned 128 results suggesting the buffer is not large enough.
2026-09-24T19:39:58-07:00 h1seiex.cds.ligo-wa.caltech.edu kernel: h1isietmx: ERROR - Waiting for ADC cycle 1242, live read is 62682, mm: 0, ioMemCtr: 1242
2026-09-24T19:39:58-07:00 h1seiex.cds.ligo-wa.caltech.edu kernel: h1hpietmx: ERROR - Waiting for ADC cycle 1242, live read is 62682, mm: 3, ioMemCtr: 1242
2026-09-24T19:39:58-07:00 h1seiex.cds.ligo-wa.caltech.edu kernel: h1isietmx: ERROR - An ADC timeout error has been detected, waiting for an exit signal.
2026-09-24T19:39:58-07:00 h1seiex.cds.ligo-wa.caltech.edu kernel: h1hpietmx: ERROR - An ADC timeout error has been detected, waiting for an exit signal.
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu rts_awgtpman_exec[11050]: H1:HPI-ETMXIOP cycle timeout
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu rts_awgtpman_exec[11207]: H1:ISI-ETMX_CDMON_ST2_V2_I_IIOP cycle timeout
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu rts_awgtpman_exec[10903]: CONIOP cycle timeout
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu systemd[1]: rts-awgtpman@h1hpietmx.service: Main process exited, code=exited, status=1/FAILURE
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu systemd[1]: rts-awgtpman@h1hpietmx.service: Failed with result 'exit-code'.
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu systemd[1]: rts-awgtpman@h1hpietmx.service: Consumed 11.418s CPU time, 42.4M memory peak.
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu systemd[1]: rts-awgtpman@h1iopseiex.service: Main process exited, code=exited, status=1/FAILURE
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu systemd[1]: rts-awgtpman@h1iopseiex.service: Failed with result 'exit-code'.
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu systemd[1]: rts-awgtpman@h1iopseiex.service: Consumed 10.982s CPU time, 76.6M memory peak.
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu systemd[1]: rts-awgtpman@h1isietmx.service: Main process exited, code=exited, status=1/FAILURE
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu systemd[1]: rts-awgtpman@h1isietmx.service: Failed with result 'exit-code'.
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu systemd[1]: rts-awgtpman@h1isietmx.service: Consumed 11.149s CPU time, 44.2M memory peak.
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu cps_xmit[10899]: Closing client
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu cps_xmit[10899]: message repeated 2 times: [ Closing client]
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu cps_xmit[10899]: Closing out OpenMX and exiting
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu systemd[1]: rts-transport@cps_xmit.service: Main process exited, code=exited, status=1/FAILURE
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu systemd[1]: rts-transport@cps_xmit.service: Failed with result 'exit-code'.
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu systemd[1]: rts-transport@cps_xmit.service: Consumed 4min 46.006s CPU time, 28.1M memory peak.
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu systemd[1]: rts-awgtpman@h1hpietmx.service: Scheduled restart job, restart counter is at 1.
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu systemd[1]: rts-awgtpman@h1iopseiex.service: Scheduled restart job, restart counter is at 1.
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu systemd[1]: rts-awgtpman@h1isietmx.service: Scheduled restart job, restart counter is at 1.
2026-09-24T19:39:59-07:00 h1seiex.cds.ligo-wa.caltech.edu systemd[1]: Started rts-awgtpman@h1hpietmx.service - Advanced LIGO RTS awgtpman: h1hpietmx.
Jennie W, Marc P, Fil C,
Summary: We still haven't found the issue with the segment 4 on QPD B and why it's noise is ~40 times higher than the other segments.
Marc and I checked (with a voltmeter) that the cable that takes the QPDB signal from chamber to the TIA variant 2 chassis is not connected to chamber ground and that it is connected to chassis ground at the other end that plugs into the TIA chassis.
The chassis input socket shield is also grounded to the rack ground through the front panel of the chassis.
To check that the high noise in segment 4 is not due to any problems with the shield, we plugged in a breakout board (which disconnects the cable shield from the socket shield) and checked the dark noise spectras again using the method and offsets detailed in alog #92010.
The high noise on segment 4 was unchanged by this.
This is making it look more likely that the problem is in chamber.
Tomorrow Marc and will use the breakout board to swap segment 3 and 4 at the TIA chassis input just to check this.
If the problem is only shown on the channel connected to segment 4 on the QPD then the problem is in chamber.
If this test shows that the problem persists on the same TIA channel then the next thing we might try is opening up the chassis to check if whitening is engaged for each quadrant (see D10001974 for wiring diagram of aLIGO ISC QPD Transimpedance Amplifier Primary Filter PCB). If the problem is only shown on the channel connected to segment 4 on the QPD then the problem is in chamber.
As a cross check I then turned off the measurement offsets in the QPD filter banks and re-opened the SPI shutter. Here is a graph of the spectra with light on the QPDs and you can see all four quadrants respond similarly for each QPD.
I put the dark offsets on the QPDs back to nominal and reset the IFO phase for the reference and measurement interferometers after unshuttering the laser.
Edit on Friday morning: I forgot to uinshutter the laser, have done this and reset the IFO phases again.
(Jordan V., Travis S., Gerardo M.)
Since controller for the large ion pump (IP12) at X-End had railed, see attached plot, and following a suggestion from others, yesterday we added a second controller to the large ion pump. Now, both of the controllers are railed. Let's see how long it takes them to recuperate.
We have started looking at the synthetic supersensors we created in seiproc for SPI commissioning and there are some things going on there I don't understand. For the 2 attached plots I look at 3 different versions of the table motion or loop error point, some calibrated GS13 CAL channels, the synthetic supersensors and the ISO loop inputs. For each subplot, red is the supersensor, blue is CAL CART GS13s, and green is the ISO in, first image is HAM2, second is HAM3, they weren't taken at the same time, so the spectra don't look exactly the same. I (probably naively) would expected all of these too look the same, with a caveat about sensor correction for the supersensor channels, the cps used there is before the sum with sensor correction, so the GS13 CAL and supersensor not matching between .1 and a few hz for X,Y and Z is because of that. What I (and I think Brian and Jeff) don't understand is why the ISO IN channels don't match. The input to the iso loops should just be the sum of the blended cps +senscor and gs13s. The blend filters I put in seiproc to construct the synthetic supersensor are the same ones we run nominally on the ISI. For the rotational degrees of freedom these should be the easiest to understand, but RX & RY for HAM2 and HAM3 are very different. Not sure what is going on. I had found one case of wrong sensors connected to filters in seiproc for HAM2 Z, but that has been fixed.
I have checked the signal routing out of the ISI master blocks to ipc senders to ipc receivers in seiproc and down to filter modules that generated the supersensors and haven't found any more errors, but it's a lot to look through. I have also spot checked that the right filters are installed in a number of places where supersensors don't look right, and have not found any errors so far there, either. I will try to keep looking. One of the next things I will do is read all the filters in matlab and plot them there, to make sure that all the filters are right.
I just checked the blend filters. As far as I can tell, all of the blends loaded into seiproc for these channels are correct.
To remove the confusion caused by the sensor correction, we will change the pick off point for the cps one that includes the sensor correction signal. This will only matter for the X,Y and Z dofs. Attached screenshot shows the change, the X pickoff on the left is the current before sc sum, Z on the right is the new pickoff point downstream of the sc sum.
I think this is probably an issue of loops limited by sensor noise. I just did a quick check on the platform at Stanford, and this shows up very clearly
(Tech Demo is fully isolated, passive measurement with the 0p6 blend on stage 2, looking at the X DOF. No sens corr from the ground)
My CPS sensors are not as good as the aLIGO versions.
2 plots, first with various signals, second with some coherence
Story: figure 1: Look at the inputs and outputs of the CPS and GS13 signals in the blend being used (blend #1) . The filtering looks as expected, the CPS gets a low pass (brown dashed to brown solid), and the GS13 gets a high-pass and a calibration conversion from velocity sensor to disp (ie (flat at 1 nm/sec above 1 Hz, scaling as f^2 from DC to 1 Hz) -> 1 cnt/nm) - green dashed to green solid.
The magenta signal is the sum of these two sensor signals, and the sum is very much below either signal up to about 10 Hz. So - these signals are entirely coherent below 10 Hz, and they cancel. This is likely because each sensor is adding noise, the loop is supressing the in-loop noise by imposing it as motion on the table, and now both sensors see the motion. See T2500279 for math about this.
The second plot shows the coherence between the CPS filter out and the GS-13 filter out. indeed, they are very, very coherent.
--
So - There is sensor noise, big deal. The sensors are limited by their noise and so is the platform. This is not news. You should be wary about believing what in-loop sensors tell you. duh.
BUT - it would be very useful to make a differential signal on HAM2-HAM3 from the onboard sensors to compare with the SPI. We obviously need to think about a reasonable way to do this. Using the supersensor while we drive the tables should be fine because the sensors are not noise limited. During normal operation we should think a bit more...
(sorry for the terrible image quality)
(Travis S., Jordan V., Richard M., Gerardo M.)
After the installation of CHeTA viewports, we connected an ISP-1000 scroll pump and a SS-500 cart to each of the main turbo pumps at the X beam manifold and Y beam manifold. After getting power sorted out to the ISP-1000s, thanks Richard, we started the pumpdown for both of the manifolds.
Something that we did noted was the new gauge for PT-180 shows almost 1000 Torr for pressure at atmosphere, this is not correct, then the other gauge for PT-170 shows 750 Torr for pressure at atmosphere, also not right.
Pumpdown has been stopped at the end of the day, and will be restarted tomorrow morning by Jordan.
Attached is a plot of both manifolds initial pumpdown.
Continued pumpdown of the XBM and YBM this morning, using 1x ISP1000 and 1x ISP500 for each volume.
| Starting Pressure: 45 torr | Start Time: 8:25 am |
| Turbo Crossover Pressure: 500 mtorr |
Turbo On: 3:10 pm (XBM) 3:25 pm (YBM) |
Total roughing time was ~ 10 hours, 3 hours and 15 minutes yesterday + 6 hours and 45 minutes today.
Once the turbopump reached full speed and chamber pressure was ~5E-5 Torr, I transitioned from the roughing pumps to the dedicated ISP250 and 80 l/s turbopump for the foreline.
Cooling water was adjusted so that pump and controller temps were ~40C. Setpoints adjusted to 1E-5 Torr.
We will need to leak test the 3 newly installed viewports before opening gate valves.
We leak checked the 3 ports which had viewports installed. Ports: YBM: A-1F VP3 and XBM: A-1C VP2 and VP4
We first removed viewport covers and bagged the viewport flanges leaving the conflat seal exposed, since the viewports are o-ring sealed and were previously leak tested.
No helium signal was observed above the leak detector background ~2E-10 Torr-l/s.
(Jordan V., Travis S., Robert S.)
Both gate valves, GV1 and GV2 were opened today, no issues encountered during the operation of both large gate valves. Robert was there to listen to the stroke of the large gate valves, GV1 does make a little bit of noise, but GV2 doesn't make noise. Attached is a plot of the pressure response at BSC2, corner vacuum volume is being pumped by two turbo pumps, XBM and YBM now. Dave B. on the controls to take care of the alarm settings, thanks Dave.