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.

After today's reboot of h1guardian0, its load averages are staying in the 6-7 range. We'll see if it ratchets back up as it has done in the past month (see plot).

Duncan, Dave

I installed Duncan's latest version of cal/common/scripts/ext_alert.py and started running it as user controls on h1fescript0 at 15:36PDT.  It has been running for an hour so far with no problems, and correclty reported the FERMI GRB event from 20:09UTC (13:09PDT).

You can view the GRB information in the "Latest astrophysical event alert" section of the CAL_INJ_CONTROL MEDM screen, accessible from the SITEMAP via the corner station CAL pull down, "HWINJ CTRL" option.

All of the SDF monitors are now cleared (show no diffs) except the SUS SR3.  As stated in alog 18777 SR3 has optical lever feedback enabled for stability purposes.  Since this is new we will keep it on the DIFF list until it proves itself helpful.  See attached for snapshot of the 2 OK DIFFs on SR3.  OPS will need to open the TABLE in order to see that these 2 DIFFs are the same as the snapshot, and no more, no less.

During the cleaning house, we also updated the comparison snap files on SDFs of the following since there were models/database changes made over the last month+:

IOPSUSEX

IOPSUSEY

IOPSEIH16

OMC

OAF

SudarshanK, DarkhanT

To keep the things similar between LHO and LLO for ER7, the displacement calibration coefficient (volt to meter conversion factor) on Pcal main read out channels TX_PD _OUT and RX_PD_OUT are switched off. The calibration coeffcient for each channel, if needed, can be found at DCC #1500252. These channels will be recorded to the frames in volts for now. 

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

Dave created a dummy target area where I stuck an autoBurt.req file which will start capturing all of the SUS alignment offsets on the auto-hourly basis.  This will aid in realignment after a Tuesday set of reboots.  (Recall, the reboots usually preceed a burt restore which often houses old alignment offset values.  - And the age of each restore file is different so the alignment settings are from a variety of alignments, not a matched set.  Therefore, we have been having to perform major realignments after Tues maintance, such as today.)

In the future - find and restore the latest locked good alignment from the hourly backups in:

/ligo/cds/lho/h1/burt/2015

under the appropriate date /h1ifoalignepics.snap

For ASC modelers, here are screenshots of our matrices in full lock.  

Nutsinee, Pat Meyers, Marissa

In the recent LHO locks, we've noticed a line in DARM that wanders around between ~410-420 Hz, consistently appearing in every lock from May 13th to the present. For example, here is a spectrogram of 2 hours from May 15.

There is a peak around that frequency in the Rayleigh plot (This plot shows the standard deviation of the PSD divided by the mean in each frequency bin. For a random Poisson-distributed signal, this ratio should be one.) For example, the Rayleigh plot from May 15 shows this peak, and going back through the summary pages, this non-stationarity in the spectrum appears to have been there since May 13.

Looking further back, we saw that there was a wandering line around the same frequency in the March 27th lock, but its frequency drifted much more slowly; see this 2 hour spectrogram.  

Pat has used STAMP-PEM to look for coherence with other channels but hasn't found any obvious culprit. We've also made spectrograms of many other channels, including MICH, PRCL, and SRCL, which don't show the same line.

Nutsinee also did some follow-up to see if this was the same as the "seismic bumbling line" from ETMX (see alog 17681), but found that it is quite different. For example, compare the DARM spectrogram with this 2 hour ETMX spectrogram from May 15 (at the same time as the spectrogram shown above for DARM). At this time, the seismic line wanders between 200 and 240 Hz, with no obvious correlations with the DARM wandering line.

J. Kissel, J. Betzwieser

Joe had uncovered a particularly nasty bug in the wiring of the CAL-CS front end model's reproduction of the digital actuation chain in the SUS (see LHO aLOG 18465). He's committed a bug fix, I've svn up'd and recompiled, reinstalled, restarted, and restored the front end code with the new fix.

Details:
--------
As you know, in the suspensions, one has the ability to choose between a distributed and offloaded hierarchy for the actuation. In the CAL-CS model, a stripped-down, longitudinal-only version of this hierarchy option has been installed such that we can exactly replicate what's been installed in the actual SUS hierarchy for the DARM / DELTA L calibration. As Joe says,
"At some point the tag coming from the LOCK_L3 output (shown in magenta) and the L3_ISCINF output (shown in orange) had been switched"
which causes indescribably confusing things to happen with the hierarchical control (at least not without a serious exercise in loop math). The two attachments show the before and after.

Yikes! Good catch Joe!

To run timing slaves in the EE shop, a fiber was pulled from port 8 on the MSR timing master to EE.