Posted are data for the two long term storage dry boxes (DB1 & DB4) in use in the VPW. Measurement data looks good, with no issues or problems being noted. I will collect the data from the desiccant cabinet in the LVEA during the next maintenance window.   

These are the past ten day trends.

Dan, Travis

Tonight during our long lock we measured the decay time constant of the ITMX bounce mode.  At 10:10 UTC we set the intent bit to "I solemnly swear I am up to no good" and flipped the sign on the ITMX_M0_DARM_DAMP_V filter bank and let the bounce mode ring up until it was about 3e-14 m/rt[Hz] in the DARM spectrum.  Then, we zeroed the damping gain and let the mode slowly decay over the next few hours.

We measured the mode's Q by fitting the decay curve in two different datasets.  The first dataset is the 16Hz-sampled output of Sheila's new RMS monitors; the ITMX bandpass filter is a 4th-order butterworth with corner frequencies of 9.83 and 9.87Hz (the mode frequency is 9.848Hz, +/- 0.001 Hz).  This data was lowpassed at 1Hz and fit with an exponential curve.

For the second dataset I followed Koji's demodulation recipe from the OMC 'beacon' measurement.  I collected 20 seconds of DELTAL_EXTERNAL_DQ data, every 200 seconds; bandpassed at 9 and 12Hz, demodulated at 9.484Hz, and lowpassed at 2Hz; and collected the median value of the sum of the squares of the demod products.  Some data were neglected on the edges of the 20-sec segment to avoid filter transients.  These every-200-sec datapoints were fit with an exponential curve.

Results attached; the two methods give different results for Q:

RMS channel: 594,000

Demodulated DARM_ERR: 402,000

I fiddled with the data collection parameters and filtering parameters for both fits, but the results were robust.  When varying parameters for each method the results for Q were repeatable within +/- 2,000, this gives some sense of the lower limit on uncertainty of the measurement.  (The discrepancy between the two methods gives a sense of the upper limit...)  Given a choice between the two I think I trust the RMS channel more, the demod path has more moving parts and there could be a subtlety in the filtering that I am overlooking.  The code is attached.

Times in UTC

7:00 Came in to find the IFO had been locked to LSC FF for several hours already, left it as is

9:57 Seeing that Livingston had dropped lock, switched Intent Bit to commissioning, and with a suggestion/assistance from Dan H., undamped the bounce mode of  ITMX for a ringdown measurement of its Q.  Gain of H1SUS-ITMX_M0_DARM_DAMP_V set to 0.0 (from 0.3) for ringdown.  Will need to set back to actively damp the mode once Dan is satisfied

10:58 Switched Intent Bit back to undisturbed

14:11 Switched Intent Bit to commissioning.  Edited LSC_FF guardian to bring laser power back to 24W.  Switched Intent Bit back to undisturbed.

14:35 Lockloss (Richard volunteered to take blame)

14:39 Reduced power back to 16W.  Initial alignment.

15:00 Handoff to Patrick.

King Soft Water was on site yesterday and replaced 4 of the 9 membranes in the R.O. system, the other 5 are on order. This seemed to make a noticeable difference in that the water system actually ran all night without tripping. The water was also tested yesterday and found to be in very good condition.

model restarts logged for Tue 02/Jun/2015
2015_06_02 04:40 h1fw0*
2015_06_02 06:49 h1fw0*
2015_06_02 10:57 h1iopsush34
2015_06_02 10:59 h1susmc2
2015_06_02 10:59 h1suspr2
2015_06_02 10:59 h1sussr2
2015_06_02 11:31 h1calcs

* = two unexpected fw0 restarts. Restart of h1sush34 for re-calibration of 18bit-DACs. New calcs model.

I was able to replace one coarse regulator with a new flowmeter  and these are the results of that change.

Submitted by Bubba.

Dan, Travis

Around 06:50 UTC we started to observe frequent glitching in the PRCL and SRCL loops that generated a lot of nonstationary noise in DARM between 20 and 100Hz.  The glitches occur several times a minute, it's been two hours of more or less the same behvaior and counting.  Our range has dropped by a couple of megaparsecs.  The first plot has a spectrogram of DARM compared to SRCL that shows a burst of excess noise at 08:08:20 UTC.

The noise shows up in POP_A_RF45_I and POP_A_RF9_I, but not so much in the Q phases, see second plot.  (MICH is POPA_RF45_Q, PRCL and SRCL are from the I-phases.)  A quick look at the PRM and SRM coil outputs doesn't reveal a consistent DAC value at the time of the glitches, so maybe DAC glitching isn't a problem, see third plot.  The three optical levers that we're using in the corner station (ITMX, ITMY, SR3, all in pitch) don't look any different now than they did before 0700 UTC.

