Dan, Cheryl, Evan

Sometime after 6 am local yesterday, we lost the ability to have stable locks with full input power.

It's not clear what about the interferometer changed, but the symptom again seems to be a slow drift of the AS36→SRM yaw loop which causes a sudden lockloss after a few minutes at full power.

In the end we simply retuned the input matrix elements for this loop in order to keep AS90 and POP90 from drifting downward at high power.

Before, the matrix elements were

ASA36I→SRC1: −3

ASB36I→SRC1: +1,

and now they are

ASA36I→SRC1: −3

ASB36I→SRC1: +0.5.

This combination was not chosen particularly carefully, but it is good enough to get to high power. We may want to see if there is a better combination.

The attachment shows the behavior of the four AS36 signals during power up and the subsequent full-power lock.

10 day plot of dust at EY - do we know why EY is so dusty?

Annoying dust alarm at EY silenced with alarm level changes:

- old: 2000 (yellow, dashed line), 3000 (red dahsed line), note that EY routinely goes above these alarm levels

- new (not saved but running tonight): 5000 (yellow solid line), 10000 (red solid line)

Jenne, Sheila, Terra, Cheryl, Corey

Tonight we worked on some ASC (the wind was gusting to 30mph when we started this, the IFO locked just fine but the buildups were fluctating at low frequencies).  At first we wanted to check on CHARD.  We increased the gain for CHARD P by 6dB, and then were able to add a gentle boost (the same MSboost used in DHARD) to increase the gain at low frequencies.  The attched screenshot and template were measured at 3Watts, with the new configuration (which is in guardian) and the ITM oplevs on.  For an old measurement taken at 23 Watts see Evan's alog 19934

Jenne did a similar job for yaw, adding the same gentle boost, and including the 20dB in the guardian. Both the pitch and Yaw loops could have ugfs below 1 Hz as the power increases, but they should be stable.

Once we increased the power to 24 Watts, we found we weren't stable for more than 5 minutes.  This happened both before and after the CHARD changes.  We ran Hang's lockloss script which picked MICH ASC loops as a suspicous channel.  We locked at 15 Watts were we seemed to be indefintely stable, and measured both MICH loops.  They look fine, I'm just attaching them here so we have the templates. 

Travis, Sudarshan

We calibrated the EndY photon calibrator today. We have started reporting the final calibration factors in Newtons/Volt of PD  readout as per our new calibration scheme detailed in alog # 20334. The new calibration factors compared to the the last calibration is tabulated below and is also uploaded to T1500252.

A detail comparison that includes physical parameters, intermediate ratios, optical efficiency  is attached.

• Started off the shift watching TJ working on bringing back up H1 post-Maintenance.
• Have made several attempts to get H1 locking (although it was dropping out at various points.)
• Given walk-thru of Lockloss templates by Jenne & also Hung's Lockloss tool
• Commissioners team have continued working on getting H1 back up.

Locates at SITEMAP > SUS > VIOLINS. This monitor simply turns the log RMS output of the violin monitor into a bar chart. One bar chart monitors two frequencies due to the lack of filter bank space (only those that have known to cause trouble get its own narrow BP filter). Low value is 0 and high is 4. The green marks indicate the violin (RMS) amplitudes after 10 minutes of a lock stretch. Healty violin modes shouldn't go pass the green marks and some should get better as time passes. More fine-tuning can be done but it's good for now. I will put in the first harmonics once we know more about them.

Roughly from last night (5:00UTC [10pmPT]), EY has been steadily increasing in dust levels (and obviously alarming constantly the whole time).  0.3um counts are over 10,000.  No other VEAs are seeing an increase in dust like this building.  I don't see a temperature increase.  Could a door be open?  HVAC issue?  Something burning? 

(Will send an email to Bubba, Jeff B, John)

J. Kissel, for the locking recovery team (S. Dwyer, J. Driggers, B. Weaver, J. Warner, T. Shaffer, C. Gray, K. Kawabe)

During the heat of battle, today's maintenance day seem no less chaotic than the past month of horrific Teusdays. However, all being said, we were able to recover the IFO to DC READOUT by 23:30 UTC (4:30p PDT). The commissioning team has decided to stay in DC READOUT for further work on the ASC system for stability further up the guardian state ladder, so they consider the IFO recovered. (This does mean we have not yet confirmed that we can completely recovered the ~60-70 MPC IFO, but we have no evidence to suspect that today's maintenance activities have spoiled the *noise* of the instrument).

