M5.5 - 42km SSW of Betafo, Madagascar

Reported twice by Terramon, once by USGS

Was it reported by Terramon, USGS, SEISMON? Yes, Yes, No

Magnitude (according to Terramon, USGS, SEISMON): (5.4, 5.5), 5.5, NA

Location: 42km SSW of Betafo, Madagascar, 20.158°S, 46.633°E, 8.7 km depth 

 

Starting time of event (ie. when BLRMS started to increase on DMT on the wall): ~ 23:20 UTC

Lock status? Not locked at time

EQ reported by Terramon BEFORE it actually arrived? Unknown.

model restarts logged for Tue 10/Jan/2017
2017_01_10 08:47 h1nds1

Complete h1tw1 offloading, reconfigure daqdrc on nds1.

model restarts logged for Mon 09/Jan/2017
2017_01_09 10:02 h1tw1

Restart tw1 after NFS failure Fri 06

model restarts logged for Sun 08/Jan/2017 - Sat 07/Jan/2017 No restarts reported (minute trends unavailable due to h1tw1 NFS error)

model restarts logged for Fri 06/Jan/2017
2017_01_06 08:13 h1nds0
2017_01_06 08:13 h1nds1

Restart both nds's as tw1 offloading starts. h1tw1 stopped NFS exporting at 17:20 this day.

model restarts logged for Thu 05/Jan/2017 - Wed 04/Jan/2017 No restarts reported

Outside of the NDS, TW1 and FW0 restarts, the rest of the DAQ has now been running for 37+ days (DC, FW1, FW2, GDS-BRCSTR).

TITLE: 01/12 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 67.1386Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Just made it back to observing. Lockloss likely from snow removal at end X ringing up BRS X.
LOG:
15:46 UTC John starting clearing snow by CP1
16:13 UTC Starting initial alignment
16:20 UTC Terra called from LLO to ask about our state. They will probably start a test.
16:36 UTC John at end Y clearing snow
16:46 UTC Krishna turning sensor correction at end Y off
16:52 UTC Krishna turning sensor correction at end Y back on
16:58 UTC May have accidently moved PR2 instead of BS during MICH_DARK_LOCKED. Trended back and changed pitch back to previous value. Went back to redo PRM_ALIGN.
17:01 UTC Accidently selected INPUT_ALIGN_OFFLOADED instead of PRM_ALIGN_OFFLOADED. Reselected PRM_ALIGN.
17:04 UTC Karen to warehouse
17:15 UTC Initial alignment complete
17:28 UTC John done clearing snow at end Y, working way back to corner
17:34 UTC Sensor correction had not actually been turned back on at end Y. Reselecting guardian state turned it on.
17:45 UTC Lockloss at INCREASE_POWER. HAM6 ISI tripped.
17:52 UTC Karen out of warehouse
18:07 UTC Lockloss at INCREASE_POWER. HAM6 ISI tripped.
18:20 UTC Gerardo to end Y to check on IP controller. Not going into VEA. Not changing BRS.
18:42 UTC Damped PI mode 27
18:46 UTC NLN
18:50 UTC Changed H1:SYS-MOTION_C_PICO_D_CURRENT_ENABLE from Enabled to Disabled. Observing.
19:02 UTC GRB. LLO is down. Called LLO control room. Joe says he did not receive alert. LLO currently down due to wind.
19:19 UTC Damped PI modes 27 and 28
19:22 UTC Kyle to mid Y to take pictures
19:26 UTC Damped PI mode 27. Had to change phase.
19:34 UTC GRB. LLO is still down.
19:49 UTC Chandra running down Y arm
19:52 UTC Ran passive a2l check: /opt/rtcds/userapps/release/isc/common/scripts/decoup/DARM_a2l_passive.xml. Looks fine.
20:08 UTC Greg to warehouse
20:19 URC Greg back from warehouse
20:20 UTC Kyle back from mid Y
20:32 UTC Joe to mid Y and end Y to shovel snow
21:25 UTC Bubba starting clearing snow on X arm
21:36 UTC Joe back from mid Y
21:38 UTC Damped PI mode 28
21:50 UTC Gerardo, Filiberto and Marc starting WP 6430
22:23 UTC Out of observing for Sheila to test affect on DARM of closing beam diverter
22:37 UTC Sheila done. Back to observing.
22:58 UTC Gerardo, Filiberto and Marc done
23:08 UTC Lock loss. BRS X in fault. Bubba at end X clearing snow with front end loader close to building.
23:15 UTC Changed ISI Config at end X to BLEND_Quite_250_SC_None.
23:25 UTC Bubba on the way back from end X
23:26 UTC John to mid X
23:46 UTC Changed ISI Config at end X back to BLEND_QUITE_250_SC_BRS
00:05 UTC Corey reports front end loader is back at corner station
00:09 UTC Krishna rerequested ISI Config at end X to BLEND_QUITE_250_SC_BRS
00:14 UTC Observing

