11am local

28 sec. to overfill CP3 with 1/2 turn open on bypass LLCV (bypass exhaust valve remains open)

Next fill due Fri.

It looks like the code restarts yesterday made BRSX upset. Right now, the DRIFTMON channel is swinging about 10k counts, p2p. Krishna suggests "several thousand" is too high for the damper to be useable. It sounds like I'll need to re-center the table, after the BRS has settled down some. We'll keep monitoring, but for now the SEI_CONF manager needs  to be left in a state that doesn't use BRSX, currently in WINDY_NOBRSX, though VERY_WINDY and some of the earthquake states will work as well. TJ has confirmed that with the BRSX_STAT node in error, SEI_CONF will not complete a transition to a state that uses the BRSX, but a code restart or INITing SEI_CONF could get around that.

Attached trend shows that trouble started around 18:30 UTC yesterday, which I think is about the time we did several restarts of the BRSX Beckhoff.

Attached is the OLTF in two configurations with 7dB VGA gain.

50W (actually 48W), AC coupling OFF, and boost ON (solid line)

50W (actually 48W), AC coupling ON, boost OFF (dashed).

UGF is about 9kHz with phase margin of 40 deg or so (boost ON) or 50 (boost OFF).

Boost buys us about 9dB more gain at 1kHz.

I asked Kiwamu to do an analog measurement up to higher frequency on the floor.

J. Kissel, K. Izumi

Kiwamu and I sat down again this morning to review the suspected sign error in the L3 / TST / ESD path in the calibrated output (see LHO aLOG 29860). He's convinced me -- just like what had happened in July (LHO aLOG 28396) -- after the most recent flip of the ETMY L3 ESD bias sign (LHO aLOG 29397), although I had accounted for all of the digital changes in the L3 path, I did not change the replica of the actual to reflect the real actuation strength sign flip. 

Several decisions have been made so as to prevent this problem in the future:
(1) We've decided against changing anything in the CAL-CS front-end calibration for future ESD bias sign flips.
In the real ETMY L3 path, when the ESD bias sign is flipped, it changes the sign of the real-world ESD actuation. As such we compensate that change by changing the sign of the gain in the L3_DRIVEALIGN_L filter bank. In doing so, that means there's no change in the overall LSC super-actuator transfer function. Because there is no change in the overall transfer function, we therefore do not need to change the replica of the path in CAL-CS.

In the past, we've changed the CAL-CS replica to save our sanity aesthetically -- such that, for example, we can look at the DRIVEALIGN matrix gain in both the actual ETMY SUS and in CAL-CS and they match. But if one does so, one MUST change the sign of the real ESD (H1:CAL-CS_DARM_ANALOG_ETMY_L3_GAIN). This is what was not done in July, nor was it done in late August, because there's no digital equivalent in the control system to remind me. 

In light of us (well, me) failing to keep this replica path correct, forgetting to code up a setting change here or there every time, we find the cons of keeping things aesthetically the same out-weighing the pros. 

We will no longer touch the CAL-CS calibration settings when we flip the bias sign in the future.

