Jenne, Rana

In order to symmetrize the hard/soft drives, we want the ITM and ETM actuation functions to be identical (i.e. the PUM pit to TM pit TF). Previously Evan and Rana adjusted the TOP stage damping to make all the TMs the same. We also balanced the common / differential drives using the AS port WFS.

Today we realized that this was not as good as we thought since the PIT optical lever servos were on for the ITMs, but no other OL servos were on. So the PIT DoF was an admixture of hard/soft all of this time. So we measured the OLG for all of the TMs and turned on the loops for the ETMs, so now the PIT OLDAMPs are on for all the TMs. The same filters are ON for all 4 loops, and we adjusted the gains to make the OLG sweeps look the same (to within ~10-20%):

G_ITMX = -300

G_ITMY = -300

G_ETMX = -440

G_ETMY = -300

Nergis, Sheila, Haocun

As posted in alog 27820, the IMC transfer function has a high gain around 800kHz, and we thought that may be reduced by lowering the FSS loop gain, which was proved to be true.

We reduced the FSS loop gain for 6dB (the common gain from 20dB to 14dB;  the fast gain from 22dB to 16dB) , and the IMC loop gain dropped about 16dB from -4dB to -20dB at 800kHZ.

The measurements were taken from 10Hz to 5MHz. The green curve was measured before reducing the FSS gain, and the yellow one was measured after lowering the gain.

Currently, we left the FSS loop gain values to be the lower ones, which can be turned back up later if needed.

LLCV bypass valve 1/2 turn open, and the exhaust bypass valve fully open.

Flow was noted after 58 seconds, closed LLCV valve, and 3 minutes later the exhaust bypass valve was closed.

Next over-fill = Wednesday, June 22nd.

Jenne, Rana, Haocun

We added filters to C/DHARD Pitch and Yaw loops to reduce low frequency noises.

These are low pass filters at 35Hz, as shown in the figure attached. We used same filters for CHARD and DHARD, and the noises from 30-100Hz were reduced by a factor of 10.

Nutsinee, Kiwamu, Alastair (remotely)

We have aligned the CO2 Y beam relative to the main interferometer beam. We are ready for various TCS tests again.

We aligned the beam by doing the same exercise as Aidan and Alastair did back in this February (25353). According to what Aidan calculated, the precision of the adjustment is about 20 mm which should be good enough (recall that the CO2 beam size is twice bigger than that of the main laser i.e. 100 mm or so in radius). We hooked up an analog function generator to the modulation input of the AOM driver which resides on the right hand side of the TCSY table. We drove it with an offset of 0.5 V and an amplitude of ~0.2 V at a frequency of 50 Hz. The frequency is chosen to be higher this time because the interferometer had higher noise floor below 40 Hz (dominated by CHARD control noises). We steered pico motor G which corresponds to a mirror on top of the periscope. After an iterative adjustment, we ended up with [x, y] = [-17500, 27000] in the pico motor readout. Note that these values are almost comparable to the previous adjustment by Aidan and Alastair. As a result of the alignment, the CO2 coupling to DARM increased roughly by a factor of 10 -- indicating a better overlap between the CO2 projection and the main interferometer beam.

Side note is that we saw a slow drift (with a small oscillation on a time scale of 10 min.) in the observed CO2 power during the adjustment in which the CO2 power monotonically kept decreasing by 10% or so over an hour or two. After unplugging the function generator, we also saw the power drifting back to the nominal power at a faster rate. A seemingly coherent behavior was visible yaw and pitch of QPDs A and B. No idea why.

