I noticed that the CW hardware injection excitation had stopped running at 15:47PDT Thursday 6/30. Using monit I have just restarted it.
State of H1: did not make it through Initial Alignment, Sheila and Jenne working on it
Activities:
listed in previous alog 28149
Since that alog:
Current Activities: Jenne and Sheila out to LVEA to measure MC open loop gain
h1iscex lost timing
Jim, Dave:
at 09:41 PDT h1iscex lost its timing sync. Possibly due to a power cord being moved which drives the independent DC powered timing slave in the IO Chassis. Models were restarted at 11:50 PDT.
h1susetm and h1omcpi new models
Jeff, Carl, Dave
New h1susetm[x,y] and h1omcpi models were installed. DAQ was restarted
New Vacuum Controls code
Patrick, Dave
New Vacuum controls Beckhoff code was installed at all 7 locations. Required a DAQ restart.
alog tiny font fixed
an entry made this morning set the font size to x-small. This was fixed.
Ready to upgrade h1fw0 to 10 GigE if it becomes unstable WP5985
Jim, Dave
If h1fw0 becomes unstable, we will upgrade its CDS-LDAS link from 1GE to 10GE using borrowed LDAS cards. The next time it crashes it will not restart. We'll wait until 4pm PDT and then allow a restart.
The code on each Beckhoff vacuum controls computer has been updated to incorporate the new PI controller. All of the cryopumps are back on PID control. TJ and I turned back on the ESD high voltage at end X and end Y. Dave has updated the DAQ. This completes WP 5972.
The PT100 cold cathode is no longer forced on. Since Gerardo changed the wiring it should no longer need to be. (alog 28024) I noticed that the PT110 cold cathode stays on whether or not it is requested to be. I can't recall if this was hardwired to remain on?
After Patrick installed the new PID loop controller and rebooted, I set the smoothing factor on all cryopumps to 0.999.
Fil has hooked up the End Y Illuminator to a power supply temporarily until he can get the Beckhoff system back up to control it. This was done at my request so our SURF students can continue working on the PCal Beam Localization project.
Ysled has been replaced. Below I attached a screenshot of the streamed images. The spare sled doesn't fit in the connector as well as the old one. The front part of the spare sled is slightly thicker. See pictures for details.
The dead sled number is 12.02.44 and the replaced spare is 07.14.264
Last week I disconnected TCS AOMs and the AOM drivers from water supplies but didn't have time to drain the hoses. Today I went in and finished the job. I left all the hoses on the tables except for one CO2Y AOM hose. The particulates wouldn't drain out and still stuck at the end of its quick connect. I don't think we ever want to plug that thing back in.
,
Here's what the table looks like now.
I also brought back a handful if particulate samples of anyone wants them.
J. Kissel I've completed the weekly charge measurements; results attached below. I've also flipped the ETMX and ETMY bias signs, as per our plan for testing if ISC and CAL can handle the collateral damage of mitigating charge in this fashion. For now, I've only flipped the bias, and am waiting to see if what we coded in to guardian two weeks ago (see LHO aLOG 27890) will take care of the rest of the settings changes that account for that flip. Just for clarities sake, since I *know* where gunna start losing track of which direction the bias was flipped -- today the biases were flipped as follows: ETMX from -9.5 [V] to +9.5 [V] ETMY from +9.5 [V] to -9.5 [V] Though we had originally intended to flip the bias signs every week, last week's maintenance was far too hectic so Betsy was only able to get charge measurements at the last minute on Wednesday (see LHO aLOG 28093), and Thursday was too hectic with calibration measurements (and the IFO was already locked when I remembered) that we forgot to flip the bias sign. So, we flip this week on schedule. As we have found when we'd done rapid flipping last summer, the charging rate after a sign flip is unpredictable. For example, though it's difficult to quantify with only two data points, between the last flip and today the charging rate is rather fast on ETMX (5 [V / week] as opposed to 2.5 [V / week] prior to the last flip). This is the sort of thing we need to keep an eye on, lest we again forget for a week, or the apparently-random-walking of charging rate starts, on average, bringing us to accumulate charge of a particular sign. This might also indicate that flipping the bias sign every two weeks (instead of every week) is better, given our frequency of charge measurements and the need to have several before establishing a trend.
As per alog entry 28145 a pair of diodes in the front end laser were MIA this morning. Suspect it was due to a faulty Beckhoff terminal as this terminal did not light up with the front end diode box on. We replaced the front end diode box and the corresponding module does light up. The SMA fibre connectors were all tweaked to maximise the diode power. The fibre connectors were examined with an infrared camera, typical temperatures were about 25-26 degC. The laser is up and running. Should be okay for the engineering run. We will need to tweak things after the run however. Jason, Peter
I forgot to mention that the relock counter for the injection locking was reset in Beckhoff. Currently reads at 1. Front end operating hours currently reads 32319 hours, even though the front end diode box is new.
Chris Whittle, Jenne, Jeff K Wanted to test methods of measuring ITM charge. We didn't have DARM to check, but the code for length drive charge measurements seems to work. This code (/ligo/svncommon/SusSVN/sus/trunk/QUAD/Common/Scripts/ESD_ITM_charge_measurement.py) measures the DARM response at various bias voltages and finds the TM charge as the zero crossing. We tried driving the ITMY ESD to see if we could do the same optical lever charge measurements as the ETM. We tried turning off UL and LL to get a yaw drive. Changing the voltage bias on the test mass resulted in no change in phase in the optical lever (as would have been expected). We also tried a pitch drive and single quadrant drive and saw the same lack of phase change. We need to confirm the mappings for the ESD quadrant switches. The SUS overview screen was inconsistent with the binary I/O screen. We also need to make sure that the analog switches are actually switching.
J. Kissel, D. Barker As Darkhan caught last week (LHO aLOG 28126), when we installed the new individual stage oscillators on the QUADs (LHO aLOG 27733), we neglected to store the excitation channels in the frames. Today, I've added those channels to the ETM QUAD master model, stored inthe science frames at 512 Hz, and restarted the SUS. Channels: H1:SUS-ETMY_LKIN_P_LO_DQ 512 H1:SUS-ETMX_L1_CAL_LINE_OUT_DQ 512 H1:SUS-ETMX_L2_CAL_LINE_OUT_DQ 512 H1:SUS-ETMX_L3_CAL_LINE_OUT_DQ 512 H1:SUS-ETMX_LKIN_P_LO_DQ 512 H1:SUS-ETMY_L1_CAL_LINE_OUT_DQ 512 H1:SUS-ETMY_L2_CAL_LINE_OUT_DQ 512 H1:SUS-ETMY_L3_CAL_LINE_OUT_DQ 512 Model Change to: /opt/rtcds/userapps/release/sus/common/models/QUAD_MASTER.mdl
As found, RGA was valved-in to Y-end -> Will take a few scans in an hour or so
I am short pwr supplies for the electronics so I had to de-energize the filamnet, i.e. leaving the configuration as found.
With the measured sensing function (28123) in hand, we did an MCMC-based numerical fitting for the sensing function (see E. Hall, T1500553).
The fitting results are
[New sensing function form]
As reported by Evan (27675), it seems that the extra roll off in the DARM response at low frequencies are due to an SRC detuning (or something equivalent). While such detuning should be suppressed by some control loop ideally, we decided to include the detuning-induced functional form in addition to the ordinary single-pole response. We use the following approximated form for the DARM response
S(f) = H / (1 + i f / fc ) * exp( -2 * pi * f * tau) * f^2/(f^2 + fs^2)
where H, fc, tau and fs are the optical gain, DARM cavity pole, time delay and spring frequency. Some details of the derivation will be reported later. Apparently, we now have an additional quantity (i.e., fs) to fit.
Note that since H1 seems to be in (unintentionally) an anti-spring detuning, fs should be a real number whereas it should be an imaginary number for a pro-spring case. Obviously, Q is set to infinity for simplicity.
[MCMC-based numerical fitting]
Following the work by Evan (T1500553), we adapted his code to include the spring frequency as well. In short, it is a Bayesian analysis to obtain posteriors for the parameters that we want to estimate. We gave a simple set of priors as follows for this particular analysis.
The quad plot below shows the fitting result. The estimated parameters are obtained by taking the mean values of the resutling probability distribution. As usual, the two plots on the left hand side show a bode plot of the measured and fitted data. The two plots on the right hand side show the residual of the fit. As shown in the residuals, there are several points which are as big as 20% in magnitude and 6 deg in phase below 10 Hz. Otherwise, the residual data points seem to be within 10-ish % and 4 deg. The code is attached in pdf format.
EDIT: I am attaching the actual code as well.
A detailed derivation of the new functional form can be found at https://dcc.ligo.org/LIGO-T1600278
EvanG noticed that we have unintentionally included high frequency poles in the previous analysis (28157). So we made the same fitting for the data with all the high frequency poles removed.
Here are the fitting results for the latest data:
Since the bode plot looks very similar to the one posted above, I skip showing it here. Observe that the time delay is now smaller than it was because we now don't have the high frequency poles.
C. Cahillane, K. Izumi I have added in a new term to our sensing function fit, an optical spring Q factor to gain back phase information. From the functional form f^2/(f^2 + f_s^2) we only get a magnitude correction from detuning, but we also expect detuning to slightly affect phase in the sensing function response. This can be clearly seen in lower right subplot Figure 1 of this comment, where Kiwamu originally plotted the full RSE sensing function. Here we see that when we have 1 degree of detuning we also have +1.5 degree phase difference at 10 Hz when compared to the sensing function without detuning. In the phase residual plot in the original post you can see this phase loss in the actual ER9 sensing measurement. In order to try and gain back some of this phase information, we have added in an additional term to the detuning function:f^2 f^2 ----------- ===> ----------------------- f^2 + f_s^2 f^2 + f_s^2 - i*f*f_s/QThis adds another parameter to our fit, but lets us get back phase information lost to detuning. ********** Figure 2 shows Kiwamu's original fit parameters posted above in red alongside my new results in green. I argue that including the optical spring Q factor has improved the phase fit significantly. Quantitatively, here are the phase Χ-Square values:With Optical Spring Q Χ-Square = 85.104 Without Optical Spring Q Χ-Square = 819.28********** I have modified Kiwamu's SensingFunction.ipynb into a SensingFunctionSimulation.ipynb which fits to both phase and magnitude of the sensing function. SensingFunctionSimulation.ipynb is attached as a zipped file in this aLOG and is also in a Git repo called RadiationPressureDARM owned by Kiwamu. Fit parameters:Optical gain = 9.124805e+05 +/- 8.152381e+02 [cnts/m] Cavity pole = 3.234361e+02 +/- 5.545748e-01 [Hz] Time delay = 5.460838e+00 +/- 3.475198e-01 [usec] Spring frequency = 9.975837e+00 +/- 5.477828e-02 [Hz] Spring Inverse Q = 1.369124e-01 +/- 3.522990e-03(I choose to parametrize using inverse Q = Q^{-1} because Q^{-1} can be zero.)
WP 5984--Addressing a couple month old bug, see SEI log 989 for details. Summary: We had added a condition to turn off Damping if a platform trips but this code is common for HEPI and the ISI and the HEPI does not have a damping state so there was an error. This was reverted and Friday Arnaud added a conditional to the code that excluded the HEPI from this action; it was tested at LLO. I've updated the python code and restarted all the HPI nodes--no impact to the platforms. See attached for keystrokes. WP closed.
Duh, of course since the code is common, I actually need to restart all the SEI and ISI guardians as well. This has been done and the platforms were not affected--thanks guardian programmers! And thanks to Arnaud for pointing this out to me. The txt file attached has the restart record.
Jeff K, Darkhan
Summary
Three DQ channels need to be added to the H1SUSETMY front-end model:
H1:SUS-ETMY_L1_CAL_LINE_OUT_DQ
H1:SUS-ETMY_L2_CAL_LINE_OUT_DQ
H1:SUS-ETMY_LKIN_P_LO_DQ
Details
SUSETMY model (both at H1 and L1) was updated to use synchronized oscillators to inject calibration lines into L1, L2 and L3 actuation stages to track temporal variations in the strengths of the drivers (LHO alog 27733). An additional calibration line is injected through Lock In oscillator (see attached screenshot 1).
In order to analyze time-dependent calibration of the drivers we need the excitation signals to be stored in the frames.
Hopefully, we will update the H1SUSETMY model on next Tuesday, Jul 5, 2016.
Darkhan suggests these are the channels to use:
TST / L3 35.3 0.11 H1:SUS-ETMY_LKIN_P_LO_DQ
PUM / L2 34.7 1.1 H1:SUS-ETMY_L2_CAL_LINE_OUT_DQ
UIM / L1 33.7 11.0 H1:SUS-ETMY_L1_CAL_LINE_OUT_DQ
With his help, for the pcalmon SLM pipeline looking at these "new" frequencies here,
https://ldas-jobs.ligo-wa.caltech.edu/~gmendell/pcalmon_new_freqs/daily-pcalmonNavigation.html
the configuration is now set to:
set channelFrequencyList {H1_R,H1:SUS-ETMY_LKIN_P_LO_DQ,35.3aup;H1_R,H1:SUS-ETMY_L2_CAL_LINE_OUT_DQ,34.7aup;H1_R,H1:SUS-ETMY_L1_CAL_LINE_OUT_DQ,33.7aup;H1_R,H1:CAL-PCALY_EXC_SUM_DQ,35.3aup,34.7aup,33.7aup,331.9aup;H1_R,H1:CAL-DARM_ERR_WHITEN_OUT_DBL_DQ,35.3aup,34.7aup,33.7aup,331.9aup;H1_R,H1:CAL-DARM_CTRL_WHITEN_OUT_DBL_DQ,35.3aup,34.7aup,33.7aup,331.9aup;H1_R,H1:CAL-PCALY_TX_PD_OUT_DQ,35.3aup,34.7aup,33.7aup,331.9aup;H1_R,H1:CAL-PCALY_RX_PD_OUT_DQ,35.3aup,34.7aup,33.7aup,331.9aup;H1_R,H1:CAL-DELTAL_EXTERNAL_DQ,35.3aup,34.7aup,33.7aup,331.9aup;H1_HOFT_C00,H1:GDS-CALIB_STRAIN,35.3aup,34.7aup,33.7aup,331.9aup}
I've regenerated the SLM data for July 1. The suggested channels above do not yet exist, and SLM will put 0's in for these until they do.
These new channels has now been added to the frames. See LHO aLOG 28156
J. Kissel, J. Driggers, T. Shaffer, D. Tuyenbayev, E. Goetz, K. Izumi Over two ~1-2 hour lock stretches, I've managed to get the measurements needed for a baseline calibration update for ER9. Complete success! We'll work on the data analysis tomorrow, but I list the locations where all measurements have been committed to the CAL repo below. Of particular notes for the configuration of the IFO while doing these measurements: - The OMC DCPDs have *no* stages of whitening employed. We've decreed that given the unknown success rate of PI damping over the next few days, it's more robust to leave the whitening off. We're not gaining too much in the high frequency end of the sensitivity anyways. - All suspensions, including ETMY, have had their PUM stage switched to "Acq ON, LP OFF," i.e. state 2, or the highest range (i.e. not low noise). After some digging, Jenne found this was changed for some reason about a month ago, and maybe a setting that got lost in the power outage or something. I don't think either of these seemingly detrimental configurations are all that bad for ER9, given the bigger sensitivity issues elsewere. Also note, in order to break the correlations we've found in O1 data between measurements of Actuation Stage Strength (see e.g. LHO aLOG 28096), I've taken an independent PCAL2DARM sweep for every isolation stage. Measurements needed for Sensing Function: /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER9/H1/Measurements/PCAL/ 2016-07-01_H1_PCAL2DARMTF_4to1200Hz_SRCTuned.xml Exported as: 2016-07-01_PCALY2DARMTF_4to1200Hz_A_PCALRX_B_DARMIN1_coh.txt 2016-07-01_PCALY2DARMTF_4to1200Hz_A_PCALRX_B_DARMIN1_tf.txt /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER9/H1/Measurements/DARMOLGTFs/ 2016-07-01_H1_DARM_OLGTF_4to1200Hz_SRCTuned.xml 2016-07-01_H1_DARM_OLGTF_4to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKIN1_tf.txt 2016-07-01_H1_DARM_OLGTF_4to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKIN1_coh.txt 2016-07-01_H1_DARM_OLGTF_4to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKEXC_tf.txt 2016-07-01_H1_DARM_OLGTF_4to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKEXC_coh.txt Measurements needed for Actuation Function: /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER9/H1/Measurements/FullIFOActuatorTFs/ 2016-07-01_PCALYtoDARM_FullLock_L1.xml 2016-07-01_H1SUSETMY_PCALYtoDARM_ForL1Drive_FullLock_tf.txt 2016-07-01_H1SUSETMY_PCALYtoDARM_ForL1Drive_FullLock_coh.txt 2016-07-01_H1SUSETMY_L1toDARM_FullLock.xml 2016-07-01_H1SUSETMY_L1toDARM_State1_FullLock_tf.txt 2016-07-01_H1SUSETMY_L1toDARM_State1_FullLock_coh.txt 2016-07-01_PCALYtoDARM_FullLock_L2.xml 2016-07-01_H1SUSETMY_PCALYtoDARM_ForL2Drive_FullLock_tf.txt 2016-07-01_H1SUSETMY_PCALYtoDARM_ForL2Drive_FullLock_coh.txt 2016-07-01_H1SUSETMY_L2toDARM_FullLock.xml 2016-07-01_H1SUSETMY_L2toDARM_State2_FullLock_tf.txt 2016-07-01_H1SUSETMY_L2toDARM_State2_FullLock_coh.txt 2016-07-01_PCALYtoDARM_FullLock_L3.xml 2016-07-01_H1SUSETMY_PCALYtoDARM_ForL3Drive_FullLock_tf.txt 2016-07-01_H1SUSETMY_PCALYtoDARM_ForL3Drive_FullLock_coh.txt 2016-07-01_H1SUSETMY_L3toDARM_LVLN_LPON_FullLock.xml 2016-07-01_H1SUSETMY_L3toDARM_LVLN_LPON_FullLock_tf.txt 2016-07-01_H1SUSETMY_L3toDARM_LVLN_LPON_FullLock_coh.txt
J. Kissel, E. Goetz Just to post a status report before I disappear for the 4th, Evan and I have used Evan's new infrastructure to produce a model of the DARM open loop gain and sensing function from the above measurement. As one can see, there's still some work to do cleaning up the systematics in the model, but we're close. There're several things that are immediately evident: - We have not changed the model's optical gain value from O1, so it's not terribly surprising that the optical gain model is high by 20%. - There is total and obvious detuning. So much so, that I think this is what's causing the severe drop in open loop gain. - The drop in open loop gain is pretty nasty -- it causes sharp gain peaking at 10 Hz (as shown by the screenshot of the DTT template). Kiwamu's working on a fitting routine that is similar to Evan's MCMC results from O1 (see T1500553), but advancing those results to include the effects of detuning so that we can add this to the model. Stay tuned! Lots of work to do before Wednesday!
Evan G., Jeff K.
I processed the suspension actuation coefficients for the L1, L2, and L3 stages using the preliminary DARM model based on the one used during O1. We know that there need to be some modifications made, but the take home message here is that the actuation coefficients are about as to be expected. All are within ~5% of their O1 values. See attached figures.
The first attachment shows the UIM stage actuation coefficient. We have not yet included the BOSEM inductance and we have not yet included any actuator dynamics, so there is remaining discrepancy above ~20 Hz. There also appears to be some sort of phase wrapping issue that we still need to sort out.
The second attachment shows the PUM stage actuation coefficient. Things look pretty good here, although there may be some fluctuating optical gain which we have not yet accounted for in the measurement.
The third attachment shows the TST stage actuation coefficient. Again, there may be some fluctuating optical gain not accounted for in the measurement, and there is a phase wrapping issue to be sorted out.
Next on the agenda is to sort out the above issues and establish the actuation coefficients for the ER9 run.
The sensing function attached above includes uncompensated high frequency poles from the whitening chassis and the transimpedence amplifier, so there will be some delay assocated with these values.
To see only the optical response, we have removed these high frequency poles, as well as the analog AA and digital AA transfer functions, in the attached data file.
J. Kissel
Summary
We're adding three new calibration lines around 30 Hz on the ETMY actuation stages in order to narrow down the uncertainty in actuation strength independently for each stage. Depending on the success of their analysis, and interference with IFO operations, we'll decide whether to leave them on for ER9. We may also push further forward with cancelling these lines with the Y-end PCAL, but for now, I turn them on without cancelling for the week prior to ER9. We may also push further forward an cancel these lines with the Y-end PCAL, but for now, I turn them on without cancelling for ER9.
Motivation
Recall that during O1, H1 had a static, ~2% systematic error in the collective actuation strength ("kappa PU"), narrowed down using cumulative integration time allowed for by the overall DARM loop line coupled with the ESD-only line (see e.g. LHO aLOG 24569 or LHO aLOG 25031). We intend to differentiate between the strength of the upper stages for the future, using their constant presence to bring the uncertainty in relative actuation strength to be essentially zero. Once we cancel these lines with PCAL, that'll bring the absolute calibration uncertainty to essentially zero.
Line Details
For now, without the man-power for further study of their "optimal" location, I've just stolen L1's ~30 Hz calibration line frequencies from O1 (see original source T1500377), given that they'll not be involved in ER9. The details of the new lines are:
Isolation Stage Frequency Amplitude Oscillator Channel
TST / L3 35.3 0.11 H1:SUS-ETMY_L1_CAL_LINE
PUM / L2 34.7 1.1 H1:SUS-ETMY_L2_CAL_LINE
UIM / L1 33.7 11.0 H1:SUS-ETMY_LKIN_P_OSC
These new values have been accepted into the DOWN and SAFE SDF files.
This is in addition to the "normal" calibration lines from O1 that will still be on such that we can replicate the O1 calculation without extra effort.
On the TST / L3 stage, we now have *two* calibration lines, and this is such that we can still reproduce the O1 calibration line, time-dependent parameter tracking without changing anything. However, because we're not yet confident enough in the PCAL cancelling scheme for it to completely replace the O1 method, and we haven't installed / replaced any infrastructure. Thus, for now, I've stolen one of the Optical Lever Lock-in Oscillator and piped it out to the DAC output as a longitudinal drive using the LKIN2ESD matrix.
The above aLOG entry has some very confusing typos. Here's what I actually meant (and now includes the swap because of the need for synchronized oscillators -- see LHO aLOG 28086): Isolation Stage Frequency Amplitude Oscillator Channel TST / L3 35.3 0.11 H1:SUS-ETMY_L3_CAL_LINE PUM / L2 34.7 1.1 H1:SUS-ETMY_L2_CAL_LINE UIM / L1 33.7 11.0 H1:SUS-ETMY_L1_CAL_LINE And to replicate the O1 calibration line scheme: Isolation Stage Frequency Amplitude Oscillator Channel TST / L3 35.9 0.11 H1:SUS-ETMY_LKIN_P_OSC
will keep h1fw0 running overnight. the 4pm deadline passed, all daq systems have been running for 3 hours now. Reminder, difference now is that two 64kHz channels have been removed from the commissioning frame, six 512Hz channels added to science frame.