(2) We've removed all CAL-CS changes from the ISC_LOCK guardian.
While assessment and control system compensation for the bias flip still live in the ISC_LOCK and SUS_PI guardians, we've removed all modification to CAL-CS settings from the ISC_LOCK guardian. We've remove execution of these steps by commenting out the relevant lines in the ISC_LOCK guardian:

        # Check for BIAS flip on ETMY
        # Note that SUS_PI guardian also is affected by ETMX Bias Flipping. 
        #            There are checks and appropriate actions in there too. -Kissel, Hardwick 08/31/2016
        if ezca['SUS-ETMY_L3_LOCK_INBIAS'] < 0:
        #    ezca['SUS-ETMY_L3_ESDOUTF_UL_GAIN'] = +1   # Commented out after finding that compensating for the 
        #    ezca['SUS-ETMY_L3_ESDOUTF_LL_GAIN'] = +1   # Bias flip down stream of the linearization just does
        #    ezca['SUS-ETMY_L3_ESDOUTF_UR_GAIN'] = +1   # not work.
        #    ezca['SUS-ETMY_L3_ESDOUTF_LR_GAIN'] = +1
            ezca['SUS-ETMY_L3_DRIVEALIGN_L2L_GAIN'] = -30.0
            ezca['SUS-ETMY_L3_ESDOUTF_LIN_FORCE_COEFF'] = -124518.4
        #    ezca['CAL-CS_DARM_FE_ETMY_L3_DRIVEALIGN_L2L_GAIN'] = -30.0          # Commented out after second occurrence
        #    ezca['CAL-CS_DARM_FE_ETMY_L3_ESDOUTF_UL_GAIN'] = +1                 # of overall sign error in L3 path of 
        #    ezca['CAL-CS_DARM_FE_ETMY_L3_ESDOUTF_LIN_FORCE_COEFF'] = -124518.4  # CAL-CS. LHO aLOG 29868.
        #    ezca['CAL-CS_DARM_ANALOG_ETMY_L3_GAIN']= -1
        else: # flip everything.
        #    ezca['SUS-ETMY_L3_ESDOUTF_UL_GAIN'] = +1   # Commented out after finding that compensating for the 
        #    ezca['SUS-ETMY_L3_ESDOUTF_LL_GAIN'] = +1   # Bias flip down stream of the linearization just does
        #    ezca['SUS-ETMY_L3_ESDOUTF_UR_GAIN'] = +1   # not work. LHO aLOG 29397.
        #    ezca['SUS-ETMY_L3_ESDOUTF_LR_GAIN'] = +1
            ezca['SUS-ETMY_L3_DRIVEALIGN_L2L_GAIN'] = +30.0
            ezca['SUS-ETMY_L3_ESDOUTF_LIN_FORCE_COEFF'] = +124518.4   
        #    ezca['CAL-CS_DARM_FE_ETMY_L3_DRIVEALIGN_L2L_GAIN'] = +30.0          # Commented out after second occurrence
        #    ezca['CAL-CS_DARM_FE_ETMY_L3_ESDOUTF_UL_GAIN'] = +1                 # of overall sign error in L3 path of 
        #    ezca['CAL-CS_DARM_FE_ETMY_L3_ESDOUTF_LIN_FORCE_COEFF'] = +124518.4  # CAL-CS. LHO aLOG 29868.
        #    ezca['CAL-CS_DARM_ANALOG_ETMY_L3_GAIN']= +1
        ezca['SUS-ETMY_L3_LOCK_BIAS_GAIN'] = 1


Attached is a screen shot of the relevant MEDM screens to aide discussion.

• Guardian issues will be addressed by Jaime upon his next visit. (next weekish)
• SAFETY MEETING TODAY
• ER10 will NOT begin at the end of next week. More about this after tomorrows JRPC meeting.
• Thursday WILL be used for maintenance. Duration not specified. (PCal work; Kyle at EX; opportunistic CDS electronics work)

SEI - BRSX is severly rung up since last night. Team is working on it.

SUS - Nothing to report

CDS ELT - Everything seems ok

VAC - only 1 PT140 now. CP4 exhaust flow measurements being done today. New vacuum gui

PSL - Nothing to report

FAC - FRS maintenance

COMMISH - intensity stabilization is working as intended

I've stepped all four ring heaters consecutively tonight by 4 W each to identify which test mass belongs to the new 17783 Hz/47.7 kHz PI mode (alogs 29820 and 29838). The shift in frequencies of the test masses is dominated by a change in the Young's modulus which we can alter via the ring heater power; by stepping each ring heater and finding which causes a larger relative frequency shift of the mode in question, we can identify which test mass the mode is from.  See T1600080 and LLO alog 18002 for more info. All power changes below were applied to both top and bottom ring heater. All times UTC.

ETMX: 0.75 --> 2.75 @ 9:29 --> 0.75 @ 9:48

ETMY: 0 --> 2 @ 9:49 --> 0 @ 10:08

ITMX: 0.25 --> 2.25 @ 10:08 --> 0.25 @ 10:29

ITMY: 1.25 --> 3.25 @ 10:31 --> 1.25 @ 10:41

