Andy, Josh, Dan, 

We found (using the script described in 17791 and 18588) that some of the COMM channels (LSC-Y_COMM_CTRL_OUTPUT, LSC-X_COMM_CTRL_OUTPUT) used for tidal offload from the IMC were hitting their limits during some of the recent H1 locks. The attachments show: 

1) LSC-Y_COMM_CTRL_OUTPUT and LSC-X_COMM_CTRL_OUTPUT at the end of the first short observation intent time from the summary page today. Note, they are saturating at 10 um for this whole lock. 

2) Same channels for the end of the next lock, COMM tidal is not saturating during this lock. 

3) IMC-F during the lock when COMM tidal is saturating, note it is running away to very high values. 

4) IMC-F for the second lock, when COMM tidal isn't saturating.

Additionally, we see some additional noise during the first lock where COMM was saturated, and at those times DARM coherence with MCL, PRCL, and SRCL also increases. This may or may not be caused by the saturation, but we thought it worth reporting. 

5) Spectrogram of DARM during first lock. 

6) Coherence-o-gram of DARM vs MCL (note: a followup spectrogram indicates MCL got much noisier at the time with higher coherence) during first lock. 

Side note: We also saw ISI-GND_BRS_ETMX_RY_OUTPUT going between its limits, but Jeff says this is an out of loop tilt sensor, so we'll ignore it. 

I have been setting the observation bit to undisturbed even though the range is incorrect.

The calibration of DRMI (PRCL, SRCL and MICH in um, alog 14067) has been entirely moved to the CAL-CS model from the OAF model (alog 16698). In addition, I updated the optical gains so that they are accurate in full lock.

For those who remotely access the DRMI spectra, here are the channels that you can look at:

• MICH/PRCL/SRCL unsuppressed displacement in um: H1:CAL-CS_MICH(or PRCL, SRCL)_DQ
• MICH/PRCL/SRCL suppressed error signal in um: H1:CAL-CS_MICH(or PRCL, SRCL)_ERR_DQ
• MICH/PRCL/SRC feedback signal in um: H1:CAL-CS_MICH(or PRCL, SRCL)_CTRL_DQ

Also, be careful that all these channels have digital whitenings for preseving numerical precision and therefore need anti-whitening using zpk( [100; 100], [1,1], 1) for real data analysis.

The scripts to estimate the optical gains and compare the models with some measurements can be found in the calibration svn:

aligocalibration/trunk/Runs/PreER7/H1/Scripts/lsc

The scripts are named as:

• H1MICH_OLTFmode_20150517l.m
• H1PRCL_OLTFmodel_20150517.m
• H1SRCL_OLTFmodel_20150517.m

To estimate the optical gains, I used the data from 2015-May-14th that Evan measured for me (alog 18487) in full lock.

BTW, since the OAF model is still running, one can still get some data out of it. The calibration in OAF have not been maintained at all and therefroe the calibration must be wrong.

Here are some plots for entertainment purpose:

Note that the MICH open loop measurement deviated from the model at high frequencies above 60 Hz or so. Not sure why.

VAC:
Tuesday:
Routing steel tubing at end stations for TMDS
Run up turbo to replace gauge at end station

FAC:
Membranes for RO are on order, may be replaced Tuesday

In the first observation intent time from today, there are DAC glitches in MC2 M3. They don't obviously appear in DARM at the time we checked, but they do appear in a number of channels. The first plot is an Omega scan showing glitches in MC_L, and the second shows that they correspond to zero crossings in MC2 M3 control.

Observation Bit: Commissioning 

16:07 Realign after Lockloss
18:10 Dick G. - Going into Optics Lab
19:20 Dick G. – Out of Optics Lab
20:10 IFO locked at LSC_FF
20:15 Observation bit set to Undisturbed
20:36 Lockloss Reason unknown
21:45 IFO locked at LSC_FF
21:50 Observation bit set to Undisturbed
22:03 Adjust ISS diffracted power from 12% to 8%
22:17 Lockloss – Reason unknown
22:21 Re-Start initial alignment after Lockloss
22:40 Complete initial alignment
22:43 Start Guardian locking
23:14 Lockloss – restart locking process
23:55 Lockloss at Engage_ASC
00:00 Due to problems locking left IFO in a down state. 

   Very difficult to do initial alignment and to get the IFO to lock. There was a large amount of activity in the 1 -3Hz and 3 - 10Hz seismic ranges and several periods of higher winds (upper 30 mph and mid 20 mph). Large ring up in Bounce and Roll modes each time reached Engage_ASC stage. Limited success in suppressing these.     

