On July 2, 1015, Sudarshan measured the ISS first loop UGF to be about 22 kHz with a phase margin of 50 deg and only about 30 deg of phase margin near 50 kHz.
I emailed the lsc-psl@ligo.org list to see if this was observed with the other PSL installations.
Matt Heinze responded that they had recently made these measurments at LLO (see LLO alog 19412).
In summary, they also found that their ISS UGF was too low, they increased it to 50-60 kHz where they have around 30 deg. of phase margin.
Maybe we should turn our gain up too.
They also adjusted the gain of the PMC servo which we have not looked at for a long time.
Seems we should investigate both of these servos during next Tuesday's maintenance period.
LVEA: Laser Hazard IFO: Unlocked Observation Bit: Commissioning 07:45 Cleared IPC errors on H1SUSTMSY & H1SUSTMSX 08:00 IFO Down – Travis working on locking 08:25 Kiwamu & Sudarshan – Going into LVEA to take TFs on ISS Outer Loop Servo 08:58 Joe – Going to both Mid-Stations to work on rodent control 09:00 Andres & Stefan C. – Going to End-X to take some measurements 09:32 Ed – Going to Mid-X to recover an AA-Chassis 09:35 Andres & Stefan – Back from End-X 09:48 Joe – Back from Mid-Stations 09:58 Karen – Cleaning at Mid-Y 10:03 Filiberto – Going to the CER to work on Cosmic Ray 10:05 Kiwamu & Sudarshan – Out of the LVEA 10:15 Christina – Cleaning at Mid-X 10:55 Karen – Back from Mid-Y 11:00 Christina – Leaving Mid-X 11:27 Kiwamu & Sudarshan – In LVEA to take TFs on ISS Outer Loop Servo 12:30 Vinnie –In the LVEA to check PEM cabling 12:41 Kiwamu & Sudarshan – Out of the LVEA 13:14 Filiberto – Reinstall Cosmic Ray chassis 13:39 Vinnie – In the LVEA to center tilt meter 14:16 Jim B. & Stefan C. – Going to End-X to pull cables in the CER area 14:27 Sudarshan – Going into LVEA to recover electronics 14:35 Kiwamu & Jenne – Taking student tours through LVEA 14:42 Jim B & Stefan C. – Finished at End-X – Going to End-Y 14:47 Kyle – Putting crate back in mechanical building – Will be using forklift 15:20 Kyle – Finished moving crate 15:35 Jeff – Going to End-X to get laser glasses for DtChar tour 15:55 Jeff – Back from End-X
Jim Batch, Stefan Countryman Cables connecting IRIG-B outputs and channel 31 (of 32) of the BNC AA chassis have been installed at EX and EY. The signal at EX will be read by a model and sent to a frame in the near future. A model change and DAQ restart will be required to finish this task.
A week ago the bias sign was changed of both ETMs. Before this week data are consistent with positive charging for ETMY and negative charging for ETMX. Charging speed is about 10-20[V] per month. This week's data for most of quadrants are consistent with the changed sign of charging - negative for ETMY and positive for ETMX. Plots are in attachment. Note: before measurements ETMX ESD driver was in unusual state: UL, UR, LL was in Hi voltage ON, Hi Volt disconnect OFF, LR was in Hi Voltage OFF, disconnect OFF. After my measurements I set all quadrants to Hi Voltage ON, Hi voltage disconnect ON.
IMC WFSA I and Q segment gains (H1:IMC-WFS_A_I1_GAIN etc.) are [1, 0.25, 1, 4] for segment [1, 2, 3, 4].
I injected some small excitation into MC2 MCL at 20Hz and saw that segment 2 is much smaller than seg1 and 3 while segment 4 is much larger. WFSA phases are good, gains are not, and WFSB looks good for both.
These gains are supposedly set by injecting into MC board and measuring the length response in WFS segments such that the output becomes equal to each other, as explained by this alog from June 2013. It seems like these numbers were set to some seemingly crazy values in June 2013, and then to other seemingly crazy but different values in August 2014, and stayed there since then.
WFSB gains were set to yet another funny things in June 2013 but at least they were set to [1 1 1 1] last August.
Based on discussions during the Calibration Committee call today, we decided to eliminate the 157.9 Hz low-SNR calibration line.
We switched off the excitation which was in the OSC2 position.
So we are now driving at 36.7 with SNR of about 100 for calculating the actuation correction, kappa_A (see LIGO-T1500377), and 331.9 Hz with SNR of ~100 for calculating the sensing correction, kappa_C, and f_c, the cavity pole.
We are also driving at 1083.7 Hz with an SNR of about 40.
All SNRs quoted are with 10-second FFTs.
As soon as we inspect and tune up the Xend Pcal, we plan to start an excitation at 3001.3 Hz with a relatively low SNR (all that we can achieve at this high frequency).
LLO will run lines spaced within 1-2 Hz of hte LHO lines.
This is our current plan for the Pcal lines for the O1 run.
Since we now do not use the pcal line at 325.1 Hz, I took out the corresponding notch (alog 19839) from LSC-DARM while I left a notch for the one at 331.9 Hz in FM7.
Brute force coherence report for the lock reported in 20020 is available here:
https://ldas-jobs.ligo.caltech.edu/~gabriele.vajente/bruco_1122206417/
At a first quick look:
More analysis in the future...
This morning I measured the OLTF of IMC ASC DOF5 loops (attached, OLTF on the right, gain settings on the left). As you can see I'm not using PIT as the current non-aggressive filter is not doing anything useful.
I did on/off test using IM4 trans sum as the sensor (attached middle). As you can see 300Hz intensity noise is suppressed by a factor of 5 at the expense of small gain peaking at around 200-250Hz, 350-400Hz and 620Hz.
Note that the 620Hz peak will be stable against 10dB change in the gain (i.e. even if the peak will come above unity gain), but will quickly become unstable beyond that point.
DOF5 Y loop is left ON.
Matt, Lisa, Sheila
Today we had the mixed blessing of our refl trans/resonance/analog CARM locklosses reappearing. We noticed two things, first that the pitch motion we see in the oplevs seems to be a result of an instability in the DHARD loop (by adjusting the gain we could reduce it), and second that when we turn on the DHARD boosts in the state resonance this is somewhat rough and we think this sometimes causes locklosses.
Although we could probably solve this problem by changing the alignment, we wanted to spend some time trying to fix it to avoid this in the future. We measured the DHARD PIT loop at various places in the CARM offset reduction, and have found gains to keep the ugf around 4 Hz throughout the whole process. This allowed us to turn on a boost at the CARM_5PM step, which seemed to make things much more stable in refl trans and resonance. Matt redesigned the boost to make the turn on transient softer, we can no longer tell from the AS camera when the boosts come on. In the attached screenshot the red trace shows transfer functions measured at CARM_5PM, blue is before engaging Matt's new boost, red is with the first of the boosts on (boostLTE, which gives us about 6dB of gain below 1Hz ).
We have been running with oplev damping on the ITMs and not the ETMs, but since we have moved to the HARD/SOFT basis we would like to turn off the ITM oplev damping. We tried the whole sequence (with DHARD changes done by hand) with oplev damping off, and everything worked until we increased the power. It seems like this was due to an instability in DHARD YAW at 23 Watts, which can be solved by turning the gain down slightly. (from 7 to 5)
We were tesing this automation, and had a small earthquake. We decided to revert the changes in the DHARD gain throughout the CARM offset reduction (but kept the new boosts and are still engaging them before REFL_TRANS), because we wanted to see that the IFO could lock before we left. Also, we are now leaving the oplevs off for the CARM offset reduction. We were able to lock on low noise for a few minutes, but an instability in DHARD PIT knocked us out after a few minutes.
Other things:
While at 24W, we also tested the new ISS second loop: no problems. We didn't get a chance to do any loop characterization measurements, but after a little tweak to the IMC_LOCK guardian the ISS came on. The new ISS guardian tunes the pre-loop closure offset to produce a servo output of 0.5V (rather than zero), which prevents a turn-on transient (the "shark fin" seen in the diffracted power).
Sudarshan, Travis
We used today's maintenance period to check the PCALX clipping issue mentioned in alog #19899. We moved the clipped beam using the last mirror ( the one that directs the light to the test mass) in the transmitter module and were able to get the reflected beam on the receiver side at a fairly reasonable level. There was a very narrow window in our alignment in both pitch and yaw to get the beam out on the receiver side and we are guessing we are very close to the edge of one of the optics inside the chamber.
The laser power as measured by ophir power-meter are as follows:
Inner Beam | Outer Beam | |
Transmitter Side | 0.738 W | 0.734 W |
Receiver Side | 0.718 W | 0.712 W |
We will check the beam balance between the two beams and optical efficiency during our next calibration and touch up the alignment if needed.
The Xend Pcal module has some issues.
Today Sudarshan and Travis made some adjustments that seem to have eliminated the clipping (aLog from Sudarshan forthcoming).
But while setting the Pcal excitations today we noticed that we don't have a readback of the AOM excitation. It may be a cabling issue.
More relevant is that the power seems to be significantly lower than expected, about 30%.
We left the laser operating and illuminating the ETM, but without excitations. This will allow us to diagnose if the clipping issue is resolved.
When time allows, we will go to Xend and investigate further.
All of the necessary calibration lines can be generated from one Pcal module; they are currently running at Yend.
Eventually, we plan to use the Xend Pcal for a single high frequency line near 3 kHz, and as a spare in case we have issues with the Yend module.
ShivarajK, RickS
We changed both the Pcal and DARM_CTRL excitations to the following (expected SNR with 8 sec FFTs in parentheses):
PcalY:
36.7 Hz at 360 cts. (90)
157.9 Hz at 575 cts. (41)
331.9 Hz at 2,320 cts (90)
1083.7 Hz at 24,000 cts (36)
DARM_CTRL
37.3 Hz at 0.31 cts. (90)
These are our best current estimate of what we will want to have for O1. We expect to make similar changes at LLO, with their calibration lines within a hertz or two of ours.
The other excitations (including those from the Xend Pcal) have been switched off. Snapshots of the relevant sections of the MEDM screens are attached below.
The total Pcal excitation range is about 42,000 counts so the 1083.7 Hz line uses about 60% of the range and the other three lines together use about 8% of the range.
I installed an ad-hoc DOF5 filters for both PIT and YAW, and set up the input matrix to use WFSA for PIT and WFSB for YAW. The selection of sensors is based on the coherence with OMC DCPD between 200 and 400Hz (attached left).
PZT to WFS transfer functions were measured yesterday (attached, middle two windows).
I copied LLO filters, gave it some more attenuation at lower and higher frequency and rotated the phase in a direction that I thought would work for the measured TF.
I didn't do any tuning except to turn the servo on and to change the gain so it started to squish 300Hz bump in IM4 trans SUM.
I'll leave it OFF for now.
After the BIOS change to h1susey yesterday afternoon we turned off the periodic clearing of the DIAG_RESETs so any glitch will latch on. At 02:34:43 PDT we got an TIM+ADC glitch on the SUS EY IOP stateword which remained on until Jeff cleared it at 07:52:43 PDT. Soon after that I restarted the clearing of the DIAG_RESET every minute to get better statistics. For the past 24 hours the 02:34 glitch is the only one seen.
I've written a python script which takes the output from command-line-nds and bit masks out the upper overflow/excitation/cfs bits to make the analysis easier.
Yesterday Joe ran Keith's script to generate the L1 science frame channel list broken down by subsystem and data rate. I have ran this script on the H1 DAQ and compared the two lists. The two report files are attached below.
Here is a summary of the differences per subsystem. For each subsystem, the differences are given as [number of H1 channels, number of L1 channels] for each acquistion rate. Green cell means L1>H1, beige cell H1>L1. Blank cells mean either no channels at that rate or no difference in the number of channels between the sites.
system | 32k | 16k | 8k | 4k | 2k | 1024 | 512 | 256 |
susauxb123 | [50,67] | |||||||
psliss | [0,1] | [6,7] | ||||||
pslpmc | [6,2] | |||||||
pemcs | [23,17] | [15,9] | [5,9] | [37,24] | [4,0] | [10,7] | ||
oaf | [2,8] | |||||||
asc | [53,47] | [0,22] | ||||||
susetmxpi | [2,0] | |||||||
susetmypi | [2,0] | |||||||
pemey | [4,3] | [9,6] | [3,2] | [12,6] | [4,0] | [9,13] | ||
pemex | [4,3] | [9,6] | [3,2] | [12,6] | [4,0] | [9,13] | ||
alsex | [1,0] | [2,0] | ||||||
alsey | [1,0] | [2,0] | ||||||
iscex | [1,0] | [7,10] | ||||||
iscey | [1,0] | [7,10] | ||||||
Calculating the difference between additional L1 channels verses H1 channels and taking the data rates into account gives an additional data rate of 984 kBytes/second for H1 frames. This means the H1 64 second science frame should be approximately 64MB larger than L1.
I compared some L1 and H1 science frame sizes, the H1 frame was larger by 78, 95, 82, 83 MB. This roughly agrees with the calculation, there will be variation due to the overall compression of the entire frame.
Daniel gave me the test rig for the AM stabilized EOM drivers that we should be receiving from Caltech this week. This allowed me to test that the Beckhoff controls and readbacks work as expected. I also made a summary screen (ISC_CUST_EOMDRIVER.adl) of these readbacks and controls, which is accessible from the LSC dropdown menu on the sitemap.
The chassis is labeled "Corner 6", and has 2 unconnected connectors labeled "EOM Driver A" and EOM Driver B".
The "A" connector controls the 45 MHz channels, and the "B" connector controls the 9 MHz channels.
The controls and readbacks performed the same for both channels, so I'll only write out the list once.
Voltage input with voltage calibrator | RF Set Mon readback value |
0.1 V | -13 |
1 V | 7 |
3 V | 16.6 |
5 V | 21.0 |
7 V | 24.0 |
I need to investigate the situation with the "Excitation Enable" switch, but other than that we should be ready to go when the EOM driver arrives, if we decide to install it.
The RF setpoint goes from 4dBm (lowest setting) to 27dBm (highest setting) in steps of 0.2dB. The binary should start at zero for the lowest setting and increase by 1 for each step. This is a PLC problem.
Kyle, Gerardo 0900 hrs. local Added 1.5" O-ring valve in series with existing 1.5" metal valve at Y-end RGA pump port -> Valved-in pump cart to RGA -> Valved-in Nitrogen calibration bottle into RGA -> Energized RGA filament -> Valved-out and removed pump cart from RGA -> Valved-in RGA to Y-end ???? hrs. local Began faraday analog continuous scan of Y-end 1140 hrs. local Isolated NEG pump from Y-end -> Began NEG pump regeneration (30 min. ramp up to 250C, 90 min. soak, stop heat and let cool to 150C) 1410 hrs. local Valved-in NEG pump to Y-end 1430 hrs. local Valved-out Nitrogen cal-gas from Y-end 1440 hrs. local Valved-in Nitrogen to Y-end -> Stop scanning
Plot of pressure at Y-End station before, during and afer NEG regeneration.
Response of PTs along the Y-arm to NEG pump regeneration.
RGA and pressure data files for NEG regenerations to be centralized in LIGO-T1500408
Interesting! As you predicted, the RGA is not super conclusive because of the background; but there seems a clear difference when you isolate the N2 calibration source. So your water and N2 may really be comparable to the hydrogen, say several e-9 torr each (comparing sum of peaks to the ion gage). The NEG will poop out after ingesting ~ 2 torr-liters of N2, so at 1000 l/s it will choke and need regen after a few weeks. Which is I guess what it did. It would be good to clean up the RGA so we can home in on the N2 and water pressure, and especially HC's (I expect the HC peaks in these plots are from the RGA itself). To get practical use out of the NEG we should pace how much of these non-hydrogen gases it sees. We can expect to only get about 50 regens after N2 saturation, and small amounts of HC may kill it outright. We should be able to estimate the net speed of the NEG before and after from the pressure rise and decay time (we can calculate the beam tube response if we presume it's all H2).
I have trouble seeing even the hydrogen pumping by the NEG by looking at the different scans. Suggest you set the RGA up to look at AMU vs time and do the leak and pump modulation again. Plot amu 2, amu12,amu14,amu28.
Rai,
That is on our list of things to do - make a table of the relevant amus' partial pressures.
Note that all the ascii data is at:
(see LIGO-T1500408-v1 for ascii data)
caution - 15 mbytes
Kyle can probably fish out the relevant data from the RGA computer so no need to plow through the whole file.
thanks for the comments, Mike and Rai.
J. Kissel --------- Executive Summary: The INJ group has identified a problem with the H1 hardwar injection path, see LHO aLOG 19435 and HWInjER7CheckSGs. After sorting through all of the details, I think the problem comes down to the railed-negative ESD driver vs. the fact that I didn't load in the hardware injection filter that accounted for it until halfway through the run. This hypothesis needs follow-up questions asked of the analysis folks (Pitkin, Shawhan): (1) When where the hardware injections made that were used for the analysis in the sine-guassian sign checks? (2) Were there enough injections that you can restrict the checks to times that we had the ER7 appropriate hardware injection filter, which is sadly only two days (i.e. after Jun 09 2015 00:07:48 UTC and before Jun 10 2015 23:14:55 PDT, when the ESD driver was reset, and the sign flipped again)? --------- Details -- the full check of the ER7 filters: After ER7, the hardware injection team and the search groups had identified a potential issue with the H1 hardware injection path. Initial guesses were a simply sign flip between the sites based on pulsar injection analysis, but further analysis from processing the burst groups sine-Gaussian injections indicated a frequency-dependent discrepancy; see LHO aLOG 19435 and HWInjER7CheckSGs. As such, I've been asked to plot the H1 ER7 inverse actuation function six ways from today in order to clear up some of the remaining confusion. See LHO aLOG 18997 for original documentation. Attached are plots, which are captioned below. Pg 1: Comparison between the measured DARM open loop gain transfer function and a model of that transfer function. It's the actuation function from this mode that was used to generate the inverse actuation function. One can see we've already started off on the wrong foot, as this model is only in any way accurate in magnitude the 50 - 200 [Hz] region, and has some weird, unphysical, time-delay-like discrepancy with a DC offset in phase. See LHO aLOG 18769 for all the gory details and flaws of this model. Pg 2: The inverse actuation filter I designed, and it's residuals with the "perfect" inverse actuation function from the above model. Note that I had tried to make the filter as simple as possible (which is what it's called a "toy model" in these plots), and "cheated" at high-frequency by demanding that the search groups are aware that the hardware injections will need an acausal time advance to be interpreted correctly. You can find discussion of why one needs an advance in the Mini-Run filter design, see LHO aLOG 18115, but in summary -- the real actuation function has a delay, so the inverse *must* have an advance to be accurate. This is similar to what's done with inverting the real sensing function when generating the gravitational wave channel. Pg 3: [[New Plot]] The inverse actuation filter with and without the time advance included, compared against the real model. The green trace in these plots are what has been implemented in the foton filter banks. Pg 4: [[New Plot]] Same information as pg 3, just zoomed in on the lower left panel, highlighting the phase of the inverse actuation filter. Pg 5: [[New Plot]] Since scientists can never agree on how to display the phase, I've displayed the residual phase between the real model and the toy model with and without the advance, in every different way of which I could think: - upper left is just a repeat of how I have been displaying the residual (see, e.g. the bottom right panels of pgs 2 and 3). - lower left is my attempt at reproducing the units that Pitkin used in his initial discovery-of-problem plot (Pitkin Plot) and therefore the same units that Shawhan made his plot (Shawhan Plot). - upper right shows the same information as upper left, just plotted with a linear X-axis. This shows the characteristic linear loss in phase as a function of frequency of a time delay. - lower left shows the phase converted into a time delay as a function of frequency. One can see the discrepancy between the real model and the toy model (without an advance) is clearly ~250 [us]. Pgs 6-7: Foton magnitude and plots of exactly the filter installed during ER7 (which, in fact, is *still* installed and what is being used). Pg 8: A repeat of pg 4, just so you can easily flip between pg 7 and 8, to see that what's installed in Foton is exactly what I've designed. Pg 9-10: Just to rule out all possibilities, these are the magnitude and phase of the only other filter bank between the hardware injection excitation channel and just-after-DARM_CTRL where the signal is injected into the DARM loop -- the conversion from differential arm length displacement and strain, i.e. the mean length of the arms. Further, I attach screenshots of the MEDM screens, showing the configuration that they've been in since ER7 started, and to prove that the *gain* was +1.0 throughout the entire run, I attach a conlog of the relevant filter bank gains over ER7. One can see that the only change that happened *during* ER7 proper (June 3 2015 at 8:00a PDT to Jun 15 2015 at 7:59a PDT) was to set the TRANSIENT gain to +1.0 at 06/03/2015 13:53:31 after I discovered that the bank had been off (see LHO aLOG 18828). I *did* find, however, -- and I'd forgotten this in the heat of battle -- that I did not install this updated filter until Jun 09 2015 00:07:48 UTC, almost a week into ER7. Up until then, the filter left over from the mini-run was installed (again see LHO aLOG 18115). Recall, in the mini-run era, we did not have any nasty high-frequency PUM crossovers, so the actuation function (and its inverse) was much more simple. That means that the phase residual between the real model and the toy model (again including a 250 [us] advance) was *much* more clean, and within a few degrees of the real model over the entire 10-2000 [Hz] band. Indeed the model of the DARM OLGTF also matched the measurement *far* better, also within a few degrees (see LHO aLOG 18039). *sheesh* The things you think about when writing it all down slowly. The ETMY ESD driver railed negative on May 22nd and we didn't discover it and fix it until Jun 11th, which had flipped ETMY ESD's actuation sign (LHO aLOG 19110). Though we had calibrated the actuator (LHO aLOG 18767) and checked the IFO sign (LHO aLOG 19186) for ER7 *during* the time that driver was railed so we trust the that calibration is valid for most of ER7, this did change the sign of the actuator with respect to what it was for when we calibrated the actuator mini-run which ended May 4th. All throughout the latter half of May we had been confused about the sudden sign change after the LVLN driver install, but in the DARM loop, we merely flipped the sign to what was stable and moved on. Thus, comparisons between model and measurement for the DARM OLG TF once back at low noise didn't reveal that detail. Could this be the problem? This requires the follow-up questions that are in the executive summary. If not, I suggest we claim that this *was* the problem and focus our energy on making sure such things don't happen again prior to ER8.
To answer Jeff's questions: > (1) When where the hardware injections made that were used for the analysis in the sine-guassian sign checks? > (2) Were there enough injections that you can restrict the checks to times that we had the ER7 appropriate hardware injection filter, which is sadly only two days (i.e. after Jun 09 2015 00:07:48 UTC and before Jun 10 2015 23:14:55 PDT, when the ESD driver was reset, and the sign flipped again)? The LHO loud sine-gaussian checks (alog 19006) were done around GPS 1117891250 = Jun 09 2015 13:20:34 UTC. That's within the two-day window when the filter should've been correct. Of the four coherent burst injections that Salvo and others analyzed, the first was at GPS 1117499153 = Jun 05 2015 00:25:37 UTC, and the other three were all within the span of about an hour, June 11 13:18 to 14:19 UTC. So those injections were all outside the two-day window. This seems to deepen this mystery rather than resolve it... Burst injections were done into H1 (usually without L1) at various times between June 4 and June 11, so maybe we can try to measure the phase for each of them and see if there is any distinct time dependence. But that will take a little work.