TITLE: 03/11 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 5mph Gusts, 2mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.28 μm/s
QUICK SUMMARY:
Observing at 152Mpc and have been Locked for 1 hour.
WP12374 WP12370 ASC and SUS model changes.
Daniel, Jeff, Jonathan, Erik, TJ:
New models were installed for h1asc, h1susim, h1sushtts and h1suspr3. A DAQ restart was required.
WP12372 Add ISI HAM1 cards to h1seih16 IO Chassis
Fil, Marc, Erik, Dave, Jim, TJ:
h1seih16 was powered down. In its IO Chassis the bad A2 Adnaco backplane was replaced and the cards which had been moved to A3 were returned. Two additional ADCs and one additional BIO6464 were installed as per drawing (attached) which will be used by the new h1isiham1 model. Currently these cards have no external cables attached.
A new h1iopseih16 model was installed with these cards added. Note an additional 16bitDAC was not required because seismic ham models allocate a DAC per chamber, with the HEPI model using the lower 8 channels and the ISI model using the upper 8 channels. DAC-1 was already installed for h1hpiham1.
Note that this was one of two changes to the h1iopseih16 model (see SWWD section).
DAQ restart was required.
WP12373 Install new h1isiham1 Model
Jonathan, Erik, Jim, Dave:
The first version of the ISI HAM1 model was added to h1seih16. It is currently running with nothing connected to its ADC, DAC and BIO cards.
This is not something we do regularly, so we took the opportunity to document the steps needed. The list we have so far has been included as a spreadsheet.
The model was added to the DAQ. A related change to h1hpiham1 was also made. A DAQ restart was required for both.
Attachment shows the CDS Overvew MEDM h1seih16 section, now with a full complement of models.
WP12382 HAM1 SWWD
Jeff, Dave:
In preparation for HAM1 ISI install, we created a HAM1 Software Watchdog (SWWD) on h1iopsush2b and h1iopseih16. Note this is the second change to h1iopseih16 today.
There are two suspensions on HAM1; RM1 and RM2.
Despite its name, h1iopsush2b also controls ham1 suspensions. A SWWD part on h1iopsush2b reads the UL, LL, UR, LR raw ADC channels and calculates their integrated RMS values. If any value exceeds the trip level, the Dolphin IPC channel sent to h1iopseih16 is set to zero.
The IPC receiver on h1iopseih16, on receipt of a trigger signal, starts a DACKILL count-down timer. If the timer expires, it executes a DACKILL for the second DAC card, which drives HAM1 HEPI+ISI.
New h1iopsush2b and h1iopseih16 models were installed. The h1iopsush2b was done at the same time as the h1susim and h1sushtts models since these are the only models running on this front end. h1iopseih16 restart was done when this front end was powered back up after the IO Chassis work.
The SWWD MEDMs were updated with the new HAM1 system (attached)
Note: one complication is that up until now SUS SWWDs have been for larger suspensions with 6 OSEM channels (F1, F2, F3, LF, RT, SD). RM1,2 only have 4 (UL, LL, UR, LR) and so the two unused OSEM inputs have been grounded in the models. On the MEDM I just show ADC0_30, the channel prior to the duotone which is zero.
WP12358 Move Digital Video Cameras from h1digivideo2 to h1digivideo5
Patrick, Jonathan, Erik, TJ, Sheila, Dave:
We moved the six cameras which were on the last of the old servers (h1digivideo2) onto the new AMD/deb12 h1digivideo5 and powered down the old machine.
All was good until locking started, which is was discovered that for cameras which are copied to front end models the X,Y centroid EPICS channels now had offsets which the models could not handle.
For locking expediency it was decided to move the cameras back to the old server for now until the models could be configured to use to the new centroid values. Of the six models, five were moved back to h1digivideo2 (BS, ITMX_RED, ITMX_GREEN, ITMY_RED andITMY_GREEN). POP-AIR is not copied to FE models and so could stay on h1digivideo5.
At time of writing H1 has locked and been in OBSERVE for 50 minutes.
To "green up" the EDC I am running a dummy IOC on opslogin0 to serve the new channels for these cameras which were lost when we reverted them to the old software.
The camera MEDM shows which ones are still running on VID2 (attached).
DAQ Restarts:
Jonathan, Erik, Dave:
Due to the large number of changes we did two DAQ restarts today. The first was primarily for the ASC and SUS model changes and SWWD. The second was for the addition of the new h1isiham1 model and the camera move.
The EDC restart was due to new:
H1EPICS_DIGVIDEO.ini (at the time, moved 6 cameras to new server)
H1EPICS_DAQ.ini (add h1isiham1)
H1EPICS_FEC.ini (add h1isiham1)
H1EPICS_SDF.ini (add h1isiham1)
Tue11Mar2025
LOC TIME HOSTNAME MODEL/REBOOT
08:14:26 h1asc0 h1asc <<< ASC and SUS model changes
08:15:06 h1sush2a h1suspr3
08:17:36 h1sush2b h1iopsush2b
08:18:12 h1sush2b h1susim
08:18:34 h1sush2b h1sushtts
08:19:08 h1susauxh2 h1susauxh2
08:22:02 h1daqdc0 [DAQ] <<< 1st DAQ Restart (no EDC)
08:22:15 h1daqfw0 [DAQ]
08:22:15 h1daqtw0 [DAQ]
08:22:19 h1daqnds0 [DAQ]
08:22:23 h1daqgds0 [DAQ]
08:22:56 h1daqgds0 [DAQ]
08:26:16 h1daqdc1 [DAQ]
08:26:28 h1daqfw1 [DAQ]
08:26:29 h1daqtw1 [DAQ]
08:26:30 h1daqnds1 [DAQ]
08:26:39 h1daqgds1 [DAQ]
08:27:07 h1daqgds1 [DAQ] <<< GDS1 restart, but too quick
08:27:28 h1daqgds1 [DAQ] <<< seconds GDS1 restart good
08:29:46 h1daqfw0 [DAQ] <<< FW0 spontaneous restart
09:38:05 h1seih16 ***REBOOT*** <<< h1seih16 back from BP fix and card install
09:39:40 h1seih16 h1iopseih16
09:39:53 h1seih16 h1hpiham1
09:40:06 h1seih16 h1isiham1
09:40:19 h1seih16 h1hpiham6
09:40:32 h1seih16 h1isiham6
10:04:19 h1seih16 ***REBOOT*** <<< a second IO Chassis incursion to remove 3rd DAC card which is not needed
10:05:54 h1seih16 h1iopseih16
10:06:07 h1seih16 h1hpiham1
10:06:20 h1seih16 h1isiham1
10:06:33 h1seih16 h1hpiham6
10:06:46 h1seih16 h1isiham6
10:48:15 h1daqdc0 [DAQ] <<< second DAQ restart for new h1isiham1 model and various EDC INI files
10:48:28 h1daqfw0 [DAQ]
10:48:28 h1daqtw0 [DAQ]
10:48:32 h1daqnds0 [DAQ]
10:48:37 h1daqgds0 [DAQ]
10:48:48 h1susauxb123 h1edc[DAQ] <<< EDC restart
10:51:22 h1daqdc1 [DAQ]
10:51:34 h1daqfw1 [DAQ]
10:51:34 h1daqtw1 [DAQ]
10:51:35 h1daqnds1 [DAQ]
10:51:43 h1daqgds1 [DAQ]
10:52:18 h1daqgds1 [DAQ] <<< GDS1 restart
11:51:32 h1seih16 h1isiham1 <<< fix ADC card_nums, no DAQ restart needed
The camera server code on both h1digivideo4 and h1digivideo5 was updated from 0.1.16 to 0.1.17 to fix a bug in the periodic archiving of camera images (https://git.ligo.org/cds/software/cameras/pylon-camera-server/-/issues/6).
In addition Tony and Jonathan removed h1digivideo0 and h1digivideo1 from the racks as a cleanup job as part of the camera update WP.
(Jackie F., Gerardo M.)
Replaced the old batteries on the UPS units at both mid stations, both end stations, and two at the corner station.
The UPS units are dedicated supplies for the vacuum racks, the following racks were updated today:
No issues were encountered. One set of batteries had been already installed previously, see aLOG 83151.
Work done under WP #12377.
WP 12384
Power supply that provides ±18V to SUS Rack SUS-C6 (ITMY, ITMX, BS) was replaced. Fan bearings was starting to fail, causing loud grinding sound. Coordinated work with control room as this required powering off the the SUS Watchdog chassis.
F. Clara, J. Figueroa
WP 12372
The h1seih16 IO chassis was upgraded with new hardware in preparation for the HAM1 ISI installation:
The Adnaco in slot A2 was replaced. Timing issues reported in May 2023, alog 70010. The existing ADCs and DAC were moved to the new Adnaco card slot A2. The two new ADC’s were installed in Adnaco card slot A3.
D. Barker, F. Clara, E. Von Reis
Patrick T, Dave B, Jonathan H, Sheila D, TJ S
Summary: Today during maintenance more of the cameras were swapped over to the new camera code on a new server. This caused a lock loss since there was an offset with the new camera code, so the code and servers were swapped back for most cameras.
Some of these swapped cameras are ones we use in locking. At the end of maintenance, I skipped over initial alignment and started to lock the IFO. When we got to the ISC_LOCK state ADS_TO_CAMERAS, we could see the PRG get pulled away over a minute, as well as other signals on the FOMS, before we lost lock. Looking into it, the calulated P & Y, or X & Y depending on which channel you're looking at, channels were different from before the camera swap. The offset that this created moved us away from our alignment setpoints to cause the lock loss. Had I ran an initial alignment we might have run into this soon as we use the green ITM cameras, but we might have lost our alignment references there as well.
While it is possible to find and try to adjust for all of the offsets that the new code introduced, it would be much safer to do this after the IFO achieved full lock and we could transition the IFO off of the cameras, switch to the new code/servers, and then see what the offset is and adjust accordingly. Doing it while not locked risks losing our saved offsets, so we decided to revert the code and server changes for today and plan for another day to implement this.
The leaking pump seal in the chiller 1 pump has been repaired at End Y.
The following electronics were installed in the SEI-C1 rack:
U42: BSC-ISI Interface S1203890
U41: BSC-ISI Interface S1203891
U40: BSC-ISI Interface S1203983
U39: HAM ISI AA Interface S1202074
U38: HEPI AI S1202068
U37: HAM ISI AA Interface S1202075
U36: ISI Coil Driver S1103327
U34: ISI Coil Driver S1103350
U32: Binary In Interface S1203076
Part of the HAM1 ISI installation. Units left powered off. Field cabling arrived onsite today, will be installed next Tuesday.
F. Clara, J. Figueroa, M. Pirello
The LVEA has been swept.
Tue Mar 11 10:10:24 2025 INFO: Fill completed in 10min 21secs
M. Todd, C. Cahillane, S. Dwyer
Yesterday during commissioning, I ran some intensity noise injections. The excitation amplitudes were much too small to start out, so I tuned them as I went along to make sure we had enough coherence in DARM while not driving too hard (trickier at LFs). The injections were 9 bandlimited excitations injected into ISS_SECONDLOOP_EXCITATION, with the injection script located at /ligo/gitcommon/iss_noise_measurements/iss_noise_injection_caller.py. Should these need to be ran again, the individual bands can be uncommented and so the script can run all the bands sequentially by itself now that the excitations are tuned well.
When I inject below 100Hz, there starts to arise some non-linearities in the ISS_SECONDLOOP_RIN channel, which then get injected into DARM. These get more prevelant and higher amplitude as the excitation frequency band goes down. This is shown in Figure 1.
I will analyze the results and comment on this post with the calculated transfer function of intensity noise to darm using this data. The data can be found in the bandlimit-named folders in /ligo/gitcommon/iss_noise_measurements/data/. Most of the injections also have pictures of the coherence and live psds during the injection.
Notes:
The excitations were tuned by looking at the PSD of the DARM error signal while locked, using quick_psd and mapping the shape and amplitude to match it with a slightly higher amplitude. The amplitude will be far too weak as the TF is not known but by tuning the amplitudes by hand while injecting, I saw that the excitation amplitudes need to be about 15 orders of magnitude greater; but the shape of the excitation worked pretty well.
quick_psd H1:LSC-DARM1_IN1_DQ --duration 60 -t1 1422021858 --excitation
M. Todd, S. Reddy, M. Chaturvedi
Mayank, Siva and I worked on alignment yesterday to ensure that the internal alignment is still set. The alignment to the QPD should be the same alignment to the PDs, for instance. With the addition of the iris as an alignment reference we wanted to ensure that this reference still head.
We were able to maximize the QPD and PDs powers simultaneously with the iris installed, confirming everything is internally aligned. However, we are clipping on the iris aperature and need a smaller beamsize through the iris to remove this. Without the iris, our common maximized alignment yielding a QPD power of about .9 mW, while with the iris installed we have about .76 mW.
M. Todd, C. Compton, S. Dwyer
By adding a few lines of code to the SQZ_MANAGER.py, we zero the BLRMS when we are not injecting squeezing which serves only to make the BLRMS plots a little nicer. But basically it switches off the inputs and sets the OFFSET to one so the log calculation is zero-d. Then this effect is removed anytime we open the beam-diverter.
This change was svn commited in addition with some other sqz_manager changes, see alog SQZ Guardian redudancy removal
def zero_blrms():
log(f'Zeroing SQZ BLRMS by adding H1:SQZ-DCPD_SUM/NULL_LP_X_OFFSETs. Turning off input.')
for i in range(6):
ezca.get_LIGOFilter(f'SQZ-DCPD_SUM_LP_{i+1}').switch_off('INPUT')
ezca.get_LIGOFilter(f'SQZ-DCPD_NULL_LP_{i+1}').switch_off('INPUT')
ezca.get_LIGOFilter(f'SQZ-DCPD_SUM_LP_{i+1}').switch_on('OFFSET')
ezca.get_LIGOFilter(f'SQZ-DCPD_NULL_LP_{i+1}').switch_on('OFFSET')
return
def restore_blrms():
log(f'Restoring SQZ BLRMS by zeroing H1:SQZ-DCPD_SUM/NULL_LP_X_OFFSETS. Turning on input.')
for i in range(6):
ezca.get_LIGOFilter(f'SQZ-DCPD_SUM_LP_{i+1}').switch_off('OFFSET')
ezca.get_LIGOFilter(f'SQZ-DCPD_NULL_LP_{i+1}').switch_off('OFFSET')
ezca.get_LIGOFilter(f'SQZ-DCPD_SUM_LP_{i+1}').switch_on('INPUT')
ezca.get_LIGOFilter(f'SQZ-DCPD_NULL_LP_{i+1}').switch_on('INPUT')
return
M. Todd, C. Compton, S. Dwyer
At almost every state before BEAMDIV_OPEN_FDS, there was a turn_off_sqz() call, which contains some redudancies when jumping to these states.
We removed these calls (except in Down) and added them to the respective checkers for each state. (LOCK_SHG_CHECKER, LOCK_OPO_CHECKER, ETC...).
This should allow the jump between no injected squeezing states without having to call the turn_off_sqz() each time unless something unlocks.
I also added some changes to the blrms in SQZ_MANAGER.py, see alog Zeroing SQZ BLRMS during no squeezing
Changes were commited to svn with
Aubrey, Camilla
We plumb-bob marked the locations of ISCT1 and IOT2, labeled "03/25" with black pen and added labels of the heights at each corner. Example photos attached.
We removed the BSC1 temperature sensor to run some testing in the lab. Will reinstall next week.
After testing in the lab, the sensors are working as designed, outputs are clean. We reinstalled the BSC1 temperature sensor but left it floating (not attached to BSC1). The BSC3 sensor we isolated from BSC3 with a thermal pad, and the power supply was isolated from the pier it is resting on. This is an effort to remove ground loops on these systems. Will revisit next week.
M. Pirello, F. Clara
After review of the data over the week, we saw a marked improvement in temprature information so we reapplied the BSC1 sensor to the chamber along with a thermal pad to maintain electrical ground isolation. We also isolated the power box for both supplies.
M. Pirello, F. Clara, D. Barker
Attached are two examples where it seems that ALS losses lock after the ESD linearization hits its saturating limit, there are several more examples like this.
With the linearization on, we measured the transfer function from drivealign L out to LL master out to be -2.3. Taking into account the gain of 0.25 in the eul2esd matrix, we would need to add a gain of -9.2 in the drivealign matrix to try locking ALS without the linearization.
I've added in lscparams use_ESD_linearization, which is set to True right now to keep things the same as they currently are. I've added an if statement for this in the ALS_DIFF guardian that will set the ETMX_L3_DRIVEALIGN gain to -9.2 if it is set to False.
The linearization used to be turned on in ISC_LOCK's PREP_FOR_LOCKING state, but TJ commented several things out of this state that were redundant with things that SDF would take care of when safe.snaps get reverted. Since we want to use a flag to determine how this is set, I've put it back into PREP_FOR_LOCKING that checks the flag in lscparams.
At the EY station the compressor is being replaced - after the one at EX is done. In this aLog, in the comments, the progress of this operation is tracked continuously, until the 1st startup by the supplier, Rogers Machinery. Another important consideration here, is that the purge line at EY needs to be replaced (based on an FTIR test - see DCC LIGO-E2300222-v2. As it can be seen, the level of contamination reaches even the 10 ug/cm2 value). This operation will be done after the April-May vent, so the EY station will be ready to be vented after O4. 02-25 (maintenance Tuesday): the old compressor was pulled out (it is temporarily stored in the EY receiving area). The beginning of the purge and TMDS lines with the associated brackets and unistruts were taken off. The new compressor unit and dryer skid were anchored in the mechanical room. Here it is important to mention that the orientation of the inlet was brought closer to the purge line inlet into the VEA, so the overall length of the associated circulation lines will be much shorter. Next is the electrical and pneumatic installation, which will be completed in the next 1-2 weeks.
The filter tree was installed and supports anchored to the slab. Ken also reports that electrical installation is complete. Connection to the purge air header is awaiting CF fittings from the supplier. However, startup testing can continue prior to header connection.
The 1st startup of the compressor was carried out by Rogers Machinery on March 18th, during maintenance hours.
To get in Observing I had to accept some SDF diffs for SQZ, and PCALY. There was also still a PEM CS excitation point open as well. There was a notification about PCALY OFS servo malfunction so I looked at it and it was railed at -7.83, so I toggled it off and back on and it brought it back to a good value. I also did not receive a call, a voicemail just appeared.
09:21 UTC observing
H1:SQZ-LO_SERVO_IN1GAIN was left at -15 by accident, reverted to -12 and saved in sdf.
DriptaB, FranciscoL
SDF diffs for PCALY were incorrect. The timing of these changes match the h1iscey reboot done the same day (82902). Today around 19:00 UTC (almost three weeks later), we used EPICS values from the Pcal calibration update done in September (80220) to revert changes. Saved changes in OBSERVE and SAFE.