Thu Dec 11 10:16:18 2025 INFO: Fill completed in 16min 14secs
Gerardo confirmed a good fill curbside.
A quick summary of the current TwinCAT setup:
Any change of hardware needs to be reflected in the Altium workflow which serves as the basis for the system project using the provided scripts.
The Altium script will generate H1EcatC1_NetList.xml. ProcessTcNetList.ps1 will then use the netlist as an input to generate H1EcatC1_BoxList.xml and H1EcatC1_Mapping.xml.
(All located in C:\SlowControls\TwinCAT3\Source\Interferometer\H1EcatC1\Configure).
We have updated the spare Beckhoff computer to this version. The upgrade of the main Beckhoff computer is pending.
Wed Dec 10 10:11:15 2025 INFO: Fill completed in 11min 12secs
Late entry for yesterday's CP1 fill.
J. Kissel, S. Dwyer As we resume power-outage recovery lock acquisition now that the environment is more suitable than it's been in a week (LHO:88473), we (as in DIAG_MAIN) found this morning the ASC_REFL_9_I analog whitening state (whose setting is managed by Beckhoff) didn't match the digital compensation (whose setting is managed by h1asc SDF system). We suspect that this is a symptom of yesterday's beckhoff == twincat computer reboots that were necessary to support the beckhoff chassis upgrades for JAC (LHO:88463). Not sure where/if these analog whitening settings are in the Beckhoff SDFs, but I've trended - H1:ASC-REFL_A_RF9_I1_SWSTAT digital compensation setting status - H1:ASC-REFL_A_RF9_WHITEN_SET_1 analog setting status and have now reset them to "normal," with 2 stages of whitening ON, and FM1 and FM2 compensating them.
Yesterday we had trouble locking the SHG after the beckhoff restart. The scan range for the PZT was restored correctly after the restart to 45-100V, but it seems to no longer be the right range to find a resonance. This morning I changed the range to 0-100V, this allowed us to lock with the PZT voltage around 50. I've now set it to 20-100V and accepted this in SDF.
J. Kissel Post Dec 4th power outage, we've have an EPIC week of windstorms that have inhibited recovery effort, which has delayed upgrade progress. The summary pages (on their 24 hour cadence) and the OPS logs / environment summary don't really convey this well, so here's a citable link to show how bad last Friday (12/05), Monday (12/08), and Wednesday (12/10) were in terms of wind. Given the normal work weekend, it means that we really haven't had a conducive environment to recover from even a normal lockloss, let alone a 2-hour site-wide power outage. The attached screenshot is of the MAX minute trends (NOT the MEAN, to convey how bad it was) of wind speed at each station in UTC time. The 16:00 UTC hour mark is 08:00 PST -- the rough start of the human work day, so the vertical grid is marking the work days. The arrow (and period where there's red-dashed 0 MPH no data) shows the 12/04 power outage. The horizontal bar shows the weekend when we humans were trying to recover ourselves and not the IFO.
Oh right -- and also on Monday, even though the wind wasn't *that* bad, the Earth was mad from the after shocks of 7.0 mag Alaskan EQ, and there were end-station Software Watchdog trips related to it that -- because of an oversight in watchdog calibration -- scared everyone into thinking we should "stand down until we we figure out if this was because the hardware upgrades or power outage." See LHO:88399 and LHO:88415. So, Monday was a wash for environmental reasons too.
WP12916 TWO offload
Dave:
The archive and deletion of the past 6 months of raw minute trend files from h1daqtw0 is completed. The new post-O4 DAQ configuration we are testing on the 0-leg allowed the copy to be done by TW0 itself instead of using FW0 as a proxy. This sped up the copy, taking 17.5 hours instead of the previous 21 hours.
TW0 disk usage went from 95% to 2%
TITLE: 12/11 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 15mph Gusts, 9mph 3min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.47 μm/s
QUICK SUMMARY:
Initial Alignment Started.
Locking will start as soon as IA finishes.
TITLE: 12/11 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 52mph Gusts, 37mph 3min avg
Primary useism: 0.13 μm/s
Secondary useism: 0.61 μm/s
SHIFT SUMMARY:
We had Planned to lock today to get proof of life out of H1, but then...
The tumbleweeds were trying to get in from the Roof during the 70 MPH Wind conditions we had today. We let the tumbleweeds win and didn't try to lock but did other things.
Y arm was clear enough for TJ to get to, but X arm is impassable due to a tumble-anche along the road there.
Beckhoff Upgrades were done for Corner5.
Faroing was started but not finished.
JAC work has started and we were able to recover the IMC.
CDS was able to make some progress today as well.
Random notes I took throuout the day:
Dave did a restart everything here.
Frame writer restart happened today.
The Wind only Looks like it reached 114 MPH as indicated by the wind speed, but it only hit 70 MPH.
Corner 5 beckhoff install starting at 23:00 UTC
FW1 rerstart @ 23:05 UTC
Might need to reboot ASCSQZIFO or ASCSQZ0 computer: Completed.
PSL enclosure temps alarm sounded off at 23:22 UTC during the DAQ restarts.
440 channels added to H1EDC for beckhoff.
IMC recovery :
I ended up Clearing history on IMC WFS...
Reverted MC and IMC PZTs back to GPS time: 1449411452 (the last time we had the IMC locked.)
I then moved MC2 until the we had a good lock on MC_Trans. IMC-WFS_GAIN was taken from 0.04 to 0.4 and then back again to allow the WFS to move IMC.
We then offloaded it.
Forcast for tomorrow: https://alog.ligo-wa.caltech.edu/aLOG/uploads/88470_20251210180643_2025-12-10_18-06.png
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 15:57 | SAFETY | LASER HAZ STATUS | LVEA | YES | LVEA is LASER HAZARD \u0d26\u0d4d\u0d26\u0d3f (\u239a_\u239a) | 10:31 |
| 15:42 | FAC | Kim & Nellie | LVEA | y | Technical Cleaningq | 17:05 |
| 16:42 | TCS | Matt | Prep lab | n | Cheta table work | 18:52 |
| 16:50 | SEI | Randy | MY | N | Cleaning the Quad picker | 19:14 |
| 17:24 | Faro | Jason | LVEA | Y | Setting up Faro Equipment | 17:43 |
| 17:40 | PEM | Joan-Rene, Alicia | LVEA | y | Unplugging a cable | 18:57 |
| 17:40 | VAC | Jordan | Lvea | y | Purge air Dew point measurement. | 17:52 |
| 17:46 | SQZ | Sheila, Daniel, Kar Meng, Eric | LVEA | YES | HAM7 work | 20:24 |
| 18:24 | SEI | Jim | EY | N | Checking the Wind fence for damage | 20:24 |
| 18:25 | SQZ | Oli | HAM7 | y | Running parts | 18:29 |
| 18:42 | IAS | Jason, Ryan C | LVEA | y | Faroing | 20:46 |
| 18:52 | SQZ | Betsy | LVEA | y | Running parts & Info | 19:12 |
| 19:21 | JACK | Jennie W | JOAT | N | Working on JACK | 19:25 |
| 19:33 | SEI | Randy | LVEA HAM1 | y | Moving pallots near HAM1 | 21:33 |
| 20:43 | CDS | Dave | CER | N | Installing Hardward for CDS ADC upgrade | 21:43 |
| 21:40 | IAS | Jason, RyanC | LVEA | Y | FAROing HAM2 area | 22:27 |
| 22:18 | FAC | Tyler | CER | N | Checking temp alarm | 22:22 |
| 23:25 | SQZ | Sheila, Eric, Daniel, Karmeng | LVEA HAM7 | Yes | HAM7 OPO work | 01:03 |
| 23:43 | VAC | Betsy | Highbay | y | Leaving parts | 00:13 |
| 00:18 | OPS | RyanC | PCAL lab | N | Grab DM charger | 00:24 |
| 00:32 | JACK | Daniel | LVEA | y | Installing Jack Chassis | 02:32 |
| 00:33 | PEM | Ryan C | CER & LVEA | N | Setting up Dust monitor station | 00:48 |
| 00:38 | PEM | TJ | EY | N | Checking flow rate for dust pumps | 00:48 |
| 01:00 | IAS | Jason | LVEA | y | Turing off Faro | 01:09 |
Jennie W, Daniel S, Jeff K,
I added a JAC top_names part to the h1lsc model. This should be pretty simply as the JAC only has one RF PD for length feedback and two feedback paths, one to an onboard PZT and one to temperature of the JAC spacer, this latter part is done in Beckhoff.
The PZT output to the DAC is shown here.
The lower level contains a standard library REFL PD part but I removed the RF9 path and renamed the RF45 path to RF43 as this is the frequency we are using for the JAC control sidebands. There is also a block for reading out the low frequency signal 'REFL_A_DC' and a block for feedback filters 'L_SERVO'.
Jennie W, Daniel S, Jeff K,
Human Readable Summary:
Today I finished doing the last round of changes to ascimc.mdl which adds a path to do ASC for the new jitter attenuation cavity, JAC. As part of this, the IMC will no longer be using the PSL periscope PZT as a feedback path to control input alignment and instead this path will be used to align to the JAC. We have implemented logic in the IMC ASC model to use the IMC as normal just now. We have also put in the infrastructure in this model for the JAC ASC in a JAC top_names block. The JAC has 2 WFS, 1 RF PD as input and feeds back to the PSL periscope and JM1 tip-tilt suspension for alignment. These changes were built and added to the re-locked revision in the svn.
Details for the IMC: We have added a line to the output matrices of the IMC (old P and Y in medm) where the final fifth line is used to send signals to the new JM3 tip-tilt which will be installed in HAM1 during the vent downstream of the JAC and upstream of the IMC, these currently contain zeros in the fifth line but I haven't updated the medm screen for IMC_WFS yet. The ASCIMC model now contains send PCIe modules whoch correspond to the recieve modules in the SUS-JM3 model.
There is also a switch H1:ASC-IMCJAC_PZTOUTSW in the top level of the ASC IMC model to switch between the JAC servo using the periscope PZT as a feedback path (switch OFF) and the IMC servo using the PZT as a feedback path (switch ON). This has been saved in safe SDF snap file in the ON state which means the IMC should work as expected until we have the JAC installed.
I have uploaded a pic here and here of the changes made to the top level in H1ascimc.
Details for the JAC ASC: In the JAC top_names block we have the attached architecture. This has standard library blocks for the A and B JAC in-air WFS and the DC readouts of each these.
The controls are copied from the IMC model but with 2 degrees of freedom instead of 5. I have also skipped the dither locking controls as we don't seem to currently use this in the IMC.
Details for h1sqz model:
Four squeezer channels were added to h1ascimc model and removed from the h1sqz model are:
H1:SQZ-OPO_SERVO_EXC
H1:SQZ-SHG_SERVO_EXC
H1:SQZ-LO_SERVO_EXC
H1:SQZ-CLF_SERVO_EXC
- two are sent from the SQZ model, H1:SQZ-OPO_DITHER_DRIVE and H1:SQZ-LO_DITHER_DRIVE, they go into a SQZ block.
This block contains these filter banks, which we transferred from the h1sqz model. SHG_SERVO_EXC and CLF_SERVO_EXC have grounded inputs like they did the h1sqz model. The outputs are sent to the DAC0 channels highlighted with a green dotted line in this image of the h1ascimc model.
[Sheila, Eric, Kar Meng, Daniel]
At the time of removing soft cover, the particle count was ~2. We begun with the OPO dither locked. We also updated the ramp time on the PSAM controllers to be 100ms (they were at 1ms). It seems like the PSAMS are reading back the correct value (matches setpoint/target).
Betsy provided us with the screws for locking down the VIP, they are a #10 button head screw but they seem to fit in the slot for the locking mechanism. We have no washers for the #10 screw, which is not ideal. The #10 button head is not sufficiently wide enough and only engaged on one side of the slot. As a compromise, a 1/4" washer was tried to buffer this. Unfortunately, this was thick enough to prevent the screw from engaging on the threads, so two of the other bolts were installed without washers. One of the bolts that was installed is the correct bolt/washer. Once all the screws were in, the thumb screws were tightened and the OSEMs were checked. Pitch yaw and roll are all less than 1urad different. Vertical displacement is 100um different.
After finishing locking down: particle count was ~ 60
We were thinking about moving the second iris on the sqz path from between ZM3 and FC1 to between ZM2 and ZM3 so that we could see the retroreflection from the FC, but we abandoned this idea because Sheila thinks it wont be that helpful considering how difficult it seems it would be to move it there. As far as irises go, all the irises we need to install in the HAM7 chamber have been placed. We have irises installed on the transmission path to the homodyne and the CLF path on T7. It looks like the homodyne/transmission path is slightly misaligned relative to the irises placed before the vent (see images attached). We also still need to install one final iris on the green pump REFL path on T7 before we remove the OPO. We could not install this today because we could not get the SHG to lock.
We were having quite a bit of trouble dither locking the OPO, so the seed/clf input alignment may be a bit off. TEM01 and TEM00 have very similar dip fractions. By adjusting the locking code, Sheila was able to get the OPO locked to the TEM00 mode.
At the end of the day, we adjusted the iris between ZM3 and FC1 for better centering and placed 2 dogs around the OPO.
[Daniel, Karmeng]
We also placed an iris after the parascope on SQZT7 table to constraint the green reflected off the OPO.
Installed two 4-chn demod chassis and the in-vacuum interface chassis. This completes the chassis installation for JAC.
h1asc0 upgrade
Daniel, Jennie, Jeff, Fil, Jonathan, EJ, Dave:
An additional ADC was added to h1asc0's IO Chassis, Fil installed the corresponding AA chassis.
h1iopasc0 model was upgraded to add this ADC.
h1ascimc model was upgraded by Jennie and Jeff, this required a DAQ restart
h1lsc0 upgrade
Daniel, Jeff, Jennie, Dave:
New h1lsc and h1sqz models were installed. DAQ restart was required.
Beckhoff Upgrade
Daniel, Dave:
New ini files were installed for CSAUX, CSISC and CSTCS. DAQ+EDC restart was required
TW0 raw minute trends offload
offloading of raw trends from tw0 completed at 04:30 this morning. I reconfigured nds0 and started the file deletion at 16:50.
DAQ Restart
Jonathan, Dave:
DAQ was restarted twice, first for model changes, second for further model changes and EDC change (Beckhoff).
On first restart it was found that h1ascimc had removed two DQ channels used by GDS. There were returned for the second round of model/DAQ restarts.
I'm running a temporary HWS-ETMX dummy IOC on cdsioc0 to "green up" the EDC.
cds_status_ioc was upgraded to expect +1 ADC in the site wide ADC count.
Marc Daniel
We upgared the EtherCAT Corner Station Chassis 5 according to D1200132-v4 and E1200077-v4. The corresponding software changes were also comitted. This now includes all necessary upgrades to support JAC and most of the ones needed for BHD.
It's been a few minutes so far. There is emergency lighting. Luckily since it was lunchtime there were no people out on the floor. Recovery Begins!
The power was out from 2025-12-04 or Thursday Dec 04 2025 from 20:25 UTC until 22:02 UTC (12:25 PST to 14:02 PST)
h1pemex was upgraded from an 18-bit to a 20-bit DAC today, so we needed to make sure we had a calibration correction. The new filter banks that Jeff had put in (88321) for the calibration correction are called H1:PEMEX_EX_DACOUTF_1, H1:PEMEX_EX_DACOUTF_2, H1:PEMEX_EX_DACOUTF_3, and H1:PEMEX_EX_DACOUTF_4. I installed a filter called 20BitDAC that was a gain(4) in FM10 of each of these filter banks, loaded them in, and turned them on along with the input/output/gain of the filter banks. I've accepted these changes in sdf safe
Late update, but I put the channel names wrong. The new channels are called H1:PEM-EX_DACOUTF_{1,2,3,4}.
J. Freed,
I took Phase noise measurements of the 2 channel Keysight 33600A waveform generator for its use in building SPI Pathfinder in the optics lab before install. Going only off of the phase noise graphs, it is sufficient as it shows comparable results to the SRS which had a phase noise considered to be good enough for SPI pathfinder.
Key.png Shows the phase noise results. C1, C2 are the phase noise results for Channel 1 and Channel 2 on the Keysight, respectively. (Set up shown below). Shown for comparison the SRS SG392, which was suggested as a possible frequency source for SPI. The last measurement shown is the direct measurement of phase noise between the 2 channels of the Keysight. This measurement reflects the intended use case of the Keysight for SPI. As we need 2 frequencies at slightly different frequencies locked to each other and SPI will be measuring the output phase difference. Note the 60Hz peak; most likely caused by unclean AC power. This is why we are not using an AC powered device in the final installation.
Screenshot2025-12-01at50150 PM.png Shows the setup for C1, and C2. measurements. The SRS value was found with the same set up, just replacing the Keysight 33600A with a SRS. The C1-C2 is a direct measurement by plugging both channels into the BluePhase 1000. There is no 10MHz Ext back attachment in this measurment in order to best represent Keysight's theoretical performance in the optics lab.
Edit to the other comment and the main post
After a discussion with Jeff, we figured the best course of action would be to have all the generators referenced to the same generator. In order to better compare all the results. As well as, redo the plot in the previous comment to better reflect SPIs requirements as the base standard rather than the other way around.
PhaseNoiseSetUp.png Is a picture of the set up, it is similar to the previous tests except everything is referenced to the SRS. One thing I failed to mention in the previous tests and is not listed in the diagram is that the divide-by-eight goes into another Distribution Amp. before heading into the Ext. 10MHz of the function generators. Also note that the Double Mixer (DM) does not have an Ext 10MHz port. Instead it takes the 80MHz signal from the first differential amp; and a sin and cos 4096Hz signal from a CDS DAC through an AI chassis. (see 81593). Also note that the OCXO measurement took a pickoff from the first Distribution Amp instead of some sort of extra DoT.
Keyrad2.png Is the graph of phase noise measurements of the Double Mixer (DM) D2400315, a LIGO 80 MHz OCXO D080702 (Which both DM and OCXO are used in the final SPI design), and a Keysight 33600A dual source waveform generator which will be used during the SPI build. The phase noise measurements were all referenced with a SRS SG382. Note that the BluePhase 1000 set up calculates values in dBc/Hz, to convert to a more directly useful value for SPI, rad/rtHz, I used the conversion:
[rad/rtHz] = sqrt(2) * 10^([dBc/Hz]/20)
The w/o. Ref. label is a separate reference from the SRS. In SPI, there is a reference interferometer that removes noise gained along each of the arms of the main SPI Mach-Zehnder. Mathematically speaking, this subtraction has an attinuation effect on our phase noise of:
Phase Noise = D/c * f * Phase noise(w/o. Ref.)
Where D is the length mismatch in the main arm between the reference and the main interferometers (or ~30m), c is the speed of light, and f is the frequency of the phase noise. Or put another way, the plots that have the label (w/o Ref.) are the direct measurements of the phase noise while plots without that label are the theoretical effect of the noise in our system. We will experimentally test this later once SPI is installed using injections; by altering the 4096Hz CDS filter bank for the DM.
P.S. I have no idea why the OCXO noise is worse than the DM. We expected it to be better. A possibility is that since the DM measurements were taken more than a half a year ago, one of the devices was "just having a bad day" today. Investigating this, while interesting, is a lower priority than other tasks as the main goal of investigating the Keysight noise performance was achieved.
Edits to previous post. Graph: X axis label should be 'Frequency offset from 80MHz (Hz)' and y-axis label should be 'dbc'
Keyradwref.png and Keyradworef.png are the requirements for the phase noise of our oscilator with SPI having and not having a reference interferometer respectivly. In the final SPI pathfinder install, we will have a reference interferometer giving us much less stringent requirements on our oscialtors phase noise. But during the build, it may be nessisary to run tests without a reference interferometer, I plotted the without reference interferometer if that situation ever does come up.