The operator reported issues with the remote access control system. It was repeatedly asking for his credentials. I was able to walk him through adding a user to the system so that he could get some help brining with the IFO. I also was granted access. I restarted the apache instance on cdsadminctrl after reproducing the operators issue. This appears to have solved the issue. Apache was not able to negotiate the authentication. Cause currently unknown. I've opened an FRS to remind me to look at it in the morning. See FRS https://services.ligo-la.caltech.edu/FRS/show_bug.cgi?id=7677
Violin modes seem very high on DARM spectrum so I had a quick look at the damping screens. It appears that many of the filter banks (especially ETMs) have 0 input and 0 output. I also checked with the fast channels and dtt. The input seems nonzero on dtt but the output has nothing. As the result, some of the violin modes are not being damped right now. Hope it stays through the night until somebody comes in and fix this tomorrow.
This is an issue with the intermediate foton, referenced in today's alog
Some very small gains (1e-32) were being replace with zero. This only affected filter files modified between last Tuesday (3/14) and this afternoon. I ran the following filter files through "foton -c" to correct the gains: H1SUS[I,E]TM[X,Y] and H1OMCPI. The files H1SUSMC2 and H1OAF were ran through the new foton this morning, H1SUSETMYPI was modified this afternoon with the new code.
During maintenance I turned on the new op lev damping roll off filter. (34954) This means that oplev damping noise should be about a factor of 3 below the ASC noise (and the DARM noise) at 10 Hz.
Attached is a comparison of new/old open loop gain measurement made with no power in the arm, and the drive levels in low noise with the new filter engaged. For a comparison to the drives with the old cut offs see 34735
We continue the study of 34863 to explore what effects can differential ITMs cause, as motivated by the high absorption point on ITMX reported in 34853 and 34900.
This time in addition to differential thermal lenses, we also added ITM losses into consideration.
Some key messages from the simulations are:
1. The carrier build-up in the PRC is sensitive to losses (apparently), but not to the differential lensing. The RF9 build-up is more sensitive to differential lensing effects than the carrier.
2. The DARM cavity pole is NOT sensitive to ITM losses, but can be changed by differential lensing. See the first plot.
3. The SRM alignment signal is sensitive to differential lensing, but NOT to ITM losses. See the second plot.
=========================================================================
Some details:
We start from the Finesse input file T1300904, but changed the ITMX and ITMY losses each to 75 ppm, so that the carrier gain in PRC is 40. We also reduced the DARM LSC locking point to account for the losses. The SRC gouy phase corresponding to that file is 20 deg.
We first computed the DARM transfer function (ETM diff phase -> field leaving from the AS port) for a set of extra ITMX lensing, while fixing ITMX loss = ITMY loss = 75ppm. The poles were recorded and fitted with a quadratic function.
Then we fixed ITMY loss = 75 ppm but increase ITMX loss from 75 ppm to 95 ppm. We used two ITMX lensing setting, one with no extra ITMX lensing, one with extra 100 km lensing. For a given diff lensing setting, increase ITMX loss caused the carrier gain dropped from 40 to 36, as expected. At the same time the DARM cavity pole changed by no more than +- 1 Hz. On the other hand if we held loss fixed, changing ITMX lens had tiny effect on the carrier PR gain, but it affected the RF9 build up.
For SRM sensing, there was essentially no effects due to extra differential losses, as shown in the second plot for an extra ITMX lens of f=100 km, SRC gouy phase = 20 deg, and ITMX loss = 95 ppm (blue dashed) or 75 ppm (yellow dotted), and ITMY loss = 75 ppm.
So a possible scenario suggested by the simulations so far might be: when the ifo was cold, we had okay PR gain and SRM sensing. As it being heated up, the high absorption point caused both more losses (which degraded the PR gain) and extra lens (which affected SRM sensing). According to the simulation, we might also expect some drop in DARM pole. Is this observed in reality?
Analysis codes available at
https://git.ligo.org/IFOsim/Finesse_playground/tree/master/HangYu/work_diff_lens
J. Kissel I've gathered our "bi-weekly" calibration suite of measurements to track the sensing function, and ensure all calibration is within reasonable uncertainty and to have corroborating evidence for a time-dependent detuning spring frequency & Q. Trends of previous data have now confirmed time dependence -- see LHO aLOG 34967. Evan is processing the data and will add this day's suite to the data collection. We will begin analyzing the 7.93 Hz PCAL line that's been in place since the beginning of ER10, using a method outlined in T1700106, and check the time dependence in a much more continuous fashion. My suspicion is that the SRC detuning parameters will change on the same sort of time scale as the optical gain and cavity pole frequency. Note also, that I've grabbed a much longer data set for the broad-band injection, as requested by Shivaraj -- from 22:50:15 UTC to 22:54:20 UTC, roughly 4 minutes. The data have been saved and committed to: /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Measurements/SensingFunctionTFs 2017-03-21_H1DARM_OLGTF_4to1200Hz_25min.xml 2017-03-21_H1_PCAL2DARMTF_4to1200Hz_8min.xml 2017-03-06_H1_PCAL2DARMTF_BB_5to1000Hz_0p25BW_250avgs_5min.xml The data have been exported with similar names to the same location in the repo. For time-tracking, this suite took ~38 minutes from 2017-03-21, 22:18 - 22:56 UTC.
J. Kissel Because the calibration suite requires one to turn OFF all calibration lines before the measurements then back ON after, the time-dependent correction factor computation is spoiled temporarily. In the GDS pipeline, which uses FIR filters, it takes about 2 minutes for the calculation to return to normal functionality and produce sensible results (Good! this is what's used to correct h(t)). However, because the front-end's version of this calculation (NOT used in any corrections of any astrophysical or control room product) uses IIR filters, it remains polluted until one manually clears the history on all filter banks involved in the process. Normally, as the ISC_LOCK guardian runs through the lock acquisition sequence, it clears these filter banks history appropriately. However, the calibration suite configuration is still a manual action. Moral of the story -- I'd forgotten to do this history clearing until about 1 hr into the current observation stretch. The history was cleared at approximately 2017-03-22 00:10 UTC. Why am I aLOGging it? Because clearing this history does NOT take us out of observation mode. Rightfully so in the case, because again the front-end calculation is not yet used in any control system, or to correct any data stream, it is merely a monitor. I just aLOG it so that the oddball behavior shown at the tail end of today's UTC summary page has an explanation (both 20170321 and 20170322 show the effect). To solve this problem in the future, I'm going to create a new state in the ISC_LOCK guardian that does the simple configuration switches necessary so no one forgets in the future.
J. Kissel On the discussion of "Why Can't LLO the same SNR / Coherence / Uncertainty below 10 Hz for These Sensing Function Measurements?" It was re-affirmed by Joe on Monday's CAL check-in call that LLO cannot get SNR on 5- 10 Hz data points. There are two things that have been investigated that could be the reason for this: (1) The L1 DARM Loop Gain is too large ("much" larger than H1) at these frequencies, which suppresses the PCAL and SUS actuator drive signals. (2) Because of L1's choice in location of applying the optical plant's DC readout DARM offset and avoiding-DAC-zero-crossing-glitching SUS offset means there are single vs. double precision problems in using a very traditional DARM_IN1/DARM_IN2 location of the open loop gain transfer function. both investigations are described in LHO aLOG 32061. They've convinced me that (2) is a small effect, and the major reason for the loss in SNR is the loop gain. However, Evan G. has put together a critique of the DARM loop (see G1700316), which shows that the difference in suppression between 5-10 Hz is only about a factor of 4. I put a screen cap of page 4 which shows the suppression. I attach a whole bunch of supporting material that shows relevant ASDs for both during the lowest frequency points of the DARM OLG TF and the PCAL 2 DARM TF: - DACRequest -- shows that a factor of 4 increase in drive strength would not saturate any stage of the ETMY suspension actuators - SNR_in_DARM_ERR -- shows the loop suppressed SNR of the excitation - SNR_in_DELTAL_EXT -- shows the calibrated displacement driven - SNR_in_OMC_DCPDs -- shows that a factor of 4 increase in drive strength would not saturate the OMC DCPDs So ... is there something I'm missing?
Here with attached a plot showing comparison of PCal, CAL-DELTAL_EXTERNAL and GDS for the broad band injection. As expected, GDS agrees better with PCal injection signal. The code used to make the plot is added to svn,
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/PCAL/PcalBroadbandComparison20170321.m
Just to close out the question in Comment #2 above, LLO was indeed able to use LHO-like templates and drastically improve their SNR at low-frequency; check out LLO aLOG 32495. Hazaah!
J. Kissel, E. Goetz The processed results for this data set are attached. For context of how this measurement fits in with the rest of measurements taken during ER10 / O2, check out LHO aLOG 35163.
TITLE: 03/21 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 68Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Maintenance day. Tumbleweeds blocked the Xarm so that filtered out some work. I had some issues locking with ALS_DIFF not fining IR and causing a lock loss. 12 seconds after it would set the offset to 1380, the IMC would drop out and kill the lock. What eventually worked, although it did not identify the problem, was going through that step by hand and scanning through the offsets slowly. I'm not sure if it will happen again so future operators be wary.
LOG:
Ran the full script for EX but had to cut EY short after about 35min. I did not get the chance to process the data yet, but I can do it tomorrow.
I had to tag Jeff on this one to run the long_trend.m because I had nds2 troubles. Jeff ran it with no problems...
He also mentioned that we may need to flip the bias soon on ETMX because (let's see if I understood this correctly) the angular actuation is off by ~8% in some quadrants, but the longitudinal is only off by ~3% (See summary screenshot).
Sorry abandoning TJ quickly on this one. Here's what I said in regards to these plots: Last week, I'd threatened that we needed to flip the ESD bias sign on ETMY because the traditionally posted angular relative actuation strength plots continue to show changes at the level of 8-10% because appreciable effective bias voltage from charge (negative 20-30 V) is accumulating in some quadrants. Note that this is relative to zero effective bias voltage. However, if I look at the summary pages, to show me the longitudinal relative actuation strength (the fifth plot that TJ posts) as measured by the PCAL and SUS calibration lines -- the actuation strength direction that actually matters for calibration -- it shows a level of 3-4%. Note that *this* is relative to the latest calibration reference model, created Jan 4th, when the effective bias voltage was already in the negative 10 V range. In summary -- I don't think we're in dire need of a bias flip on ETMY any longer. But we remain dilligent!
We were able to get images using the Pcal camera at ENDY today and these images will be used to determine the position of the Pcal beam. (Analysis to follow). We were not able to get down to ENDX because of tumbleweed infestation. We will probably try to get images from ENDX during Thursday's commissioning effort.
Analysis can be found at: LHO alog #35347
WP 6532 Updated GDS software Ubuntu 12, Ubuntu 14, and Debian 8 workstations. This replaces foton with a new version that writes the gain coefficient in scientific notation with extended decimal places. The issue is trying to find a format that will work for gain coefficient values of 479871010208.8750610351 and 1.827245000521226e-32, as an example.
Not sure anything changed since we were not locked at the time but I used the lens controller to open the iris all the way on ITMx and ITMy. Without a beam I just have to believe they are all the way open. Perhaps next time we are out of observing and locked I will shut and open the iris to verify its function.
To save its life span.
Found a power cord plugged into the wall opposite to HAM4 (now unplugged). Probably had been plugged since last week we did the HWS table work.
While the laser was down this morning, I took a quick measurement of the ETMX pit oplev damping loop. It has about 5 dB of damping in a narrow range around 0.46Hz, and has zero phase and -10dB of gain at 1.5 Hz with no light in the arm.
Because the noise from these loops is limiting DARM at 10 Hz (alog 34735), I made a slightly more aggressive cut off (LP8 is intended as a replacement for LP10) which can be tried next time we have a chance. This is the reason there are unloaded changes in the filter files for all 4 quads right now.
I used this measurement to update the quad model with gain of the electronics and software between the PUM pitch actuators and the optical lever. See CSWG log 11209.
The gain was found simply by comparing the measured loop gain to the modeled loop gain with the installed filter, and scaling the model until matched the measurement. The gain applied to the model to make them match is 1/1500.
More measurements like this for the other suspensions will be useful for telling us if this gain factor is the same for all suspensions, or at least the same across sites.
Thanks for including the measured data, that made the analysis a lot easier.
EX had a dip in pressure around March 9th from 97.7 to 97.5, but other than that all looks good.
I forgot to link to FAMIS4530
Closed
Looking over the past week, the daily EY gliches are at 20:44 PDT (03:44 UTC). On Saturdays a second glitch occurs at 21:04 PDT (04:04 UTC). Attached plots show 03:25 to 04:10 UTC for 3/19 and 3/12 (two successive saturday evenings in local time).
Here are data from End Y with most of the pressure channels and the controller output to the pump motor.
The attached plot gives support to this argument:
Something is happening with either the Pump motor or the VFD causing an increase in pressure out from the pump. This is evident by the increasing delay in pressure response as we proceed down the Pump Station Manifold. PRESS1 is the first after the Pump, the rest are after Laminar flow resistors and the filter. BSCSUP_PRESS is way down the line at the Chamber. The PRESS1 clearly leads the down stream pressures and it steps more sharply than the others. So this is a real pressure change increasingly softened by the accumulators and resistors etc as the wave moves down the line.
The VOUT signal is the PID loop responding to the differential pressure (diff between BSCSUP and BSCRET[not shown].) There is a big step down on this channel just before the pressure step up but that wouldn't cause an increase in pressure. So, I don't believe the motor is being directed to drive harder.
I'll look over the VFD manual to see if it has any scheduled items that might cause this? That just hardly makes sense...
Edit--Extra--If the output voltage of the PID controller could actually be manipulated without the VOUT data signal registering it, that too would be a possibility...Dave is looking closer at the computer.