All times in UTC

15:00 It Seems the NPRO trippedhttps://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=19141. GRB alert/alarm is sounding so I'm getting my first look at where thing are regarding this. LASER is back up and Peter i working on getting it back into nominal operating condition. End Station LASER status is BUILDING SAFE for vent work. This means all viewports are secured, ISC tables are locked and safety signs have been transitioned.

15:31 Cleaning crew done second cleaning at EX and goin to EY

15:44 Peter to Transistion the LVEA to LASER SAFE

15:46 Turned of both CO2 LASERS.

15:57 Gary ad Danny to EX

16:00 LVEA transitioned to LASER SAFE.

16:02 Picomotors disabled at EX, EY and HAM6

16:09 Bartlett to cleaning area.

16:25 Bartlett came out and went back in to prepare HAM6 area for Vent

16:26 Cleaning crew done with second cleaning at EX.

16:33 ISS is stable now and the REFSIGNAL is set to -2.12 for 6.5% AOM diff power

16:36 GV20 (EX) closed. (not sure what time). Gary and Danny to EY to meet Kyle. GV18 Not closed yet.

16:57 Closed Green Beam ISC table shutters

17:15 Arnaud testing a script to test  MC1 suspensinon actuators

17:22 Danny and Travis at EX

18:00 Betsy, Travis, Danny and Gary to EY

18:06 Bartlett to EY

18:10 Karen and Christina into LVEA for cleaning

18:14 J Worden and co. dropping a ditch digger of at the turnaround next to VPW.

18:21 Jeff leaving EY

18:24 Ditch machine dropped off and Truck is moving to MX to pick up a scissor lift

18:28 Gary and Danny back from EY

18:46 Betsy and Travis back from EY

18:48 Hugh back from EX

18:57 GV18(EY) closed

19:12 Corey into LVEA

19:15 Betsy into the LVEA w Bay

19:30 Betsy out nd going to EX

19:38 Sheila informed me of a not so distant DAQ restart.

20:00 Danny and Travis to EY

20:16 Jim is at EX and garbing. He will lock the ISI in about 20-30 min.

20:44 Keita, Kiwamu and Corey to EX to start TMS investigation.

21:03 DAQ restart

21:15 Kate and Calum on site. They will be here for a couple of weeks.

22:18 Hugh into the LVEA to install 2 STS2 seismometers in the BG

22:32 Hugh out of the LVEA

22:42 Betsy out to HAM6 to have a look

Generated Xilinx iMPACT configuration archives (.iaf) for most recent timing firmware and uploaded them to the DCC pages corresponding to their respective device firmware:

1PPS Locking Firmware:
https://dcc.ligo.org/LIGO-E1200033

Comparator Firmware:
https://dcc.ligo.org/LIGO-E1200034

IRIG-B Firmware:
https://dcc.ligo.org/LIGO-E1200035

DuoTone Firmware:
https://dcc.ligo.org/LIGO-E1200036

