WP6337 and WP6341 complete
h1guardian0 reboot
Dave restarted the h1guardian0 machine and all of the nodes came back up without issues. The machine updates have not shown any problems so far. Only thing to note is DIAG_MAIN now has a VERY long loop time that is caused by cdsutil calls to get some data via nds1. The average loop time was ~1sec and is now ~65sec. There have been other reports and issues that I have seen that make it seem as though the nds is feeding some bad data and also taking much longer than it used it. tw0 has been having some issues today, so perhaps it is related to that. I will investigate further when I can.
HPI_HAM testing
I found the easy bug, a comma left at the end of a line. Sadly, this led to a bigger bug. The length of the list of dofs that we had put in created a state that exceeds the 39 character limit for states. After talking with Jamie we decided to try to split up these dofs and see if that will work for now. We will probably try this out next Tuesday if we can.
Gerardo, Chandra
Completed WP 6342
Turns out the annulus ion pump was bad on HAM 11 (replaced in May 2016). R&R and also upgraded the controller to a brand-new, out of package unit. Now both HAM 11 & 12 are reading 4 mA! IPs were valved in w/ turbo aux cart reading 1e-5 Torr pressure at cart turbo (we also used a hung turbo). Turbo cart is OFF, but still connected.
Gerardo updated the PV assignments on HAM 11/12 and 7/8 by swapping wires at Beckhoff racks (they were backward before). Now what you see on MEDM is what you get.
Awesome team work!
(see WP6332) Also running turbo pump connected to PT180 hardware on dome of BSC8. Coordinating with PEM folks to see if the IFO commissioning community can live with this noise source for a few days. If so, we (Vacuum) would then bake the PT180 hardware while being valved-out from the YBM and while being pumped by these temporary pumps. Will be leaving these run past the official "Maintenance Day" period so as to see what these look like if/when the IFO is in low-noise. May need to do some "on/off" tests as per Robert S.
~1654 hrs. local -> De-energized all pumps (and fan) @ BSC8. Will restart tomorrow morning.
While at the End Station doing weekly fluid level checks, the HEPI tripped off due to a fluid level trip. Two Things:
1) I have the fluid level trip point set pretty close to the running level to keep the mess minimal in the event of a leak. 2) The pressure wash task of the roof ladder had the jar wide open with an air temperature, what, mid 30s?
I did just manage to record the fluid level before the trip and it was down 1/16". I surmise the cold air reduced the volume of the fluid enough to trigger the level switch.
I've lowered the trip point about 1/4" so this should not be an issue for some time, 1/16" was just a little too little head room. Let's keep the door as closed as possible in extreme weather.
The system recovered just fine.
I have increased the chilled water set points at both end stations to 43 degrees F. This is an increase of 4 degrees.
The /trend file system (a SSD RAID) became corrupted yesterday evening at 22:59 PST. This prevented raw trend data from being written and caused the daqd process to repeatedly restart all night. The file system has been repaired and the trend writer started again. The old raw minute trend data was being copied to h1fw0 at the time, and was close to half done. The copy operation will be cleaned up and resumed.
J. Oberling, P. King
We turned off the PSL Diagnostic Breadboard this morning, per LHO WP 6317. We turned off the control signals for the DBB PZTs in MEDM, then shut off power to the DBB. It will remain in this state for the duration of O2. This closes WP 6317.
I also took the opportunity to perform the weekly PSL power watchdog reset.
Kyle called to let me know he was going into VEA at EX and Gerardo and Richard are going in as well to do RGA work. As a pre-emptive move I disabled EY as well so as not to forgetlater if things get hectic.
TITLE: 11/22 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Ed
SHIFT SUMMARY: Quiet shift. Couple of small earthquakes. Observed the entire shift. Went to commissioning for manintenance activities.
LOG:
15:45 Ken drives to warehouse
15:35 Karen to EY
15:56 Kyle to EX
I have made a filters file for LHO that includes the most recent updates to DARM model and the EPICS values (see aLOG https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=31693 ). The filters were made using revision #3847 of the calibration SVN and can be found here: aligocalibration/trunk/Runs/ER10/GDSFilters/H1GDS_1163857500.npz Several plots are attached: 1) h(f) spectrum from CAL-CS and GDS 2) Ratio of spectra (GDS / CAL-CS) 3) Residual correction filter 4) Control correction filter
C. Cahillane ER10 Actuation uncertainty budget for LHO based on theN/cttransfer function measurements from November 8, 9, 11, 12, and 18th. To be clear, these measurements have the suspension models already divided out. Additionally, we only take measurement points for UIM up to 30 Hz, and PUM up to 100 Hz, since these are the only regions they have any actuation authority. We perform 4th order linear fits in the log(f) domain of the three actuation stages, UIM, PUM, and TST:Fit = ( a_0 + a_1 * log(f+1) + a_2 * log(f+1)**2 + a_3 * log(f+1)**3 + a_4 * log(f+1)**4 ) * exp(i * 2*pi*f*a_5 + i * a_6)The coefficients [a_0, ..., a_5] are the linear coefficients governing the magnitude of the fit. The coefficient a_5 is the time delay term, and a_6 is some phase offset. I fit the magnitude in the log(f+1) domain because the data is taken with logarithmic frequency spacing, and this gives the MCMC more freedom to fit the more-uncertain low frequency data points while constraining itself in the bucket. The plus one is solog(0 + 1) = 0and notlog(0) = -infinity, so at DC we don't explode our MCMC predicted results. I fit the phase in the linear f domain because exp(i* 2*pi*f*time_delay) is the typical expression for a time delay, and this seemed to be a sufficient fit given our data. There are two types of plots shown below: the corner plot and the measurement + fit + uncertainty results. There is one such plot for each stage. Plots 1, 2, and 3 are the UIM, PUM, and TST measurements + fit + uncertainty results. The shapes represent the ER10 measurement sweeps, the green line is the MCMC MAP fit, and each individual grey line is a potential fit according to the MCMC. The 1000 grey lines together form our uncertainty budget. Plots 4, 5, and 6 are the UIM, PUM, and TST fit corner plots. These show each parameter of the MCMC, its MAP value, and its 68% confidence interval in the title. The PDF of each parameter is shown along the diagonal, while the bulk shows the covariance of each parameter with one another. The names of each parameter is slightly different from my equation above:a_0 = H_{Stage} a_1 = alpha a_2 = beta a_3 = gamma a_4 = delta a_5 = tau (time delay) a_6 = phiIn comparison with LHO aLOG 31344, the DC coefficient values found were:H_UIM = 1.2 (+ 0.8 or - 0.7) * 10^-7 H_PUM = 6.8 (+ 1.5 or - 1.5) * 10^-10 H_TST = 4.0 (+ 0.2 or - 0.2) * 10^-12However, 4th order fits may not be the best method of finding the DC coefficient, since even a small change in value on the 4th order coefficient can have a huge effect on the 0th order coefficient. But for characterizing uncertainty in our actuation plant, this is the correct way since we don't in principle know the function we're fitting for. Overall Uncertainty:UIM Stage: < 3% magnitude and < 1 degree phase uncertainty PUM Stage: < 2% magnitude and < 1 degree phase uncertainty TST Stage: < 2% magnitude and < 1 degree phase uncertainty(All stages have their maximum uncertainty at low frequency.) This level of uncertainty is exceptionally tiny, even with 4th order polynomial fits. The great deal of measurements taken constrains the fit, lowering uncertainty drastically, especially in the bucket. Once we can account for time dependence, we may be close to achieving 5% and 5 degrees, depending on the sensing function uncertainty, or becoming kappa-limited.
Jeff, Darkhan, Kiwamu,
Looking at Craig's quad bode plots, we noticed that the data often showed large deviations in the data points at 38.3 Hz, especially in magnitude. We suspect that this is due to the fact that the DARM line at 37.3 Hz was not turned off during most of the measurements. While their separation is large and about 1 Hz, the DARM line can still influence our measurement because the integration time in the measurements was set to 1 sec which is not long enough to completely reject noise neighboring by 1 Hz. Out of 5 sets of the data that Craig processed, the Nov-18 data seems the only one which had the DARM line off. Indeed, the Nov-18 data shows a small deviation at 38.3 Hz.
A lesson we (re)learned today: Do not forget to turn off the calibration lines when running a swept sine measurement.
TITLE: 11/22 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Earthquake
INCOMING OPERATOR: Nutsinee
SHIFT SUMMARY:
Earth was still ringing at beginning of shift, but eventually made headway with locking. Transitioned to PEM injections for 2nd half of shift (until a lockloss). It has been 30+min and H1 has shown no issues with ASC (i.e. recycling gain worry Sheila mentioned)...this current lock I did not pause at NOISE_TUNINGS just to see if we could make it without having to wait for any cooling.
LOG:
Today we got a good start on PEM injections, injecting in the LVEA, PSL and the ebay, magnetic and acoustic injections. Tomorrow we plan to continue in the LVEA, more acoustic and magnetic and starting some shaker and possibly RF injections. Watch for cables on the floor if you go in the LVEA.
We seem to have a problem with our yaw ASC at 1.88 Hz. In several of our recent long locks we have had motion at 1.88 Hz in several of our ASC loops, and this occasionally causes locklosses. This caused a lockloss the first time we locked after todays earthquakes.
Keita looked at that lockloss, and saw that it shows up much more in ITMY than in the rest of the oplevs.
In the lockloss plot, it looks like the SOFT loops are ringing up, but this might be misleading because the signals are more quiet than other ASC signals.
Operators:
Over the first half hour or so after we increase power, the recycling gain continues to increase. It might be that we can only transition from POP WFS to REFL WFS after this has happened.
If you need to relock tonight, you can try runing through the gaurdian as is. If that doesn't work, I'd recomend waiting about a half hour at noise tunnings before switching over to REFL WFS and closing the beam diverters.
I made a DetChar safety study hardware injection using the Guardian infrastructure. From the schedule file (rev 5233): 1163822000 H1 INJECT_DETCHAR_ACTIVE 0 1.0 detchar/detchar_03Oct2015_PCAL.txt The injection was successful. To make this happen, however, I had to manually change the "dev_mode" in INJ_TRANS.py from False to True since the interferometer intent bit was not set. I reverted this change after the injection was successful. One minor note, from the Guardian log file, I got a warning, but I don't know if it is an issue: 2016-11-22T03:52:51.02490 Aborting Logging because SIStrLog call failed -1
Our operators have been running A2L a lot lately, so I've started looking at the spot positions that we infer from those measurements.
Sheila asked specifically for a comparison of our spot positions at DC readout versus NomLowNoise. I took the times from Cheryl's alog 31630, and Nutsinee's alog 31647 and plot the spot positions in the first plot. Yellow points are those from 19 Nov 2016, 00:30:00-00:01:00, and Purple are those from 19 Nov 2016 15:10:00-15:40:00. The Xaxis is labeled with the interferometer state at the time, DC readout or NomLowNoise. I think that Sheila may have done some alignment work (alog 31628) in between these times, which is why they're not consistent between these two locks. ITMY changes in a very different way between the two locks, but the rest of the optics and degrees of freedom at least move in the same way when we power-up, even if the start or stop positions aren't the same.
I have also plotted two times when our operators ran A2L several times over a single lock stretch. alog 31560 is from 17 Nov, and alog 31678 is from 21 Nov. The dates are in the figure names attached. As we had seen during O1, if the IFO is left alone, the spots on the test masses do not change with time very significantly. The Xaxes are hours from the first time A2L was run, back in October 2015, but you get the idea that each measurement is 60-90 minutes apart. I've zoomed the scales pretty significantly here, so note the Yaxes.
Finally, the last 2 plots are our spot positions since ER10 began on ~14 Nov 2016, and just the last few days, since our last big alignment work on Friday night. Once we stopped doing alignment work, we're becoming more consistent.
For Jeff: I also attach a .mat file with the spot positions in mm, along with the gps times of each measurement. The data is in 4x2 cells at each time:
| ITMX Pit | ITMX Yaw |
| ITMY Pit | ITMY Yaw |
| ETMX Pit | ETMX Yaw |
| ETMY Pit | ETMY Yaw |
TITLE: 11/22 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
Wind: 5mph Gusts, 4mph 5min avg
Primary useism: 0.15 μm/s
Secondary useism: 0.17 μm/s
QUICK SUMMARY:
Jim handed over an H1 just as he was starting to lock after the earthquake.
Making initial locking attempts (had to tweak the BS [in CHECK MICH FRINGES] & also PRM/BS in PRMI). Made it to DRMI had now troubleshooting why we drop out of DRMI Lock after a few minutes.
Will check out A2L lines in DC Readout & then aim to get to NLN.
J. Kissel, D. Tuyenbayev, K. Izumi, E. Goetz, C. Cahillane We have successfully updated the calibration in the front-end calibration. This means the static, frequency-dependent part of the low-latency calibration pipeline is ready to go for O2. Many thanks to all who've helped get this together in such short time. Kiwamu has updated the actuation side: see LHO aLOG 31687 I have updated the sensing side: see this aLOG below. Darkhan has updated the EPICs records that store the model at calibration line frequencies: see LHO aLOG 31696 These changes have been accepted in the CAL-CS SDF system. I always hate saying this statement because it comes without an uncertainty estimate and boils down a time-dependent, frequency dependent answer to a pair of numbers -- and DELTAL_EXTERNAL is limited by the accuracy of the front-end -- but I know people like to hear it, and it's a good, simple benchmark to hit: The resulting agreement between mean values of a swept-sine transfer function between the low-latency pipeline output, CAL-DELTAL_EXTERNAL and PCAL is roughly 2% and 2 [deg] for almost all frequency points between 10 Hz and 1.2 kHz. I was minutes away from finishing a broad-band PCAL injection so we can compare the output with the GDS pipeline to get the full answer, when the 6.9 [mag] Japanese EQ hit (see LHO aLOG 31694). We'll get this during the next lock stretch. We will be working on the uncertainty budget of the next coming days (but expect us to take a Thanksgiving break). We expect the time-independent, statisical uncertainty to improve beyond that of O1 but because they haven't happened yet, we can't make claims about the systematic errors that arise from uncorrected for time-dependence. This is especially true if the evidence for a changing SRC detuning spring frequency holds (see discussion in LHO aLOGs 31665 and 31667). %%%%%%%%%%%%%%% Details: %%%%%%%%%%%%%%% Actuation Function Again, see Kiwamu's aLOG for details on the updates to the actuation function: LHO aLOG 31687. Sensing Function I've updated the front-end's inverse sensing function to the parameters that are now used as the O2 reference measurements: [Units] value(95% c.i.) Meas Date 2016 Nov 12 IFO Input Power [W] 29.5 SRC1 Loop Status ON Optical Gain x 1e6 [ct/m] 1.153 (0.003) => Inv. Optical Gain = 8.673e-7 (2.255e-09) [m/ct] DARM/RSE Cav. Pole Freq. [Hz] 346.7 (4.1) Detuned SRC Optical Spring Freq. [Hz] 7.389 (0.3) Optical Spring Q-Factor (1/Q) [] 0.0454 (0.01) => Q = 22.015 (4.84) Residual Time Delay [us] 2.3 (3.4) => consistent w/ zero, so not included aLOG LHO 31433 The front-end implementation in foton is as follows: Bank: H1:CAL-CS_DARM_ERR Module Name Design String FM2 O2SRD2N zpk([346.7;7.2231;-7.5587],[0.1;0.1;7000],1,"n")gain(5458.55) FM3 O2Gain gain(8.673e-7) The bank is screen captured and attached, just in case SDF dies. Explanation for each component in the FM2 / O2SRCD2N filter: - 346.7 Hz zero is the inverse of the darm coupled cavity pole, as fit in LHO aLOG 31433. - 7.2231 and -7.5587 Hz zeros represent in inverse of the detuned optical spring. Because of the limitations of foton and the need for anti-spring-like response, we must convert the two positive zero frequencies and Q into a positive and negative zero (i.e. one in the real, one in the imaginary plane): f^2 (2*pi*i)^2 f^2 ---------------------------- = ---------- * --------------------------- f^2 - i*(f*f_s/Q) + (f_s)^2 (2*pi*i)^2 f^2 - i (f*f_s/Q) + (f_s)^2 (s = 2*pi*i*f ; c_s = 2*pi*f_s) s^2 = ------------------------ s^2 + s*(c_s)/Q - (c_s)^2 Zeros are the roots of >> 0 = s^2 + s*(c_s)/Q - (c_s)^2 1 ( (c_s) { ( (c_s) )^2 } >> s_{+/-} = --- ( - ----- +/- sqrt { ( ----- ) - 4 (1) (- (c_s)^2) } 2 ( Q { ( Q ) } 1 ( 2*pi*f_s { ( 2*pi*f_s )^2 } >> f_{+/-} = ----(- -------- +/- sqrt { ( -------- ) + 4(2*pi*f_s)^2 } 4*pi( Q { ( Q ) } f_s >> f_{+/-} = --- ( -1 +/- sqrt { 1 + 4 Q^2 } ) 2 Q For f_s = 7.389 Hz and Q = 22.015, that means the positive and negative zeros are at 7.2231;-7.5587 Hz, as shown in the design string. - The poles at [0.1;0.1;7000] are to artificially roll off the inverse response -- these are the same as they were in ER9. Remember the 7000 Hz pole distorts the response enough that this needs to be corrected for in the GDS pipeline. This CAL-CS design is not perfect. I've exported the design back into matlab and compared it against the model using /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/Scripts/CALCS/compare_model_v_CALCS_sensing.m and I attach the discrepancy. The discrepancy at high-frequency should be the same, since we've used the 7000 Hz pole to roll off the darm coupled cavity zero as in O1. The low frequency could use some correction. The DARM UGF is now around 65 Hz, where this sensing function discrepancy starts to matter. There, the phase discrepancy is 0.52 [deg] @ 65 Hz, and works its way up to 3.6 [deg] at 10 Hz. Thus, we don't expect too much impact at all, but it needs to be quantified. I'll discuss with the GDS team to see if such a correction filter is worth it or possible. All of the above actuation and sensing function parameters have been built into the matlab DARM loop model. From here on out, we'll be using the relative, time-dependent correction to make corrections to the model such that they match any new measurements.
Nicely done Team Calibration!