[Vaishali, Jenne]
We used the last few minutes of commissioning time today to measure the ASC sensing matrix. This is the first time that we have made this measurement since POPX was installed. Per JeffK's suggestion, we turned off the 7.9Hz calibration line to avoid confusion with our 8.125Hz measurement frequency (we used his new guardian state that actually turns off all the Pcal lines, then turns them back on before we go to NLN).
Vaishali is looking at this data to compare with previous measurements, and her Finesse model.
Recall that in the table below, elements that are grayed out have lower coherence.
dof: | CHARD |
INP1 |
PRC1 |
PRC2 |
DHARD |
SRC1 |
SRC2 |
MICH |
AS_A_DC_PIT |
2.65e+02 154 |
1.5e-03 266 |
5.51e+01 -179 |
8.72e+02 319 |
6.83e+03 160 |
6.46e+01 178 |
3.23e+02 179 |
2.96e+02 118 |
AS_A_RF36_I_PIT |
1.61e+04 -22 |
1.55e-01 247 |
6.02e+03 177 |
1.06e+05 321 |
1.7e+03 -84 |
5.27e+02 0 |
1.60e+04 0.4 |
1.56e+03 -96 |
AS_A_RF36_Q_PIT |
4.55e+03 -15 |
5.2e-02 43 |
1.88e+03 -158 |
2.10e+04 178 |
1.70e+05 161 |
5.63e+02 185 |
9.97e+03 358 |
1.58e+05 122.5 |
AS_A_RF45_I_PIT |
3.5e+02 107 |
6.7e-03 265 |
4.19e+02 175 |
7.54e+03 320 |
7.76e+04 -17 |
5.73e+01 181 |
4.6e+01 203 |
1.78e+03 -58 |
AS_A_RF45_Q_PIT |
1.34e+04 -28 |
6.09e-02 73 |
3.81e+03 -3 |
6.40e+04 136 |
1.58e+06 161.9 |
4.28e+02 357 |
6.55e+03 177 |
1.25e+04 -52 |
AS_B_DC_PIT |
3.95e+02 -21 |
5.69e-03 258 |
7.8e-01 65 |
4.24e+01 128 |
7.62e+02 3 |
1.02e+02 358 |
1.74e+02 177 |
2.72e+02 -60 |
AS_B_RF36_I_PIT |
1.32e+04 157 |
1.29e-01 68 |
5.44e+03 0 |
6.90e+04 138 |
8.00e+04 161 |
4.18e+03 179.5 |
1.14e+04 357 |
7.70e+04 126 |
AS_B_RF36_Q_PIT |
1.19e+04 -23 |
2.26e-01 263 |
5.16e+03 -176 |
8.15e+04 317 |
1.33e+05 158 |
3.34e+02 184 |
7.04e+02 173 |
1.43e+05 114 |
AS_B_RF45_I_PIT |
1.21e+03 -25 |
3.05e-02 80 |
8.27e+02 -1 |
1.33e+04 137 |
1.02e+05 162 |
3.74e+01 356 |
4.14e+01 4 |
1.28e+03 -50 |
AS_B_RF45_Q_PIT |
4.50e+03 130 |
1.63e-01 259 |
2.49e+03 176 |
4.08e+04 315 |
1.35e+06 -16 |
8.21e+02 2 |
1.90e+03 188 |
1.14e+04 129 |
AS_C_PIT |
1.90e-03 -19 |
6.30e-08 260 |
2.63e-04 177 |
3.88e-03 316 |
3.05e-02 167 |
6.92e-04 0 |
3.18e-03 179 |
1.31e-03 -56 |
REFL_A_DC_PIT |
1.5e+02 -10 |
2.49e-02 82 |
3.10e+00 -156 |
5.28e+01 139 |
4.6e+01 -2 |
1.3e-01 232 |
5.7e+00 352 |
9.5e+00 117 |
REFL_A_RF9_I_PIT |
2.98e+05 -18.2 |
5.72e+01 81 |
1.6e+03 -170 |
9.33e+04 152 |
2.0e+04 -30 |
6.0e+01 206 |
1.3e+03 188 |
2.4e+03 -112 |
REFL_A_RF9_Q_PIT |
1.30e+05 -15 |
8.46e+00 82 |
5.03e+03 -2 |
1.80e+04 151 |
9.2e+03 -1 |
3.3e+01 201 |
4.4e+02 351 |
1.7e+03 127 |
REFL_A_RF45_I_PIT |
2.81e+05 -18 |
7.26e+01 81 |
1.28e+04 -176 |
5.49e+04 171 |
1.6e+04 -26 |
1.9e+01 19 |
1.2e+03 181 |
1.06e+04 126 |
REFL_A_RF45_Q_PIT |
9.28e+04 -13 |
2.61e+01 82 |
4.22e+03 -179 |
2.00e+03 61 |
8.2e+03 1 |
3.79e+01 355 |
2.3e+02 346 |
2.3e+03 -98 |
REFL_B_DC_PIT |
1.06e+02 156 |
1.29e-02 259 |
4.90e+00 -175 |
3.32e+01 319 |
2.8e+01 150 |
5.97e-02 348 |
1.8e+00 336 |
7.8e+00 110 |
REFL_B_RF9_I_PIT |
2.61e+05 -15 |
6.47e+01 261 |
4.30e+04 -1 |
1.80e+05 147 |
2.83e+04 171 |
1.26e+02 341 |
4.8e+02 224 |
2.1e+03 -156 |
REFL_B_RF9_Q_PIT |
4.05e+04 -14 |
2.87e+01 261 |
1.45e+04 -1 |
5.14e+04 146 |
9.65e+03 170 |
9.13e+01 352 |
2.2e+02 210 |
9.38e+02 -150 |
REFL_B_RF45_I_PIT |
2.78e+05 -16 |
7.77e+01 261.4 |
4.00e+04 0 |
1.01e+05 324 |
3.12e+04 174 |
1.14e+02 2 |
4.8e+02 317 |
1.56e+04 -135 |
REFL_B_RF45_Q_PIT |
1.19e+05 -15 |
3.63e+01 261 |
1.97e+04 2 |
8.93e+04 334 |
9.03e+03 164 |
4.54e+01 328 |
3.2e+02 193 |
6.19e+03 44 |
POP_X_RF_I_PIT |
1.03e+05 166 |
3.34e+00 260 |
4.57e+04 179.6 |
7.56e+05 319.0 |
9.91e+03 84 |
5.73e+02 184 |
2.8e+02 359 |
6.12e+04 107 |
POP_X_RF_Q_PIT |
4.73e+03 162 |
6.0e-02 259 |
9.69e+02 -157 |
5.35e+03 285 |
2.14e+04 165 |
1.63e+02 171 |
2.4e+02 21 |
1.86e+04 126 |
POP_A_PIT |
4.76e+00 -18 |
1.65e-05 257 |
3.47e-01 178 |
2.91e-01 137 |
5.05e-01 -21 |
1.18e-03 359 |
3.8e-03 137 |
6.50e-02 -43 |
POP_B_PIT |
1.57e+00 163 |
3.22e-05 260 |
8.55e-01 178 |
2.24e-01 319 |
1.71e-01 -25 |
2.00e-03 177 |
2.6e-03 84 |
4.14e-02 118 |
X_TR_A_PIT |
3.02e+03 162 |
1.60e-03 275 |
2.57e+00 -175 |
6.52e+01 324 |
2.82e+03 161 |
1.50e-01 337 |
8.22e-01 156 |
2.73e+00 -159 |
X_TR_B_PIT |
3.54e+03 162 |
1.96e-03 283 |
3.42e+00 -167 |
8.17e+01 330 |
3.17e+03 160 |
2.84e-01 342 |
9.88e-01 128 |
4.85e+00 -168 |
Y_TR_A_PIT |
3.76e+03 161 |
2.15e-03 261 |
3.87e+00 158 |
9.11e+01 305 |
3.71e+03 -19 |
6.97e-02 9 |
8.77e-01 314 |
1.34e+01 122 |
Y_TR_B_PIT |
1.13e+03 162 |
9.64e-04 237 |
1.42e+00 127 |
3.01e+01 274 |
1.23e+03 -21 |
1.85e-01 358 |
3.4e-01 280 |
5.29e+00 124 |
Sheila found two issues when modifying the H1ASC.txt filter file this morning:
1. A change to an existing filer caused foton to freeze up
2. Loading a change to a filter (which was turned off) onto h1asc caused lock loss
I suspect both issues were due to the fact that today was the first time the h1asc filterfile was being handled by the new version of foton (with the higher number of significant digits in the gain).
issue 1) We later found that the foton freeze up could not be reproduced, perhaps it was because the old format file was being read and modified? We'll see if this error appears in other systems.
issue 2) Since every gain was recalculated with the higher number of digits, perhaps loading all the filters glitched the system enough to cause lock loss? One suggestion is that if a filter file is being changed to the new format for the first time, we should only load all of the filters on a Tuesday morning (or perhaps perform this full load on every model at that time).
whilst looking at ASC filter changes, I was surprised that a simple -20dB gain filter changed its calculated GAIN from 0.1000000000000000 to 9.999999999999997779553951e-02. I'm not sure if this is indicative of a problem.
It looks like the drives during ALS DIFF to ETMX are about a factor of 2.5 times larger than they were 2 years ago.
Kyle, Chandra Chandra had freed a bird that had got itself stuck in the "sticky mat" used to trap insects at the X-mid earlier today. Unfortunately, it flew into the VEA. Following Keita's Thursday 1 O-clock'ish meeting, we followed up by opening all of the roll-up doors and, with the lights off, persuaded it to exit. We had to "bump" the crane bridge a few times to encourage the bird to leave - which it eventually did. (Don't get me wrong. I'm all for recycling and liberating caught birds etc. but if she next finds a struggling beached whale along the X-arm access road - she's on her own!)
The bird was stuck on the black goo mat on the floor next to roller door, not the white sticky mats that we also use to trap rodents/insects. I was happy to see it fly so well after I peeled its wing and foot off.
Link to full report: https://wiki.ligo.org/DetChar/DataQuality/DQShiftLHO20170417
Summary below (see full report for details):
Yesterday morning I did a few tests of misaligning the OMC and putting excitations on the alignment loops. (see LLO alogs 32885 and comment and 28979 ). Depending on which method you use to estimate the normal RMS OMC alignment fluctuations, the OMC jitter noise is at least a factor of 2 below DARM or better.
offset | optical gain decrease | coupling increase | offset/error signal RMS | QPD offset/QPD rms (A/B) | |
POS Y | 0.6 | 4% | x5.8 | 10 | 60/56 |
POS X | 0.5 | 13% | x2 (no coherence) | 10.4 | 80/62 |
ANG Y | 1 | 12% | x2.6 (no coherence) | 5 | na/27 |
ANG X |
1 | 22% | x4.4(no coherence) | 17 | na/35 |
You can see that the behavior of POS Y is different from the other loops, this is the only loop where my offset was large enough to measure coherence between the excitation and DARM, but it was a small change in the optical gain. My excitations were not large enough to change the RMS seen on the QPDs (second attachment shows excitation sizes). Our OMC alignment loops are very slow, it takes 2-3 minutes for them to respond to a change in offset.
Some notes on what I think is implied in the LLO alogs:
When we are locked on DC readout the ratio of the optical gains for the misaligned/aligned OMC is the square root of what the ratio of transmitted powers would be if DARM were not locked on the DCPDs (thanks Keita):
My understanding of Koji's method for estimating the rms: (Delta theta is normal alignment fluctuations, dtheta is the excitation, and theta0 is the offset. )
I think that what Koji is doing is taking the ratio of (4)/(2) (coupling increase in the table above) and estimating that that is the ratio of the offset/normal RMS.
Spring enabled the EE shop to work on setting up power for the LEMIs, and I had a look at the new signals. The top plot in the figure shows that we can see Schumann Resonances quite well, up to quite close to 60 Hz. The bottom two plots show some transient signals that might interfere with a feed-forward system.
It looks like the signals are degraded by wind. I am not surprised because we see wind noise in buried seismometers. I think we would have this vibration problem even on a perfect flat because of the variation in Bernoulli’s forces associated with gusts. It may be that a LEMI signal is generated by the wind because of slight motions of the magnetometers in the earth’s huge DC magnetic field. We buried the LEMIs about 18 inches deep (https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=29096). I think we might be able to mitigate the noise some by going much deeper. Once we have the vault seismometer working, it would be a good project to test the wind vibration hypothesis by comparing the LEMI and seismic signals.
There also seem to be some transients, some long and some short, possibly self inflicted by our system. It would be good to look into which transients would be a problem, and for those, details such as whether they are correlated with time of day, the average time between transients, etc., in order to help determine their source.
Finally, I would like to get the full system calibrated by comparing to a battery powered fluxgate magnetometer.
[Pat Meyers, Andrew Matas] We attach a few additional plots studying the Schumann resonances. Figures 1,2 show spectrograms using 16 hours of data from April 18, where the Schumann resonances are clearly visible. There are also a few glitches. We also show coherence (Figure 3) and cross power (Figure 4) between the Hanford and Livingston LEMIs. The first two Schumann resonances at about 8 Hz and 14 Hz are coherent between the sites.
We disabled the vault power on April 20th to upgrade the power supply, it will remain down until the this afternoon.
At the start of the commisioning window I started a CHARD Y measurement and Robert is setting up laser vibrometers.
TITLE: 04/20 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 56Mpc
INCOMING OPERATOR: Nutsinee
SHIFT SUMMARY:
H1 locked for entire shift. Slight dip in range due to 5.5 Russian quake. Otherwise, non-eventful night.
LOG:
TITLE: 04/20 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 61Mpc
OUTGOING OPERATOR: Patrick
CURRENT ENVIRONMENT:
Wind: 26mph Gusts, 22mph 5min avg
Primary useism: 0.10 μm/s
Secondary useism: 0.19 μm/s
QUICK SUMMARY:
H1 freshly re-locked. Modes damped as per Patrick's aLog. a2l shows ETMX out in YAW by ~.68. Will run the dither script at my first convenience.
50 minutes later, the notion of running a2l is no longer necessary. It seems the loops have pulled the alignment together quite nicely. ETMX f1 Mode4 was rung up pretty good but is slowly ringing down as are it's counter-parts. Bounce and Roll have also diminished well below reference. Range is averaging ~ 60Mpc. Winds are ion the 20mph range.
TITLE: 04/20 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC STATE of H1: Observing at 61Mpc INCOMING OPERATOR: Ed SHIFT SUMMARY: Lock loss possibly coincident with wind gust at EY. Back to observing. Bounce mode around ~9 Hz is high but damping. Turned on FM6 per Ed's suggestion to damp ETMY violin mode at ~4kHz. LOG: 23:37 UTC GRB alert. LLO also received. 04:14 UTC LLO lost lock. Out of observing to run a2l. 04:23 UTC Back to observing. 05:59 UTC Lock loss. Wind gust at EY? 06:45 UTC Observing. Turned on FM6 for H1:SUS-ETMY_L2_DAMP_MODE10 and accepted SDF difference (attached). Damped PI mode 27 by changing phase.
Checked SDF change into svn.
Have remained in observing. Range appears to have recovered after initial dip. No known issues.
Evan G., Robert S. Looking back at Keith R.'s aLOGs documenting a changes happening on March 14 (see 35146, 35274, and 35328), we found that one cause seems to be the shuttering of the OpLev lasers on March 14. Right around this time, 17:00 UTC on March 14 at EY and 16:07 UTC at EX, there is an increase in line activity. The correlated cause is Travis' visit to the end station to take images of the Pcal spot positions. The images are taken using the Pcal camera system and needs the OpLevs to be shuttered so that a clean image can be taken without the light contamination. We spoke with Travis and he explained that he disconnected the USB interface between the DSLR and the ethernet adapter, and used a laptop to directly take images. Around this time, the lines seem to get worse in the magnetometer channels (see, for example, the plots attached to Keith's aLOG 35328). After establishing this connection, we went to the end stations to turn off the ethernet adapters for the Pcal cameras (the cameras are blocked anyway, so this active connection is not needed). I made some magnetometer spectra before and after this change (see attached). This shows that a number of lines in the magnetometers are reduced or are now down in the noise. Hopefully this will mitigate some of the recent reports of combs in h(t). We also performed a short test turning off another ethernet adapter for the H1 illuminator and PD. This was turned off at 20:05:16 18/04/2014 UTC and turned back on at 20:09:56 UTC. I'll post another aLOG with this investigation as well.
Good work! That did a lot of good in DARM. Attached are spectra in which many narrow lines went away or were reduced (comparing 22 hours of FScan SFTs before the change (Apr 18) with 10 hours of SFTs after the change (Apr 19). We will need to collect much more data to verify that all of the degradation that began March 14 has been mitigated, but this first look is very promising - many thanks! Fig 1: 20-50 Hz Fig 2: 50-100 Hz Fig 3: 100-200 Hz
Attached are post-change spectra using another 15 hours of FScan SFTs since yesterday. Things continue to look good. Fig 1: 20-50 Hz Fig 2: 50-100 Hz Fig 3: 100-200 Hz
Correction: the date is 18/04/2017 UTC.
Another follow-up with more statistics. The mitigation from turning off the ethernet adapter continues to be confirmed with greater certainty. Figures 1-3 show spectra from pre-March 14 (1210 hours), a sample of post-March 14 data (242 hours) and post-April 18 (157 hours) for 20-50 Hz, 50-100 Hz and 100-200 Hz. With enough post-April 18 statistics, one can also look more closely at the difference between pre-March 14 and and post-April 18. Figures 4-6 and 7-9 show such comparisons with different orderings and threrefore different overlays of the curves. It appears there are lines in the post-April 18 data that are stronger than in the pre-March 14 data and lines in the earlier data that are not present in the recent data. Most notably, 1-Hz combs with +0.25-Hz and 0.50-Hz offsets from integers have disappeared. Narrow low-frequency lines that are distinctly stronger in recent data include these frequencies: 21.4286 Hz 22.7882 Hz - splitting of 0.0468 Hz 27.4170 Hz 28.214 Hz 28.6100 Hz - PEM in O1 31.4127 Hz and 2nd harmonic at 62.8254 Hz 34.1840 Hz 34.909 Hz (absent in earlier data) 41.8833 Hz 43.409 Hz (absent in earlier data) 43.919 Hz 45.579 Hz 46.9496 Hz 47.6833 Hz 56.9730 Hz 57.5889 Hz 66.7502 Hz (part of 1 Hz comb in O1) 68.3677 Hz 79.763 Hz 83.315 Hz 83.335 Hz 85.7139 Hz 85.8298 Hz 88.8895 Hz 91.158 Hz 93.8995 Hz 95.995 Hz (absent in earlier data) 107.1182 Hz 114.000 Hz (absent in earlier data) Narrow low-frequency lines in the earlier data that no longer appear include these frequencies: 20.25 Hz - 50.25 Hz (1-Hz comb wiped out!) 24.50 Hz - 62.50 Hz (1-Hz comb wiped out!) 29.1957 Hz 29.969 Hz Note that I'm not claiming change points occurred for the above lines on March 14 (as I did for the original set of lines flagged) or on April 18. I'm merely noting a difference in average line strengths before March 14 vs after April 18. Change points could have occurred between March 14 and April 18, shortly before March 14 or shortly after April 18.
To pin down better when the two 1-Hz combs disappeared from DARM, I checked Ansel's handy-dandy comb tracker and found the answer immediately. The two attached figures (screen grabs) show the summed power in the teeth of those combs. The 0.5-Hz offset comb is elevated before March 14, jumps up after March 14 and drops down to normal after April 18. The 0.25-Hz offset comb is highly elevated before March 14, jumps way up after March 14 and drops down to normal after April 18. These plots raise the interesting question of what was done on April 18 that went beyond the mitigation of the problems triggered on March 14. Figure 1 - Strength of 1-Hz comb (0.5-Hz offset) vs time (March 14 is day 547 after 9/15/2014, April 18 is day 582) Figure 2 - Strength of 1-Hz comb (0.25-Hz offset) vs time
[ Jenne, Vaishali ]
Today we used the commissioning window to re-measure the ASC sensing matrix for Pitch and the results show that the values for the individual DoFs hasn't changed by too much. We will now make radar plot comparisons of the same and compare them to alog 26023 .
Sensing Matrix, [W/rad]
We are trying to figure out why the measurements look different compared to 26023 .