All times are Pacific Standard Time:

All locks are at 24W LASER Power:

Tried to reset the R0 water pump twice. No luck. It will remain off until Bubba can look at it on Monday morning.

IFO wasn't re-aligned all day. AS Air image had a bit of a bulge to it. It didn't seem to matter...much.

07:30 in a bit early. I was up. Why not?

07:31 Dan on site from last night. Looks like we had a nice 6-7 hour lock. Bounce, Roll and violin modes have been mercilessly beaten down to almost nothing and Dan sauys this is now the status quo.  NICE!

08:17 IFO re-locked. Dan and I re-tweaked some bounce mode filters and did some dithering alignment to the OMC Intent bit set to undisturbed.

09:03 Jeff Kissel on site.

09:08 OIB set to comissioning

09:10  Jeff increasing DARM gain. (was too low)

09:24 OIB set to UNDISTURBED

10:25 Dan went home. He reduced the OMC dither gain in Guardian before he left because he noted that it was pushing a bit to hard on the mass. 

10:30 went out to try and reset the RO pump. no luck.

10:35 Jeff noted that a small plane flew overhead.

11:02 Bubba called in about the RO pump status. The alarm is NOT ringing in the control room and he said the pump can stay off the rest of the day and he'll look at it tomorrow. Unless it becomes a nuisance ro we run out of potable water..don't worry about it.

11:54 Jeff went home. I'm singular.

