J. Kissel I've completed an entire suite of calibration measurements this morning, which contains the first actuator assessment after the May 2017 vent. Preliminary screen shots attached, and svn file locations listed below. Actuation Function Characterization /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Measurements/FullIFOActuatorTFs/2017-06-14/ 2017-06-14_H1SUSETMY_L1_iEXC2DARM_25min.xml == A_{UIM} * C / (1 + G) 2017-06-14_H1SUSETMY_L1_PCAL2DARM_8min.xml == C / (1 + G) 2017-06-14_H1SUSETMY_L2_iEXC2DARM_17min.xml == A_{PUM} * C / (1 + G) 2017-06-14_H1SUSETMY_L2_PCAL2DARM_8min.xml == C / (1 + G) 2017-06-14_H1SUSETMY_L3_iEXC2DARM_8min.xml == A_{TST} * C / (1 + G) 2017-06-14_H1SUSETMY_L3_PCAL2DARM_8min.xml == C / (1 + G) Sensing Function Characterization /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Measurements/SensingFunctionTFs/ 2017-06-14_H1DARM_OLGTF_4to1200Hz_25min.xml == 1 / (1 + G) 2017-06-14_H1_PCAL2DARMTF_4to1200Hz_8min.xml == C / (1 + G) 2017-06-14_H1_OMCDCPDSUM_to_DARMIN1.xml == C, covering conversion from mA of DCPD sum to DARM_IN1 [ct]. 2017-06-14_H1_PCAL2DARMTF_BB_5to1000Hz_0p25BW_250avgs_5min.xml == broad band excitation to compare PCAL against calibrated Detector Output Analysis to come. Note that we should likely use (export) H1 PCALY's TX PD (as opposed to RX PD) as our displacement reference such that we're not confused by the RX PD's recently identified temperature sensitivity (see LHO aLOG 36884).
I don't see anything egregious in these plots. Correct me if I'm wrong. This closes FAMIS task 6902.
J. Kissel Having been bitten by "clipping" in PCALY beforehand, I've gotten into the habit of trending the PCAL's reported test mass displacement before / during calibration measurements. Further, I've been worried that the residual temperature fluctuations after end-station's HVAC upgrade will impact the accuracy of the PCALY's RX PD's reported reported displacement. Sure enough, the attached trend shows that the residual 0.2 [deg C] diurnal temperature swing is causing a 1.0 to 1.5% deviation in reported displacement. I'm not sure whether to request that the PCAL system be less sensitive to temperature, or if the HVAC system to control the temperature better, but we can't use the RXPD as a fundamental reference, with claimed accuaracy / precision of 0.75% if its impacted by temperature at twice that level. For record, we're in no way sure that this isn't caused by test mass pitch (also from temperature fluctuations) steering the beam into a spot that has more clipping, if the PCAL periscope's position is oscillating with temperature, it's something inside the receiver box, or something we otherwise haven't considered. That the TXPD's reported displacement remains rock-solid implies that the fluctuations are not on the input side. For now, I'll record the TXPD as reference during transfer functions.
J. Kissel The situation is similar, if not worse on H1 PCAL X -- worse, because the TX PD is also showing a ~1-2% displacement distortion following the diurnal temperature cycle. See attached trend of equivalent channels.
Opened FRS Ticket 8328, and assigned to Rick Savage.
The presence of the new diode box is quite evident. Everything else looks normal.
J. Kissel After discussing with Robert and Keita, I'm taking over the IFO to run post-vent calibration checks for about 1-1.5 hours (assuming we stay at nominal sensitivity). Will post when finished.
TITLE: 06/14 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC STATE of H1: Observing at 62Mpc INCOMING OPERATOR: Jeff SHIFT SUMMARY: Lost lock at the beginning of the shift from large earthquakes in Mexico and Guatemala. No clear reason for second lock loss. Current lock seems more stable. LOG: 10:06 UTC Untripped watchdogs 10:09 UTC Attempting to relock 10:19 UTC Starting initial alignment TMSX had to be moved to get green locked high enough on the X arm, likely because it tripped from the earthquake 10:54 UTC Initial alignment done 11:32 UTC Observing 11:40 UTC GRB 12:07 UTC GRB 12:13 UTC Lock loss 12:56 UTC Observing 13:58 UTC Karen to optics lab 14:15 UTC King soft water through gate. Here to pull water samples. 14:20 UTC Dust alarms in vacuum prep lab 14:23 UTC Ken to warehouse with pickup truck 14:40 UTC Karen out of optics lab
NLN at 12:45 UTC. Current SDF differences attached. Need to determine what to do about H1:ALS-Y_LOCK_STATEREQUEST and H1:ALS-C_LOCK_REQUESTY.
Changing H1:ALS-C_LOCK_REQUESTY to Red Locked seemed to fix both. Accepted the offsets.
Back to observing at 12:56 UTC.
Lock loss at 12:13 UTC. I was working on damping PI mode 27 but I don't think it was anywhere near high enough to cause a lock loss. Range had been degrading prior.
Back to observing at 11:32 UTC. Accepted attached SDF differences.
Earthquake has substantially subsided. Finished initial alignment. Attempting to relock.
I'm confused. I was almost certain I had updated the FMCS medm screens actually linked from the sitemap. However running svn update
in /opt/rtcds/userapps/release/fmcs/h0/medm
gave:
The conflict is because I had just started to edit this screen.
The screens linked from the sitemap now reflect the changes I had made. I'm not sure where I checked in the changes from if it was not /opt/rtcds/userapps/release/fmcs/h0/medm
. I have a copy of these screens in my home directory but they do not seem to be an svn working copy. Did someone revert /opt/rtcds/userapps/release/fmcs/h0/medm
to an earlier revision?
More confusion. The link in the SITEMAP.adl file in /opt/rtcds/lho/h1/medm
points to /ligo/lho/h0/fmcs/medm
not /opt/rtcds/userapps/release/fmcs/h0/medm
.
/ligo/lho/h0/fmcs/medm
is an svn working copy already at the most recent revision.
Perhaps something changed with the SITEMAP instead?
TITLE: 06/14 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC STATE of H1: Earthquake OUTGOING OPERATOR: TJ CURRENT ENVIRONMENT: Wind: 9mph Gusts, 7mph 5min avg Primary useism: 0.26 μm/s Secondary useism: 0.17 μm/s QUICK SUMMARY: Just lost lock coincident with earthquake.
Lock loss at 7:06 UTC. tconvert on GPS time for Seismon gives Jun 14 2017 06:38:54 UTC for time of earthquake and Jun 14 2017 07:15:03 UTC for arrival of R-20 Wave. Seismon and USGS/Terramon do not exactly agree.
Verbal alarms just announced an incoming earthquake at 07:32 UTC. Seismon has updated to the attached screenshot. 07:38 UTC USGS has reported it 07:39 UTC Spike seen on BLRMS
07:45 UTC Watchdogs starting to trip
The following watchdogs tripped:
ISI ETMX stage 2
ISI ITMY stage 2
ISI ITMY stage 1
ISI ETMX stage 1
SUS TMSX
ISI ETMY stage 1
ISI ETMY stage 2