J. Kissel

While poking around the CAL-CS model after the recent changes (see LHO aLOG 17034), I noticed two things:
(1) All of the EPICs settings had been lost, even though I'd made sure to capture a safe.snap of the model before restarting the front end model. Not sure what happened there. In the mean time, I've burtrestored the model to 02:10a PST (i.e. before I got started, while DARM was locked, happy, and producing megaparsecs), which hopefully has captured / restored most of Kiwamu's hard work (LHO aLOGs 16698, 16733, 16780, 16798, and 16843).

(2) Because of a version control mix up in the CAL_CS_MASTER.mdl library part, the names for the whitened versions of the closed-loop and open-loop DARM displacement signals, i.e. (what are now) H1:CAL-CS_DARM_RESIDUAL_WHITEN and H1:CAL-CS_DARM_DELTAL_EXTERNAL_WHITEN have changed since we last updated the h1calcs model. The bank names are now typo free -- but that means I've had to re-install the 1^5 : 100^5 (5 zeros at 1 [Hz], 5 poles at 100 [Hz]) whitening filter used to get above the double precision noise in frame storage (see LLO aLOG 16789). 

Maybe I'll ask my fellow detector engineers to help me get an SDF system up and running for this model, so we can better track the changes.

Reminder: Morning meetings will be on Monday, Tuesday, Thursday at 8:30am until further notice. Tuesday and Thrusday are reserved for extended maintenance hours (till 12) as well as 3IFO work (till 4).

SEI

• Jim - Gather data on ETMX, ITMX, HAM4, HAM5. He would appriciate no DAQ restarts for the first few hours in the morning.

SUS

• Betsy - Transfer functions on HAM4, HAM5, and ITMX after Jim.

3IFO

• Lots of work in the LVEA. Moving the ISI from the Staging building to the High Bay.

VE

• Kyle - Using the snorkel lift by BSC3 and also will put an Annulus pump cart on HAM1 for as long as possible.

CDS

• Richard - Pulling cables

J. Kissel

I'll file an aLOG later about the philosophy of design as I create the MEDM screens and fill out the infrastructure, but for now I'll indicate that I've completed the model / DAQ restarts necessary to install the infrastructure updates to the IMC / CARM calibration paths in the h1lsc, h1omc, h1susmc2, and h1calcs front-end models. A detailed log of what I've done is below. I've restarted the DAQ at ~07:31 UTC.

- brought ISC LOCK and IMC LOCK guardians to DOWN
- saved SUS MC2 alignment offsets
- brought SUS MC2 to safe state
- captured and committed safe.snaps for
/opt/rtcds/userapps/release/
sus/h1/burtfiles/h1susmc2_safe.snap << -- used SDF system, following instructions in LHO aLOG 16949
lsc/h1/burtfiles/h1lsc_safe.snap << -- used "makeSafeBackup lsc h1lsc"
omc/h1/burtfiles/h1omc_safe.snap << --  (as above)
cal/h1/burtfiles/h1calcs_safe.snap << -- (as above)
- compiled and installed relevant front-end models on h1build
make h1lsc; confirmed success; make install-h1lsc; confirmed success;
make h1omc; confirmed success; make install-h1omc; confirmed success;
make h1susmc2; confirmed success; make install-h1susmc2; confirmed success;
make h1calcs; confirmed sussess; make install-h1calcs; confimed success;
- h1lsc has an IPC error before getting started, but cleared and stayed clear after diag reset (no other models had IPC errors reported)
- brought HAM3 SEI to OFFLINE (with a spurious GS13 watchdog trip along the way)
- restarted relevant front-end code
on h1lsc0 -- cdsCode; starth1lsc
   This lit up the CDS overview with IPC errors as expected, on h1omc, oaf, lscaux, asc, ascimc, and the globally controlled sus (the MCs 1-3, PRs M&2, SRs M&2, BS, OMs, RMs, and TMs). Decided to complete model restarts before clearing errors.
on h1omc -- starth1omc
on h1calcs -- starth1calcs
    released the model still needs new IPC senders from MC2 before its IPC errors go away