Since we have now been correctly accounting for the ~0.99 AA gain used in the DARM calibration model (see LHO aLOG 32907), I have updated the control room DTT templates with the correct calibration. This is done similarly to LHO aLOG 32542.

The math needs to be updated to account for the improved understanding (see calibration subway map diagram):

DELTAL_EXT   W * [Derr/C_foton + A*Dctrl*delay]
---------- = ----------------------------------
PCAL_RX_PD    m * f^2 * AA_a/(AA_a gain) * AA_d

 m     DELTAL_EXT * [C_foton/C_real] / [W * AA_a * AA_d * OMCpoles * OMCtoCALCSdelay * lightTimeDelay * unknownSensingDelay]
--- = -----------------------------------------------------------------------------------------------------------------------
 m                                 sign * PCAL_RX_PD / [f^2 * AA_a/(AA_a gain) * AA_d]

Then the Pcal to DARM calibration is:

                                     [C_foton/C_real] * f^2
---------------------------------------------------------------------------------------------------------
[W * sign * (AA_a gain) * uncompensatedOMCpoles * OMCtoCALCSdelay * lightTimeDelay * unknownSensingDelay]

For the broad band Pcal to DARM measurement, since the calibration is applied separately to PCAL_RX_PD, we only need:

                                         [C_foton/C_real]
---------------------------------------------------------------------------------------------------------
[W * sign * (AA_a gain) * uncompensatedOMCpoles * OMCtoCALCSdelay * lightTimeDelay * unknownSensingDelay]

I have made a new control room calibration folder containing these scripts and calibration transfer function products, using the latest DARM reference model:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/ControlRoomCalib/H1_pcal2darm_correction.m
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/ControlRoomCalib/pcal2darm_calib.txt
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/ControlRoomCalib/caldeltal_calib.txt

The latest DTT measurements have been updated to include these transfer function products:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Measurements/SensingFunctionTFs/2017-01-03_H1_PCAL2DARMTF_4to1200Hz_8min.xml
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Measurements/SensingFunctionTFs/2017-01-03_H1_PCAL2DARMTF_BB_5to1000Hz.xml

WP 6430

Chandra reported issues with Y2-8 ion pump, see alog entry. Gerardo verified controller had not tripped off. Following error messages were displayed on the controller:

1. Controller found with "Error 02"
2. After restarting controller, "Error 10", excessive arcing condition has been detected

With HV cable disconnected at power supply, HV output was enabled without no issues. Disconnected HV cable at both ends, and tested with the HiPOT tester. Test failed at ~500V. Marc tested the cable with the fieldfox N9912A, and will post some data.

Fil, Gerard, Marc

Changed to new versions of the H1 DARM figure of merit displays for nuc3 and nuc6 in the control room.  New versions are in userapps, checked in to svn.