The biggest problems / time sucks and lessons learned from today:
(a) (30 minutes) (10:15 - 10:45) After the ASC model restart, we found the EPICS settings for unmonitored channels in SDF system had setting that meant the ASC was blasting the suspensions with non-sense. LHO aLOG 20442
(b) (30 minutes) (12:15 - 12:45) Communication issues between small side commissioning projects cause the IMC to go into high power with lock/unlock oscillations. (no aLOGs yet)
(c) (2 hours) (12:55 - 14:55) Discovering the the ASC output matrix had been reshuffled in the model but not on the MEDM screen, so we were feeding green WFS control to the wrong suspensions. LHO aLOG 20433.

Also it didn't cause a loss in recovery time, but they did cause greater confusion for the recovery team and expose that we still have a failure of communication:
(d) TMSX satellite amp repair was not planned, nor was the operator or relocking team informed that it was happening while it was happening LHO aLOG 20448.

Regarding (b) and (d), the intent is not to further shame or embarrass anyone (and apologies if it does, no offense is meant). The point is to remind you that the relocking team is here to help you. If you have a commissioning or repair task that needs doing, tell us ahead of time (the Monday prior, preferably, but at least a few hours in advance), so we can coordinate your task with all other tasks that we know will be going on. We've worked hard to make sure we know everything that is planned to better help those activities succeed. If you tell us ahead of time, we have a chance to think about the broader impact, and can hopefully avoid collisions, and reduce recovery time. Our experience and the interferometer has informed us that no matter how little impact you think your commissioning or repair task will have, it will have an impact on the IFO or someone else's little commissioning/repair task, so let's work together to minimize it!

We are getting better at this, thank you for everyone's hard work and help.

JeffreyK, Darkhan

To test new GDS pipeline that estimates DARM parameters kappa_{tst}, kappa_{p/u}, kappa_C and f_c we've updated reference values that were calculated from ER7 model (see LHO alog #20291 for earlier values).

New values entered for ESD line at 35.9 Hz are

H1:CAL-CS_TDEP_ESD_LINE1_REF_C_REAL 1.2896e+06
H1:CAL-CS_TDEP_ESD_LINE1_REF_C_IMAG -189585
H1:CAL-CS_TDEP_ESD_LINE1_REF_C_NOCAVPOLE_REAL 1.30877e+06
H1:CAL-CS_TDEP_ESD_LINE1_REF_C_NOCAVPOLE_IMAG -59171.7
H1:CAL-CS_TDEP_ESD_LINE1_REF_D_REAL 8.8387e+09
H1:CAL-CS_TDEP_ESD_LINE1_REF_D_IMAG 1.12814e+10
H1:CAL-CS_TDEP_ESD_LINE1_REF_A_TST_REAL -4.38814e-17
H1:CAL-CS_TDEP_ESD_LINE1_REF_A_TST_IMAG -3.39859e-17
H1:CAL-CS_TDEP_ESD_LINE1_REF_A_PUM_REAL -2.61782e-17
H1:CAL-CS_TDEP_ESD_LINE1_REF_A_PUM_IMAG 4.21051e-17
H1:CAL-CS_TDEP_ESD_LINE1_REF_A_UIM_REAL -5.14962e-21
H1:CAL-CS_TDEP_ESD_LINE1_REF_A_UIM_IMAG -2.34929e-21
H1:CAL-CS_TDEP_ESD_LINE1_REF_OLG_REAL -1.05327
H1:CAL-CS_TDEP_ESD_LINE1_REF_OLG_IMAG -0.791652

for PCALY line at 36.7 Hz:

H1:CAL-CS_TDEP_PCALY_LINE1_REF_C_REAL 1.28869e+06
H1:CAL-CS_TDEP_PCALY_LINE1_REF_C_IMAG -193725
H1:CAL-CS_TDEP_PCALY_LINE1_REF_C_NOCAVPOLE_REAL 1.30872e+06
H1:CAL-CS_TDEP_PCALY_LINE1_REF_C_NOCAVPOLE_IMAG -60499.8
H1:CAL-CS_TDEP_PCALY_LINE1_REF_D_REAL 8.99945e+09
H1:CAL-CS_TDEP_PCALY_LINE1_REF_D_IMAG 1.15726e+10
H1:CAL-CS_TDEP_PCALY_LINE1_REF_A_TST_REAL -4.2798e-17
H1:CAL-CS_TDEP_PCALY_LINE1_REF_A_TST_IMAG -3.22538e-17
H1:CAL-CS_TDEP_PCALY_LINE1_REF_A_PUM_REAL -2.41611e-17
H1:CAL-CS_TDEP_PCALY_LINE1_REF_A_PUM_IMAG 4.01322e-17
H1:CAL-CS_TDEP_PCALY_LINE1_REF_A_UIM_REAL -4.53934e-21
H1:CAL-CS_TDEP_PCALY_LINE1_REF_A_UIM_IMAG -1.9945e-21
H1:CAL-CS_TDEP_PCALY_LINE1_REF_OLG_REAL -1.03047
H1:CAL-CS_TDEP_PCALY_LINE1_REF_OLG_IMAG -0.772912