on h1sush34 -- starth1susmc2
on h1oaf0 -- starth1calcs
- Hand-cleared all IPC error messages with a diag reset on all affected model's GDS_TP screens; confirmed no lingering errors were present.
- cleared SUS MC2 and ISI HAM3 watchdogs from SUS model restart
- brought HAM3 SEI up to ISOLATED (accompanied by another spurious GS13 watchdog trip)
- brought SUS MC2 to ALIGNED
- brought IMC_LOCK guardian back to LOCKED, confirmed successful relock of IMC, appearance of light on AS port in the same camera position it was when I got started
- shutdown DAQ / FB / h1dc0 at 07:31 UTC to clear remaining DAQ errors; confirmed the only remaining error is from h1oaf model, who is now missing some CARM / IMC senders
- committed all model changes to the userapps repo,
   ${userapps}/lsc/h1/models$
   Sending        h1lsc.mdl
   ${userapps}/omc/h1/models$
   Sending        h1omc.mdl
   ${userapps}/sus/h1/models$
   Sending        h1susmc2.mdl
   ${userapps}/cal/common/models$
   Sending        CAL_CS_MASTER.mdl
   ${userapps}/cal/h1/models$ 
   Sending        h1calcs.mdl
Committed revision 9944.

DONE!

Dan Hoak asked me about upconversion around the OMC dither lines at 575.1 Hz, 600.1 Hz, 625.1 Hz and 650.1 Hz, since the upconversion seen in L1 has been quite large at those frequencies (amplitude and band size). 

We don't yet have the long stretches of DC readout data used to look at L1 lines, but a quick look at the Feb 26 H1 lock confirms that upconversion around dither lines in H1 is large too. Plots made with ldvw are attached. The fine structures around 575.1 and 600.1 Hz are nearly identical to each other. The same goes for 625.1 and 650.1 Hz, but their structures differ significantly from those of the two lower-frequency bands. 

To repeat a comment made in the LLO alog originally, CW searches in such severely contaminated bands are pointless. We CWers hope that the bands affected by the dithers can be shrunk before O1 begins. (Of course, there are many more pressing issues to address before that...)

J. Kissel

The IFO is down (and has been for ~4 hours, most likely because of the 6.4 [mag] EQ in Indonesia) and I'm beginning updates to the LSC, OMC, SUSMC2, and CALCS models to fix up the IMC/CARM calibration paths, so I've turned OFF the observation intent bit around 14:50 UTC (6:50a PT). 

I've also switched the ISC LOCK and IMC LOCK guardians to the DOWN state. I found that MC2 had not had its alignments saved, so I've saved them.

Gabriele, Sheila, Alexa, Evan

Summary

We have engaged the DHARD WFS Y (and P) at 3 Hz on resonance with a reduced oplev damping gain in the ETMs. Again, to start off we closed the DHARD Y WFS  with 3 Hz BW at 50pm CARM offset. Since this loop is also stable at low BW, we will leave it in the low BW configuration at this point, so that we are at a 3 Hz BW on resonance.

Details

We had tried engaging the new DHARD Y loops as described in LHO#17006. However, we quickly found that this configuration was unstable. So, we removed the partial plant inversion FM6 and took a plant TF. We found that the plant that Gabriele had measured with the oplevs was slighlty different than the @50pm plant (see Gabriele's comment). We adjusted FM6 accordingly to compenstate for the peaks seen between 1 and 5Hz. FM6 is now zpk([-0.3303+i*15.1459;-0.3303-i*15.1459;-1.9027+i*16.6711;-1.9027-i*16.6711; -0.2672+i*19.227;-0.2672-i*19.227],[-0.6659+i*18.7;-0.6659-i*18.7;-0.509+i*11.519; -0.509-i*11.519;-1.0404+i*15.4844; -1.0404-i*15.4844], 1)gain(0.469248).

To close the loop at low BW at 50pm CARM offset, we engage FM2, FM3, FM4, FM6, FM9 with a gain of 30. FM6 is described above, and the remaining filters are the same as in LHO#17006. With a gain of 360, this gives a UGF of 3 Hz and a phase margin of 36 deg.