Observation Bit: Commissioning

16:00 Day shift IFO to LCS_FF

16:08 Lockloss – Guardian recovering

17:35 IFO Locked at LCS_FF

17:38 Lockloss – Guardian recovering – Will take the IFO to LSC_FF at lower power (16.6w)

18:24 Set Observation bit to Undisturbed

00:00 Some glitches but Lock held at 48Mpc

I have created the FIR filters for the GDS calibration during ER7.  The filters are based on the following models:

Total_Actuation = Actuation * AI * ActuationTimeDelay
Total_Sensing = Sensing * AA * OMCWhiteningPoles * SensingTimeDelay

These models follow directions given in LHO alog #18769.  

Actuation is model(2).par.A.total from aligocalibration/trunk/Runs/PreER7/H1/Results/DARMOLGTFs/2015-06-01_LVLNDriver_DARMOLGTF.mat.  

Sensing is model(2).par.C.total from aligocalibration/trunk/Runs/PreER7/H1/Results/DARMOLGTFs/2015-06-01_LVLNDriver_DARMOLGTF.mat.

AA is the antialiasing filter, which is model(2).par.C.antialiasing.total loaded from aligocalibration/trunk/Runs/PreER7/H1/Results/DARMOLGTFs/2015-06-01_LVLNDriver_DARMOLGTF.mat.

AI is the anti imaging filter, which is model(2).par.A.antiimaging.total loaded from aligocalibration/trunk/Runs/PreER7/H1/Results/DARMOLGTFs/2015-06-01_LVLNDriver_DARMOLGTF.mat.

OMCWhiteningPoles are the super-Nyquist-frequency poles of the OMC whitening.  This is model(2).par.C.uncompensatedomcdcpd.c from aligocalibration/trunk/Runs/PreER7/H1/Results/DARMOLGTFs/2015-06-01_LVLNDriver_DARMOLGTF.mat.

The ActuationTimeDelay is model(2).par.t.actuation from aligocalibration/trunk/Runs/PreER7/H1/Results/DARMOLGTFs/2015-06-01_LVLNDriver_DARMOLGTF.mat (in seconds), and the SensingTimeDelay is model(2).par.t.sensing + model(2).par.t.armDelay from aligocalibration/trunk/Runs/PreER7/H1/Results/DARMOLGTFs/2015-06-01_LVLNDriver_DARMOLGTF.mat in seconds.

To generate the FIR filters, run create_td_filters_ER7.m in aligocalibration/trunk/Runs/ER7/Common/MatlabTools/.  I've attached plots of the frequency response of the actuation and inverse sensing FIR filters compared to the models they are based on.  In the plots, the left column shows the FIR frequency response in blue and the original frequency model in red (magnitude on top, phase on bottom).  The right column shows the relative error in magnitude on top and the phase error in degrees on bottom.

In addition, I performed a test where I took some random DARM_CTRL and DARM_ERR data and calibrated in the time domain with the FIR filters and in the frequency domain with the original frequency models.  I've also attached a plot of the comparison between this frequency domain calibration and the time domain calibration.  

For unknown reasons, dmtviewer on the Mac Mini computers cannot get data from Livingston.

DMTviewer is used to view data produced by the DMT systems for both Livingston and Hanford observatories. It is used in the control room to display recent seismic data and inspiral range data on projector or TV monitors. The dmtviewer program may also be run on a control room workstation or operator workstation.

To display the inspiral range on a workstation:

1. Open a terminal window, type the commands shown in bold text
2. cd /ligo/home/controls/FOMs
3. kinit albert.einstein (Use your own name!)
4. (Enter your ligo.org password)
5. export DMTWEBSERVER=marble.ligo-wa.caltech.edu:443/dmtview/LHO,llodmt.ligo-la.caltech.edu/dmtview/LLO
6. dmtviewer HL-Range2.xml
7. In the DMT viewer, click on "Run" near the bottom of the display.
8. In the DMT viewer, click on the "Graphics" tab near the top of the display.
9. You can hide the option panel by clicking the small box with the left arrow directly under the "Monitors" tab.
10. When you are done using dmtviewer, you should enter the command kdestroy to dispose of your kerberos ticket.

Note: These procedures are found on the CDS Wiki. Search for "DMTviewer" and use the DMTviewer article.

Shivaraj, Marco, and I have just recently finished developing an online low-latency earthquake monitoring webpage, utilizing Michael Coughlin's seismon code, that is now available for use.

