Shift Summary: The IFO was locked and observing for the past 5.5 hours. At 19:23 lost lock due to a Mag 6.9 EQ near the Solomon’s. Primary microseism is up to 8.0um/s, secondary is 1.5um/s. HAM6 ISI was the only tripped. I put the SEI_CONF LARGE_EQ_NOBRSXY.
Put the SEI_CONF back to WINDY. Microseism has calmed down. Start relocking.
Double the fun!
1:30 pm local
Finished installing TCs at CP4 exhaust. Needed to swap TC wires at beckhoff rack.
CP4 took less than 1 min. to overfill at 70% on LLCV. Returned to nominal 38%. I filled CP4 from beckhoff console at MY to verfiy LN2 flow out exhaust when TCs read below -30C.
CP3 took 36 min. to overfill at 50% on LLCV. Nominal at 19% (from previous 18%).
Dave Barker pointed out that CP3's Dewar level readback is noisy as he was writing an alarm script that looks at slope. Trending back 3 years, it looks like this noise comes and goes with cold weather, and is somewhat diurnal.
IFO has been locked and Observing for 5.5 hours, when lost lock due to Mag6.9 EQ near the Solomon Islands. Primary microseism remains high but is starting to come down. Should be able to try relocking soon.
Attached are plots of the reference cavity transmission for the past week. Plotted along with
the laser room temperature, and the reflection locking photodiode output. The decay is not due
to any degradation of the pre-modecleaner transmission.
Correction almost always involve a pitch alignment correction, most of which is the top
mirror mount in the periscooe.
Terra asked detchar to investigate whether changing PI damping settings might cause glitches. Conclusion - they do not, at least for the examples I've seen.
I looked at 22 examples from alogs 31892, 31824, 31560, 31516, 31485, 31461, 31444, 31440, 31191 where operators reported changing the settings on modes 3, 26, 27 and 28 in either/both phase and gain. I plotted a 10 minute timeseries around the times reported in the alogs of channels SUS-PI_PROC_COMPUTE_MODE#_DAMP_GAIN and SUS-PI_PROC_COMPUTE_MODE#_PLL_PHASE and a spectrogram of GDS-CALIB_STRAIN of the same time. Two of the times I could not find any change in either the phase/gain so I really only looked at 20 examples.
Attached is an example where both the phase and gain of mode 28 were changed by the operator in alog 31485. The change in gain and phase makes no obvious glitches/change to the spectrogram. All other exmaples I have seen show no obvious change either. When pycbc live triggers have been available (because they only get generated when we're in oberserving) I can not find any noticeable change.
If you really want to look through all the plots yourself they are here.
Thanks Laura!
PI phase and gain settings are currently unmonitored in observe SDF, so we can keep them that way. Note that saturating the ESD drive does couple into DARM, so if you ever try significantly increasing PI gains (say, above 15,000), it would be best to drop out of Observe.
Ran LOAD on the SUS_PI Guardian to load new code, per Owl Shift operator.
At 19:23 lost lock due to a Mag 6.9 EQ near the Solomon’s.
Primary microseism is up to 9.0um/s, secondary is 1.5um/s. HAM6 ISI was the only trip. I put the SEI_CONF LARGE_EQ_NOBRSXY.
Posted are the OpLev trend plots for the past week. The BS summary plot show a steady downward trend. FAMIS #4705
I have made a filters file for LHO that includes the corrections made by Evan G. and Jeff K. (see https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=32329 ). The filters were made using revision #3929 of the calibration SVN and can be found here: /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/GDSFilters/H1GDS_1165269650.npz The parameters used to make these filters are: /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/Common/params/IFOindepParams.conf /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/params/H1params.conf /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/params/2016-11-12/H1params_2016-11-12.conf /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/params/H1_TDparams_1165269650.conf /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/Scripts/CAL_EPICS/D20161122_H1_CAL_EPICS_VALUES.m Several plots are attached: 1) h(f) spectrum from CAL-CS and GDS 2) Ratio of spectra (GDS / CAL-CS) 3) Residual correction filter 4) Control correction filter https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=32329
Ops Shift Transition: 12/09/2016, Day Shift 16:00 – 00:00 (08:00 - 16:00) - UTC (PT)
TITLE: 12/09 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 72.1525Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Troubles with PI, seem to be handled now.
LOG:
Had troubles with PI that kept breaking lock as the IFO heated up, required modifying some filters, but it seems stable now.
There is a pending PI guardian change that still needs to be loaded, but I didn't want to knock us out of observing, I've told Jeff.
The load on the DCS detchar box became very high again, preventing the generation of the H1 Det Char Summary Pages. See alog: 32380. I've rebooted the detchar box and sent out emails. The summary pages should begin to catch up again, though this will take a little while.
Getting to NLN tonight hasn't been a problem so far, but there seem to be a forest of features at 18khz that are upset, and I don't see any filters to handle them. Attached spectra are from the current lock stretch (blue) and the 2 hour lock from 23 hours ago. The features around 18040 hz have been the most problematic, maybe the current bandpasses are good for some of the peaks in that region, but not others? The peak at 18038.5 has been the worst, none of the filters seem to do any good. So far I've had the best luck using a gain of 1000 on Mode 27, but .....
And before I could hit post 18038.5 rang up and broke the lock.
Just got done talking to Terra and Keita. With Keita's approval (because it seems to be required to get the IFO running stably), Terra walked me through making a new bandpass filter for this mode:
cheby2("BandPass",4,40,237,240)butter("BandPass",2,237,240)notch(238.5,20,30)gain(31.6228)
This is installed as 18038p5Hz in FM5 on Mode 27 (Terra suspects this mode is also on ETMY). Turning it on created SDF diffs that I've accepted, and I hit the intent bit 20 seconds before 6:00 local.
Jim is awesome and mode seems to be holding stable.
This one was a bit confusing because we have two ETMY modes close to one another, one at 18038ish Hz and one at 18042ish, Hz as seen in Jim's spectum. This is probably the source of TJs problems last night (sorry TJ), though when I checked earlier today the peak I trended from his shift was within the BP so I didn't suspect that to be the problem. Jim scooted over the BP and PLL set frequency to be over the 18038 Hz mode. Next day I'm in, I will create a new mode so that the two can be differentiated. Note though that the 18042 Hz mode did not go unstable just now even though we weren't damping it. I'll look into the last several locks and see which seems to be the regularly problematic one. We also weren't driving quite hard enough; Jim increased the damping gain which worked much better.
For now: If Mode27 seems unresponsive, open PI DTT and check if the growing peak is at 18038 or 18042 Hz. Then check the following:
Posted are the plots for the CPS Sensor Spectra.
We have a diagnostic setup at BSC8 that we need to run for several consecutive days. This setup utilizes rotating shaft vacuum pumps that have the potential of effecting the IFO data. Prior to the start of O2, we had Robert S. monitor the IFO signal(s) while it was locked and in "Low Noise" both with the pumps on and also off, i.e. we did "on/off" tests (see alog entry 31802). Additionally, and on more than one occasion, we had ran these for several consecutive days during which the IFO experienced long lock stretches at good sensitivity. As such, we were hoping that someone could examine the pertinent IFO data during the following two time segments to look for any evidence of these pumps running. In both cases, the pumps in question were running continuously: November 24th, 0230 UTC to November 29th, 1800 UTC and December 5th, 1900 UTC to December 7th, 0035 UTC.
Attached is a zipped tar file of spectral comparisons for the two pump-on periods cited and for an intervening pump-off period. Since I don't know what the pump frequency is supposed to be, I'm not sure where to focus attention, but I'm not seeing gross differences other than higher 60-Hz harmonics in both pump-on periods (is that expected from the pumps?), along with the overall greater excitation / upconversion of violin modes and the presence of "silent" calibration lines at 22.3 and 30.1 Hz in the first pump-on period. Here are the FScanned data intervals used: pumpon-1 -- 23.5 hours of SFTs collected between Nov24th, 0230 UTC and Nov 29th, 1800 UTC pumpon-2 -- 11.5 hours between Dec 5th, 1900 UTC and Dec 7th, 0035 UTC pumpoff -- 78 hours between Nov 30, 14:00 UTC and Dec 5th, 14:00 UTC If there are particular frequencies where I should be expecting disturbances, let me know and I'll do some zooming.
Kyle informed me offline that the pumps run at 1720 RPM (28.667 Hz) with small turbos running at 90,000 RPM (1500 Hz). Attached are zooms of bands around the first four harmonics 28.667 Hz (band sizes increase linearly with harmonic number) and around 1500 Hz. I don't see anything jumping out at me in any of the low-frequency bands that indicates an artifact restricted to pump-on times. The region around 1500 Hz is harder to interpret because of different average quad violin mode excitations and associated up-conversion. Fig 1 - 28.5-28.8 Hz Fig 2 - 57.0-57.6 Hz Fig 3 - 85.5-86.4 Hz Fig 4 - 114.0-115.2 Hz Fig 5 - 1480-1520 Hz
It seems like there are some PI modes that we are no longer damping that are slightly run up according to the dtt. I also wonder if the peaks at around 13000hz are modes that we had not had issues with before, or maybe something else entirely? I don't see any mention of them on the PI medm and they are currently the highest. I will try to damp some of the other ones if they get any higher.
The attached shows the PI dtt just after reaching low noise.
Well I think things are stable now. I ended up flipping the sign for the both the phase and gain on mode 27. Mode 26 also came up and changing the phase got it to, very slowly, go down. I took some screen shots of the dtt template at 20min, 26min, and 32min into the lock. The modes that the Striptools said were ringing up, didnt necessarily agree with the dtt. I dont remember how much the modes can shift in frequency, but it seems like some of them were off by a couple of hz.
A couple things:
Please any operator contact me at any time if help/explanations/etc is needed.
For the couple hz off thing, I was mainly refering to the frequencies listed on the medm above the modes. I'm not sure how accurate these are suppose to be, but like mode 27 says 18041, and the dtt was saying that 18038 seemed to be more rung up (see second attached). I didn't remember how much they shifted, and I did not look at the actual filters themselves at the time.
I was able to make it work (on the second try) with just changing phase and gain so I didn't look into it too much after that. But, yes, following your instructions and changing the BP would have been next on the list.
In alog32385 you mention that you will put a reference trace to show what is normal and what is not. I would love this because I looked at the dtt picture that is on the wiki and saw that it was much different. Either way, it was a good learnign process for me since I have only ever had to change phases for PI modes.