for DARM line at 37.3 Hz:

H1:CAL-CS_TDEP_PCALY_LINE1_REF_OLG_IMAG -0.772912
H1:CAL-CS_TDEP_DARM_LINE1_REF_C_IMAG -196826
H1:CAL-CS_TDEP_DARM_LINE1_REF_C_NOCAVPOLE_REAL 1.30868e+06
H1:CAL-CS_TDEP_DARM_LINE1_REF_C_NOCAVPOLE_IMAG -61495.8
H1:CAL-CS_TDEP_DARM_LINE1_REF_D_REAL 9.12151e+09
H1:CAL-CS_TDEP_DARM_LINE1_REF_D_IMAG 1.17888e+10
H1:CAL-CS_TDEP_DARM_LINE1_REF_A_TST_REAL -4.19953e-17
H1:CAL-CS_TDEP_DARM_LINE1_REF_A_TST_IMAG -3.10345e-17
H1:CAL-CS_TDEP_DARM_LINE1_REF_A_PUM_REAL -2.2773e-17
H1:CAL-CS_TDEP_DARM_LINE1_REF_A_PUM_IMAG 3.87215e-17
H1:CAL-CS_TDEP_DARM_LINE1_REF_A_UIM_REAL -4.13563e-21
H1:CAL-CS_TDEP_DARM_LINE1_REF_A_UIM_IMAG -1.76881e-21
H1:CAL-CS_TDEP_DARM_LINE1_REF_OLG_REAL -1.01416
H1:CAL-CS_TDEP_DARM_LINE1_REF_OLG_IMAG -0.759088
H1:CAL-CS_TDEP_DARM_LINE1_REF_A_USUM_INV_REAL -1.12869e+16
H1:CAL-CS_TDEP_DARM_LINE1_REF_A_USUM_INV_IMAG -1.91871e+16

for PCALY line at 331.9 Hz:

H1:CAL-CS_TDEP_PCALY_LINE2_REF_C_REAL 373718
H1:CAL-CS_TDEP_PCALY_LINE2_REF_C_IMAG -890155
H1:CAL-CS_TDEP_PCALY_LINE2_REF_C_NOCAVPOLE_REAL 1.20595e+06
H1:CAL-CS_TDEP_PCALY_LINE2_REF_C_NOCAVPOLE_IMAG -540755
H1:CAL-CS_TDEP_PCALY_LINE2_REF_D_REAL 7.75468e+10
H1:CAL-CS_TDEP_PCALY_LINE2_REF_D_IMAG -8.57657e+09
H1:CAL-CS_TDEP_PCALY_LINE2_REF_A_TST_REAL -9.24752e-19
H1:CAL-CS_TDEP_PCALY_LINE2_REF_A_TST_IMAG -1.86072e-19
H1:CAL-CS_TDEP_PCALY_LINE2_REF_A_PUM_REAL 1.11411e-19
H1:CAL-CS_TDEP_PCALY_LINE2_REF_A_PUM_IMAG 1.83559e-19
H1:CAL-CS_TDEP_PCALY_LINE2_REF_A_UIM_REAL -2.19997e-26
H1:CAL-CS_TDEP_PCALY_LINE2_REF_A_UIM_IMAG -3.04968e-27
H1:CAL-CS_TDEP_PCALY_LINE2_REF_OLG_REAL -0.0175432
H1:CAL-CS_TDEP_PCALY_LINE2_REF_OLG_IMAG 0.0586971

kappa_tst correction factor (- 1 / A_0^tst(f_tst)) * (C_0(f_pcal) / (1 + G_0(f_pcal))) * (C_0(f_tst) / (1 + G_0(f_tst)))^{-1} is

H1:CAL-CS_TDEP_REF_INVA_CLGRATIO_TST_REAL 1.425e+16
H1:CAL-CS_TDEP_REF_INVA_CLGRATIO_TST_IMAG -1.17617e+16

and A(f_ctrl) correction factor (C_0(f_pcal) / (1 + G_0(f_pcal))) * (C_0(f_ctrl) / (1 + G_0(f_ctrl)))^{-1} is

H1:CAL-CS_TDEP_REF_CLGRATIO_CTRL_REAL 1.425e+16
H1:CAL-CS_TDEP_REF_CLGRATIO_CTRL_IMAG -1.17617e+16

Most of these new values have been accepted in SDF_OVERVIEW table. Some of the values (that are very small) show difference in SDF even after "accept"+"confirm".