12:00 ripples showing up on strip tool, probablty as a result of the 5.0 mag quake that struck the Aleutians at 18:07:45UTC? ( i don't think the timing is coincidental enough)

12:10 Got some SRM vocalizations, AS Air cam got a bit jittery but she's holding steady as a rock!(famous last words?)

12:50 HPI-PUMP_EX_DIFF_PRESSURE alarmed (Yellow).

13:39 both ITM oplevs and the BS oplev are showing oscillations in Pitch ~15min prior and also starting to wander up and down.

13:42 Lockloss. OIB auto-switched off.

13:56 Re-locked @ DC readout 

14:10 Set the gain on ETMX_M0_DARM_DAMP_R to 200 to improve roll mode after lock settled awhile. Turned on DHARD_P filter 9 (:12^2) because Dan told me that it was a good idea. No Dither align on OMC this lock.

14:14 OIB set to UNDISTURBED

14:40 Oplevs starting to show "ringing" . This time it seems to be ETMY being the biggest offender with ITMY and ITMX tied for second place. The BS doesn't seem to be involved in this heat.

14:54 Lockloss

15:10 Re-locked. Adjusted/Engaged filters as before except turned gain on ETMX_M0_DARM_DAMP_R up to 500. I intitially set the gain at 300( then changed it to 500 after the intent bit was set) I then turned on dither alignment to OMC @ .07 master gain. Range about 58Mpc.

15:59  ETMY oplev showing large oscillation again. Lockloss. All yours Jeff. 

Tonight I worked on (re)commissioning the OMC alignment dither and measuring the AS power as a function of DARM offset.

OMC Alignment Dither

Since (re)commissioning the OMC ASC dither last month, the yaw loop had become unstable.  In case this becomes a persistent problem, I've written a script that will measure the dither sensing matrix, invert, and loads the resulting control matrix into the appropriate fields in the DACTMAT matrix.  (Not sure what DACTMAT means...I would have called it DITHER2DOF.)  The script is here (I have committed it to the svn):

~userapps/release/omc/common/scripts/ditherDCsense.py

The script inserts DC offsets into the OMC ASC loops and measures the response in the dither error signals.  It's gentle enough that it can be run in DC readout without breaking the lock.  Using the script I recalculated the dither control matrix and turned the dither loops back on; a screenshot of the new control matrix is attached.  They work, but I recommend very low gain - 0.05 on the OMC ASC master slider.  This reduces the UGF of the loops enough that noise is not being injected into the OMC alignment; with the gain too high there is clear scattering noise at low frequencies.  Enabling the dither gave the range a 1-2Mpc boost.  For now this is not in the Guardian, but we should start using the dither alignment.

If you use the script, keep an eye on the OMC SUS and make sure the offsets to the ASC loops don't saturate the drive.  If this happens your matrix will have a problem and you will not go to dither today.

Interestingly, the optimal alignment on the QPDs is different in the 2.3W and 23W states.  Is this due to some junk light in the DRMI?  For now I have left the QPD offsets to have the optimal low-power alignment, assuming that the dither will be engaged later on.  At high power the dither alignment pushes the OMC in pitch such that the outputs to the DAC are ~90k counts.  This seems like a lot to me, and we can't offload the drive anywhere, except perhaps some pico-motoring on the AS WFS to make the tip-tilts point the beam at a charitable angle.  We need to work out a HAM6 centering scheme that doesn't use the OMC SUS.

DARM Offset Scan

With the alignment into the OMC optimized I scanned the DARM offset at 2.3W input power and measured the DCPD Sum.  Plot attached; the curve is very well fit by a quadratic with a small static offset from the origin, about the same magnitude that Stefan, Keita and I observed two weeks ago - a few tenths of a picometer.  So, no surprises.  Note, the data points in the plot have error bars representing the 1-sigma statistical noise in the measurement, but they are too small to see.

In the second plot attached I have scaled the data to 125W input power, to make a comparison with Fig. 7 of the LSC design document (T1000298).  From this simple scaling it looks as though the DARM resonance we observe is much narrower than in T1000298...but I think I'm forgetting what parameters are assumed in Fig 7.  There was an error in my plotting - the data are a reasonable match to Fig 7 if a factor of 125/1.84 is applied to the DCPDSum, where 1.84 is the power incident on the PRM with 2.3W into the IMC.  (Note on this log-scale plot you can see the slight assymmetry in the data points, indicating a static DARM offset.)  Our standard low-noise, high-power configuration is 23W, and an offset of 1e-5 counts, which we think is 14pm.  With these settings we get ~18mA in DCPD Sum.

Other Notes

Tonight I've been increasing the ETMX roll mode damping gain to 200.  Also I've been engaging the DHARD rolloff filter (:12^2), this seems to improve the noise around 20Hz.

There is a very narrow line at exactly 3801Hz that I haven't seen before.  There's no sign of aliasing - the high-frequency features in DARM, as measured by the 64kHz DCPD channels from the DAC, have not changed dramatically.  The line has been slowly growing all night.  This could be an 8th harmonic violin mode of ETMY, although the exact integer frequency is a little suspicious.  I have added another notch to the ETMY_L3_LOCK filter bank, vStop8+9, but I have not turned it on.

J. Kissel

I've taken a DARM Open Loop Gain TF for this lock stretch (after adjusting the DARM gain to match prior measurements). I'm going to start processing the past several DARM OLGTFs (see LHO aLOGs 18662, and 18709), including this one, using our new precise knowledge of the actuation scale factor (see LHO aLOGs 18711 and 18718).

Since this is a DARM OLGTF with a new low noise ESD driver (though without the LP filter engaged), and the new hierarchical control scheme involving all three lower stages of ETMY, I figure I'd over-document it. Attached is a conlog and screen shot of the MEDMs for all the relevant digital filter banks and Binary IO Control involved in the DARM loop for this kind of lock stretch.

Stay tuned!

This darm OLGTF has been committed to the CalSVN under 
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER7/H1/Measurements/DARMOLGTFs/2015-05-31_H1_DARM_OLGTF_LHOaLOG18733_ETMYL3LPOFF.xml

model restarts logged for Sat 30/May/2015

no restarts reported.

Evening Shift Summary
LVEA: Laser Hazard
Observation Bit: Commissioning 

16:00 Re-locking the IFO after several earthquakes 
16:45 Dale – Locking the LSB and leaving
17:00 Kiwamu - Damping the bounce and roll modes before full locking
18:35 Jeff – Running PCal TFs 
18:35 CS_WS_RO – alarm
18:40 – Bounce and roll modes low enough to try full locking
18:42 - Lost lock - Guardian recovering IFO
19:00 – Reset RO system
19:20 – IFO bounce & Roll modes low enough to try relocking
21:23 CS_WS_RO alarm – Will leave down for rest of the night
21:51 Jeff – Finished running TFs
21:52 Evan – Take IFO to 24.2w
22:00 Lost lock – Guardian recovering IFO
22:14 IFO locked at 24.2w
22:19 Lost lock – Guardian recovering IFO
22:36 IFO locked at 24.2w
22:42 Jeff - Turned down continuous wave injection by factor of 10
23:28 Set intent bit to Undistributed

Got alarm on CS RO system.
Bubba talked me through a system reset. 
CS RO system is back up and running. 

To Reset RO System:

1). The RO system is located in the "water room", (through door to the right) in the Carpenter's shop
2). The RO Panel (OSMO 23G) is to the left just inside the door to the water room
3). Press the "mute" button to silence the alarm
4). Press the "Off" button to shutdown the RO system
5). Press the "On" button to restart the RO system
6). When the RO transfer pump starts - the pressure gauge should be reading around 58psi

   The RO transfer pump is a red vertical pump on the floor half way down the back wall.  
    

