I set up an accelerometer on the beam tube and measured the accelerations as I simulated the tapping that I observed during cleaning, and my tapping experiment mentioned here: https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=19038. Examination of the time series indicated that accelerations during typical taps reached about 1 m/s^2. I suspect that some taps reached 1g. The figure shows spectra for metal vs. fist taps. The above link notes that I was unable to produce glitches while hitting the beam tube with my fist. The fist and metal taps both had about the same maximum acceleration of 1 m/s^2 (ambient acceleration levels are about 4 orders of magnitude lower), so the source of the difference in liberating the particles is probably not acceleration. Instead, it may be the change in curvature of the beam tube, which would be expected to be greater at higher frequencies. The responses from metal taps in figure 1 peak at about 1000 Hz while the fist taps peak at about 100 Hz. These results are consistent with a hypothesis that the metal oxide particles are liberated by fracture associated with changes in curvature rather than simple vertical acceleration.
When I was producing glitches in DARM for the link above, I noticed that we did not get glitches every metal tap but every several metal taps. I tried to quantify this by making many individual taps at several locations along the beam tube. Unfortunately, we lost lock with the first loud glitch and I did not get a chance to repeat this before the vent. Nevertheless, it would be good for DetChar to look for smaller glitches at the time of the taps given below. Allow a 1 second window centered around the times given below for my tap timing uncertainty. I tapped once every ten seconds, starting at ten seconds after the top of the minute so that there were six taps per minute.
UTC times, all on June 14
Location Y-1-8
20:37 - 20:38 every ten seconds
20:47 - 20:50 every ten seconds
Next to EY
20:55 - every ten seconds until loss of lock at 20:56:10
I don't think the IFO stayed locked for the whole time. The summary page says it lost lock at 20:48:41, and a time series of DCPD_SUM (first plot) seems to confirm that. I did a few spectrograms, and Omega scanned each 10 seconds in the second series, and the only glitch I find is a very big one at 20:48:00.5. Here is an Omega scan. The fourth tap after this one caused the lock loss. Detchar will look closer at this time to see if there are any quiet glitches. First we'll need to regenerate the Omicron triggers... they're missing around this time probably due to having too many triggers caused by the lockloss. I'm not sure why there's a discrepancy in the locked times with Robert's report.
Any chance this could be scattered light? at 1 m/s^2 and 1 kHz, it is a displacement of 25 nm, so you don't need fringe wrapping.
I think that you would expect any mechanism that does not require release of a particle to occur pretty much with every tap. These glitches dont happen with every tap.
Here I present some results from our first Pcal sweep measurement (alog 19128 and 19132) in 5-5000 Hz frequency range.
The main conclusions are:
-----
This time, our traget was the sensing function or the DARM optical plant in counts/meters. To access the sensing function, we essentially need two different measurements i.e. a TF from ETM displacement to DARM_IN1 [cnts/meters] and DARM loop suppression [cnts/cnts]. Jeff took an open-loop TF and Pcal sweep for each arm, but unfortunately the Y arm measurement did not complete (alog 19128). Approximately 8 hours later of Jeff's measurements, TJ managed to measure a sweep of Pcal Y and DARM suppression TFs (alog 19132). So in total we have three different Pcal sweep data sets as follows,
The first two measurements were from a same lock stretch, and the last from a different lock stretch. All the measurement were made with a PSL requested power of 17 W. The plots below show the main results:
The first plot shows the estimated sensing functions from all three sweep measurements. As seen in the plot, signal-to-noise ratio becomes significantly low above a few kHz. Also as the sweep goes across the fundamental and the second harmonic of the violine modes, the coherence dropped and hence a low signal-to-noise ratio. The cyan solid curve represents the model that we have used for generating GDS and CAL-CS where the DC gain is set to 1.311x-6 cnts/meters and a cavity pole frequency to 355 Hz. Additionally, I set a delay time of the model to 55 usec by eye-ball fitting without any good explanation.
The second plot shows the residual between the measrured and model transfer functions. Even though the first two measurements were from the same lock stretch, they differed by approximately 20 % from each other. I am not sure what caused the descrepancy, but it is clear that the descrepancy is mostly in the scaling factor. The last measurement, which was from a different lock stretch showed a lower optical gain by 20 %. We know that our LSC automation can cause such a variation in the optical gain (alog 19014). So I believe that this 20% reduction is real and not due to some calibration in Pcal. Also the first and third measurements showed significant drop in the magnitude below 10 Hz by more than 50 %. Since the phase does not seem to roatte below 10 Hz, this is not a simple zero-pole argument. Looking at the Pcal active intensity stablization servos, Darkhan and I cofirmed that there was no saturation when the low frequencies were measured (although Pcal Y seemed to have saturated at the beginning of the measurement, meaning higher frequencies). We have no idea.
The analysis code, measurements and figures can be found in:
[sus crew]
Following the in chamber work from today at end-Y we took quick TFs on the quad and the transmon. They look ok.
Since the pump won't happen before tomorrow I started matlab tfs for all DOF.
The measurement will be running for few hours.
More clue on the TMSX measurement showing a different TF than before the vent (cf log below 19246). I looked at the response from pitch and vertical drive to the individual osems (LF, RT) and it looks like something is funny with the RT osem which should have the same response as the LF one, cf light red curves below
EDIT : Actually, LF and RT osem response are superposed on the graphs (green LF lies under red RT), so their response is the same.
ETMY ant TMSY transfer functions were measured on thursday after the doors went on, with chamber at atmospheric pressure. They did not show signs of rubbing, cf the first two pdf attached showing good agreement with previous measurements.
Today, I remeasured the vertical dof, after the suspension sagged ~120um from the pressure drop, and it still looks fine, cf figures below.
ETMX and TMSX were measured today when pressure in chamber was about 3 Torrs, after the QUAD sagged by about 130um.
The second pdf attachment on the log above was supposed to show TMSY transfer functions. Attached is the correct pdf.
Kyle -> Soft-closed GV7 and GV5 -> Vented HAM6 Bubba, Hugh, Jim W. -> Removed HAM6 South and East doors Kyle, Gerardo -> Installed NEG and TMDS reducer nipple+valve+elbow at X-end Danny S., Gary T., Gerardo, Kyle -> Hung North door on BSC10 (NOTE: Noticed ~1 hour before hanging door on BSC10 that the purge-air drying tower had been left off since tying-in the 1" TMDS line on Monday afternoon -> Turned it back on and notified the ETMY discharge crew
Forgot to log -> Purge-air measured <-39 C just prior to venting HAM6
To test the power-up status of the SUS HWWD, I activated the SUS ITMY HWWD which is located in the CER SUS-C6 rack. The long DB-37 cables which run from the ITMY M0 OSEMS were not connected to the monitor ports of the HWWD. I found the cables on the top of the rack, and after verifying they were connected to the monitor ports of the satellite amps for ITMY M0 (located in the LVEA beer garden) I plugged them into the HWWD.
After the tests were completed, I disconnected the cables in the CER and returned them to the top of the rack.
Scott L. Ed P. 6/15/15 Cleaned 33 meters ending at HNW-4-076. Removed lights and move to next section north. Test results posted here. 6/16/15 Rehang lights, vacuum support tubes, spray heavily soiled floor areas with water/bleach solution and begin cleaning beam tube. Cleaned 19 meters ending at HNW-4-077. 6/17/15 Cleaned 60.6 meters ending at HNW-4-080. A total of 3603 meters of tube have been cleaned to date.
Hugh, Bubba, Andres, Jeff B. After removing the HAM6 south & east doors, we rolled two cleanrooms and a garb room around the south and east sides of the HAM5/6 big cleanroom. The fans are on. There will be a cleaning of these cleanrooms in the morning. NOTE: The south corridor from just before HAM5 to the north side of the HAM5/6 big cleanroom is blocked. Access to the north side of the output arm will be from the long way around.
Will run the Aux cleanrroms overnight before using. Thxs to Andrias Jim Bubba JeffB
Dan Hoak gave us a clue on page 19067 and then Bas Swinkels ran Excavator and found that the channel H1:SUS-OMC_M1_DAMP_L_IN1_DQ had the highest correlation with the fringes. Andy Lundgren pointed me to equation 3 from “Noise from scattered light in Virgo's second science run data” which predicts the fringe frequency from a moving scatterer as f_fringe = 2*v_sc/lambda. Using the time from Dan and the channel from excavator and the fringe prediction, I wrote the attached m-file. Fig 1 shows the motion, velocity, and predicted frequency from OMC M1 longitudinal. Figure 2 shows the predicted frequency overlayed with the fringes in DELTAL. Math works.
PS. Thanks to Jeff and the SUS team for calibrating these channels and letting me know they are in um. Thanks to Gabriele for pointing out an error in an earlier draft of the derivative calculation.
Remember -- HAM6 is a mess of coordinate systems from 7 teams of people all using their own naming conventions. Check out G1300086 for a translation between them. The message: this OMC Suspension's channel, which are the LF and RT OSEMs on the top mass (M1) of the double suspension (where the OMC breadboard is the bottom mass), converted to "L" (for longitudinal, or "along the beam direction", where the origin is defined at the horizontal and vertical centers of mass of M1), is parallel with the beam axis (the Z axis in the cavity waist basis) as it goes into the OMC breadboard.
Jeff, thanks very much for that orientation; that diagram is extremely useful. The data leads me to think the scattering is dominated by the L degree of freedom though. Here's why - In raw motion, T and V only get a quarter of a micron or so peak-peak, while L is passing through 2 microns peak-peak during this time (see figure 1, y axis is microns). Figures 2, 3, and 4 are predicted fringes from L, T, and V. L is moving enough microns per second to get up to ~50Hz, whereas T and V only reach a few Hz. I'd be happy to follow up further.
Peter F asked for a better overlay of the spectrogram and predicted fringe Frequency. Attached 1) raw normalized spectrogram (ligoDV), 2) with fringe frequency overlay from original post above, 3) same but b/w high contrast and zoomed.
Also, I wanted to link a few earlier results on OMC backscattering: 17919, 17264, 17910, 17904, 17273. DetChar is now looking into some sort of monitor for this, so we can say how often it happens. Also, Dan has asked us if we can also measure reflectivity from the scattering fringes. We'll try.
Calibration Team
The gravitational wave strain h(t) is given by h(t) = Delta L/L where Delta L is is computed using
Delta L = ± (Lx - Ly)
The sign of Delta L can be determined using Pcal actuation on the test mass. Pcal only introduces a push force so pcal readout signal (truly pcal excitation) is minimum when the testmass is away from the corner station (closer to pcal laser). From the first plot the phase between DARM/PCAL is ~ -180 degrees (DARM lags PCAL) which suggests that DARM signal from ETMX will be maximum when pcal is minimum (ETMX further away from corner station). Similarly, from second plot, since DARM and PCAL have a phase difference of ~-360 degrees (essentially 0 degrees), the DARM signal from ETMY is minimum when the pcal is minimum. This shows that the sign convention for the Delta L is '+'
Also the slope of the curve gives the time delay between Pcal and DARM signal chain. The time delay is about 125±20 us. This time delay can be accounted for, within the uncertainity, from the difference in signal readout chain outlined in Figure 3 attached.
Refer to LLO alog #18406 for the detailed explanation behind this conclusion.
I believe this sign check and the sign check at LLO are correct. For the record, below is how I reached that conclusion: The photon calibrator laser can only push, but there is a nonzero baseline intensity and you modulate the intensity around that. The question is, if you apply a positive voltage to the PCAL system input, do you get more force or less force on the test mass? Figure 21 of the PCAL final design document seems to show that the undiffracted beam through the AOM is what is sent to the test mass, so increasing the amplitude of the 80 MHz drive to the AOM REDUCES the force on the test mass. However, the AOM driver electronics could introduce a sign flip when it conditions the input voltage. To check that, I pulled up PCAL excitation and receiver photodiode data (e.g. H1:CAL-PCALX_EXC_SUM_DQ and H1:CAL-PCALX_RX_PD_OUT_DQ) and plotted a short time interval at GPS 1117933216. I saw that the PCAL photodiode signal variations are basically in phase with the PCAL input excitation, with just a ~30-40 degree phase lag at ~500 Hz, presumably from filter delay. So, applying a positive voltage to the PCAL system input causes more force on the test mass, and anyway the PCAL receiver photodiode measures intensity directly. I confirmed this for all four PCALs (H1 and L1, X and Y) and also confirmed that the transmitter and receiver photodiodes vary together. The PCAL pushes on the front of the ETM, i.e. on the face that the primary interferometer beam reflects off of. This being a pendulum, the ETM is closest to the laser (i.e., the arm is shortest) when the force is at its MAXIMUM. LLO alog 18406 has a comment consistent with that: "Theory of pendulums suggests that Pcal signal will be minimum when ETM swings further away from corner station". LHO alog 19186, above, has a statement, "pcal readout signal (truly pcal excitation) is minimum when the testmass is away from the corner station (closer to pcal laser)", which is more ambiguous because the ETM being away from the corner station would put it FARTHER from the PCAL laser. But both draw the correct conclusion from the data: with the intended sign convention, DARM should be at its positive maximum when the X arm is longest (ETMX is farthest from the corner station; PCALX intensity is at its minimum) or when the Y arm is shortest (ETMY is closest to the corner station; PCALY intensity is at its maximum), and that is what was reported at both sites.
Peter,
I disagree with one assumption in your argument, but it does not disprove (or support) the rest of your conclusions.
"The question is, if you apply a positive voltage to the PCAL system input, do you get more force or less force on the test mass? Figure 21 of the PCAL final design document seems to show that the undiffracted beam through the AOM is what is sent to the test mass, so increasing the amplitude of the 80 MHz drive to the AOM REDUCES the force on the test mass. However, the AOM driver electronics could introduce a sign flip when it conditions the input voltage."
As far as I know there's no sign flip in AOM electronics. Undiffracted beam gets dumped in BD2, while diffracted beam is sent to the ETM.
Unfortunately I couldn't find an explicit noting of it in our recent DCC documents.
Oh, the diffracted beam gets sent to the test mass? Then I agree, there isn't a sign flip in the electronics. (In figure 21 in the document, it looks like the undiffracted beam went to the test mass.) BTW, I've posted a multi-frequency look at the hardware injection actuation sign (and amplitudes and time delays) at https://wiki.ligo.org/Main/HWInjER7CheckSGs.
Following up an earlier report on narrow lines in early ER7 data ("ER7A"), attached are spectra and a longer list of lines found in the 5-2000 Hz band from examining an inverse-noise-weighted average spectrum over 149 hours of full-ER7 DC-readout data, using 30-minute Hann-windowed FScan SFTs. The overall spectrum is similar to before, but the additional data reveals more structure. Here are highlights and lowlight of apparent changes:
Thanks Keith!
Regarding the OMC dither lines, we had been running with the dithering enabled, but for nearly all of ER7 the error signals for the OMC-ASC loops were derived from the QPD signals. So, the dither lines were injected, but not suppressed. This choice was made because the dither signals acquire a large pitch offset when we run at high power, enough that using those error signals can saturate the OMC-SUS as the alignment loops try to correct. (The reason for the offset is not understood, maybe due to some junk light on the other QPDs used in HAM6 alignment that is not significant at low power.) Our preferred solution is to use something other than the OMC-SUS to center the beam, and switch to the dither loops for alignment. I wanted to keep the dither lines present to monitor the alignment drift during the run, this is something I haven't had a chance to follow up.
Before ER8 we will either switch to the dither signals for OMC alignment and move the frequencies above 2kHz, or decide to run on the QPD signals and turn off the dithering. Either way these nefarious lines won't be in the band. :)
I modified and restarted the BSC-ISI models to close ECR E1500245, E1500253 and E1500270. The changes are listed below, and described in details in the attached pdf.
* removed sts blrms calculation from the sensor correction of stage 1. The calculation is now done at the top level. A list of the new channel names is provided in the attached text files
* Added a pick off of stage 1 CPS X and Y signals to feed the LSC model through PCIE senders on BS ITMX and ITMY
* Added a path from sus to the error point of the stage 1 controls to use for tidal feedback (mainly for LLO).
I added a SUS OFFLOAD link to the BSC overview screen, which pops up the filtering window.
The modified medm and model files listed below have been commited to the svn.
arnaud.pele@opsws7:/opt/rtcds/userapps/release/isi/h1/models$ svn st
Corey, Keita, Kiwamu,
We conituned working on the remaining tasks for the TMSX in chamber (see alog 19157 from yesterday).
This morning we installed the strain reliefs for the two QPDs in which we had a difficulty inserting a screw due to bad threading. Today, we brought 10-32 screws so that the screw can go all the way through to the back without any interference from the bad threads. We put combination of a nut and washer on the other side to hold the 10-32 screw and the strain relief parts. We did this on the two QPDs. So now all four QPDs have the strain reflef parts installed.
We then balanced the table such that the green light is retro-reflected off of ETMY. The table seemed to have pitched by some amount. We decided to move the counter mass at the bottom of the table. The adjustement went very smooth and we were able to get the beam retrao-reflected all the way back to the PD on the ISCTEX table. Touching the TMS digital bias suggested that the pitch angle is good with a precision of about 4 urad. While pitch is good, yaw seemed to be slightly off. So we moved the digital bias in yaw as well and confirmed that adding an additional +40 urad (resulting in a bias of ) in the digital bias can give us a decent alignment on the reflection PD. So we are good in yaw too.
After initial balancing we were concerned that we did not use vented washers for the two QPDs which required the screw/nut workaround. Keita found that one QPD did NOT have a vented washer, so a vented washer was installed. This required a re-balance. We were a little off in pitch, so a counterweight (1/4-20 screw) was added to pitch the TMS.
Photos of this work from Mon afternoon & Tues morning is on ResourceSpace here.
(And ready for the SUS crew to take over.)
Green QPDs were confirmed to work using green beam on the day we entered the chamber.
Today (June 17), with a help from Gary, IR QPDs were confirmed to work using LED flash light.
(times in PST)
0:04 - Locked @ LSC_FF, started PCAL swept line measurement
0:29 - PCAL measurment done, started DARM OLGTF measurement
0:50 - Both measurements done and no more for now it seems, Intention Bit set to Undisturbed
The transfer functions that TJ measured for us have been renamed to be more obvious names as follows:
According to trend data, both mesurements seemed to have done at 17 W. The first file currently resides in aligocalibration/trunk/Runs/PreER7/H1/Measurements/DARMOLGTFs. The other one is in aligocalibration/trunk/Runs/ER7/H1/Measurements/PCAL_TRENDS.
By the way, according to what we had in the calibration svn, TJ must have accidently updated Jeff's DARM OL and Pcal Y sweep measurements with the above latest measurements. I restored Jeff's two measurements back to the previous revisions in the svn. So we now have both Jeff's and TJ's measurements checked in the SVN.
There were eight separate locks during this shift, with typical inspiral ranges of 60 - 70 Mpc. Total observation time was 28.2 hours, with the longest continuous stretch 06:15 - 20:00 UTC on June 11. Lock losses were typically deliberate or due to maintenance activities.
The following features were investigated:
1 – Very loud (SNR > 200) glitches
Omicron picks up roughly 5-10 of these per day, coinciding with drops in range to 10 - 30 Mpc. They were not caught by Hveto and appear to all have a common origin due to their characteristic OmegaScan appearance and PCAT classification. Peak frequencies vary typically between 100 - 300 Hz (some up to 1 kHz), but two lines at 183.5 and 225.34 Hz are particularly strong. These glitches were previously thought to be due to beam tube cleaning, and this is supported by the coincidence of cleaning activities and glitches on June 11 at 16:30 UTC. However, they are also occurring in the middle of the night, when there should be no beam cleaning going on. Tentative conclusion: they all have a common origin that is somehow exacerbated by the cleaning team's activities.
2 – Quasi-periodic 60 Hz glitch every 75 min
Omicron picks up an SNR ~ 20 - 30 glitch at 60Hz which seems to happen periodically every 70 - 80 min. Hveto finds that SUS-ETMY_L2_WIT_L_DQ is an extremely efficient (use percentage 80-100%) veto, and that SUS-ETMY_L2_WIT_P_DQ and PEM-EY-MAG-EBAY-SEIRACK-X_DQ are also correlated. This effect is discussed in an alog post from June 6 (link): "the end-Y magnetometers witness EM glitches once every 75 minutes VERY strongly and that these couple into DARM". Due to their regular appearance, it should be possible to predict a good time to visit EY to search for a cause. Robert Schofield is investigating.
3 – Non-stationary noise at 20 - 30Hz
This is visible as a cluster of SNR 10 - 30 glitches at 20 - 30 Hz, which became denser on June 11 and started showing up as short vertical lines in the spectrograms as well. The glitches are not caught by Hveto. Interestingly, they were absent completely from the first lock stretch on June 10, from 00:00 – 05:00 UTC. Daniel Hoak has concluded that this is scattering noise, likely from alignment drives sent to OMC suspension, and plans to reduce the OMC alignment gain by a factor of two to stop this (link to alog).
4 – Broadband spectrogram lines at 310 and 340 Hz
A pair of lines at 310 and 340 Hz are visible in the normalized spectrograms, strongest at the beginning of a lock and decaying over a timescale of ~1 hr as the locked interferometer settles into the nominal alignment state. According to Robert Schofield, these are resonances of the optic support on the PSL periscope. The coupling to DARM changes as the alignment drifts in time (peaks decay beacuse the alignment was tuned to minimize the peaks when the IFO is settled.) Alogs about this: link, link, link.
There are lines of Omicron triggers at these frequencies too, which interestingly are weakest when the spectrogram lines are strongest (probably due to a 'whitening' effect that washes them out when the surrounding noise rises). Robert suspects that the glitches are produced by variations in alignment of the interferometer (changes in coupling to the interferometer making the peaks suddenly bigger or smaller).
5 – Wandering 430 Hz line
Visible in the spectrograms as a thin and noisy line, seen to wander slightly in Fscan. It weakened over the course of the long (14h) lock on June 11. Origin unknown.
6 – h(t) calibration
Especially noisy throughout the shift, with the ASD ratio showing unusually high variance. May be related to odd broadband behavior visible in the spectrogram. Jeff Kissel and calibration group report that nothing changed in the GDS calibration at this time. Cause unknown.
Attached PDF shows some relevant plots.
More details can be found at the DQ shift wiki page.
I believe the 430 Hz wandering line is the same line Marissa found at 415 Hz (alog18796). Which turns out, as Gabriele observed, to show coherence with SRCL/PRCL.
Ross Kennedy, my Ph.D. student, implemented tracking of this line over 800 seconds using the iWave line tracker. Overlaid with a spectrogram, you can see that there is quite good agreement as the frequency evolves. We're working on automating this tool to avoid hand-tuning parameters of the line tracker. It would also be interesting to track both this line and PSL behaviour at the same time, to check for correlation. In the attached document there are two spectrograms - in each case the black overlay is the frequency estimate from iWave.