There is another suspected failure of the power supply at the Staging building fire panel. This is supervisory alarm that will also trigger a local alarm at the OSB FACP. Johnson Controls has been made aware of the issue as has our monitoring provider. Given the nature of the alarm, there should be no triggering of any bells/horns/strobes etc., nor interruption to HVAC. Should the panel across the hall from the CR signal an alarm, please simply acknowledge (ACK) to silence. T. Guidry
Ibrahim, Oli, Betsy
Context:
The first article BBSS was built late 2023 and TFs taken for the first time 01/05/2024. These can be found in alog 75787 among other places in the X1 logbook. Transfer functions largely agreed with the dynamical model with a few changes outlined in alog 76381.
Last few months:
Following RAL's most recent trip, we have rebuilt the BBSS with the following major changes:
The Present:
As of 07/03, M1 OSEMs have been reconnected, centered and the second round of TFs taken on 07/03 (attachment 1). In comparison with 01/05 results (attachment 2), they seem extremeley noisy. Diagnostics in the following alog.
The following settings seems to be working for now and I will commit it in the lscparams after a couple of IFO lock stretches.
New settings (ITMY05/06):- FM5 FM6 FM7 FM10 Gain +0.01 (new phase -90 degree), might increase the gain later on depending upon how slow the damping is.
Nominal settings (ITMY05/06): FM6 FM8 FM10 Gain +0.02 (phase -30deg)
Given below are settings I tried this morning and it did not work,
1. no phase, 0.01 gain - increase
2. -30 phase, -0.01 gain - increase
3. +30 phase, 0.01 gain - increase
4. -30 phase, 0.01 gain - IY05 decreasing (both filters) IY06 increasing (both filters)
5. -60 phase, 0.01 gain - IY05 decreasing (both filters) IY06 increasing (only in narrow filter)
---
After talking to TJ, I have set the gain to zero on lscparams and saved it but not loaded it since we are OBSERVING. Will load it once there is a target or opportunity.
DARM spectra attached below shows that both the modes are slowly decreasing, next I will try and bump up the gain to 0.02.
ITMY 05/06 - FM5 FM6 FM7 FM10 Gain +0.02 has been saved in lscparams and violin mode Guardian has been loaded for the next lock.
Ran Bruco now we' ve moved spot on PR2 (alog 78878) 2024/07/10 16:18 UTC (1404663547) from when our range was ~156MPc: Link: GDS_CLEAN_1404663547/
In last week's bruco 78879, Sheila pointed out that the LVEA accelerometers and HAM2 coherence has around 30-40Hz.
Wed Jul 10 08:14:48 2024 INFO: Fill completed in 14min 44secs
Jordan confirmed a good fill curbside.
I noticed this at the end of my shift yesterday, and now that the IFO has had a longer lock it has confirmed that ITMY mode 6 is slowly ringing up through the lock. These modes are right on top of each other so we have always struggled to damp them well, but we have found settings that have worked for most of O4. Whatever changes we've made with the IFO recently have made those settings not work.
I'm mainly writing this as a reminder for operators to keep an eye on these modes. Hopefully I'll find a setting that will work, but these ones are always a headache.
I am on it now, will play with the gain and phase to try and find out a setting which works.
TITLE: 07/10 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 7mph Gusts, 6mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.05 μm/s
QUICK SUMMARY: Locked for almost 6 hours after the earthquake passed through. range is much better than yesterday, tipping into the 160's a bit.
TITLE: 07/10 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Earthquake
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Currently relocking and at MOVE_SPOTS. We were knocked out by a large earthquake and it kept us from trying to lock for two hours. I ran an initial alignment and relocking is going quickly. The two other locklosses from my shift are a mystery to me, but from the first lock we can clearly see that our range is lower after today's activities, although the second lock of my shift, the 36 minute one, we did get up to 155Mpc pretty fast, so maybe it was just that first lock back.
And maybe this already has an alog somewhere, but Gerardo noticed that a peak at 20 Hz was pretty big during our first lock back after maintanence. Looking back, it first appeared on may21st, and although its height fluctuates, the past week and a half it seems to have gotten progressively larger.
LOG:
23:00 Detector Observing at 147 Mpc
00:29 Out of Observing to tune sqz
00:39 Back to Observing
01:20 Lockloss
01:47 We were cycling through MICH_FRINGES so I took us to DOWN to start an initial alignment
02:11 Initial alignmet done, relocking
02:57 NOMINAL_LOW_NOISE
03:00 Observing
03:37 Lockloss
- going to run initial alignment again since during the last one we had some ground motion that might've affected alignment
- ALS_XARM had to adjust the fiber polarization
04:06 Initial alignment done, relocking
05:04 NOMINAL_LOW_NOISE
05:06 Observing
05:16 Lockloss from earthquake, staying in downn while earthquake passes
07:26 Starting an initial alignment
07:45 Initial alignment done, relocking
Note: ITMs still only have measurements processed through May 21st. I can look into this over my next couple of shifts.
Closes FAMIS#25998, last checked in alog78873
Frequencies above 10 Hz look good for all spectra.
Many spectra have peaks at 1 Hz on their vertical sensors that haven't been there at least the past few weeks - every HAM and every BSC suspension on Stage 1
Compared to the last check, ETMY Stage1's vertical sensors are much louder between 4 and 10 Hz, and seem to line up with the oscillations of the horizontal sensors. The horizontal sensors are also elevated between 4 and 6 Hz.
Another :(
Lockloss @ 07/10 05:16UTC due to an incoming 6.7 earthquake. We had been locked for only 12 minutes :(
We were knocked out by the S waves, the R waves aren't coming for another hour so we are going to be down for a good while.
FranciscoL
After one week of having the inner beam centered on the Rx sensor (LHO:78810), on July 09, we moved the beam from center to the right.
This movement was done to double check the changes seen after our move on May 14 (LHO:77840). LHO_XY_Comparison_dataVmodel_1399180506-1404571480.pdf shows the full cycle and nominal results of our series of pcal beam movements, which ended on 24-07-09 @ 08:00 PT. The plot legend shows the value given by the weighted mean of each week using the mean value of each observing stretch for the distribution. The *raw* data for each observing stretch is plotted in gray but, for scaling purposes, some of that data is outside the range of the plot. The black line is what we expected the X/Y comparison to yield from the beam movements that we made. EDITORS NOTE: The vertical axis on the plot is in HOPs (Hundreth of a percent). Although some changes are unexpected, these are not concerning or significant changes that will affect LHO calibration. It is also an ongonig investigation, we are learning as we go.
The movement done in May 14 is seen on the first step of the plot, a week after having both beams centered, where the weighted mean yields a value of 0.99747 – a change of -25 HOPs from the previous week. However, as seen in the model, we expected the line to change by +19.2 HOPs. The rest of the movements *agree* with our model. Further analysis and diagnostics are pending but the main takeaway is that the data does not match the model for this one move, which motivates repeating the measurement.
During this procedure, we used keithley DVM (KVM) 1424277 instead of the FLUKE handheld DVM.
EndStationLog.pdf lists the voltage values after each significant step of procedure T2400163. The steps represent writing down a voltage value after a particular change to the beam position. Some highlights from the recorded values.
The KVM was calibrated using a Martel voltage/current calibrator (Martel) after the procedure. The KVM was configured to a range of 10V and a resolution of 6.5 "FAST digits ("FAST" is referred to the time it takes for the ADC on the KVM to integrate; a 6.5 FAST resolution corresponds to an integration time of 16s) . The following table lists the voltages provided by the Martel and the corresponding readings displayed on KVM 1424277.
Martel [V] | KVM [V] |
---|---|
0.000 | 00.00012 |
3.000 | 03.00018 |
3.383 | 03.38328 |
4.000 | 04.00027 |
In summary, (1) using a KVM increased the resolution of our measurements for the beam movement procedure. (2) The 'Initial' measurement changed by 8 HOPs from the last voltage measurement from the previous movement (3.382V), done on July 02 (LHO:78810). (3) The initial and final voltage measurement during today procedure changed by 4 HOPs.
05:06 Observing
Currently not sure of cause, but the lockloss was a lot smoother/less sudden than most other locklosses, which I thought was interesting. I think EX L3 sees it first (the little jolt right after the cursor and before it dips down), but there aren't any saturations or glitches that happen before the lockloss like we tend to see in a lot of other locklosses.
03:00 Observing
WP11970 h1susex 28AO32 DAC
Fil, Marc, Erik:
Fil connected the upper set of 16 DAC channels to the first 16 ADC channels and verified there were no bad channels in this block. At this point there were two bad channels; chan4 (5th chan) and chan11 (12th chan).
Later Marc and Erik powered the system down and replaced the interface card, its main ribbon cable back to the DAC and the first header plate including its ribbon to the interface card. What was not replaced was the DAC card itself and the top two header plates (Fil had shown the upper 16 channels had no issues). At this point there were no bad channels, showing the problem was most probably in the interface card.
No DAQ restart was required.
WP11969 h1iopomc0 addition of matrix and filters
Jeff, Erik, Dave:
We installed a new h1iopomc0 model on h1omc0. This added a mux matrix and filters to the model, which in turn added slow channels to the DAQ INI file. DAQ restart was required.
WP11972 HEPI HAM3
Jim, Dave:
A new h1hpiham3 model was installed. The new model wired up some ADC channels. No DAQ restart was required.
DAQ Restart
Erik, Jeff, Dave:
The DAQ was restarted soon after the new h1iopomc0 model was installed. We held off the DAQ restart until the new filters were populated to verify the IOP did not run out of processing time, which it didn't. It went from 9uS to 12uS.
The DAQ restart had several issues:
both GDS needed a second restart for channel configuration
FW1 spontaneously restarted itself after running for 9.5 minutes.
WP11965 DTS login machine OS upgrade
Erik:
Erik upgraded x1dtslogin. When it was back in operation the DTS environment channels were restored to CDS by restarting dts_tunnel.service and dts_env.service on cdsioc0.
Tue09Jul2024
LOC TIME HOSTNAME MODEL/REBOOT
09:50:32 h1omc0 h1iopomc0 <<< Jeff's new IOP model
09:50:46 h1omc0 h1omc
09:51:00 h1omc0 h1omcpi
09:52:18 h1seih23 h1hpiham3 <<< Jim's new HEPI model
10:10:55 h1daqdc0 [DAQ] <<< 0-leg restart for h1iopomc0 model
10:11:08 h1daqfw0 [DAQ]
10:11:09 h1daqnds0 [DAQ]
10:11:09 h1daqtw0 [DAQ]
10:11:17 h1daqgds0 [DAQ]
10:11:48 h1daqgds0 [DAQ] <<< 2nd restart needed
10:14:02 h1daqdc1 [DAQ] <<< 1-leg restart
10:14:15 h1daqfw1 [DAQ]
10:14:15 h1daqtw1 [DAQ]
10:14:16 h1daqnds1 [DAQ]
10:14:24 h1daqgds1 [DAQ]
10:14:57 h1daqgds1 [DAQ] <<< 2n restart needed
10:23:07 h1daqfw1 [DAQ] <<< FW1 spontaneous restart
11:54:35 h1susex h1iopsusex <<< 28AO32 DAC work in IO Chassis
11:54:48 h1susex h1susetmx
11:55:01 h1susex h1sustmsx
11:55:14 h1susex h1susetmxpi
Power Spectrum of channels 0 through 15. No common mode issues detected.
Channel 3 & 9 are elevated below 10Hz
It is unclear if these are due to the PEM ADC or the output of the DAC. More testing is needed.
New plot of first 16 channels, with offsets added to center the output to zero. When offsets were turned on, the 6Hz lines went away, I believe these were due to uninitialized DAC channels. This plot also contains the empty upper 16 channels on the PEM ADC chassis as a noise comparison with nothing attached to the ADC. Channel 3 is still noisy below 10Hz.
New plot of second 16 channels (ports C & D), with offsets added to center the output to zero. This plot also contains the empty lower 16 channels on the PEM ADC chassis as a noise comparison with nothing attached to the ADC. Channel 3 is still noisy below 10Hz, signifying this to be an ADC issue, not necissarily a DAC issue. These plots seem to imply that the DAC noise desnity while driving zero volts is well below the ADC noise floor in this frequency range.
Lockloss @ 07/09 01:46UTC after 8.5 hours locked
02:57 UTC Observing
We made a PRCL excitation we should later be able to use to create a PRCL FF, saved in lsc/h1/scripts/feedforward/PRCL_excitation.xml and exported .txt files.
I didn't taken PRCLFF injections, but the same high pass is used in MICH as PRCL, both fed to ETMY, so I used the last MICHFF injections for this.
Used NotItter_PRCL_FF_PrepareData.ipynb and InteractiveFitting to make a first go at a PRCLFF fit. See attached. This is ready for h1lsc load coefficients and then will be in FM1 as 7-10-24.
Lock loss 1404445312
5 hours and 42 mins seems like a standard lock for this week. LSC-DARM saw an odd wiggle before lock loss, normally I see an ETMX output that matches this but I didn't see that this time.
Back to Observing at 0528 UTC.
I ended up slightly moving PR3 P from -122.2 -> -121.6 and Y from 98.8 -> 98.6. This brought the beatnote up to around -14.5dBm, up from the -18 or so that I started at, and ALSX power moved up as well. when DRMI locked POP18 looks to be higher than it was the last handful of locks over the last few days. I ran through an initial alignment and then it went right up.
EX L3 does oscillate 16 ms before DARM sees the lockloss, although it might be possible that the slight drop (marked in green) is DARM seeing it??
The first attachment shows spectra (GDS CALIB STRAIN clean, so with calibration corrections and jitter cleaning updated and SRCL FF retuned) with OM2 hot vs cold this week, without squeezing injected. The shot noise is slightly worse with OM2 hot, while the noise from 20-50Hz does seem slightly better with OM2 hot. This is not as large of a low frequency improvement as was seen in December. The next attachment shows the same no squeezing times, but with coherences between PRCL and SRCL and CAL DELTAL. MICH is not plotted since it's coherence was low in both cases. This suggests that some of the low frequency noise with OM2 cold could be due to PRCL coherence.
The optical gain is 0.3% worse with OM2 hot than it was cold (3rd attachment), before the OMC swap we saw a 2% decrease in optical gain when heating OM2 in Decmeber 74916 and last July 71087. This seems to suggest that there has been a change in the OMC mode matching situation since last time we did this test.
The last attachment shows our sensitivity (GDS CALIB STRAIN CLEAN) with squeezing injected. The worse range with OM2 hot can largely be attributed to worse squeezing, the time shown here was right after the PSAMs change this morning 78636 which seems to have improved the range to roughly 155Mpc with cleaning; it's possible that more psams tuning would improve the squeezing further.
Times used for these comparisons (from Camilla):
Side point about some confusion caused by a glitch:
The first attachment shows something that caused me some confusion, I'm sharing what the confusion was in case this comes up again. It is a spectrum of the hot no sqz time listed above, comparing the spectrum produced by dtt with 50 averages, 50% overlap, and BW 0.1 Hz (which requires 4 minutes at 15 seconds of data), compared to a spectrum produced by the noise budget code at the same time. The noise budget uses a default resolution of 0.1Hz and 50% overlap, and the number of averages is set by the duration of data we give it which is most often 10 minutes. The second screenshot shows that there was a glitch 4 minutes and 40 seconds into this data stretch, so that the spectrum produced by the noise budget shows elevated noise compared to the one produced by dtt. The third attachment shows the same spectra comparison, where the noise budget span is set to 280 seconds so the glitch is not included and the two spectra agree.
Comparison of sensitivity with OM2 hot and cold wihtout squeezing:
The next two attachments show spectra comparisons for no sqz times with OM2 hot and cold, (same times as above), the first shows a comparison of the DARM spectrum, and the second shows the range accumating as a function of frequency. In both plots, the bottom panel shows the difference in accumulated range, so this curve has a positive slope where the sensitivity of OM2 hot is better than OM2 cold, and a negative slope where OM2 hot is worse. The small improvement in sensitivity between 20-35 Hz improves the range by almost 5Mpc, then there is a new broad peak at 33Hz with OM2 hot which comes and goes, and again a benefit of about 4Mpc due to the small improvement in sensitivity from 40-50 Hz.
From 90-200 Hz the sensitivity is slightly worse with OM2 hot. The coupled cavity pole dropped from 440Hz to 424Hz while OM2 warmed up, we can try tuning the offsets in AS72 to improve this as Jennie and Keita did a few weeks ago: 78415
Comparison of with squeezing:
Our range has been mostly lower than 160 Mpc with OM2 hot, which was also true in the few days before we heated it up. I've picked a time when the range just hit 160Mpc after thermalization, 27/6/2024 13:44 UTC to make the comparison of our best sensititivites with OM2 hot vs cold. This is a time without the 33Hz peak, we gain roughly 7 Mpc from 30-55 Hz, (spectra and accumulated range comparisons) and loose nearly all of that benefit from 55-200 Hz. We hope that we may be able to gain back some mid frequency sensitivty by optimizing the PSAMs for OM2 hot, and by adjusting SRM alignment. This is why we are staying with this configuration for now, hoping to have some more time to evaluate if we can improve the squeezing enough here.
There is a BRUCO running for the 160Mpc time with OM2 hot, started with the command:
python -m bruco --ifo=H1 --channel=GDS-CALIB_STRAIN_CLEAN --gpsb=1403531058 --length=400 --outfs=4096 --fres=0.1 --dir=/home/sheila.dwyer/public_html/brucos/GDS_CLEAN_1403531058 --top=100 --webtop=20 --plot=html --nproc=20 --xlim=7:2000 --excluded=/home/elenna.capote/bruco-excluded/lho_excluded_O3_and_oaf.txt
It should appear here when finished: https://ldas-jobs.ligo.caltech.edu/~sheila.dwyer/brucos/GDS_CLEAN_1403531058/
(Jenne, Jordan, Gerardo)
On Monday June 24, I noticed an increase on pressure at HAM6 pressure gauge only. Jordan and I tried to correlate the rise on pressure to other events but we found nothing, we looked at RGA data, but nothing was found, then Jenne pointed us to the OM2 thermistor.
I looked at the event on question, and one other event related to changing the temperature of OM2, and the last time the temperature was modified was back on October 10, 2022.
Two events attached.
Some more analysis on pressure vs OM2 temperature in alog 78886: this recent pressure rise was smaller than the first time we heated OM2 after the start of O4 pumpdown.