J. Kissel, K. Kizumi, S. Karki

While trying to commit our results from last night to the CalSVN, we discovered that every folder was complaining that the it was not a working copy of svn, e.g.:

jeffrey.kissel@opsws5:/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER7/H1/Scripts$ svn st
svn: warning: '.' is not a working copy

Totally confused, we went to the trunk of the repo, and it said messages about discrepant svn client versions:

/ligo/svncommon/CalSVN/aligocalibration$ svn st
svn: The path '.' appears to be part of a Subversion 1.7 or greater
working copy.  Please upgrade your Subversion client to use this
working copy.


In order to make progress on the work stations (i.e. the h1boot server) Kiwamu made a back of the repo into 
/ligo/svncommon/CalSVN/aligocalibration_backup_20150530/
and made a fresh checkout of the repo, in the normal path:
/ligo/svncommon/CalSVN/aligocalibration
which regained its normal functionality.

He then started digging around the log history to figure out what happened and found a bunch of commits from the LHO PCAL team yesterday evening... and then Sudarshan joined us for a happy (??) Saturday discovery.

We've diagnosed the problem (a totally innocent user just doing what the computer told him to do -- he should not be blamed for any of this!!):
Sudarshan was at the End Station trying to check in pictures of PCal camera on (new? old?) CDS Laptop called cdsmbp0. He tried to do an svn st just to check on things, and an svn update before he committed (very good!), but he got the following error message:
[controls@cdsmbp0 Measurements]$ svn st
svn: E155036: Please see the 'svn upgrade' command
svn: E155036 Working copy '/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER7/H1/Measurements' is too old (format 10, created by Subversion 1.6)
[controls@cdsmbp0 Measurements]$ svn update
svn: E155036: Please see the 'svn upgrade' command
svn: E155036 Working copy '/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER7/H1/Measurements' is too old (format 10, created by Subversion 1.6)

He obediently then followed the instructions:
[controls@cdsmbp0 Measurements]$ svn upgrade
svn: E155019: Can't upgrade '/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER7/H1/Measurements' as it is not a pre-1.7 working copy root, the  root is '/ligo/svncommon/CalSVN/aligocalibration'
[controls@cdsmbp0 Measurements]$ cd ../../../
[controls@cdsmbp0 Runs]$ cd ../../
[controls@cdsmbp0 aligocalibration]$ ls
branches tages trunk
[controls@cdsmbp0 aligocalibration]$ svn upgrade
Upgraded '.'
Upgraded 'trunk'
Upgraded 'trunk/Runs/'
#etc
#etc
#HERE'S A CRAZY BIT
Upgraded 'trunk/Runs/PreER7/H1/Measurements/FreeSwingMich/2015-05-27'
Upgraded 'trunk/Runs/PreER7/H1/Measurements/FreeSwingMich/2015-05-28'
nfs server cdsfs0:/ligo: not responding                               # <<< what the heck??
nfs server cdsfs0:/ligo: is alive again
Upgraded 'trunk/Runs/PreER7/H1/Measurements/DARMASDs/'                # <<< OK... moving on... ??
Upgraded 'trunk/Runs/PreER7/H1/Measurements/ElectronicsMeasurements/'
#etc
#etc
Upgraded 'branches'
Upgraded 'tags'
[controls@cdsmbp0 aligocalibration]$

