travis.sadecki@LIGO.ORG - posted 12:21, Monday 07 August 2017 (38047)
Ops Day Mid-shift Summary
Lock is 21.5 hours old. No issues.
Lock is 21.5 hours old. No issues.
With Gerardo's help, I collected images of optics and baffles in HAM2 from all currently available viewports, with a focus on identifying fiducials for evaluating the input alignment. The full report is T1700230, and the most notable fiducials are listed below with images attached.
Fiducials of note:
TITLE: 08/07 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 55Mpc
OUTGOING OPERATOR: Patrick
CURRENT ENVIRONMENT:
Wind: 3mph Gusts, 2mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.05 μm/s
QUICK SUMMARY: No issues handed off. Lock is 17 hours old.
TITLE: 08/07 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC STATE of H1: Observing at 54Mpc INCOMING OPERATOR: Travis SHIFT SUMMARY: Rode through a series of earthquakes in Papua New Guinea. Remained in observing the entire shift. LOG: N/A
M 5.3 - 156km SSW of Lorengau, Papua New Guinea 2017-08-07 12:12:11 UTC 3.351°S 146.777°E 10.0 km depth or M 5.3 - 171km SSW of Lorengau, Papua New Guinea 2017-08-07 12:02:50 UTC 3.510°S 146.819°E 10.0 km depth H1 remained locked.
Have remained in observing. No issues to report.
TITLE: 08/07 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 52Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
Wind: 6mph Gusts, 5mph 5min avg
Primary useism: 0.26 μm/s
Secondary useism: 0.05 μm/s
QUICK SUMMARY: Riding through an earthquake. So far still locked.
M 5.8 - 139km SW of Kokopo, Papua New Guinea
2017-08-07 06:26:44 UTC 5.401°S 151.557°E 34.5 km depth
Remained locked.
TITLE: 08/07 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 54Mpc
INCOMING OPERATOR: Patrick
SHIFT SUMMARY:
Nothing exciting to report. On large glitch in the last hour. Handing off to Patrick.
LOG:
This doesn't seem to be causing any glitching anywhere but the 3-10 Hz anthropogenic Z-axis has been climbing for the last two hours. This is also translating into the 10-30Hz BLRMS too. I don't see anything correlating with this.
Nothing else to report. H1 going on 5.5hours locked. Livingston dropped a couple of times. Still observing.
TITLE: 08/06 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Aligning
OUTGOING OPERATOR: Travis
CURRENT ENVIRONMENT:
Wind: 6mph Gusts, 4mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.06 μm/s
QUICK SUMMARY:
Arrived to find a2l needing to be run and Livingston was down, so I did. Dr Kissel is here measuring and plotting. Travis had nothing to report. Looks like business as usual.
23:28 H1 back to Observing
TITLE: 08/06 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 52Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY: JeffK doing ISI noise investigations from 19:00-21:22 UTC. One lockloss at the end of that time, but recovery was simple. No issues currently.
LOG: See previous aLogs.
J. Kissel Having finished the BSC-ISI drives early and with an hour to spare, I spent ~30 minutes tuning up templates to find if other QUADs than ETMY have the same kind of spurious high frequency dynamics on their UIM stage; a part of the approved end-of-run close-out measurements for the CAL group (see JRPC page). ETMY was confirmed to have far-from-simple-f^(-6)-roll-off in UIM actuation to test mass response above 100 Hz back in ER10 (see LHO aLOG 31603), so I was copying those templates. Unfortunately, I was only able to complete one frequency band of broad-band injections for ETMX, and then I broke the lock on the second band trying to get more SNR. The data I did get lives here: /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Measurements/FullIFOActuatorTFs/2017-08-06/ 2017-08-06_H1SUSETMX_L1_PCAL2DARM_HFDynamicsTest_100-250Hz.xml 2017-08-06_H1SUSETMX_L1_iEXC2DARM_HFDynamicsTest_100-250Hz.xml which was enough to show, indeed, some nasty resonant feature in UIM actuation in that band. In the fullness of time, I'll process, plot, and post this data once I get the rest of the suite as I'd had before, but processing the broad-band ISI injections is a priority at the moment. Note: taking this data required me to briefly turn off all calibration lines on PCALX (333.9, 1083.3, and the roaming line which was at 2001.3 at the time of lock loss). However, all was restored after the lock loss, and the lines are back on wit the roaming line driving 2001.3 again.
J. Kissel I spent 2.5 hours of IFO time today (or 3 hours even if you consider the lock-loss likely caused by me, and recovery from a part of it) gathering some more data on the recently found coupling between BSC-ISI's ST2 and DELTAL_EXTERNAL (see LHO aLOG 37752). Today, I drove in RX/RY (Pitch for each arm) and RZ (Yaw / Longitudinal for all) instead of X / Y (Longitudinal for each arm). The templates for the drive live here: /ligo/svncommon/SeiSVN/seismic/BSC-ISI/H1/Common/Data/ 2017-08-06_BSCISI_ST2_BB_RXRY_Injections.xml 2017-08-06_BSCISI_ST2_BB_RZ_Injections.xml However, they don't yet contain references for all times where I've driven. That'll come as I gather data from the frames. I'll recommit once I'm finished gathering all the data and plotting it. Plots and Analysis to come.
Relocked without any issues, just the usual tweaking of ETMs to get ALS to lock. Sudarshan called about the lockloss and said that likely the PCal X HF line would be reverted to a 1501.3 Hz due to the lockloss, and asked me to change it back to 2001.3 Hz when at NLN. I did so.
SDF diffs accepted in order to go to Observe (see screenshots). These are the same SDF diffs, but inverted, that Ed accepted at the last lockloss (see aLog 38009). Should these become unmonitored, or is something else bad going on here??
Either Kissel measurements or incoming EQ. Or some combination thereof.
Sudarshan called and requested that I change the PCal X high frequency line to 2001.3 Hz (previously 2501.3 Hz). This was done at 20:06 UTC.
No issues and lock is 40 hours old. Kissel just showed up on site and plans to do some noise investigations (approved by Vern), so we'll likely be out of Observing shortly.
Commissioning mode at 19:04 UTC.
FAMIS 6909 HAM3 V1 seems elevated. BS ST1 all DOF seem elevated. ETMY ST1 H2 seems elevated. ETMY ST2 V2 seems elevated. ITMX ST1 all DOF seem elevated. ITMX ST2 V3 seems elevated. ITMY ST1 all DOF seem elevated.
J. Kissel, R. McCarthy Some investigation on this... Date Jun 26 2017 Aug 02 2017 Time GPS 1182506160 - 1182506760 1185730620 - 1185731220 Time UTC 09:55:42 - 10:05:42 17:36:42 - 17:46:42 Time PDT 02:55:42 - 03:05:42 10:36:42 - 10:46:42 Richard points to data from the Jun 26th FAMIS check, in LHO aLOG 37138, worried that this might be exposing something wrong after the July 6th Montana EQ. - I've trended the global seismic configuration, and we were in "WINDY" at both these times, so this rules out a different configuration of the ST1 controls (i.e. I'd thought it was maybe that we were in a higher blend filter, or sensor correction for the site was off or something.) - The summary pages don't show a difference between the ST2 / Suspension Point performance on these two days, which means whatever excess that ST1 is seeing is controlled below the sensor noise of ST2 GS13s, which is good. (Not summary pages are a media spectra for the entire UTC day, not just for these 10 minute periods used for this FAMIS test). - Then I realized there should be a large difference in the 1-3, 3-10 Hz input ground motion, just due to the difference between 3am local and 10am local anthropogenic activity. I attach spectra comparing ground motion (as measured by the STSs on the ground in all VEAs), and they agree with what's shown in the ST1 CPS -- in the 0.8 to 20 Hz region, there are features that show roughly an order of magnitude more motion in all buildings comparing the Jun 26th time and Aug 02 time. This is not at all indicative of anything wrong. (Aug 02 is the reference, Jun 26 is the non-reference data). We should standardize at what time of day we use to gather data for inspection in this FAMIS task. The test was designed to look for elevation in the *sensor noise* of the ISI's capacitive position sensors, indicative of problems we've seen with the electronics -- i.e. the flat, above 10 Hz, featureless part of the spectra will be elevated above the black line if there's badness. There will likely *always* be feature-full, residual seismic motion that's visible in these spectra that can be different from test-to-test, especially on stage 1 in the 1-30 Hz range because ST1 does not isolate this region (that job is left for stage 2 / ST2). One can't necessarily *know* that the feature-full full stuff is "real" residual seismic data, but this test is designed for you to ignore that stuff, and focus on the high frequency flat portion of the spectra. Standardizing that we take the data in the middle of the night, local time, when there is less 1-30 Hz input ground motion (since most people are asleep), means the platform will be moving less, and expose more CPS sensor noise, and this'll be a more focused test.
I've updated both HAM and BSC python scripts to look at 2 am local using gpstime.tconvert('2am today') . I've also left code in, commented out, so that the measurement time can be specified in the terminal. It would be nice to have some easier to find or use documentation for some of these libraries. I knew there was tconvert python stuff, but had no idea where to find how to use it.