On resoncance with a gain of 30, we measured that the UGF is 3.5 Hz with a phase margin of 36 deg.

This is in the guardian now.

Evan, Alexa, Gabriele, Sheila

We have closed 8 DRMI ASC loops with the arms off resonance.  Ordered fast to slow they are:

• AS36BQ -> BS (FM2 (integrator),FM2 (low pass) and FM10, (plant inversion).  For pitch we have a gain of 1 a ugf of 3 Hz, and 70 degrees of phase margin.  For yaw we have a gain of 0.7, a ugf of 3 Hz and 65 degrees of phase margin.  As these loops are engaged the oplev damping is ramped off. 
• refl A 9 I - refl B 9I -> IM4 (FM2 and 3 only) gain of 0.1 for pit, -0.01 for yaw.  this loop takes a few seconds to converge.  
• refl A 45 I - 0.66* refl A 9 I -> PR2 (gain of 0.1 for pit (the loop goes unstable with higher gain), 0.3 for Yaw.  
• POP B -> PRM  FM2+3, gain of -3000 for pit 3000 for yaw.  (this loops is verry slow, it takes about a minute to converge.)

These loops are now all turned on by the guardian, mich comes on first, there is a pause and the rest come on.  We can leave these on for the first steps of the CARM offset reduction.  We have manually been turning off all of them except for MICH at this point.  We tried leaving the PRM loop on once, this caused bad drift without the 2 refl loops closed. 

WARNING:  the guardian turns on 6 loops durring the DRMI ASC step that need to be turned off manually before the CARM offset is reduced too much

Washing is complete from corner station to double door X-1-4. Lights and equipment are relocated to single door between X-1-4 and X-1-5 doors. Cleaning will begin tomorrow moving south. 

730 Karen, Cris - LVEA

849 Corey - EY

902 Kyle - LVEA Looking for parts for tomorrow

906 Bubba - LVEA Check on the cleanroom test stand

916 Bubba - Out

918 Kyle - Out

918 Corey - Out

1537 Dave B. - CER

   Have posted two sets of plots; one is with no zoom and the other with zoom in on ITMX and BS. The four peaks on ITMX has some time correlation with the peaks on ITMY and ETMY. The time of the second peak on the BS correlates with the third peak on ITMX. There is no clear pattern with the peaks on all 7 OpLevs being plotted. Will discuss with the OpLev folks.  

   These plots are run with minute trends not second trends, due to an error with plotting the second trend data. I an looking into the cause of this error.   

Laser Status: 
SysStat is good
Output power is 32.3 W (should be around 30 W)
FRONTEND WATCH is Green
HPO WATCH is Red

PMC:
It has been locked 0 day, 15 hr 14 minutes (should be days/weeks)
Reflected power is 2.0 Watts  and PowerSum = 24.9 Watts.
(Reflected Power should be <= 10% of PowerSum)

FSS:
It has been locked for 0 h and 17 min (should be days/weeks)
Threshold on transmitted photo-detector PD = 1.18V (should be 0.9V)

ISS:
The diffracted power is around 9.3% (should be 5-15%)
Last saturation event was 15 h and 17 minutes ago (should be days/weeks)

Coherences for last nigh lock are available here:

https://ldas-jobs.ligo.caltech.edu/~gabriele.vajente/bruco_1109322016/

Here is my summary of the summary:

• No more coherence with BS ISI at low frequency
• Low frequency shows coherence mostly with MICH, SRCL and PRCL
• We still have the significant coherence with SRCL/PRCL at all frequencies, likely due to frequency/intensity noise. We'll have to try and tune the IMC longitudinal locking point soon
• There is large coherence at 967 - 974 Hz with ISI_HAM2_BLND_GS13RZ and ISI_HAM5_BLND_GS13RZ
• The 3 kHz bump, which is larger at the beginning of the lock and smaller close to the end, shows large coherence (basically 1) with IMC length control LSC-MCL_OUT. Maybe it's a gain peaking of the REFL servo?

The coherence of DARM with the BS ISI pitch sensor was no more present in last night lock, likely because Evan engaged the ISI second stage.

In the first attached plot, the red traces are with ISI stage2 on, blue traces off.

However, be aware that the alignment status of the IFO is likely different in the two locks, so we might have less coherence because of a better alignment.

The first attached figure shows a spectrogram of the DARM signal during last night lock. I had a look at one hour of data from 9.00 UTC.

The noise is highly non stationary almost everywhere. Looking at the longer spectrogram in the summary pages, it seems that the ~3 kHz bump got better later in the lock. However, I'm focusing at lower frequencies.

Scattered light

The second and third plots show a clear signature of scattered light arches, that contribute to the sensitivity quite often, and up to 120 Hz some times. I don't know what is causing them yet, but they're quite loud in the low frequency region, which is still relatively noisy.

Non stationarity in the hundred Hz region

The region between 50 and 500 Hz is very non stationary, see the 4th plot for a zoom in the spectrogram. To understand this I computed the BLRMS of DARM in the band between 130 and 160 Hz. There are a lot of quite fast excursions, probably glitch like.

I tried to correlate the BLRMS with angular signals. I could use both the ASC error signals or the local sensors of the optics (optical levers or shadow sensors). The 5th plot shows the result of the fit of local sensors (and their square) to the BLRMS. Altough I'm not able to properly reconstruct the largest BLRMS excursions, the trend seems quite explained by the angular motion. It's likely that when we have a larger than normal angular excursion, some highly non linear phenomenon create an increase of noise that I can't easily catch with my analysis.

I used a channel ranking algorithm to find out which angular motion is mostly rsponsible for the BLRMS variation. The algorithm is the same already used at LLO, with small improvements. The code is attached. basically, the algorithm starts with the BLRMS and fit every channel one by one to it. It selects the channel that gives the largest reduction in the residual error. It then moves on again, fitting the residual of the first fit again with every single channel, and select again the best one as before.

The result ranking, shown in the last attached picture, is that the most relevant motions seem to be: ETMY_YAW, SRM_PIT, SRM_YAW and BS_YAW. As a reminder, DHARD PIT has 3 hz bandwidth, while YAW is still low.

Alexa, Evan, Gabriele, Sheila

We have closed 6 low bandwidth loops with DRMI locked with arms off resonance today, based on what we learned from talking to LLO yesterday:

INP1: REFLA9I-REFLB9I -> IM4 PIT and YAW

PRC2: REFLA45I-REFLA9I -> PR2 PIT only (YAW signal seems to have an offset)

SRC1: ASB36I-> SRM pit only, although error signal loks OK for Yaw as well

MICH: ASB 36Q -> BS, PIT and YAW

In the past we had phased AS36 to maximize the BS signal in Q, but we noticed today that the Q signal is contaminated by SRM.  We rephased AS B 36 to minimize the SRM signal in Q, this reduced the SRM pitch motion seen by AS36 B Q by 40 dB.  

We have not attempted to close the AS_C-> SR2 loop, since we are far off center on AS_C.  It seems that we will have to check search for the alignment that minimizes clipping on the Faraday and use picomotors to re-center AS_C,; we already know that we are clipping on AS_C when we are well aligned for the OMC PDs.  (alog 16831 ).  Despite this, it looked like ASB 36 I was a decent signal for SRM in both pitch and Yaw. 

The wind gusts are at around 30mph, we could see from the ALS control signals that the arms are moving more than usual, so I changed the end stations to the high blends and we are using BRS sensor correction at end X.  (configuration described in alog 16583)

Gabriele, Alexa

Gabriele had accidently unlocked the MC this morning, and had trouble relocking it. I know people had trouble with the MC yesterday morning, but there was no alog about this ... :(

The input power this morning was set to 5 W. When MC would try to acquire lock, the MC2 M3 LOCK L would reach the limit. I adjusted the input power to 2.8W and we locked immediatly. The IMC "DOWN" guardian adjusts the MC common mode board input gain depending on the input power (Power <4, 4 = 10); it's possible that the init and locked gain set for 5 W is not correct. This is something we new was not ideal, and we will correct. If you are having trouble locking the MC and the alignment looks good, I would suggest requesting the input power to 2.8 W and see if that works.