This upgraded the hidden .svn configuration file in the entire repo in a way that is incompatible with any version of the svn client prior to 1.7. YUCK!!

It turns out that every computer does not source the svn client binary from the h1boot server as I would have imagined -- so this laptop was using its own copy of the svn binary /usr/bin/svn, which was of a later version than what is normally used on the work stations:
work stations: svn, version 1.6.17 (r1128011) compiled Aug 13 2014, 20:41:52
this laptop: svn, version 1.7.10 (r1485443) compiled Aug 13 2013, 15:31:22

What's worse, is that this "upgrade" to svn version 1.7.10 caused the entire h1boot server's copy repo to fail on the work stations as shown above immediately degrading the whole repo to just a normal unrepoed directory structure and it's not at all backward compatible. Even still more confusing -- svn version 1.6.17 doesn't even have an option to svn upgrade so we didn't believe (at first) what Sudarshan did was even possible.

Thankfully
- Sudarshan left the terminal open on this laptop so we were able to document everything that happened in great detail from this laptop's terminal session
- Kiwmau has made the back up mentioned above, 
- *and* Sudarshan ran an svn st after the upgrade on this laptop, so we know everything that wasn't committed of was modified. (see attached)
So nothing should be lost, we know the status of everything, and we can work to merge the backup back into the repo and move with out too much guess work.

However -- the SysAdmins (don't worry -- this wasn't your fault either!! This is a *terrible* backward compatibility issue with the SVN clients. I blame them!!):
 We should make sure all computers on site running svn cleint 1.6.17. IF and when we want to upgrade to svn client 1.7 or higher, we need to be absolutely sure that we do it to all computers at once.
OR we should demand that all computers are using a client that is hosted on the h1boot server, such that no computer is using an individual copy of an svn client.
 
#scaryscaryscary
#yakshaving

Tonight I followed up on the work that Stefan & I started two weeks ago, and switched the power-up step in the Guardian to come after the transition to DC readout.

Now, the OMC is locked at 2.3W input power, DARM offset = 3.7e-5 counts / 52 pm.  These settings were chosen to provide 20mA at the DCPD Sum.  At the transition to DC readout, the overall OMC-READOUT_ERR_GAIN is set to match the DARM gain on AS_Q, and the power normalization is absorbed by the OMC-READOUT_PREF_OFFSET, as Stefan described in the earlier entry.

During the INCREASE_POWER step the DARM offset (which after the handoff is set via OMC-READOUT_X0_OFFSET, in picometers) is stepped down to maintain the same photocurrent out of the DCPDs.  This *should* maintain the DARM gain through the quadratic scaling of DCPD Sum as a function of DARM offset...but it's not perfect.  I tried this twice today, and after the power-up finished, the DARM loop gain was too low by 30%.  Not sure if this is due to the initial gain matching before the handoff (this step still needs some work, maybe a tdssine measurement would be better), or some non-quadratic change in the response as we go from ~50pm to 16pm.  Stefan, Keita and I observed a small static fringe offset, we should make a careful measurement of DCPDSum vs DARM offset to check that what we think is quadratic really is.