The peak counts was ridiculously high for both HWSX and HWSY. I attached a screenshot of a streamed image below (don't remember which HWS this belongs to). Powercycled the camera and the frame grabber didn't help so I powercycled the hwsmsr computer. HWSY had trouble starting up so I reconstructed the reference (.mat) files.

TITLE: 06/20 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Corey
SHIFT SUMMARY:
LOG:

• 14:20 - Chris S to EX to check on wind fence settings.
• 15:17 - GRB (We are locked at INCREASE POWER 23.2W)
• 15:40 - Christina opening up OSB receiving door.
• 17:04 - Kiwamu to LVEA to recenter TCS CO2 Y
• 17:05 - Keita to LVEA to check ISS connections
• 17:16 Keita out
• 17:17 - Kiwamu to LVEA to transition to laser HAZARD and then open up TCSY table.
• 17:28 - Fil and student to CER mezzanine
• 17:37 - Fil and student out
• 18:05 - Jeff B to EY receiving area
• 18:55 - Kiwamu and Nutsinee to LVEA to change TCS setting
• 19:00 - Christina OSB rollup door, then to MY
• 19:20 - Jeff B back
• 19:32 - Christina, Karen leaving MY
• 19:52 - Nutsinee to LVEA?
• 20:30 - Keita to LVEA to work on ISS
• 20:36 - Kiwamu and Nutsinee out for lunch
• 21:19 - Gerardo to MX
• 22:02 - Jeff B to MY
• 22:05 - Kiwamu and Nutsinee to LVEA
• 22:17 - Jeff B from MY to MX
• 22:19 - Lockloss (~15 hr lock)
• 22:26 - Gerardo to MY to overfill CP3
• 22:55 - Gerardo back

The vacuum group is adjusting liquid levels in CP5. This activity will cause alarms from CP5.  These can be ignored for the next few days.

Peter, Jason, Jeff B.   

   Posted are the 7 day trends of the PSL chillers. The Diode chiller looks OK. The Crystal chiller circuit shows a steady rise in pressure and a decrease in flow. Temperatures in all four heads remain constant. There are some differences in the head flows, which are not yet understood. 

   These changes in flow and pressure start on 06/06/16 after (1) the inline filters were changed and (2) the site was recovering from a 3 day power outage.

   We are going into the PSL during the Tuesday maintenance window to check the plumbing system. I am monitoring the pressure, flow, and temperature on a daily basis.           

While we were centering WFSA and WFSB we discovered that adjusting the beam in pitch shows up as yaw on the WFS medm, and adjusting the beam in yaw shows up as pitch on the medm.

It's unclear how long this has been the situation.

   Attached are the OpLev trends for the past 7 days. SR3 Yaw has a bit of a downward trend, as does the ISI-HAM2 Yaw. ISI-HAM2 had a big bump up, but is back on trend line.  

Here are the past 10 day trends for the PSL. Things appear relatively normal in terms of the ongoing degradation of power as the diodes grow nearer to the end of their "lives". As always, further in depth analysis can be offered by Jason O. or Peter K. Chiller particulars are being closely monitored by Jeff B.

FAMIS# 4521

Presures look normal. The drop is  from the power outage.

SEI, SUS - Regular maint tomorrow.

Fac - Wind fence posts in, fabric on today.

Vac - CP5 acting up, ongoing investigation.

Clean - Move 2 crates with forklift tomorrow EY -> MY.

CDS - Cabling for BRS install, move power supplies in bier garten, minor maint issues, 5 more work stations in computer users room.

PSL - DBB work tomorrow.

The interferometer was stably locked at 25W (23.3W measured) for the last 4h, and all violin modes are damped to nothing (actually better than in O1).

Here is what I think we should do next:

- The one attempt going to higher power was unlocked by the Izumi-Ballmer instability at the main pendulum frequency. Time to mitigate that - ISS 3rd loop?

- The quick attempt in thermal tuning that Peter and I did suggested that we had too much central heating. We should nail down the optimal thermal tuning.

- Also, time to switch OMC_PD whitening and impedance back to low-noise.

Conor, Jeff K

Summary:
- Conversion of ISI Suspoint motion into the DoF basis works for the arms, with limited fidelity.
- Corner station DoFs seem not to work, possibly some problem with inclusion of the Beamsplitter.
- IPC communication between ISI and SUS at ETMY is spoilt somehow.

The GS-13s on stage 2 are used as witnesses for residual motion. Their outputs are calibrated to nm, and converted to suspension point motion using Euler matrices (Cart2Eul). The output is in the local suspension coordinates. For example, the channel 'H1:ISI-ITMX_SUSPOINT_ITMX_EUL_L_DQ' is the longitudinal motion of ITMX, which is along the normal vector pointing outward from the HR surface, in the global +X direction.

These suspension point motions are IPC'd to the OAF model, and in the case of the ETMs this involves some multiplexing/AI-filtering for communication down the arm. In OAF they are combined into the IFO degrees of freedom based on  T1500610 .

As a sanity check, I fetched the ISI-model Suspoint channels and matrix'd them into the IFO DoFs in Matlab, for comparison with the OAF DoF channels. For the arms (XARM, YARM, CARM, DARM), things seem to be somewhat okay. I confirmed this by eye, and then took the spectrum of the subtraction (attachment 1, CARM_Spectrum). The residual is consistent with the dynamic range of single-precision floats (about 10^9), at least at high frequencies. A quick software-only transfer function using four poles at 0.1Hz and white-noise injection in a spare filter bank shows a similar total dynamic range (attachment 2, DTT_dynamic_range). The anti-imaging filters, for transmission of the ETM signals along the arm, should allow a considerably smaller residual than we see at low frequencies, and I don't really know what else might cause this.

The corner station DoFs are substantially wrong, visible directly in the time series' (eg attachment 3, MICH_time_series). Since MICH only uses the ITMs (confirmed to be 'okay') and the Beamsplitter, presumably the difference arises there. PRCL and SRCL are similarly incorrect.

Document T1500610 has some minor errors in the Suspoint->IFO-basis definitions, but the current matrix has correct values as far as I could see. It also points to the Suspension model versions of the Suspoint motion, eg 'H1:SUS-ITMX_M0_ISIWIT_L_DQ', but the model uses the ISI versions. Initial testing revealed discrepancies between:
    'H1:ISI-ETMY_SUSPOINT_ETMY_EUL_L_DQ'
    'H1:SUS-ETMY_M0_ISIWIT_L_DQ'
visible in attachment 4 (ETMY_IPC_issue). The other 3 test masses didn't show this gross level of disparity.

Jenne, Nutsinee Sheila

We had trouble with locking the arm in IR for inital alingment, because PSL-POWER_SCALE_OFFSET was different from the input power.  We added a statement to the "IDLE" run state of LASER_PWR (the generator of states when not changing the power) that will adjust the normalization if it is more than 0.5Watts wrong. 

            if abs(ezca['PSL-POWER_SCALE_OFFSET'] - ezca['IMC-PWR_IN_OUTMON'])> 0.5:
                ezca['PSL-POWER_SCALE_OFFSET'] = ezca['IMC-PWR_IN_OUTMON']
 

After Sheila's log about the BS causing locklosses, I wanted to check a few things in the guardian code and I found what looks like conflict in the code. In /opt/rtcds/userapps/release/isi/h1/guardian/  ISI_BS_ST2.py, line 4

ISOLATION_CONSTANTS['CART_BIAS_DOF_LISTS'] = ([ ] , [ ])

the empty brackets at the end indicate the ISI is not set to restore any Cartesian locations.  This is supposed to be the code that sets what dofs are restored when the ISI re-isolates, and is particular to the beamsplitter.

However, in  /opt/rtcds/userapps/release/isi/common/guardian/isiguardianlib/isolation/ CONST.py lines 102 (for BSC ST1) and 122 (for BSC ST2) both read

            CART_BIAS_DOF_LISTS = ([], ['RZ']),

CONST.py is common code, and I would interpret this to mean that all BSCs are restoring a stored RZ location. This isn't a problem for the other BSCs, because they never change state, but if we turn on the ST2 loops for the BS, this code could force the ISI to rotate some after the loops come on. The attached trend shows the last ten days of the BS ST2 RZ setpoint and locationmon, and they track each other, so I dont think the BS is returning to some old RZ location, but someone who understands this code should explain it to me.

J. Kissel 
WP #5932

Today's model modifications come in three parts: 
(1) Independent Synchronized Oscillators for each isolation stage of the QUAD for calibration lines
(2) Updated CAL-CS model with better demodulation scheme that spits out coherence and uncertainty
(3) Changed all CAL-DELTAL and CAL-DARM channels to double precision and removed whitening
Below are all the details.

------------- Part (1)
In order push the PCAL vs. SUS actuation calibration line cancelling scheme for ER9/O2 forward (see T1600218 and T1600215), I've installed independent, longitudinal, synchronized oscillators in each of the UIM/L1, PUM/L2, TST/L3 stages of all of the QUAD models. See first attachment for screenshot of the QUAD OVERVIEW screen that now has the CAL_LINE block beneath every LOCK bank. Sadly, due to the recent split in QUAD library part models, I'd forgotten to add the needed EPICs channel for GPS synchronization to the ITMs. We'll install them tomorrow morning. 
I've committed the following new models: 
/opt/rtcds/userapps/release/sus/common/models/
Sending        FOUROSEM_DAMPED_STAGE_MASTER_WITH_DAMP_MODE.mdl    <-- Used in PUM/L2 stages
Sending        FOUROSEM_STAGE_MASTER_OPLEV_TIDAL.mdl              <-- Used in UIM/L1 stages
Sending        QUAD_MASTER.mdl                                    <-- Added EPICs record for GPS sync time on TST/L3 stage for ETMs

and accordingly modified MEDM screens:
M       SUS_CUST_QUAD_ITM_OVERVIEW.adl
A  +    SUS_CUST_QUAD_ISTAGE_CAL_LINE.adl
D       SUS_CUST_QUAD_L3_CAL_LINE.adl
M       SUS_CUST_QUAD_OVERVIEW.adl


------------- Part (2)
In addition, as a continuation of the improvements to using those calibration lines to track changes in the DARM loop parameters, I've followed Joe's instructions (see LHO aLOG 26491) and updated the CAL-CS model to demodulate PCAL and DARM error signals at given frequencies and produce parameter estimates, coherence estimates, and even uncertainty estimates. 

Darkhan will be working on commissioning the infrastructure with Joe.


------------- Part (3)
Finally, I've converted all of the calibrated DARM channels to double precision. *EXCEPT* for DELTAL_EXTERNAL, which is needed to display on the wall in the control room via DTT (which sadly, cannot yet handle double precision; see CDS Bug 1003).  

As a result, and as per Joe's advice I've turned OFF all dewhitening filters that condition the following (new) channels stored in the frames: 

H1:CAL-DARM_CTRL_WHITEN_OUT_DBL_DQ 
H1:CAL-DARM_ERR_WHITEN_OUT_DBL_DQ 
H1:CAL-DELTAL_CTRL_DBL_DQ  
H1:CAL-DELTAL_CTRL_PUM_DBL_DQ  
H1:CAL-DELTAL_CTRL_TST_DBL_DQ 
H1:CAL-DELTAL_CTRL_UIM_DBL_DQ  
H1:CAL-DELTAL_RESIDUAL_DBL_DQ  

We need to investigate if we're now happy with the signal fidelity without whitening or if we just need to re-assess the whitening. Again, I've retained single precision on H1:CAL-DELTAL_EXTERNAL_DQ, so its whitening filter remains ON.