State of H1: locking and making it NLN
Assistance: Sheila, Evan
Activities:
Site:
More musings on the wind. - summary - Brian suspects that the motion of the building above 20 mHz is caused by turbulence generated at the building by the wind, and that below 20 mHz it is caused by the overall wind velocity. There is strong evidence of vortex shedding along the building. We see significant lateral tilting of the slab (ie transverse to the wind direction), and the motion along the wind direction shows a change in character which coincides with Strouhal number, which describes the vortex shedding scale. - not so summary - Jim W reported a big windstorm starting early in the morning local time on Oct 14. https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=30592 I took a look at the impact of the this wind storm on the tilt of the End Y slab as seen by the ground STS-2 and BRS. We know this slab bends, so this is just the motion near the tank, not of the whole floor. All the data, plots, and matlab code is in the seismic SVN at seismic/Common/Documents/T1600506_LHO_wind/wind_data_oct15 Pages 1-3 wind history. - wind is variable, but high The data spans 21 hours, starting at about 11pm pacific time on Oct 13. The wind really gets going at about 1 am PDT Oct 14. There are several hours where the speed at EY is in the 15-20 m/s (33-44 miles/hour). The wind speed is different at the two end stations. The wind direction at EX shows that mostly the wind comes from the SW, up along the Y arm towards the corner station. WE ASSUME that the wind direction is similar at EY, even though the direction indicator there remains broken. (see pg 14 for the direction read by the EY station - you can see that it is broken.) Pages 4-7 Data selection Because the wind is variable, I decided to use just 3 segments where the wind is pretty steady. These are labeled t3, t12, and t13 for the hour they span. t12 = avg speed = 15.1 m/s, time span = hour 11.5 - 12.5 t13 = avg speed = 9.2 m/s, time span = hour 12.6 - 13.7 t3 = avg speed = 8.4 m/s, time span = hour 3.0 - 4.2 Pages 8-10: Coherence is very low above 20 mHz Plot the coherence of various signals at end Y during the three times. The BRS and the STS-2 Y signals are very coherent from 10 -100 mHz during 15 m/s wind at 9 m/s, they are very coherent, but the primary microseism is evident at 70-80 mHz as a drop in the coherence. Below 20 mHz, there is some coherence between the wind speed (also speed^2) and the STS-Y signal. Above 20 mHz there is no coherence between wind speed and anything. The lack of coherence could be caused by the pixelization of the wind speed, but more likely is caused by turbulence at the building. ie - the speed at the anemometer is not a good measure of the net force on the building at 30-100 mHz because the turbulent flow of the air around the building means that wind speed/ building force at various points across the building at 30-100 mHz (30 sec to 10 sec periods) are not coherence with each other or the anemometer. This does not sound crazy because turbulence is chaotic. page 11-12: tilt motion of End Y The wind is blowing in the -Y direction. The building is tilting in both X and Y - the X motion is 2-3 times larger that the Y motion. This is interesting, and I'm not sure why we see this. Points to consider: 1) Maybe there is wind blowing in X? I don't think so. All the data we have says the wind is blowing along Y. 2) Vortex shedding - air blowing along the sides of the building causes big vortices, which break off and buffet the building side-to-side. This certainly happens with flag poles etc. I am sure this is happening, but I can't calculate how large an effect this is. 3) STS-2 location on the floor - The floor bends, and the farther you are from the walls, the smaller the tilt is at your location. I think the STS-2 is closer to the big +X wall than it is to either the smaller walls at -Y or +Y (-Y is the wall closest to the corner station). So maybe because the sensor is closest to the X wall, it is seeing more of the tilt in the X direction (rY). Again, this is probably true, but I'm not sure how much of an effect this is. Whatever the cause, the effect is quite clear at the sensor location, and thus at the location of the ETMY optic. Second plot on page 12 is the tilt seen by the EY BRS. The spectrum seems to have a corner at about 300-400 mHz. page 13 - BRS subtraction performance We see the BRS subtraction is beating the End-Y STS 2 above 15 mHz, and doing very well above 30 mHz. The two plots on page 13 compare the Y motion seen by the STS-2 Y in the corner station with the STS-2 Y motion on the floor in Y-end and with the real-time tilt-corrected signal formed by subtracting the BRS from the STS-2 ('H1:ISI-ETMY_SUPER_Y_OUT_DQ') It is interesting to see that the y-end station has significant excess motion above 250 mHz in the high wind. this may be affecting the subtraction at 40-100 mHz (mccs2 might be able to tell you, but I have not checked). Page 14 - tilt scaling with wind speed. Does the tilt spectra scale like avg wind speed^2? Nope! Plot 14 shows 3 BRS spectra, each with a polynomial fit. average wind speeds are: t12 = 15.1 m/s, t13 = 9.2 m/s, t3 = 8.4 m/s, (t12/t3) = 1.81, (t12/t3)^2 = 3.3 (t13/t3) = 1.1, (t13/t3)^2 = 1.2 (t13/t12) = 1.64, (t13/t12)^2 = 2.7 If the ground tilt were simply a shaped spectrum which scaled as wind^2, then the dashed blue curve would be a flat line at 3.3, the dashed red line a flat line at 1.2, and the dashed purple would be a flat line at 2.7. Clearly this is not the case. turbulence? more turbulence at high wind speeds? Page 15 - EY wind direction indicator is still busted. EX sensor says the wind is mostly blowing in the -Y direction. EX sensor signal is wierd and crappy. Only processing I did was to take the the sensor readings, and if they were > 180, then I subtracted 360 from them. EY is still busted, but we knew that already. On the shape of the BRS rotation curve: A casual look at the ground rotation indicates there might be some change in the slope of curve at about 200 mHz for the blue, 15 mps curve, and a similar bend at about 130 mHz in the red/ yellow curve for the 8-9 meter/sec wind speed. This corner is very close to characteristic frequency given by the Stouhal number for vortex shedding. Interesting! WARNING - These dimensionless numbers are intended to give a sense for the scaling of what is going on, NOT to predict what will happen (unless you happen to have a perfectly spherical building with no ground nearby) Strouhal number for vortex shedding (https://en.wikipedia.org/wiki/Strouhal_number) For a Reynolds number of 1e7, the Strouhal number, St, is ~0.3. St = f * L / v. here the characteristic length is the length of the building so L is about 80 ft = 24 meters f = 0.3 * v /24 for v = 15 m/s, f = 0.19 Hz for v = 9 m/s, f = 0.11 Hz Reynold's Number The flow is turbulent; the reynolds number is ~10^7 (https://en.wikipedia.org/wiki/Reynolds_number) Reynolds number = ( velocity * L)/(kinematic-viscosity) kinematic-viscosity = 1.460×10−5 m2/s for the atmosphere at sea level.(wikipedia) L = 18 meters (building width) or 12 meters (building height) v = 9 to 15 m/s R1 = 15 m/s * 18 m / 1.46e-5 (m^2/s) = 18* 10^6 R2 = 9 * 12 / 1.46e-5 = 7 * 10^6 - so if you are breaking off vortices at something like the frequency given by the Strouhal number, then I guess it is not crazy to think the building rocking will show that characteristic frequency. Need to follow up with someone who knows about these things!
Yesterday with the boot of h1oaf, the matrix elements for Modes 27 & 28 began using TRY QPD CHAN2 rather than OMC DCPD CHAN2. This is because the safe.snap was set for TRY QPD CHAN2. This file had not been updated since 18 October, even though these elements were set on 20 October. Based on the trends, looked like this was spotted again last Tuesday when the OAF was restarted, again, the SDF was not updated.
There are currently ~40 diffs on the SDF and no NOT_MONITORED channels. Maybe some of the gains and filters of these channels should be not monitored so things like signal source path changes will stand out.
I have written a script to decode the STATE_WORD reported on a model's GDS_TP MEDM screen. The script is called decode_state_word and takes the STATE_WORD as its argument.
For example, last night the h1iopoaf0 STATE_WORD went from 512 to 652 (data obtained from dataviewer trends)
david.barker@zotws2: decode_state_word 512
OVERFLOW
david.barker@zotws2: decode_state_word 652
ADC
DAC
DACKILL
OVERFLOW
J. Kissel (Belated entry from last night) During last night's ~1hr lock stretch over 02:00-03:00 UTC, I've continued a second round of tuning on the actuation side of the reference transfer functions for speed while retaining SNR. I was only able to make it through the lower two stages (L2 and L3, or PUM and TST) of H1SUSETMY before the IFO began having problems LHO aLOG 31345, but those series of 4 templates (to PCAL2DARMs and two iEXC2DARMs) can now be run in under 20 minutes. The frequency vectors go from 5 Hz to 1.2 kHz for all stages -- the lower limit defined by the inability for the PCAL to drive above the noise to any lower frequency, and the upper limit defined by the integration time and actuation strength of the QUAD. Note, we want to go out to ~1 kHz not because the actuator plays and important role in the DARM loop up there, but to better nail down and delays that have been otherwise constantly confusing (see e.g. LHO aLOG 29259). I've also increased the density of points above 100 Hz, in order to improve the fidelity of future fits. The new data live here: /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/Measurements/FullIFOActuatorTFs/2016-11-08/ 2016-11-08_H1SUSETMY_L1_iEXC2DARM.xml 2016-11-08_H1SUSETMY_L2_iEXC2DARM.xml 2016-11-08_H1SUSETMY_L2_PCAL2DARM.xml 2016-11-08_H1SUSETMY_L3_iEXC2DARM.xml 2016-11-08_H1SUSETMY_L3_PCAL2DARM.xml Again, note that the L1 template has in complete data, and I was not able to get a corresponding PCAL2DARM transfer function. Will try again one more time this week -- hopefully we can find the problems impacting our duty cycle so this isn't a burden.
The attached plots show a length noise injection into the PMC using TFIN. The first plot is calibrated in Volts for the HV_MON, whereas the second plot is calibrated in displacement. The coupling coefficient at 1 kHz is about 3.5 x 10-8 between the PZT and DARM length.
The reference traces 0 and 1 are without injection, whereas reference traces 2, 3 and 4 are from before the changes on the PSL table on Tuesday.
A measurement done at the very beginning of the run had about half the coupling—indicating that the coupling depends on thermal lensing.
The attached plot shows frequency and intensity noise measured by the IMC/REFL and second loop ISS sensors.
There is coherence above 1 kHz with intensity noise. Using the intensity noise coupling TF from alogs 30274 or 29926, one can conclude that it doesn't couple through intensity noise. The intensity noise is at 10-8 RIN/rtHz at 1 kHz. With a coupling of 10-13 m/RIN, we are far below the DARM noise.
The frequency noise produced by the PMC length noise is of the order of 1 Hz/rtHz at 1 kHz. It will be suppressed by the FSS, IMC and REFL. As such it is much too small to be responsible for the coupling directly. There is however, coherence with frequency noise as seen by REFL_A_RF9_I in the 1 kHz region. Assuming the REFL control signal is dominated by IMC sensing noise which seems to be around 2 x 10-4 Hz/rtHz at 1 kHz for 25 W input, see alog 31138, and using the noise coupling from alog 31176, we get a number around 10-19 m/rtHz at 1 kHz. So, it is conceivable that the PMC noise produces error point offsets in the REFL servo which in turn propagate to DARM as frequency noise.
We saw an increase of the PMC length noise coupling to DARM, when we misaligned SRM by 20 µrad. According T0900142 the requirement for SRM is 2.5 µrad which puts the required 3x10-6 /rtHz at 1 kHz with a safety factor of 10. So, for 20 µrad, a jitter of 7x10-6/rtHz at 1kHz is at the DARM noise level at full sensitivity. Our jitter was roughly 5x10-6/rtHz and it made a difference at the 1x10-19 level. Maybe somewhat higher than expected but close.
Looking at the IMC WFS signal we can clearly see the PMC length noise injection. If we take the 260 Hz periscope peak as a reference, this doesn't explain the coupling to DARM. What is surprising is that even without length noise injection (REF traces), the coherence between IMC WFS and PMC HVMon is large at frequencies between the jitter peaks.
This measurement was repeated with just the IMC locked at 25 W and ISS second loop enageged. This did not change the HV MON coherence with the IMC WFS nor the coherence with MC_F.
Sheila reported that Nutsinee switched the SEI_CONFs to BLEND_45mHz_SC_useism last night but looking this morning I see that it did not switch the Blend on ETMY. I manually switched the (X & Y dof) Blends only; the Sensor Correction did switch to not use the BRS. Otherwise all switching worked with Sensor Correction for all Test Masses and no BRS in use at the Ends.
by the way, I noticed this issue because I saw the SDF differences at the end stations were not the same. Since this is a guardian controlled feature, it might be argued that it would be Not_Monitored. Were that the case...
In case you are wondering what difference this can make...
The attached asd shows the ETMs 12 and 6 hours ago. 12 hours ago (ref traces) the ETMY was in 250mHz blends while the ETMX was in the 45mHz blend. 6 hours ago was after the ETMY was actually switched to 45mHz blends.
The thick green and brownish curves become much more like the others after the blend switching and moving the blend gain peaking away from the secondary microseismic peak.
The second attachment are trends of theX & Y ARM SUSPOINT Motions based on the ISI's onboard GS13s and the ETMY and ITMY SWSTAT showing when the ITMY blend switched but the ETMY did not and then this morning when the ETMY switched to the same blend as the ITMY. When the two ISIs are in different blends, the motion is clearly larger although based on these trends. Based on the XARM Motion though, not clearly a better blend overall.
ETMY_ST1_CONF wasn't switching properly because I had found an issue with the guardian when trying to write some different configurations. I forgot to revert the code to a properly working state. Sorry. I've fixed the configuration, and tested that it works on ETMY.
State of H1: aligned and locking, has made it to NLN but lost lock, ALS Y arm fiber polarization shot up to 28%, now adjusted back down
Activities:
H1 Observations:
It appears that the new channels in the h(t) frames contain some NaN or inf values that the DQ program refused to process. This cause the low-latency data to hang. In order to repair this I had to set an environment variable and restart the process managers on h1dmt0 and h1dmt2. Hopefully everything will run smoothly from here out.
Attached are the results of the BSC and HAM spectra as requested by FAMIS 6871. I didn't see anything glaring, but I also don't know what I'm looking at.
Generally these all look fine with regard to the intention of this test. There are no outlying base levels in the higher frequency (above the 'details' < 20 Hz) range.
here is the timeline of yesterday evening's h1oaf0 DAC problem which required a restart of the IOP model
All times are local PST.
Prior to the problem, h1iopoaf0 STATE_WORD is 512 (OVERFLOW)
delta-T | time | event |
0:00 | 19:23:00 | IOP DAC drives go to zero volts. h1iopoaf0 STATE_WORD=652(ADC,DAC,DACKILL,OVERFLOW) |
+5:00 | 19:28 | phone conversation, decision to restart IOP models |
+11:00 | 19:33 | models restarted after killing them, DAC drive is restored. Presumably killing model h1susprocpi caused lock loss |
Jeff,
This monitor has been regularly sounding. Below are the PSL dust monitors in their current configurations. There were no incursions today. No fans or environmental controls were changed and winds are below 10 mph.
16:51 Daniel and Keita out to LVEA to work on PMC
17:09 Hugh reports that ISI_CONF reporting ETMY at BLEND_45mHz_SC_useism is actually incorrect. It's actually set to the 250mHz.
17:13 LASER tripped (injection locking) while Keita and Daniel working in PSL rack. Jason coming to control room to restart.
17:56 Relocking resumed
17:57 Cheryl on site
J. Kissel, D. Tuyenbayev Following preliminary results from Darkhan on the individual actuation strength of the UIM and PUM stages for H1SUSETMY (see, thus far LHO aLOG 31275), and the current delightfully long lock stretch with them in place, I'm bringing this study to a close. I've turned off the temporary L1 and L2 calibration lines at 33.7 and 34.7 Hz, respectively. We do not intend on turning on these lines again for the duration of the run. These lines were turned OFF at Nov 07 2016 21:21:49 UTC.
Summary
A refined analysis of the L1, L2 and L3 stange actuation strenghts was done using the data from last several days that include several low-noise lock stretches. Actuation strength factors are:
KU = 8.020-8 +/- 2.983-10 N/ct ( std(KU) / |KU| = 0.0037 )
KP = 6.482-10 +/- 2.748-12 N/ct ( std(KP) / |KP| = 0.0033 )
KT = 4.260-12 +/- 1.313-14 N/ct ( std(KT) / |KT| = 0.0031 )
Details
Following 4 lines were used to calculate the factors: UIM (L1) line at 33.7 Hz, PUM (L2) line at 34.7 Hz, TST (L3) line at 35.9 Hz and PcalY line at 36.7 Hz. The most recent DARM model parameters were used for this analysis. Also, values past Nov 5 were calculated with the updated DARM filters (see LHO alog 31201), not accounting for this would produce results biased by 1-2%.
Each data point is a quantity calculated from 10s FFTs. The outliers were removed in two steps:
- took the mean and the standard deviation of all data points in intervals when the IFO range was >=50 MPC, removed 3-sigma outliers;
- removed the 3-sigma outliers from the mean of the remaining data points.
The mean values and the standard devitaions noted above were taken from GPS time interval [1162369920 1162413500], ~11 hours of low-noise data (blue markers). Standard errors on the mean values, std(Ki) / sqrt(N), are orders of magnitude smaller compared to the Pcal and the DARM loop model uncertainties (number of data points in the seletected interval - N=4251).
For preliminary results from Nov 4 data and before see related reports: 31183, 31275.
Recall the ER8/O1 values for these coefficients were 'Optic' 'Weighted Mean' '1-sigma Uncertainty' '1-sigma Uncertainty' 'Stage' '[N/ct]' '[N/ct]' '%' 'ETMY L1' '8.17e-08' '3.2e-09' '3.9' 'ETMY L2' '6.82e-10' '5.2e-13' '0.076' 'ETMY L3' '4.24e-12' '4.1e-15' '0.096' from LHO aLOG 21280. Comparing against numbers above, KU = 8.020-8 +/- 2.983-10 N/ct ( std(KU) / |KU| = 0.0037 ) KP = 6.482-10 +/- 2.748-12 N/ct ( std(KP) / |KP| = 0.0033 ) KT = 4.260-12 +/- 1.313-14 N/ct ( std(KT) / |KT| = 0.0031 ) This means a change of (ER8 - ER10)/ER8 = ETMY L1 0.0183 ETMY L2 0.0495 ETMY L3 -0.0047 We will compare these numbers against those determined by frequency-dependent transfer functions, e.g. the to-be processed data from LHO aLOG 31303, and update the low-latency/ calibration accordingly next week. It will also be interesting to re-cast the L1 and L2 numbers into a combined actuation strength change from ER10/O1, and compare it against the constantly calculated kappa_PU and check consistency there.
Data points prior to DARM filter update mentioned in the report were analyzed with the help of following DARM model parameters:
ifoIndepFilename : ${CalSVN}/Runs/PreER10/Common/params/IFOindepParams.conf (r3519)
ifoDepFilename : ${CalSVN}/Runs/PreER10/H1/params/H1params.conf (r3640)
ifoMeasParams : ${CalSVN}/Runs/PreER10/H1/params/H1params_2016-10-13.conf (r3519)
and after the the DARM filters were updated (GPS 1162336667) the following configuration was used:
ifoIndepFilename : ${CalSVN}/Runs/PreER10/Common/params/IFOindepParams.conf (r3519)
ifoDepFilename : ${CalSVN}/Runs/PreER10/H1/params/H1params_since_1162336667.conf (r3640)
ifoMeasParams : ${CalSVN}/Runs/PreER10/H1/params/H1params_2016-10-13.conf (r3519)
Scripts were uploaded to CalSVN at
${CalSVN}/Runs/PreER10/H1/Scripts/Actuation/2016-11-08/
5 days SLM data (75 MB): ${CalSVN}/Runs/PreER10/H1/Measurements/Actuation/2016-11-08/
Plots: ${CalSVN}/Runs/PreER10/H1/Results/Actuation/2016-11-08_H1_UPT_act_strengths_*
We discovered that in the single-line analysis we had an incorrect sign for TST stage actuation (we incorrectly set the sign of the N/ct coefficient).
The updated results have been posted in LHO alog 31668.
This is a comparison between the ISS, ILS and PMC signals before (REF traces) and after the changes in the electroncis and the modulation depth, see 31095.
A few observations:
A better plot showing the relationship between the ILS and PMC mixer and HVMon signals.
Reducing the ILS gain by 16 dB increases the noise seen by the PMC by the same amount below 1 kHz. This change reduced the ILS ugf from ~10 kHz down to ~1 kHz.
The PMC PZT is decribed in alog 30729:
The ILS PZT is
Evan, Stefan,
We re-measured the frequency noise coupling to DARM from the four sensors we have: REFL9 (in-loop), and POP9, REFL45, POP45 (all out-of-loop).
Plot 3 shows that transfer function in m/ct. (For REFL 9, the calibration from Evan 1.5e-7W/ct, see e.g. 30286. We didn't calibrate the others in W yet.)
Plot 1 shows the projection of all 4 sensors to DARM. The fact that POP9 disagrees with the others - but is coherent with them (Plot2) suggests that what limits our sensing is not frequency noise.
Finally, Plot 4 shows the relative calibration of the four sensors for frequency noise.
The xml files are in
/ligo/home/controls/sballmer/20161103/FreqNoiseProjection.xml
/ligo/home/controls/sballmer/20161103/REFLPOPV2.xml
Also, for reference, the frequency noise injection was done between 21:36:50 and 22:02:50 UTC on Nov 03 2016.
Here is a frequency coupling TF calibrated into meters per hertz, using the above data.
The calibration uses the whitening gain (12 dB), the digital gain (0.36 ct/ct), the ADC gain (216 ct / 40 V), the demod gain and transimpedance (2600 V/W), and an assumed CARM plant with a dc gain of 13 mW/Hz and a pole at 0.63 Hz. The numbers for the plant come from OLTF budgeting from O1 (so these numbers are quite old and may have changed).