Notice that in the A_TST, A_PUM, A_UIM for ESD line (at frequency f_tst) include time delays due to IOP error checking (3 IOP cycles) + IOP computation (1 * IOP cycle) + zero order hold delay (0.5 * IOP cycle), but does not include 1 SUS computation cycle time delay (that was included into respective quantities for other cal lines). This means that when calculating kappa_{tst} in GDS pipeline (see eq. 9 in T1500377-v6), there is no need to account for time delay when using X_tst signal. Other values C, OLG and (G used for CLGRATIO calculations) include full time delays associated with sensing and actuation.

Eric and Jim Batch

Eric wrote to Jim on Aug 10:

The ability to access EPICS channels appears to have disappeared at LHO when connected to h1hwinj:

[hinj@h1hwinj1 eric.thrane]$ ezcaread H1:CAL-INJ_TINJ_STATE
channel H1:CAL-INJ_TINJ_STATE not accessible

However, the same command works fine from cdsssh:

eric.thrane@cdsssh:~$ ezcaread H1:CAL-INJ_TINJ_STATE
H1:CAL-INJ_TINJ_STATE = 1

This problem appears to have occurred after ER7 since we would have seen errors during transient injections otherwise. Your assistance would be greatly appreciated.

Jim wrote back on Aug 11:

The problem has been resolved.  An update turned on some rather restrictive network filtering.

Charge measurements was done on both ETMs.
It is the first measurements after changing the bias sign on ETMY (changed Aug, 10 (alog 20410), history and motivation in 20387).
Results are in attachment. Too early to discuss the new tendencies.

V. Sandberg & R. McCarthy

The SUS-TMSX OSEM Satellite Box was driving a ~2kHz oscillation on its DC power line again. (See https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=20428) This time we replaced the satellite box.  Verified that H1:SUS-TMSX_M1_OSEMINF_RT_IN1 and H1:SUS-TMSX_M1_OSEMINF_SD_IN1 were behaving themselves.  Work was done during the interval 18:00 - 18:45 UTC (11:00am - 11:45am PDT).

Apologie: I failed to follow my own rules and neglected to notify the operator on duty before we left and changed out the satellite box at End X.  Shame and humiliation duly noted.  :-(  Fortunately, no damage was done.

We made a state a week or so ago that offloads the ASC in full lock to the alingment sliders.  This offloads the top mass of every optic that we control with ASC (except PR3) to the alignment sliders.  We are not offloading PR3 since it moves so much due to wire heating.  

We've tried this a few times and it works and we are able to relock afterwards, so I've added it to the main guardian path, ater the transition to DC readout.  

h1susex re-install original computer WP5430

Dave, Carlos, Jim:

The original h1susex front end computer was re-installed at EX to fix the glitching seen with the newer faster computers. The script which was clearing the EX glitch errors has been stopped, any FEC errors will now latch on until cleared by the operator.

h1tcscs model change WP5422

Duncan, Nutsinee, Dave:

The new L1 TCS model was installed on h1tcscs. A new TCS_MASTER.mdl was used. The h1tcscs.mdl file was modified to: add the ez_ca_read parts to get TCS CO2 and Ring Heater channels from the Beckhoff computers (corner and end stations) into the model; add new inputs to the CO2 parts for RH input; add ODC output from the CO2 parts; add new ODC block; add SHMEM ODC sender (to be injested by h1odcmaster model).

I discovered that there is a naming mis-match in the Beckhoff Ring Heater channels in the corner station slow controls system. There is no mismatch in the end station Beckhoff systems. I modified h1tcscs use use the H1 names.

Conlog channel reconfiguration

Dave:

After the TCS, CAL and ASC model changes I rescanned the channel lists for Conlog. It still showed a disconnection for the Guardian LSC_CONFIG node, which I tracked down to a very out-of-date autoBurt.req file for h1guardian0 target. I updated the autoBurt.req file and reconfigured Conlog, it is now happy.

H1LSCAUX filter coeff load

Dave:

The h1lscaux model was reporting a modified filter file. I took a look and could not see any difference between the current file and the archived file. I pushed the coeff-load button to clear this.

DAQ Restart

Dave:

After the TCS, CAL and ASC model changes, the DAQ was restarted. There were no GDS frame broadcaster changes made today (ECR is pending).

• SR3 20 Hz elliptic LPF (for M2 oplev coupling) was replaced with a more gentle 8 Hz LPF with slightly less attenuation in the stopband, but more attenuation around 20 Hz. [Attachment.] This was done without knowledge of the SR3 oplev OLTF, so it is possible we can design a more aggressive filter.
• dHard pitch gain is turned up by a factor of 2 (to 20 ct/ct), since it seems like it is able to kill that abominable 1 Hz pitch oscillation.
• cHard pitch gain turned down by 20 dB (by turning on FM1), and a 9 Hz LPF is engaged to kill angular control noise that can be seen in DARM between 10 and 20 Hz.