WP11540 Remove SDF safe->OBSERVE exceptions for h1seiproc and h1brs
TJ, Jim:
TJ made changes to guardian to remove the exception that h1seiproc and h1brs do not transition to OBSERVE.snap. h1brs OBSERVE==safe, h1seiproc has a separate OBSERVE.snap which Jim will verify is correct.
WP11546 New FMCS STAT code base
Erik:
Erik rewrote the FMCS STAT IOC to use this new softIOC python module. The code was restarted.
New Guardian node
Camilla, Dave:
Camilla started a new Guardian nodel called SQZ_ANG_ADJUST. I updated the H1EPICS_GRD.ini file. DAQ+EDC restart was required.
DAQ Restart:
Jonathan, Erik, Dave:
The DAQ was restarted to include the new GRD channels into the EDC. This was a good restart with no issues.
cdsioc0 reboot
Erik, Dave:
Erik updated and rebooted cdsioc0. There were some issues getting Picket Fence running again, which Erik resolved. We were reminded that I was running a temporary HWS ETMY IOC in a tmux session, Erik switched this over to a systemd service via puppet.
Jordan
We ran the functionality test on the main turbopumps in MY and EY during Tuesday Maintenance (11/28/23). The scroll pump is started to take pressure down to low 10^-02 Torr, at which time the turbo pump is started, the system reaches low 10^-08 Torr after a few minutes, then the turbo pump system is left ON for about 1 hour, after the hour the system goes through a shut down sequence.
MY Turbo:
Bearing Life:100%
Turbo Hours: 208
Scroll Pump Hours: 74
EY Turbo:
Scroll pump made a grinding sound after getting to ~ 5E-2 Torr. I closed all valves and stopped the test. The scroll pump only has 200 hours on it so it will be disassembled to figure out the source of the noise. I have swapped the scroll pump with a new ISP250, but did not have time to run the turbo test. I will resume next tuesday and add a comment to this alog with the EY results.
Closing WP 11544 and FAMIS 24917
After swapping the scroll pump, I ran the functionality test on the EY main turbopump during Tuesday maintenance, no issues were encountered during this test.
Turbo Hours: 1275
Scroll Pump Hours: 72
Bearing life: 100%
Closing WP 11553 and FAMIS 24941
F. Mera, D. Sigg, M. Pirello
Per WP11548:
The Squeezer 4 rack was modified duplicating the EL3692 terminals in the positions M13, M14, M19 and M20. Wiring was modified to have readings in CH1 only.
TwinCAT solution was updated accordingly, the system was restarted and succesfully verified with the new configuration.
SQZ 4 rack serial: S2101205
Clean room over Ham 6 lights were turned off
Wifi was turned off at the corner and both arms, except MSR.
LVEA has been swept.
Tuesday maintenance activities are wrapping up - locking thereafter.
Fil Marc Daniel
Today we pulled the lond d-sub cables going from the CER to the squeezer racks. This completes the electronics installtion for the SQZ PMC with the exception of the on table devices.
Closes FAMIS 25967, last checked in alog74134
BSC:
Script reports the following are elevated: ITMX_ST2_CPSINF_{H3, V1, V3 }
ITMY_ST1_CPSINF_{V2, V3}, ETMX_ST1_CPSINF_V2 are elevated at high frequency
HAM:
The HAMs look fine
Workstations were updated and rebooted at about 1500 UTC. This was an OS update. conda packages were not affected.
Tue Nov 28 10:03:40 2023 INFO: Fill completed in 3min 37secs
TC-A min = -90.1C
TITLE: 11/28 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 3mph Gusts, 2mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.19 μm/s
QUICK SUMMARY:
IFO was locked (but not observing due to Tues magnetic injections). Sheila unlocked IFO through planned DARM configuration change.
PSL 102 dustmon is still stuck and giving warning: "dust counts did not change please investigate". See Oli's eve (11/27) summary alog 74421 to follow the story on this.
Currently we have the Magnetic injections begin measuring the background at 15:20UTC, taking the IFO out of observing at 15:21:45UTC. They finish at 15:40UTC and the IFO goes back into observing for 5 minutes before the in-lock charge measurements start at 15:45UTC. Charge measurements now finish at 15:59:45UTC, adjusted in 74186. Ryan S and I can work together move the measurements to avoid the 5 minutes in observing.
TITLE: 11/28 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Earthquake
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Relocked twice today, both locklosses (74432, 74438) being due to earthquakes. Had some issues with the first relocking, needing to go to GREEN_ARMS_MANUAL before running the initial alignment, and after still going through PRMI. Second relocking I also needed to touch both arms and we ended up going through CHECK_MICH_FRINGES on the way up. We are currently at LOWNOISE_COIL_DRIVERS. Other than that, everything was relatively normal.
We actually just got a verbals call out for an incoming earthquake from Fiji that is in the middle of the green zone on the EQ Response Zones script so hopefully we will be able to stay up!
LOG:
00:00UTC Detector holding in DOWN due to earthquake
00:40 Started Locking
- Needed to align ALSX manually, then on to an Initial Alignment
- 01:30 Initial Alignment completed, on to Locking
02:22 NOMINAL_LOW_NOISE
02:25 Observing
06:30 Earthquake mode activated
06:31 Lockloss due to earthquake
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
00:35 | Louis & Dana | LVEA | n | Tour | 01:05 |
Lockloss 11/28 @ 06:31UTC due to earthquake from Alaska
Summary of the report:
Observing at 160Mpc and Locked for almost 2 hours now
TITLE: 11/28 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Earthquake
OUTGOING OPERATOR: Austin
CURRENT ENVIRONMENT:
SEI_ENV state: EARTHQUAKE
Wind: 1mph Gusts, 0mph 5min avg
Primary useism: 0.32 μm/s
Secondary useism: 0.21 μm/s
QUICK SUMMARY:
Detector went down due to an earthquake(74432) and we are currently having another earthquake pass through so we will be holding in DOWN for a bit longer.
00:40 11/28 Started relocking
02:25 Observing
Sheila, Camilla, Jenne, Austin
We droped out of observe for a few minutes to start running the sqz angle adjustment guardian state using the ADF that Naoki wrote on Wed (74376). This changed the sqz angle by a few degrees in the first 2 minutes it was on, which improved the sqz blrms slightly.
Because Vicky put some code in ISC_LOCK that set the SQZ_MANAGER request to it's nominal state, the only change we had to make was to change the nominal state of SQZ_MANAGER, and this should now be used in future locks. The new SQZ_MANAGER state is ADJUST_SQZ_ANG_ADF state number 110
After several hours this still seems to be working, and our SQZ BLRMS have been stably a little better.
We had two IFO re-locks last night with this servo running, plot attached. Comparing the first 2 hours of the lock with the servo running and without, the yellow and green BLRMS 300-1000Hz are more stable and lower with the new servo, this is great! Purple (4.6kHz) also improves more quickly.
The IFO range is still changing over the first hour of the lock but this is expected as the IFO thermalizes and may be less than the 1h30-2h we were seeing without the servo. Maybe the ADF RMS changing can tell us something about this.
TITLE: 11/23 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:
The last hour has shown a drops in range while being in OBSERVING. In the last 30min the range drops have been less severe, but this is an odd one.
Had a few bumps out of observing due to the squeezer, but it would only be for about ~2min as the squeezer relocked itself. L1 came back to Observing this shift.
LOG:
The range fuzziness that started at 11/23 07:02UTC, also mentioned in 74387. From SQZ BLRMs can see that this is in the 80-140Hz region, plot attached. This is not related to SQZ unlock/relock as it was 45 minutes before. The SEI states didn't change at this time. Can't see anything in PEM channels in CS and Ends, plot attached. CS Fan5 appears to change it's readback around an hour after the range fuzziness started, plot attached.
Can see some change in FAN5 around the time the range fuzziness started this morning at 15:31UTC, plot attached.
Ryan C also did some investigation in 74383.
Fan5 seems fine: Eric helped me look into Fan5 and Air Hander 3 that is linked to this fan. This Fan is off but the channels will pick up air flow from other fans. The noise just seems to change on ~few hour period making it look suspiciously in time with DARM fuzziness starting. We see no significant changes in the last few weeks.
DARM while range fuzzy: As suggested by Robert, attached is DARM in two range dips during glitches (yellow at 07:02UTC, red at 08:35UTC) and green was more typical of what DARM looked like during this fuzzy time (DARM broadly increasing and decreasing in 20-200Hz region). I can see no obvious scattering arches but Robert suggested using the Q-transform tool of ldvwweb to check these glitches: Arianna did this in 74455.
WP 11533
Checked the HAM4 ISI Coil Driver Chassis. Issue reported last week of noisy fan. Fan is spinning and noise reported last week has not returned. Will leave WP open another week.
Second week of monitoring fan. No issues, closing work permit.
Artem, Gabriele, Sheila, Louis Plots and Jupyter notebook with these results are also available here.ESD quadratic noise
This is a follow up on investigation of potential non-stationary noise at Handford introduced by the ESD drive, reported in 73913 and previous entries linked from there. The idea is that from the ESD signal, Vs, and bias, Vb, voltages we can reconstruct ESD force applied to the mirror, using equations in LIGO-T1700446. The force component linear in Vs gets subtracted by the control loop and therefore does not affect DARM. But the force component quadratic in Vb and both linear and quadratic in Vb can couple to DARM. Therefore in this report, we are calculating respective force components and projecting them to DARM. Then respective ASDs and spectrograms are compared.Selection of input channels
The ESD drive voltages are recorded by Monitors, H1:SUS-ETMX_L3_LVESDAMON_LL_OUT_DQ for Vs and H1:SUS-ETMX_L3_ESDAMON_DC_OUT_DQ for Vb. Important note here: we initially tried channel H1:SUS-ETMX_L3_ESDAMON_UL_OUT_DQ to get Vb, but it looks like it's not connected to anything and recording ASD noise... The H1:SUS-ETMX_L3_ESDAMON_DC_OUT_DQ seems to be fine. Also, LIGO-T1700446 specifies calibrations for voltage channels (equations 13 and 16), but currently the channels mentioned above are already calibrated to voltage.![]()
Calculating force terms
Calculation is based on equation 3 in LIGO-T1700446, but this equation is modified in the following way:
I did the same exercise but now for GPS time 1382909598 (and up to +22 mins from it), where bias voltage was set at 409V. Below you find plots where you can see that noise went up* (ASD) but apparent non-stationarity is reduced (spectrograms), which is consistent with Gabriele's findings in comment in 73935, specifically this and this plots.![]()
* Currently noise ASD is actually higher than DARM, this is not realistic but the modelling is not 100% precise. What is important here is relative changes with respect to results with "standard" level of bias voltage. Plots and Jupyter notebook with these results are also available here.
Another way to look at ESD quadratic noise. The DARM strain band-limited RMS (computed between 16 and 30 Hz and normalized to the median over time) is correlated to the total RMS of the ESD drive (dominated by the low frequency component, below 10 Hz)
Tue28Nov2023
LOC TIME HOSTNAME MODEL/REBOOT
12:12:04 h1daqdc0 [DAQ] <<< 0-leg restart
12:12:13 h1daqfw0 [DAQ]
12:12:13 h1daqtw0 [DAQ]
12:12:14 h1daqnds0 [DAQ]
12:12:22 h1daqgds0 [DAQ]
12:12:35 h1susauxb123 h1edc[DAQ] <<< EDC restart for GRD
12:20:44 h1daqdc1 [DAQ] <<< 1-leg restart
12:20:56 h1daqfw1 [DAQ]
12:20:57 h1daqtw1 [DAQ]
12:20:58 h1daqnds1 [DAQ]
12:21:07 h1daqgds1 [DAQ]