The site refreshes once every 5 minutes to get the most recent data and then calculates the P/S wave arrival times at each site (llo, lho, geo, virgo), amplitude (velocity induced on accelerometers), source magnitude, source time, distance, and lat/lon. The webpage can also be used as an early warning system and indicates the likelihood of appreciable seismic disturbance at each observatory. This is determined by a set threshold amplitude using previous studies done by Michael Coughlin over initial LIGO data. The link to this page is provided below.

https://ldas-jobs.ligo.caltech.edu/~hunter.gabbard/earthquake_mon/seismic.html

SVN up /ligo/svncommon/SusSVN/sus/trunk/QUAD/Common/MatlabTools/QuadModel_Production.

I updated the quad model with the measured ETMY violin modes for harmonics 1 to 7.  I got these values from 17610, 17365, 18764, and 18614.

Mode 4 is a bit of a guess because the measured values I saw are not identified by suspension. But ETMY is the highest for the other modes I was able to compare, so I chose the highest I saw in that range. I averaged the numbers where different values are posted for each fiber. The model doesn’t yet account for different frequencies in different fibers (but I can add this if we need to).

Hopefully this helps clear up some discrepancies between the modeled and measured loop gain seen on page 2 of https://alog.ligo-wa.caltech.edu/aLOG/uploads/18769_20150602030143_2015-06-01_LVLNDriver_H1DARMOLGTF.pdf

Got the IFO to lock at high power (@ 23W) for about 3 minutes before Lockloss. Winds are in the high teens to low 20MPH. Will bring the IFO to DC-Readout and then adjust the power up manually.  

07:53 Christina opening OSB receiving rollup door
08:00 Peter to H2 PSL enclosure (WP 5233)
08:00 Karen and Christina to mid and end stations to clean
08:08 Jodi moving 3 boxes of TCS equipment in LVEA
08:12 Richard to end X to replace wireless router (WP 5236)
08:26 Bubba checking on RO alarm, then replacing nitrogen regulators on LTS containers in LVEA (WP 5238)
08:31 Jodi back
08:31 Richard called from end X to test phone
08:39 Jodi to mid X to look for mirror
08:43 Joe to LVEA to flush eyewash stations, put water in lift trucks, etc.
08:49 Filiberto to end Y to test cabling (WP 5103)
08:52 Peter done
08:58 Richard back
09:01 Jodi back
09:05 Jodi, Nutsinee to LVEA to get viewport guards
09:18 Karen, Christina leaving end Y, going to mid X then end X.
09:25 Jodi and Nutsinee back
09:39 Kyle to end Y to turn RGA bakeout on, then end X to run up turbo (WP 5237)
09:40 Mitchel going to mid and end stations (not VEAs) to get serial numbers
09:40 Joe back
      Jim B., Dave pulling fibers under floor tiles
09:55 Karen and Christina leaving mid X, going to end X
09:56 Hugh checking HEPI fluid reservior levels
09:58 Filiberto back
10:06 Bubba back
10:08 Nutsinee and Rick taking pictures of ETMX (WP 5240)
10:20 Joe back to continue previous work in LVEA
10:26 Dave updating h1calcs model (WP 5241)
10:26 Bubba pulling tubing for TMDS
10:27 Karen and Christina leaving end X
10:36 Jim B. done with floor tiles
10:50 Dave, Jeff K. restarting h1sush34 IO chassis for 18 bit dac recalibration
10:59 Joe back
11:09 Hugh back
11:10 Nutsinee and Rick done
11:25 Karen and Christina to LVEA to clean
11:26 Jeff K. restarting h1calcs model
11:32 Kingsoft water through gate, notified Bubba (WP 5239)
11:35 Mitchell back
11:37 Restart of guardian machine
11:54 Karen and Christina out of LVEA, opening OSB receiving rollup door to empty cardboard container
12:10 Pepsi truck through gate
13:28 Kyle done

Karen and Christina report that the phone is not working at mid Y.
Kyle reports that a set of cables is pushed against a pyramid shaped pier at end Y.

Cheryl, Evan, Kiwamu, Patrick, Sheila
Had trouble running through an initial alignment after maintenance. It turned out that the safe.snap files used for h1sush34 had the gains set to 0 for the inputs to MC2 and PR2. We changed these back to 1 by hand. The safe.snap files will need to be fixed.
Sheila enabled optical lever DC alignment feedback on SR3. (alog 18777)
We had trouble getting past the RESONANCE state. We stopped in the CARM_5PM state and Cheryl adjusted the alignment of one of the power recycling mirrors. After this we were able to lock twice on LSC_FF.

This is work I completed a while ago (the 7th of May if Matlab is to be believed), but I wanted to put this in for comparison with my log 18453. These are the new (as of May 7th) and old isolation filters for ETMY. ETM's are definitely harder to do that ITM's, but loops should be very similar now on all BSC chambers