(Late entry from yesterday's maintenance)

h1tw1 offload old minute trends

Jim

h1nds1 was restarted to use the recent offload of minute trends from h1tw1.

WP 6411 Add Chiller Yard H2O Supply Temperatures to cell phone alerts

John, Dave:

CS, EX and EY chiller yard supply water temperatures were added to the cell phone alert system. Alarm levels are HIGH=55F, LOW=32F.

With some help from Jim Batch, Evan G and Jeff K I've updated the DARM FOM for display on nuc3.  The gold trace in the new version is updated to a spectrum taken in the O2 configuration, when the range was good (75MPc, Dec 13th).  This should make it easier for operators to asses the current performance of H1 against what it has been in O2.  

The old gold reference from Jan 30th 2016, which is smiilar in range but has better low frequency sensitivy, is still saved in the template. 

With Keita's permission, I did a quick test of closing the pop beam diverter.  

Background:

We have been running with the POP beam diverter open, and saw in the past that there was a scattered light problem from ISCT1 (30835, the comment to this alog reports that the beam diverter would be automatically closed, but because of ASC problems we have actually been running with it open)  Since the range has been slowly deteriorating over the last few weeks, (see the trend of H1's range over most of O2 so far in attachment) I wondered if our alingment has drifted so that the scattering problem from ISCT1 is worse.  Keita agreed that it was worth a quick test.  

We closed the beam diverter at 22:24:25 UTC Jan 11 2016 and opened it again at 22:34:30 UTC.  Based on the spectrum and range, this didn't have a big impact, so it seems like the POP path on ISCT1 is not the culprit for this range drop.   We are now back to observing with the normal configuration. 

J. Kissel

I've completed creating an updated parameter set for the matlab DARM loop model that  contains the updates from the fit of the 2016-11-12 calibration reference measurements (see LHO aLOG 31433 for original measurement set, and LHO aLOG 32989 for updated analysis). 

I've compared the model output against those measurements using
${CalSVN}/aligocalibration/trunk/Runs/ER10/H1/Scripts/DARMOLGTFs/compareDARMOLGTFs.m  (r4123, ls: r4123)
Results are attached. The agreement is excellent.

I also attached the sensing and actuation function fit parameter results, just for completeness -- including nlinfit results (and because LHO aLOG 32989 has some typos, only corrected in its comment, LHO aLOG 33090).

                                                       Former Value        MAP     (95% C.I.)  MAP       (95% C.I.)
                                                       2016-11-12          2016-11-12 (nlinfit)      2016-11-12 (MCMC)

 Optical Gain                K_C         [ct/m]        1.15e6              1.166e6 (0.0003e6)        1.164e6   (0.0002e6)
 Couple Cav. Pole Freq.      f_c         [Hz]          346.7               347.2   (5.8)             346.7     (2.7)
 Residual Sensing Delay      tau_C       [us]          2.3                 2.12    (5.5)             2.3       (2.3)
 SRC Detuning Spring Freq.   f_s         [Hz]          7.4                 7.38    (0.3)             7.38      (0.16)
 Inv. Spring Qual. Factor    1/Q_s       [ ]           0.05                0.046   (0.013)           0.046     (0.008)

 UIM/L1 Actuation Strength   K_UIM       [N/ct]        8.164e-8            n/a                       8.104e-8  (0.2%)
 PUM/L2 Actuation Strength   K_PUM       [N/ct]        6.841e-10           n/a                       6.773e-10 (0.04%)
 UIM/L3 Actuation Strength   K_TST       [N/ct]        4.389e-12           n/a                       4.346e-12 (0.05%)

Not only is the model in excellent agreement with the measurement, the nlinfit fit parameter values are in excellent agreement with the MCMC values with the sensing function. As with the updated / new 2017-01-03 model (LHO aLOG 33004), I've used the nlinfit values to update the sensing function parameter set. For the actuator coefficients, I've again used 
${CalSVN}/aligocalibration/trunk/Runs/ER10/H1/Scripts/FullIFOActuatorTFs/
    getActValuesForParamsFile.m   (r4126, lc: r4126)
and the clunky process described in LHO aLOG 33092.
Also, I've run the fitting algorithms on *only* the reference measurement data set (i.e. I did not run on multiple measurements worth, assuming no and/or compensating for time-dependence).

I've committed the following model pieces to the Cal SVN repo:
(r = svn revision, lc = last changed revision)

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/
O2/DARMmodel/src/
    DARMmodel.m        (r4093, lc: r3511)
    computeSensing.m   (r4093, lc: r4025)
    computeActuation.m (r4093, lc: r4003)

Param Files
O2/Common/params/
    IFOindepParams.conf (r4042, lc: r4002)

ER10/H1/params/
    H1params.conf       (r4121, lc: r4121)

ER10/H1/params/2016-11-12/
    H1params_2016-11-12.conf                      (r3944, lc: 3786)
    measurements_2016-11-12_sensing.conf          (r4122, lc: r4122)
    measurements_2016-11-12_ETMY_L1_actuator.conf (r3944, lc: r3810)
    measurements_2016-11-12_ETMY_L2_actuator.conf (r3944, lc: r3810)
    measurements_2016-11-12_ETMY_L3_actuator.conf (r3944, lc: r3810)
 

More notes:
- I did not update the export of foton implementation of the inverse sensing function. This is because
    (a) DCS "offline" calibration filters DARM_ERR and DARM_CTRL directly with FIR filters. For the DARM_ERR filter, the inverse sensing function is computed directly from the matlab model and does not suffer from IIR filter warping, and does not need low- or high- frequency cutoffs that the front-end pipeline must have for causality.
    (b) If we *were* to regenerate GDS calibration, which correct the front-end for its flaws -- including this inverse sensing function filter -- then we would need to use exactly what filter was in place, and the 
${CalSVN}/aligocalibration/trunk/Runs/
    ER10/H1/Measurements/Foton/
        2016-12-07_H1CALCS_InverseSensingFunction_Foton_SRCD-2N_Gain_tf.txt (r3921, lc: r3921)
file is what was used, at least from 2016-12-07 to 2016-12-22, until it was *actually* updated on 2017-01-03.

What to do from here:
- Use the loop model to push new EPICs records that document model values at calibration line frequencies
- Use the new loop model to generate DCS FIR filters to recalibrate the all data from the pre-winter break from raw DARM_ERR and DARM_CTRL.
- Push hard for uncertainty estimations for both the first part of O2 and data post-winter break.

In observing, but range has degraded quickly from start of lock. Just started climbing back. Now around 60 MPc. Front end loader is parked.

Starting CP3 fill. LLCV enabled. LLCV set to manual control. LLCV set to 50% open. Fill completed in 42 seconds. TC B did not register fill. LLCV set back to 14.0% open.
Starting CP4 fill. LLCV enabled. LLCV set to manual control. LLCV set to 70% open. Fill completed in 108 seconds. TC A did not register fill. LLCV set back to 35.0% open.

The test takes an average of the last 120s of H1:CAL-PCAL(X/Y)_RX_PD_OUTPUT and compares it to nominal values that I found by taking many different averages over times without clipping. If the percent difference is greater than 1% it will notify.

Set to observing at 18:50 UTC. Had to revert one SDF difference: Changed H1:SYS-MOTION_C_PICO_D_CURRENT_ENABLE from Enabled to Disabled. See attached screenshot.

TITLE: 01/11 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 60.9258Mpc
INCOMING OPERATOR: Jim may or may not decide to venture in (I have been in contact with him this evening)
SHIFT SUMMARY:
H1 has been in OBSERVING for almost 6hrs at a fairly steady 60Mpc.

Continue to experience non-normal winter weather with forecast for possibly more snow overnight & freezing temperatures.  Have also had fairly blizzard like conditions with winds just below 20mph.  Have been in contact with OWL shift operator with regards to coverage & they will do what feels safe.  

I am leaving NOW to brave roads home & so H1 will be flying on automatic pilot for a few hours or until the morning. 

I have talked with William Parker (LLO operator) and aprised him of our situation.

LOG:

DIAG_MAIN message:   PCAL:  Y RX PD is 0.01 OFF

• Last person other than me....at 4:30pm (0:28utc)
• H1 has been UNDISTURBED since 22:43utc
• 0:34-1:34 GRB Stand Down Time
• 2:14 PI Mode 27 quickly rang up.  Sign change damped it.
• 2:33 TCSy Chiller LOW flow (no action taken)

I have produced filters for offline calibration of Hanford data from the beginning of O2 A until the end of 2016. The filters can be found in the calibration SVN at this location:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/GDSFilters/H1DCS_1163173888.npz

For information on the calibration model, see
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=31693
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=32329
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=32907

For suggested command line options to use when calibrating this data, see:
https://wiki.ligo.org/Calibration/GDSCalibrationConfigurationsO2

The filters were produced using this Matlab script in SVN revision 4050:
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/TDfilters/H1_run_td_filters_1163173888.m

The parameters files used (all in revision 4050) were:
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/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_1163173888.conf
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/Scripts/CAL_EPICS/D20161122_H1_CAL_EPICS_VALUES.m

Several plots are attached. The first four (png files) are spectrum comparisons between CALCS, GDS, and DCS. Kappas were applied in both GDS and DCS plots with a coherence uncertainty threshold of 0.4%. Time domain vs. frequency domain comparison plots of the filters are also attached. Lastly, brief time series of the kappas and coherences are attached, for comparison with CALCS.