The links for these .iaf files on the FPGA code page of the Timing Wiki (https://awiki.ligo-wa.caltech.edu/aLIGO/TimingFpgaCode) are now functioning.

To correct problems with the Simulink web view of models (accessible from https://lhocds.ligo-wa.caltech.edu/simulink/) several models have been changed to be saved at the top level of the model.  If this isn't done, the top level of the model is not generated for the web view.  The models which were changed are:

h1iscex
h1iscey
h1isietmx
h1pemcs
h1pemex
h1pemey
h1pemmx
h1pemmy
h1susauxb123
h1susauxh34
h1susetmx
h1susim

There are still a few models that need to be changed.  

Attached is a noise budget for the DARM spectrum from 2015-06-07 00:00:00Z–02:00:00Z. Notes:

• This spectrum was for 24 W, with SRC WFS retuned and the EX ESD off (LHO#18923 et seq.).
• The quantum noise level is retuned using the null stream (LHO#19077).
• Since the last noise budget, MICH FF was retuned (LHO#18878). SRCL FF is still off.
• MICH, SRCL, and frequency noise coupling TFs were retaken on 2015-06-14 in a similar configuration. Since the interferometer calibration was off, I measured the couplings into OMC sum and then undid the DARM loop and optical gain in order to get a freerunning DARM estimate.
• The intensity noise coupling TF was not retaken. However, from Gabriele's bruco projections around the same time (LHO#18935), it seems like the intensity coupling in the bucket is roughly consistent with what is shown here.
• At high frequencies, I think the frequency noise coupling TF taken on the 14th is somehow underestimating the true coupling on the 7th. The coherence from that time (LHO#18924) seems to support the idea that almost all of the DARM noise above 6 kHz is frequency noise. Either the coupling changed, or perhaps I have not undone the high-frequency response of the OMC sum channel correctly.
• From 10 to 15 Hz, I think the MICH and SRCL projections are suffering from some noise in the coupling TF measurements. From Sheila's entry yesterday (LHO#19139) we can already see that most of the DARM noise here is A2L coupling.

Conclusions:

• In the bucket, we are limited by intensity noise from 120 to 400 Hz. From 60 to 120 Hz, there is still some other broadband noise that is limiting us.
• We are limited by SRCL noise around 50 Hz, but we knew that already and we are already trying feedforward (LHO#19139).
• Above a few kilohertz (and maybe already above 2 kHz), we have a nontrivial amount of frequency noise.

Restarted the data concentrator because of changes to the h1asc and h1oaf models.

model restarts logged for Sun 14/Jun/2015
2015_06_14 00:04 h1fw1*
2015_06_14 15:31 h1fw1*

* = unintentional restart. Last day of ER7.

Have locked HEPI at X End.

The rotational DOFs are within ~100nrads of the closed loop running position.  The Translational DOFs were let go as the Rots were dialed in:  X -5um, Y +67um, Z +108um.  These are the deltas from the nominally servo'd position.

The PSL is back up. PMC is locked @ 23.2W w/2.4W in refl. This is slightly over the 10% that is consideredthe high range of optimal.

The ISS is stabilized at 7.2%diffracted power.

The FSS TPD is showing 1.34V

Frontened watchdog not reset (RED) output power @ HPO is 28.9W

HPO  (not used) watchdog is RED.

 ISS is stable now and the REFSIGNAL is set to -2.12 for 6.5% AOM diff power

Visitors: Arnaud, Katie (SURF student), Ivan (STAR program) Gary T. and Danny S., Stefan from Columbia U(timing system), Curtis Rau (SURF Student)

SEI: General maintanance. Also supporting the Vent activities.

VAC: Kyle preparing for End Station vents. Doors should be off by this afternoon. ALS LASERS will need to be turned off.

SUS: Danny S and Gary T on site to assist with discharging tests masses and working on EX pitch issues.

FAC: Clean Rooms and Dust Monitors are running - second cleaning of End Sytations in progress. Beam Tube cleaning is on ongoing.

I think that's it?

This is a minor update to those discussed in log 18987. In addition to importing live damping filters from the sites into the model (with a 5 min delay), you can now request damping filters from a specific gps time. So svn up ../SusSVN/sus/trunk/QUAD/Common/MatlabTools/QuadModel_Production.

The requirements are the same for reading live damping filters: you must have nds2 and various corners of the noise budget svn on your computer. See the notes at the bottom of this log.

The model script, generate_QUAD_Model_Production, has instructions on how to run the model with all the various features. An example of generating a model with damping filters from a specific gps time is show here:

quadModel = generate_QUAD_Model_Production(frequency_vector,'h1etmy',[],0,true,'gps1118413940h1etmy',0,0,true,8);

* frequency_vector is some frequency vector you specify.

* 'h1etmy' is the customized H1 ETMY parameter file ('quadopt_fiber' is the general quad file). All other quads have parameter files now too, but h1etmy is the only unique one at this point.

* true (the first one) says you want damping

* 'gps1118413940h1etmy' says you want the damping filters from H1 ETMY that were running at gps time 1118413940. The 'gps' prefix is what triggers the flag to read from the given gps time.

* true (the second one) says you want violin modes

* 8 says you want the first 8 violin modes in the model (2 is the default if not specified)

I am not sure how this does foton file version control when reading the filters. It claims it is loading the foton file from the given gps time, but for all I know it is actually loading the current foton file and simply displaying the gps time you gave it. One of the noise budget experts may know more about this (the site filter reading code is adapted from the noise budget stuff, courtesy of Chris Wipf).

In general, let me know if any of these new feature do not work properly, or should be modified in any way. They have been tested on my laptop, but there could be something I have missed.

The generate script has instructions for setting up your computer to get the running damping filters from the sites (either live or from a gps time). This text is copied here:

> Follow noise budget SVN checkout instructions here

https://awiki.ligo-wa.caltech.edu/aLIGO/NoiseBudget

Checkout the following addpath paths:

svnDir = '../NbSVN/aligonoisebudget/trunk/'   (the '..' must be the same as for the SusSVN, e.g. /ligo/svncommon/)    

addpath(genpath([svnDir 'Externals/SimulinkNb/']))

addpath([svnDir 'Common/Utils/NoiseModel/'])

addpath([svnDir 'Common/Utils/'])

> Follow NDS2 install instructions here

https://wiki.ligo.org/viewauth/RemoteAccess

Matlab should be pointed to this version of liveparts.m:

../NbSVN/aligonoisebudget/trunk/Externals/SimulinkNb/SimulinkNb/liveParts.m

Came into the control room this morning to find that the laser had tripped.  Went to
see the Beckhoff PC and the status indicator showed "Power error (WD)" illuminated.
Not sure what caused the the reduction in power.  I do know that this morning the
lights in my office flickered a couple of times, which may or may not coincide with
the laser's power demise.  We will check the UPS log and see if it registered a switch
to batteries or something like that.

Scott L. Ed P.

6/11/15
Cleaned 43 meters ending 16.7 meters north of HNW-4-072.

6/12/15
Cleaned 30 meters ending 6.8 meters north of HNW-074.
Cleaning progress has slowed as we are trying to make as little noise as possible during ER-7.

Sheila, Dan, Evan

ETMY ring heater on, operating at 22 Watts input power

I turned on the ETMY ring heater with the same settings as the ETMX one, 0.5 Watts on the top and bottom.  Since then we've been locking with 22 Watts, we haven't had any long stretches but that is probably because of other activities.  

A2L tuning for test masses L2

I injected an excitation at 12 Hz into L2 of each test mass pitch and yaw, and tuned the A2L coefficents until the coupling became bilinear.  The gains that I ended up with are shown in the attached screenshots.  I also chanmged the ramp times on all of these filter modules and accepted all of these changes into SDF.  The gains may need to be retuned in the future but they seemed to stay stable over several locks today.  Screenshot attached. 

ETMX roll mode could be damped with AS 45Q Yaw

With the improvement in the sensitivity below 20 Hz, the ETMX roll mode was again more than an order of magnitude above the DARM noise floor.  We cannot improve anymore by increasing the damping gain using the AS 45Q pitch signals, the mode is now in the noise of those signals.  However, the AS 45Q YAW signals both see this mode with an SNR of better than 100.  Durring the vent we can expand the matrix used to send ASC signals to the suspensions so that we can try using YAW.  

SRCL FF

With the reduced noise from A2L the coherence with SRCL increased, so I made another attempt at SRCL FF.  Evan called and told me about a filter that he made last night, which is intended for use in feeding SRCL to ITMY L2.  I used this filter, and found that with a gain of -0.5 this works well. The second attached screenshot shows the coupling from SRCL out to DARM IN with no feedforward, and with the feedforward engaged.  The coupling is reduced by 6dB at 20 Hz, and more at ghier frequencies although the measurement lost coherence.  The last attached spectrum shows the sensitivity improvement due to both A2L and SRCL FF.  The calibration may be off here because the ESD drive strength changed.

The bad news is that we seem to loose lock a few minutes after engaging this feedforward, and we are having a good deal of difficulty relocking today. 

New nominal state for guardian,

I added a new state to the gaurdian, which does nothing other than check for lock.  It is called NOMINAL_LOW_NOISE, the index is 600, and I hope that we can add any additional states before it from now on, to minimize confusion.  Also, it is handy to have a state which does nothing.  

No inital alingment needed for 24 hours.

I came in this morning to find the IFO still locked, it had been locked for nearly 12 hours.  After it dropped lock (probably my fault) I didn't do any inital alingment, and I haven't done it since, so the alignment has not been done for about 20 hours now and things seem OK.  I think that over the engineering run we were probably doing inital alingment much more often than necessary, it would be good to keep track of how often we really need to do it.  

Locklosses in switching to DC readout

 We've had several TR_CARM locklosses and a new type of lockloss that seems to have shown up in the last 2 days, durring the switch over to DC readout. Dan and I commented out the DARM boost that gets tured on as the first thing in the DC_READOUT state of the ISC_LOCK guardian, we are engaging it by hand after the transition for now.  unclear...

1315 hrs. local -> Leaving site now

J. Kissel, T. Sadecki, D. Hoak, E. Merilh

As a last ditch effort to be able to recocile the calibration for the rest of the run, given the drastic change to the ETMY ESD, I've completed a DARM OLGTF, and also tuned and completed a PCAL EX to DARM transfer function. I got halfway through the same transfer function using PCAL EY, but the lock broke from some sort of seismic disturbance. The interferometer was at 17 [W] requested input power for all of the below measurements, I attach the relevant digital parameters that are relevant (sadly the list is growing! as so many things are changing!).

Analysis to come, but the measurements have been committed to the CalSVN repo here:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER7/H1/Measurements/DARMOLGTFs
2015-06-13_H1_DARM_OLGTF_LHOaLOG19128_ETMYL3LPOFF.xml

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER7/H1/Measurements/PCAL_TRENDS
2015-06-13_H1PCALEX_2_DARM.xml
2015-06-13_H1PCALEX_2_DARM_stronger.xml

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER7/H1/Measurements/PCAL_TRENDS
2015-06-13_H1PCALEY_2_DARM_stronger.xml

For the PCAL sweeps, I've modified the following settings from what Sudarshan had set up (2015-06-12_pcal_sweep_X.xml in the same folder) such that (a) the measurement would complete in a reasonable amount of time, (b) we'd get coherence over the entire band of measurement, and (c) that the frequency vector would match the DARM OLGTF:
- Changed the frequency range to 5 to 5000 [kHz]
- Changed the frequency vector from linear to logarithmic
- Changed the user-defined amplitude format to Envelope
- Increased the number of cycles to 25
- Increased the duration of a cycle to 1 [sec]
- Increase the drive strength in various frequency bands where there remained no coherence