TITLE: Dec 19 OWL Shift 08:00-16:00UTC (00:00-08:00 PST), all times posted in UTC
Outgoing Ops: Ed
Quick Summary: Useism is hanging at 90th percentile. Violin modes are relatively high (damping still turned off). Wind below 10 mph. Using 45mHz blen everywhere. Have StripTool running to monitor ETMs CPS sensors as Jim suggested (which Ed kindly passed on the information). The computer opposite to Ops station is very slow...
TITLE: Dec 18 EVE Shift 00:00-08:00UTC (16:00-00:00 PDT), all times posted in UTC
STATE Of H1: Observing
SUPPORT: Jason
INCOMING OPERATOR: Nutsinee
SHIFT SUMMARY:
After repeated locklosses waiting at various stages of the locking sequence after I had changed the blends to QUITE_90 as recommended. I decided to switch back to the 45mHz blends at the end stations. I let the IFO “cook” on ENGAGE_ASC_PART3 for a good long while before advancing. I can’t say conclusively that this change in the ISI blends did the trick, but the IFO went all the way to NLN/78Mpc and it’s been there ever since. EQ bands are nominal. The mean uSeism is slightly above the 90th percentile. Wind is calm. Handing off Locked IFO to Nutsinee.
ACTIVITY LOG:
04:34 Lockloss while at ENGAGE_ASC_PART3
05:00 Switched end station blends to Quite_90 (off axis) to see if locking would improve.
05:33 still no satisfaction locking. Lock breaks at DC_READOUT_TRANSITION, repeatedly. I put a call in to Sheila.
05:32 OMC SUS watchdog tripped.
05:53 it appears that when DC_READOUT_TRANSITION occurs that OMC_LOCK reports OMC not ready as it may still be in TUNE_OFFSETS.
06:05 Waited at ENGAGE_ASC_PART3 for OMC to move to READY_FOR_HANDOFF. Lockloss occured, this time, at the very next step (REFL_IN_VACUO)
06:21 Locklos occurred sitting on ENGAGE_ASC_PART3 Grasping at straws at this point. Haven’t heard back from Sheila.
06:51 FINALLY! Locked at NLN. Switched back to 45mHz blends at Ends. Had to manually start ISS second Loop
MID-SHIFT SUMMARY:
After the lock loss that occurred at 02:54UTC caused by earthquake in Vanuatu and about a 1 hr stand down to permit ring down, re-locking is being delayed by locklosses at various stages in the sequence.
EQ bands have come back down below .1um/s. The mean uSeism is right about the 90th percentile. Wind is calm. Re-locking marches on.
ACTIVITY LOG:
00:32 Timing error occurred H1SUSETMX.
DRMI Unlocked (Dec 19 02:54:05 UTC)
6.2 128km N of Isangel, Vanuatu
2015-12-19 02:10:53 UTC10.0 km
02:55 reset timing error
03:55 DRMI failed to grab solid. DId PRMI align
04:00 I had to reboot the ops station as dataviewer kept crashing
04:12 lost lock at DC_READOUT_TRANSITION
04:22 Lockloss at REDUCE_CARM_OFFSET
ITLE: Dec 18 EVE Shift 00:00-08:00UTC (16:00-00:00 PDT), all times posted in UTC
STATE Of H1: Observing
OUTGOING OPERATOR: Jim
QUICK SUMMARY: IFO recently re-locked. µSeism @ 90thpercentile. EQ bands nominal. Winds ≤ 10mph.
TITLE: 12/17 Day Shift: 16:00-24:00UTC
STATE of H1: Observing
Support: Typical control room crowd
Quick Summary: Mostly quiet. Evan did some work on DARM, I worked on EX HEPI, lost lock late but got it back in time for the party
Shift Activities:
C. Cahillane I have updated the LHO uncertainty budget, fixed some bugs, and generated fewer, more relevant plots. All calibration versions are included in every budget. I will review the details each version below: C00: No kappas, no static systematics applied C01: No kappas, static systematics applied C02: kappa_tst and kappa_C applied, kappa_pu and cavity pole not applied, static systematics applied C03: "Perfect", so all kappas and cavity pole applied, static systematics applied Whenever I do ratio comparisons between model response functions, the "perfect" C03 model is in the denominator. ***** PDFs 1, 2, and 3 ***** These contain the C01, C02, and C03 uncertainty budgets at GPS Time = 1126259461. (Kappas provided by Darkhan in aLOG 11499. Thanks Darkhan!) Plot 1 is the calibration version response function over C03's response function. Plot 2 is four plots. The mag and phase squared uncertainty components plots and the total mag and phase strain uncertainty by itself. Plots 3-6 are just enlarged versions of Plot 2. ***** PDF 4 and 5 ***** PDF 4 is the Sensing fits and statistics PDF 5 are the Actuation stages fits and statistics ***** PDF 6 ***** This 4 way subplot of all the calibration versions together on one plot. I plot the mag and phase response functions and their ratios. For the C01 calibration version, we have under 7% and 4 degrees of uncertainty (See PDF 1, Plot 2) For the C02 calibration version, we have under 6% and 3.5 degrees of uncertainty (See PDF 2, Plot 2)
C. Cahillane To reproduce these plots, go to the Calibration SVN and go to .../aligocalibration/trunk/Runs/O1/Common/MatlabTools/strainUncertainty_Final_O1.m and open this file. At the top of the file (lines 11-15) you can change the IFO you want uncertainty for (L1 or H1) and the GPS time. Run this file after you change it. The code takes < 5 minutes to run. It should post resulting plots in .../aligocalibration/trunk/Runs/O1/[IFO]/Results/Uncertainty/ where IFO is replaced by H1 or L1.
We went to commisioning as LLO was down, as I was setting up ETMX they came back online. As I returned ETMX to its nominal state so we could go back to observing I broke the lock.
The sensor correction on ETMX HEPI needs to be changed, it is using a bad filter. I think it's using a filter that we adjusted for the T240 that used to be installed there. The fix is a simple copy, paste from another bank, but its causing a lot of extra motion at EX. But it's possible that there maybe other issues
I noticed yesterday that the EX ISI Z performance was bad at low frequency compared to the other chambers. First plot shows each test mass chamber T240 Z spectra. Red is ETMX, blue is ETMY, green is ITMX, brown is ITMY. Around 10mhz ETMX is doing very poorly, it should look like ETMY, which is in a similar configuration. ITMX and ITMY look different because they are still running the 90mhz blends in Z, as Hugh logged a couple weeks ago, alog 24115. I immediately expected some component of the Z sensor correction on ETMX, because we use a broad band low frequency sensor correction whose gain peaking is in this frequency band, somewhat lower than the 45 mhz blend. I did an on/off comparison of the Z sensor correction (LLO was down, so I asked the Mike if looking at this was okay). Second plot is the ETMX Z T240 (dashed lines) and STS ground (solid) with Z sensor correction on (red) and off (blue). The dashed red shows the expected suppression of the microseism, but there is a whole lot of extra motion at 10 -50 mhz, the dashed blue shows that this disapperars when I turned the sensor correction off. That I've seen, none of the other BSCs see this, so I think the other filters are correct.
This extra motion is spilling over into other DOFs, mostly RX/RY. The third plot is HEPI IPS (solid) and L4C (dashed) RX, red is sensor correction on, blue is off. RY is similar, but it looks somewhat worse because these measurements were taking when the IFO was locked, so Tidal was running: the X low frequency motion looks really bad on HEPI because of this, RY probably sees some of that.
It's possible this is contributing to the EX ISI ringing up, but the extra RX/RY motion is a little too high in frequency. I've been watching ETMY CPS's today and ETMY X is rung up because of wind. Maybe we have noticed EX ringing up because winds have been mostly north south lately? Or maybe we just can't lock with EY rung up.
The filters are shown in my last plot. Red is the current filter, blue is what the other chambers are running. The gain peaking on red is ~20 at 15 mhz, the gain peaking on blue is ~10 at 30 mhz.
I've continued to analyze stochmon's results (found here) for coherence between the h(t) channels of L1 and H1. One interesting line is at 74 Hz, at which I get coherences at both H1 and L1 from corner station accelerometers. You can find the full results for the coherence here and here, but I've attached some relevant summary slides. Any idea where this is coming from?
Tagging the SEI, SUS, AOS, ISC, and SYS group, since the majority of these channels are projected versions of the ITMY ST2 GS13s and I suspect solving the problem will require action from a broad number of groups. ~74 [Hz] is roughly the right frequency for the fundamental of QUAD cage resonances. For H1 and L1 ITMY specifically, See LHO aLOG 5322; The X (beamline) direction attachment shows a broad resonance at ~75 [Hz]. Similarly for LLO LLO aLOG 7214, though the Q of the resonance is significantly lower. Suggested mechanism for coupling to DARM: the QUAD's cage is attached (mechanically) to the the ISI-ITMY's ST2. Thus the GS13s (the most sensitive local sensor in the chamber at those frequencies) are likely to see these resonance, where the resonance is excited by residual ground motion. However, the QUADs are great isolators at least frequencies, so we can rule out "traditional" coupling via direct transmission of this residual motion through the suspension chain to the test mass. What's more likely is that the cage itself is picking up scattered light from some source, and coupling it directly into the cavity's beam line. Note that a similar frequency, low Q feature was found on H1 ETMX while our end-station beam diverter was inadvertently left open for the beginning of the run, see LHO aLOG 22350. I suspect the same mechanism is at play here -- scattered light glinting off the QUAD cage into the IFO beamline.
TITLE: 12/18 OWL Shift: 08:00-16:00UTC (00:00-08:00PST), all times posted in UTC
STATE of H1: Observing at ~75 Mpc.
Incoming Operator: Jim
Support: Jim, Jenne
Quick Summary:
The range has been ratty since 8 hours ago. Omicron shows band of glitches around 20 Hz and between 100-200 Hz. I don't see any significance changes in environment from 8 hours ago. I dig through the summary page breifly and found SR3 oplev spectogram looking very nasty started 8 hours ago, but the spectrum doesn't show any misbehave osems. So the cause of these glitches is still unknown.
Shift Activities:
Nutsinee asked me to have a look-see at SR3. As you can see in the attached plot (1 day trend), the oplev sum is doing something very weird starting a few hours ago, but the optic motion (as seen by both the oplev and the osems) seems totally fine. So, something is likely funny with the SR3 optical lever laser, but since we don't ever use it in-loop, it's not a high priority for fixing right now.
DMT Omega looks glitchy between 100-200Hz. Useism have reached 90th percentile. Low wind (<5mph). A 5.6M earthquake at North of Ascension Island is coming through. LLO is already down. Hope we ride this one......
TITLE: 12/17 OWL Shift: 08:00-16:00UTC (00:00-08:00PDT), all times posted in UTC
STATE of H1: Observing
Incoming Operator: Jim
Support:
Quick Summary:
Very quiet night. Nothing to complain.
Shift Activities:
TITLE: 12/17 EVE Shift: 00:00-08:00UTC (16:00-00:00PDT), all times posted in UTC
STATE of H1: Observing for last 8+hrs with range of ~75Mpc
Incoming Operator: Nutsinee
Support: None needed
Quick Summary:
A nice quiet shift. useism holding steady at 0.4um/s for the last 24hrs. The winds seem to be calming down. And the snow is still on the ground. Range has been a little ratty-looking 70-80Mpc.
Shift Activities:
Evan G, Jeff K
Summary:
We finally processed the data Jeff collected (aLOG 21325) to investigate the mysterious zero near 100 Hz. Unfortunately, while we began to further understand the calibration measurements, we also uncovered new issues needing investigation.
Solved:
New mysteries:
Details:
Taking Jeff's measurements of the driver electronics (plotted magnitude only called rawXX.pdf attached) and dividing by the fitted values for the low-pass filters from aLOG 21283, we can see the remaining effect of the BOSEM in the circuit (see XX.pdf attached). We plot the magnitude and phase of each state. Left hand plots are over the full range of 1 Hz to 10 kHz, while right hand plots are zooms from 1 Hz to 200 Hz.
Fortunately, from these measurements, we can confirm that the DC transconductance is: UL = 578 uA/V, LL = 589 uA/V, UR = 582 uA/V, LR = 600 uA/V. Earlier measurements (see 21127 and 21142) had found that this was off by a factor of 2, but we do find the expected value. However, when trying to understand the "zero-like device" we found that the frequency dependence at higher frequency goes like f^{3/4}! Now we are confused.
Looking closely at the low frequency region, and in the zoom (right hand plots) we see that the fitted zero-pole pair doesn't quite take out the low-pass filters for state 3 and state 4 (last two low-pass stages). This could be because of the buffers in the driver electronics, but we are not sure if this is really the cause.
We also started looking at the parameters file for the CAL model and found that the UIM parameters have the wrong zero-pole pair and, in addition, are not using the fitted low-pass filter values. This needs to be rectified.
The script that plots these results is in:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Scripts/Electronics/analyze_uimdriver_wBOSEM_20150908.m
Integration Issue 1179 filed regarding the lack of using the measured UIM z:p parameters in the DARM model.
The omicron scans of the top ten Hanford BBH/BNS triggers on December 16th show a notable recurring wave-like glitch. The glitches are present in the following scans: https://ldas-jobs.ligo-wa.caltech.edu/~jacob.broida/Dec16/BBH/GW/1134302174/ https://ldas-jobs.ligo-wa.caltech.edu/~jacob.broida/Dec16/BBH/GW/1134294300/ https://ldas-jobs.ligo-wa.caltech.edu/~jacob.broida/Dec16/BBH/GW/1134291513/ https://ldas-jobs.ligo-wa.caltech.edu/~jacob.broida/Dec16/BNS/GW/1134295111/ Inspection of the auxiliary channels revealed that these signals seem to stem from one channel: H1:ASC-Y_TR_B_PIT_OUT_DQ.The scans for this channel are visible here: https://ldas-jobs.ligo-wa.caltech.edu/~jacob.broida/Dec16/BBH/1134302174/#H1:ASC-Y_TR_B_PIT_OUT_DQ https://ldas-jobs.ligo-wa.caltech.edu/~jacob.broida/Dec16/BBH/1134294300/#H1:ASC-Y_TR_B_PIT_OUT_DQ https://ldas-jobs.ligo-wa.caltech.edu/~jacob.broida/Dec16/BBH/1134291513/#H1:ASC-Y_TR_B_PIT_OUT_DQ https://ldas-jobs.ligo-wa.caltech.edu/~jacob.broida/Dec16/BNS/1134295111/#H1:ASC-Y_TR_B_PIT_OUT_DQ The rest of the scans from December 16th can be accessed from the chart here: https://ldas-jobs.ligo-wa.caltech.edu/~jacob.broida/Dec16/Results.html
BCV Results for the above glitches. BBH Glitches https://ldas-jobs.ligo-wa.caltech.edu/~sudarshan.ghonge/BCV/O1/H1_glitch_151216_bbh/H1_1134289817_1134329417_webpage/ BNS Glitches https://ldas-jobs.ligo-wa.caltech.edu/~sudarshan.ghonge/BCV/O1/H1_glitch_151216_bns/H1_1134282617_1134336617_webpage/
I saw the signal flatted out twice in a row. The lock wasn't broken. Same thing also happened twice during my shift last night. Is this problem becoming worse?
Also Ops computer and two other computers I've tried to logon to are equally VERY VERY SLOW. They're pretty much frozen. There's even a big gap when the verbal alarm was telling me time ("CURRENT TIME ------------- SOMETHING UTC") It took forever just to take a screenshot and attach it to this alog........ Let's hope the we don't lose lock because I don't know how to bring it back up with a frozen computer......
10:18 UTC I stepped out for a bit. Came back and saw a missed call. I don't know how to review the missed call number (sorry these wired phones are ancient technology to me. I will learn next time.). I'm back in the control room now.
The computers are better now.......