[Jenne, Vaishali]
We were checking amplitudes for measuring the ASC sensing matrix at the POP WFS, and when I made a typo and excited SRM by a factor of 10 more than I meant to, we lost lock. Ooopsies. TJ has the IFO back on the way to NLN now.
We'd like to measure what the sensing matrix at the in-air POP WFS looks like, so that we can compare with the simulations. The POP WFS weren't in place the last time we measured the ASC sensing matrix back when Hang was last on site.
WP 6523
I was asked by Terra to check whether mode 23 (32761.5 Hz ETMY) is visible also in the TRY QPD.
So I excited mode 23 today during the commissioning window --- we see the mode in the TRY signals as well.
* * * * * *
The way the mode shows up is such that segments 2 and 4 don't see the mode in a 0.1 Hz resolution FFT at all while the mode shows up in segments 1 and 3 (diagonal pair) in a differential way. Note that the excitation was done by driving the UR and LL segments of the ETMY ESD in common. The attached shows comparison of the spectra with and without the excitation.
Apparently, the OMC has a better signal-to-noise ratio than the TRY QPD by a factor of 100 or so.
Also, because of the aliasing effect, the mode is split into two components after the 32800 Hz mixing operation; one at 22.5 Hz (= 32800 Hz + 32761.5Hz + 2^16 Hz) and the other at 38.5 Hz (= 32800 Hz - 32761.5 Hz). Usually the PLL for this mode is locked to the higher frequency one, 39 Hz.
Adjusted ALS fiber polarization for the X and Y arms, they were 11 and 22 respectively.
| Work Permit | Date | Description | alog/status |
| 6536.html | 03/22/17 11:46 AM | Measure ASC sensing matrix at POP WFS | |
| 6535.html | 03/22/17 08:54 AM | Secure the TCS Safety Interlock box on top of the TCS rack in the mechanical room. Work might require the TCS 24V power supply to be powered down, to allow dressing of power cables. | |
| 6534.html | 03/22/17 08:54 AM | Investigate some authentication problems in the remote access control system. May restart the system. See https://services.ligo-la.caltech.edu/FRS/show_bug.cgi?id=7677 | |
| 6533.html | 03/21/17 01:28 PM | Power off HWSY SLED. | 34976 |
| 6532.html | 03/21/17 12:03 PM | Install a new version of gds software. The only change is foton, writing gain coefficients with a different precision. | 34979 |
| 6531.html | 03/21/17 10:11 AM | Lead two others through the LVEA on a tour. (VIP visit) | |
| 6530.html | 03/21/17 08:33 AM | Make sure iris is fully open on both IR camera lenses. This can be done without opening the enclosure with the lens controller. | 34977 |
| 6529.html | 03/20/17 10:47 AM | Injections similar to those described in alog 34623 at lower frequencies (HAM1+HAM6). Tamper injections in corner station to localize coupling location. Possibly other tests including looking at downconverion in IPSs and OMC fringe wrapping. | |
| 6528.html | 03/20/17 09:02 AM | Remove faulty HFW card from h1hfwsmsr server | |
| 6527.html | 03/19/17 09:36 PM | Access to pcal system and camera to take pictures and possibly move the pcal beams | 34980 |
| 6526.html | 03/17/17 02:06 PM | Potentially (undecided if we will perform this work at all), fire up the electrolytic welder which is part of the fiber welding set of equipment, in order to do some flame polishing of COC ears which have blemishes. Angus has used such equipment so we will be learning how to use it, or will just use it while he visits for these 2 days. Work will take place in fiber lab in LSB. We've already spoken to Bubba regarding the safety of this task - he will look it over with us on Monday when/if we start. | |
| 6525.html | 03/17/17 08:19 AM | Turn off the HWSSX SLED (via medm button) during lock loss. Leave off until instructed to turn it back on. This is for Aidan to make a measurement to compare with latest set in alog 34853. | |
| 6524.html | 03/15/17 11:49 AM | Briefly run the fire protection pumps to test the new alarm system being installed. I will alert the control room operator when we start and stop the pumps. | |
| previous Work Permits | |||
| 6489.html | 2017-02-16 16:35 | Fix tconvert on Debian 8 workstations, as it is now, it cannot convert dates of the form "Oct 15 2016 12:34:56 UTC" when the month is Oct. Every other month works. | 34966 |
We are currently in a scheduled commissioning time, but are still locked.
The trucks still seem to be hauling something along Route 10, but not making as big of an impact as on Monday.
There was some noise reported during Jim's shift, and maybe some ~3k noise continuing into mine. Investigations continue.
Starting CP3 fill. LLCV enabled. LLCV set to manual control. LLCV set to 50% open. Fill completed in 43 seconds. LLCV set back to 16.0% open. Starting CP4 fill. LLCV enabled. LLCV set to manual control. LLCV set to 70% open. Fill completed in 259 seconds. TC A did not register fill. LLCV set back to 43.0% open.
FRS7667. Hugh, Jim, Dave
we have tracked the daily/weekly HEPI pump controller glitches to when crond deamon runs anacron/logwatch job at 04:02 daily and 04:22 weekly on Sunday.
When the clock was fixed at EY from being 7 hours 34 minutes in the future yesterday, today's EY glitch happened at exactly 04:02 PDT (and not 20:44 PDT as it was prior).
We are investigating 1) how can a cron job cause this issue and 2) can we just turn crond off safely.
attached image shows today's EY glitch at 11:02 UTC (04:02 PDT)
I've gone through the path of what cron and anacron do each day and each week. I've culled the list down to the following on h1hpipumpctrley:
hourly : no actions (no change)
daily: only log rotate (removed 8 actions)
weekly: no actions (removed 2 actions)
Lets run the rest of the week with this EY mod to see if it reduces the glitches.
I noticed this morning that the ASC P INMON FOM showed more signal than I was used to seeing. When I looked at trends for the last 4 hours, it looks like they started to ring up around 11:00 UTC, first attached pic. When I took spectra before and after, it was immediately obvious that the quad .43hz mode was higher in the after time. My second plot is before(solid) /after (dashed) spectra of the CHARD/CSOFT P inputs, but DHARD/DSOFT and MICH also see this. Looking at the quad M0 L damp ins shows a similar result, third plot, I just show ITMY(dashed before/ solid after), but all the quads look similar. Not sure what changed, but this also kind of lines up with the drop in range this morning.
The ITMY oplev has the most suspicious behavior while the longitudinal modes were rung up. All four test-mass oplevs saw the extra motion at 0.43 Hz, but ITMY also saw a number of other modes misbehaving. One might have been the P2 mode at 1.3 Hz, and there were several other peaks that appeared. The ITMY oplev or other part of the ASC control might be a good place to start looking. Attached is a spectrum of new structures appearing in the sum (blue is a quiet reference), and a spectrogram showing the new peaks appearing in pitch.
TITLE: 03/22 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 67Mpc
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
Wind: 5mph Gusts, 4mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.19 μm/s
QUICK SUMMARY: On a 10.5 hour lock stretch. Environment is calm, but the ASC P seems to be a bit noisy. Jim will add more on his findings on this. Hopefully we don't have the trucks like we have the past few days.
TITLE: 03/22 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 66Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
LOG:
Quiet shift, except for the ASC getting noisy starting at about 11:00 UTC. Trying to log now, but tired.
I looked to see if LHO would benefit from doing better L2A decoupling on some of the corner station suspensions, similar to Arnaud & Marie's work at LLO (LLO alog 31459, for instance). The attached PDF shows the coherences between the different PD PIT & YAW INMONs used for ASC and the M1_DRIVEALIGN_L_OUTMONs for PRM, MC2, BS and SRM, during a windy time a couple of weeks ago. I'm a little confused because PRM and MC2 seem to have a lot of coherence with a lot of PDs, but maybe folks who know the ASC system better can make sense of this. SRM shows somewhat less coherence, but more than the BS. Each page is a different PD, the top plot is coherence between each suspensions length drive and the spot pitch. The bottom plot on each page is the yaw coherence. I believe the color scheme is the same for all plots.
Shift Summary: Ran A2L DTT check – Pitch and Yaw are both somewhat elevated. Tumbleweed baling has finished for the day. Work will continue on the X-Arm tomorrow.
Problem #1 - Started getting OMC DCPD saturations (due to Violin Mode 508.2 ring up), but lost lock before damping. Contacted Sheila and tried to give remote access.
Problem #2 – Could not give Sheila remote access due to a problem with the authentication server. Contacted Jonathan who corrected the problem (FRS 7677 aLOG #43993).
Problem #3 – There was a problem with the Foton filter files generated after last Tuesday’s maintenance window until today at 13:00, when Jim B. fixed this problem. See aLOG #43992 for description. Contacted Dave B. who rebuilt the Foton files for the SUSs and H1OMCPI. When I reloaded, the filter files the WDs for ITMX & ETMY tripped. By the time this was all squared away the violin modes had calmed down a bit.
Relocked the IFO without the ALS_DIFF problem had during the day shift. I had to dress up BS Yaw a little bit, but no other tweaks were required.
We were back to Observing in time to receive a GRB alert.
05:06 (22:06PT) start one hour stand-down for GRB alert.
Support - Sheila, Dave, Jonathan Problem #1 - Started getting OMC DCPD saturations (due to Violin Modes 508.2 ring up), but lost lock before damping. Contacted Sheila. Problem #2 – Could not give Sheila remote access due to an issue with the authentication server. Contacted Jonathan who corrected the problem (FRS 7677 aLOG #43993). Problem #3 – There was a problem with the Foton filter files generated after last Tuesday’s maintenance window until today at 13:00, when Jim B. fixed it. See aLOG #43992 for description. Contacted Dave B. who rebuilt the Foton files for the SUSs and H1OMCPI. When I reloaded, the filter files the WDs for ITMX & ETMY tripped. By the time this was all squared away the violin modes had calmed down a bit. Relocked the IFO without the ALS_DIFF problem TJ had during the day shift. I had to dress up BS Yaw a little bit, but no other tweaks were required to reach NLN. Back to Observing and fighting with PI Mode-27.
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.
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.