We believe this arrangement is an improvement, because locking the OMC and transitioning to DC readout is more robust at low power, and also I suspect the power-up is more stable on DC readout.  I have increased the PSL waveplate velocity during the power-up (now it's 20, it was 10, not sure about the units), this worked without any trouble.  I am leaving the IFO locked at 23W in the LSC_FF state, with the intent bit set to "Undisturbed."  The range says 65Mpc - could it be true?  Earlier tonight there was a slow angular drift that killed a 23W lock, I am not sure how long we will last.  Also the ITMX oplev loop is ringing for quite some time after each lockloss, it may be a challenge for the IFO to relock on its own.

A screenshot of the new guardian sequence is attached.  I committed the ISC_LOCK.py code before and after the change.  I tested the new sequence twice without a hitch.

Kiwamu, Jeff, Dan, Cheryl, Eric

We successfully tested the transient injection code tinj at LHO for the first time.  This is also the first test of tinj since we added interaction with EPICS channels and migrated to svn.  An earlier version had been previously demonstrated at LLO.  The tests were carried out between GPS = 1117004777 - 1117006270.  We scheduled the standard BNS injection (1.4 on 1.4 msun with optimal orientation at 45 Mpc) that has been used in previous tests [1].  This file, which lives in svn, is called injection_H1.out.  The goal of the test was to inject this waveform with increasing loudness until the folks at LHO could see the signal sweeping across the strain spectrum.

The first attempt failed to inject because H1:CAL-INJ_TINJ_ENABLE = 0.  We set the value to 1.  The next several attempts (GPS = 1117004777, 1117004993, 1117005152) failed to show up because the transient gain in the CAL model was set to zero.  We set it to one and started over.  The following injections were successful:

1117005396 2 1 injection_
1117005598 2 4 injection_
1117005756 2 10 injection_
1117005914 2 100 injection_
1117006170 2 100 injection_

The first column is GPS time, the second is injection type (2 = CBC), the third is scale factor, and the last column is the prefix for the injection file.  Dan and Kiwamu weren't 100% sure they were seeing the BNS signal until we injected with a scale factor of 100.  During the last injection, (scale factor = 100), Jeff and Eric watched the output of HWINJ filter bank.  At the very end, it reached a value of ~50 counts, which did not exceed the current HWINJ LIMIT  = 200.

We fixed a bug with tinj.  First, we fixed a bug, in which the value of TINJ_PAUSE was interpreted incorrectly (1 should have been 0).  Also, the binary executable for tinj included in svn yielded a library error:

tinj: error while loading shared libraries: libmwlaunchermain.so: cannot open shared object file: No such file or directory

So, we recompiled a version that works at LHO and recommitted to svn.  NOTE: we have left tinj running in the background for a stability test.  However, there are no planned injections currently scheduled.

[1] https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=17073

Dan, Evan, Sheila

Tonight we started to look at the angle to length couplings of our test masses.  We injected lines into pitch and yaw on the PUMs, and adjusted the A2L gains to minimize them.  Using the math in the 40 meter alog and Jax's alog, we can estimate the miscentering from these measurements

After we had adjusted these, we saw an improvement in the spectrum below 20 Hz.  The line in the attached screen shot at 16.6 Hz with sidebands at half a hertz are the excitation.  Keep in mind that this is on the new ESD driver and we haven't redone the calibration yet, but clearly this improved the noise below 20 Hz.  

Earlier in the evening we were having difficuulty powering up because of a pitch instability at the main suspension resonant frequency that showed up in all the test masses.  We moved the QPD offsets for pitch back to what they were may 15th, (they had been changed last tuesday).  We then remeasured the miscentering for pitch only, things were a little bit better.  Once we increased the power to 17 Watts, the IFO was stable and we repeated some of the measurements.  We were able to power up to 23 Watts without seeing the instability twice, but lost the lock quickly for other reasons.

Dan, Kiwamu, Evan

List of things done today:

• The ETMX UIM coil driver had tripped off sometime yesterday, and we drove down to the end station to turn it back on.
• In ETMY L3 drivealign, there is now compensation for the LVLN driver summing network. The compensation is a zero at 152 Hz and a pole at 3.2 kHz. This brings the high-frequency DARM phase response back to its previous shape. (See attachment.)
• In the DARM_OFFSET state, the DARM gain is now increased by a factor of 2 and the low-frequency boost (FM7) is engaged. This makes DARM more stable during the transition to dc readout. However, this throws off the procedure for determining the scale factor between OMC DC and AS45Q, so sometimes the transition causes the DARM gain to decrease.
• A high fifth-harmonic violin mode was causing the ETMY ESD to saturate, so there is now a stopband filter in the ETMY L3 LOCK filter bank (since DARM is full).
• LOWNOISE_ESD_ETMY has been rewritten for the new transition procedure. It has been tested (once) and works.
• We took a crossover measurement of ETMY L2. We tried to get ETMY L1 as well, but it seems currently that it's quite low (below 1 Hz). The gain in the L1 LOCK filter can be pushed up from 0.16 to 0.22 without issue (and maybe even further).