Note we just lost lock around 10:42, probably due to these ITM steps. 

Driving the ITM ESDs to saturation in a single quadrant raises peaks in DARM.

We've only briefly (and at first accidentally) investigated. I drove ITMY and ITMX ESD UL to saturation at 17783 Hz and we see a broad peak in DARM over an order of magniture above noise floor at 81.9 Hz for each. Also drove ITMX same quadrant at 15006 Hz and saw several peaks in DARM, most notably at 55 Hz and 110 Hz. We'll do proper injections next. 

Kiwamu, Terra, Lisa

We had a hard time dealing with bounce and roll modes tonight and that slowed us down.

After keeping them under control, we followed directions from Daniel and we engaged the  ISS boost  (gain increase from 5dB to 7dB, boost 1 on -- we believe this is supposed to give us a factor of 2 suppression at 2 kHz, with higher gain at 100 Hz). 

The higher suppression of intensity noise around 100 Hz exposed a suspicious shape in the noise curve, so we decided to triple-check the calibration by making complete calibration measurements (see Kiwamu's entry).

With the new calibration filters, the suspicious shape at 100 Hz disappeared, and we got back a more familiar curve...and some Mpc, SensMon is around 60 Mpc.

The "jitter/intensity/(frequency?)" noise coupling to DARM stabilizes in a bad place after a while at 50W (yellow is O1 reference, all the other colors are curves taken at different times during the lock in low noise), making DARM worse between 500 Hz and 1 kHz, and even more clearly above 3 kHz. So there is more work to do to figure out how to keep the coupling low.


We leave the IFO to Terra for PI tests.


Some details:

- bounce and roll modes are becoming a problem, they required constant attention during lock acquisition;

- we had an error message once complaining that the ISS third loop was not engaged, and we couldn't move on in the locking sequence; Kiwamu bypassed the problem by forcing power increase (we also had some problem closing the ISS second loop from the medm screen (?)) 

- there have been (at least) a couple of ISS instabilities that prevented us from staying locked in DRMI; we "fixed" them by increasing the diffraction power, that happened at least twice today

- we reversed the change to the DARM gain, now it is back to 1400 

Lisa, Kiwamu,

We think that the calibration has been wrong and therefore it lifted up the noise floor below 300 Hz. We need another set of eyes tomorrow to doublecheck our theory (we are currently too sleepy to do systematic investigation).

In short, we believe that the sign of ETMY L3 stage in CALCS (or somewhere else similar to it) is wrong which is exactly the same situation as what happened in this past July (28396).

Because I knew that our DARM open loop model is accurate and consistent with the recent measurement (29748), I made a calibration filter for DARM_IN1 which converts DARM_IN1 to DARM displacement as opposed to the use of both DARM_IN1 and DARM_OUT. Here is a comparison of the CALCS spectrum against the spectrum derived from DARM_IN1.

As shown in the plot, the CAL CS spectrum overestimates the noise floor below 300 Hz or so. This is exactly the same behavior as what we have experienced in this past July. In addition, we have noticed that the noise floor of CALCS changed as a function of the DARM control gain which should not happen in the calibration scheme used in CAL CS. Also, when we flipped the sign of the EY L3 stage in CAL CS, the leve of the noise floor became identical to the one derived by DARM_IN1 and also became insensitive to the control gain. This increased our confidence that the L3 sign was wrong in CALCS.

We are leaving the L3 stage gain flipped (DRIVEALIGN_GAIN -30 --> +30) for the night. If our theory is correct, we regain the binary range back to ~60 Mpc with this change.

Also, we took a DARM open loop and PCAL sweep measurement within the same lock stretch. We did not analyze them yet, but they are available at:

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER10/H1/Measurements/PCAL/2016-09-21_H1_PCAL2DARMTF_4to1200Hz.xml

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER10/H1/Measurements/DARMOLGTFs/2016-09-21_H1_DARM_OLGTF_4to1200Hz.xml

Also, my code which generated the calibration filter for DARM_IN1, as well as, the generated filter are available at:

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER10/H1/Scripts/ControlRoomCalib/CalibrateH1DARM_IN1.m

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER10/H1/Scripts/ControlRoomCalib/DARM_IN1_calib.txt

Cheryl, Kiwamu,

Related to 29808, 29793, WP6165

[Modified generic interface box is now installed]

We have replaced the generatic interface box with a modified box (S1103802) in the PSL booth today. The box was the one for reading out the EOM pick off (IMC-PWR_EOM) and the periscope power (IMC-PWR_IN). Their associated AC channels are now with a gain of 200 at high frequencies above 4 Hz as described in Daniel's log (29808).

[PDA55 is installed for monitoring the light before EOM]

In addition, we have newly installed a PDA55 in order to monitor intensity noise before the EOM. See the attached for the setup.

As shown in the picture, the PDA55 recieves light leaking to the first steering mirror after the PMC. According to a handheld power meter, the power level of thie light was about 1 mW. The PDA55 with the lowest gain setting gave us a DC voltage of 4 volts.

Currently IMC-PWR_EOM_AC and IMC-PWR_EOM_DC are connected to this new PDA55 and not to the actual EOM pick off.

[Some cleaning up]

There was an undumped reflection back form a lens (IO-MB_L2). We put a beam dump by the Faraday isolator of the ALS.

Also, some pictures are available in ResourseSpace https://ligoimages.mit.edu/?c=1712

Title:  09/20/2016, Evening Shift 23:00 – 07:00 (16:00 - 00:00) All times in UTC (PT)
State of H1: IFO is down due to a problem with the Guardian. CDS is working on the resolution.      
Commissioning: 
Outgoing Operator:  Ed
 
Activity Log: All Times in UTC (PT)

23:00 (16:00) Start of shift
23:35 (16:35) Rick & Travis – Back from End-X
23:37 (16:37) Ben – Going into LVEA to look for tools
23:42 (16:42) Ben – Out of the LVEA
00:05 (17:05) Kiwamu & Nutsinee – Out of LVEA
00:07 (17:07) Dave – DAQ restart (WP #6174)


Title: 09/20/2006, Evening Shift 23:00 – 07:00 (16:00 – 00:00) All times in UTC (PT)
Support:  Jenne, Sheila, Lisa, Kiwamu      
Incoming Operator: N/A

Shift Detail Summary: Ran initial alignment after Guardian fixed and people out of LVEA and End-X. Commissioning and relocking took up the bulk of the shift. Environmental conditions of light winds and low seismic activity all shift. 

The End-X BRS was rung up all shift. Using ISI_CUST_CHAMBER_GND_BRS.adl to monitor. No change in signals during the shift, so per Jim W. did not make any adjustments or changes.

Jeff K, Dave B, Darkhan T,

Overview

Coherence calculation settings were updated today's after a minor bug fix in CAL-CS.

We discovered that some of the reference EPICS records that are used for calculation of kappas in the front-end were not set (or lost after a DAQ restart). The records were populated with values calculated from the DARM model for ER9.

Details

• Today we modified CAL-CS synchronized oscillator demodulation for DARM_LINE1 to include an ability to set a desired phase (LHO alogs 29852, 29853). After this update the replica of the DARM_LINE1 excitation, used for calculation of time-dependent parameters ("kappas"), uses SINGAIN and COSGAIN settings of the synchronized oscillator (which weren't set before). Both of these gains must be set to be the same as CLKGAIN.

Similarly, SUS_LINE1 synched oscillator SINGAIN and COSGAIN values must be set to be $(IFO):SUS-ETMY_L3_CAL_LINE_CLKGAIN multiplied by DAQ downsampling TF magnitude at this frequency (35.9 Hz at LHO). Synched OSC phase must be set to the DAQ downsampling TF phase at the line frequency (not sure if we need to put positive or negative phase). Previously SUS_LINE1 synched OSC parameters were not set properly and the coherence was not calculated (see attachment 4, coherences calculated during last 4 days).

Both DARM_LINE1 and SUS_LINE1 oscillator parameters were updated, the changes were accepted in SDF_OVERVIEW.

• We updated the EPICS records that are used for calculation of κ_c and f_c, H1:CAL-CS_TDEP_PCALY_LINE2_REF_A_USUM_(REAL|IMAG) and H1:CAL-CS_TDEP_CAVITY_POLE_PCAL_FREQ:

Old : H1:CAL-CS_TDEP_PCALY_LINE2_REF_A_USUM_REAL 0
New : H1:CAL-CS_TDEP_PCALY_LINE2_REF_A_USUM_REAL -1.73852e-19

Old : H1:CAL-CS_TDEP_PCALY_LINE2_REF_A_USUM_IMAG 0
New : H1:CAL-CS_TDEP_PCALY_LINE2_REF_A_USUM_IMAG -1.03541e-19

• The oscillator phase field was added to the MEDM screen CAL_CS_TDEP_DARM_LINE and some minor fixes were made to the CAL_CS_TDEP_OVERVIEW screen. The changes were committed to cds_user_apps repo, r14297.

J. Kissel, S. Dwyer, L. Barsotti

At the advice of DetChar (LHO aLOG 29828) we've balanced the DCPDs, which indeed hasn't been done since the new breadboard and PDs were installed (LHO aLOG 28862). Unlike the previous pair of DCPDs which were out-of-the-box perfectly balanced (see LHO aLOG 17650), the current pair has an imbalance of 2.1106%. This value has been entered into H1:OMC-DCPD_BALANCE, and accepted into the SDF "down" state for the h1omc model.

Method:
For the DCPD sum, we take an average of the two: A/2 + B/2.
The h1omc front-end infrastructure is built such that the percentage imbalance, e, is applied to both equally: A*(1 + e)/2 + B(1 - e)/2
So, the transfer function measurement of DCPD A/B is (1+e)/(1-e) ~ 1 + 2e. Since the transfer function magnitude is 0.957788, then the imbalance we enter will be e = ((A/B) - 1) / 2 = 0.021106 = -2.1106%.

We also found this value gradually (because we weren't sure how the infrastructure worked), by confirming the imbalance that minimized the DCPD NULL stream (and the coherence drops to zero). Overshooting the imbalance (e.g. by entering in -4.2%) shows a clear sign flip from the reference trace where there is 0% imbalance compensation.

Ben Keita Daniel

We updated the ISS box:

• Gain of 1/10 in the excitation input. This should allow us to leave this path enabled for a fine adjusting the offset.
• Boost moved to 4kHz (from 500Hz)
• Analog outputs added to the front panel
• Removed the old ISS and cabled all PDs of the ISS array into the new chassis. PD1-4 are now correctly read as PD1-4 in the model.

We made the following model updates:

• The legacy second loop ISS code was removed
• The "outerloop" ISS was renamed to secondloop ISS
• The QPD was moved over as well as a reference servo for the diffraction power
• The ISS second loop enable button in the first loop is now binary EPICS channel
• medm, sdf and filter files were updated to reflect these changes.

D. Tuyenbayev, J. Kissel

Darkhan had noticed that we are demodulating the ETMY SUS calibration line (which determines the test mass (L3) stage actuation strength change, kappa_{TST}) differently than that which is injected just after the DARM bank from the CAL-CS model (which determines the PUM+UIM (L1+L2) stage actuation strength change, kappa_{PU}), after we upgraded the font-end DARM loop parameter time-dependence calculations (see e.g. LHO aLOGs 29231, 29740, and 29744). In short, for the DARM line, he discovered we're not able tune the phase of the oscillator for this new time dependent analysis. If we keep this, then we'd have to maintain two sets of DARM loop model EPICs records to calculate these actuation strength changes, because offline construction of kappas must include the phase destortion of DAQ downsampling filters at the calibration line frequency, where any front-end calculation does not. Also, it seems unnecessarily confusing to demodulate various lines differently.

As such, for the DARM_LINE_MONITOR block in the 
/opt/rtcds/userapps/release/cal/common/models/CAL_LINE_MONITOR_MASTER.mdl
library, we've broken the DARM_LINE_DEMOD tee-off of the CLK output of the oscillator, and replaced it with the I phase output of a phase rotation block, which picks up the SIN and COS outputs of the oscillator.

These changes have been committed to the userapps repo.

new h1calcs model WP6174

Jeff, Darkhan, Dave:

new h1calcs model installed. DAQ restart combined this and the last h1psliss changes.

h1psliss model WP6172

Daniel, Keita, Ben, Dave:

h1psliss was restarted several time, first to primarily replace OUTERLOOP with SECONDLOOP naming. Subsequent restart for minor name tweaks. Several DAQ restarts

Clone h1fw1 WP6171

Carlos, Dave

NDS were switch to using h1fw0's frames. h1fw1 was shutdown and its boot disk is being cloned. Due to its size (1TB) this will take overnight.

Reboot h1guardian0

TJ, Dave

We did a reboot of h1guardian0, later attemps to lock the mode cleaner showed connection errors for Beckhoff channels. Running caget on h1guardian0 did get the data, but showned two paths (direct and via epics-gateway). Stop-start of the node did not force the connection. We turned off the gateway (h1slow-h1fe) and rebooted guardian. Some nodes still showed connection errors, again caget connected. Finally we started the gateway and all the connections completed. Need further investigation with Jamie.

h1guardian0 was updated prior to the reboot, we think this may have broken INJ_TRANS node.

TCS CO2 chiler tests

Dave, Nutsinee:

Confirmed that pulling the chiller cable in preparation for a power cycle of h1oaf0 IOChassis trips the CO2 lasers and should not be done.

Remove old PT140 channels from Vacuum Controls WP6166

Patrick, Dave:

After Patrick had made the Beckhoff changes, I imported his latest h0vaclx.ini file into H0EDCU_VAC.ini This went in on later DAQ restart

Add h1fw2's new diag epics channels to DAQ WP6173

Dave:

h1fw2 is running Jonathan's RCG3.2 daqd with improved diagnostics. These additional channels were added to H1EDCU_DAQ.ini and went in on a DAQ restart.

h1susprocpi model

Terra, Dave:

Terra added epics input channels for state definition. Model was changed and DAQ was restarted. Small number of slow channels were added to DAQ.

DAQ restarts

Dave:

Several DAQ restarts during the day to support the above activities. Most went cleanly, two had minor issues

On one I needed to restart the mxstream from both h1pemmx and h1pemmy

On another I need to restart the mxstream on h1sush56

J. Kissel

Now that we're approaching ER10, and the noise is getting back to O1 levels, we need to start tracking the time dependence of the SRCL detuning in the DARM response. As such, with only intuition to guide, I've added a new calibration line at 7.83 Hz, driven by PCALY at a requested amplitude of 20000 [ct] (corresponds to a DAC [ct/rtHz] of 28909, and 8.8e-13 [m/rtHz] of DARM displacement). For a 10 [sec] FFT, with the current sensitivity, this has about an SNR of 10. We can explore driving the line harder, but let's see what we get out of this -- we're already close to the limit of the PCAL AOM, and that's what I used to tune the excitation amplitude. Also note that, although we often use a 10 [sec] FFT as our SNR metric, in practice, we often use 60 or 120 [sec] FFTs (i.e. the time scale on which we expect optical plant parameters to vary), so we'll win there.

I've checked to make sure that this new line
- Does not saturate the PCALY DAC
- Does not saturate the PCALY OFS
- Does not saturate the DARM actuator when trying to control this line (ETMY SUS) 
- Does not generate any substantial harmonics or other non-linear noise in DARM

And I've also accepted the settings for this new line in the safe and OBSERVE snaps for PCALY.

Let's get this line into SLM tool and start analyzing to see if the SRC detuning moves!

P.S. We expect fisher-matrix back-up that this is roughly the "optimal" location for the SRCL line, given that we suspect the optical spring frequency to be around 9.8 [Hz]. Of course, we cannot put the line right on 9.8 [Hz], since that's exactly the frequency of the QUAD's highest vertical mode (a.k.a. "bounce" mode). I've compared 7.93 [Hz] against all of the "do not put a line here" criteria used for the original calibration lines (see LLO aLOG 15870), and this frequency does indeed satisfy those criteria especially since the line is below the astrophysical analysis band.