Displaying reports 64361-64380 of 83069.Go to page Start 3215 3216 3217 3218 3219 3220 3221 3222 3223 End
Reports until 16:56, Wednesday 17 June 2015
LHO VE
bubba.gateley@LIGO.ORG - posted 16:56, Wednesday 17 June 2015 (19202)
Beam Tube Washing
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.
Non-image files attached to this report
H1 General
jeffrey.bartlett@LIGO.ORG - posted 16:52, Wednesday 17 June 2015 (19204)
Cleanrooms at HAM6
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.    
H1 SYS
hugh.radkins@LIGO.ORG - posted 16:36, Wednesday 17 June 2015 (19203)
WHAM6 Doors S & E Removed, Aux Cleanrooms Energized, Will clean first thing AM

Will run the Aux cleanrroms overnight before using.  Thxs to Andrias Jim Bubba JeffB

H1 General
jim.warner@LIGO.ORG - posted 16:16, Wednesday 17 June 2015 (19201)
Shift Summary
8:15 Gary and crew headed to EX to work on ESD
8:30 Christina, karen to EX/Y to clean up
9:00 Corey, Jeff, Andreas to HAM6 area
9:15 JeffB back out to HAM6
11:00 Fil & Gerardo at EX for feedthru?
10:35 HAM6 2nd Cleaning
13:00 Fil to EY
14:00 HAM6 door activities
8:15 Gary and crew headed to EX to work on ESD
8:30 Christina, karen to EX/Y to clean up
9:00 Corey, Jeff, Andreas to HAM6 area
9:15 JeffB back out to HAM6
11:00 Fil & Gerardo at EX for feedthru?
10:35 HAM6 2nd Cleaning
13:00 Fil to EY
14:00 HAM6 door activities
 
H1 AOS (DetChar, ISC, SUS)
joshua.smith@LIGO.ORG - posted 11:31, Wednesday 17 June 2015 - last comment - 08:54, Friday 19 June 2015(19195)
Scattering at H1 caused by OMC M1 SUS longitudinal motion

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.

% from scattered light in Virgo's second science run data”
% http://iopscience.iop.org/0264-9381/27/19/194011 (thanks Andy for the
% pointer):
% f_fringe = 2*v_sc/lambda
Images attached to this report
Non-image files attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 14:26, Wednesday 17 June 2015 (19196)
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.
joshua.smith@LIGO.ORG - 15:04, Wednesday 17 June 2015 (19198)DetChar, ISC, SUS

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. 

Images attached to this comment
joshua.smith@LIGO.ORG - 08:54, Friday 19 June 2015 (19238)DetChar, SUS

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. 

Images attached to this comment
H1 CAL (AOS, CAL)
sudarshan.karki@LIGO.ORG - posted 10:01, Wednesday 17 June 2015 - last comment - 14:41, Sunday 12 July 2015(19186)
Gravitational Wave Strain h(t) sign convention determination using Pcal

Calibration Team

Sign of h(t):

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 '+'

Time Delay between Pcal and DARM:

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.

Images attached to this report
Comments related to this report
peter.shawhan@LIGO.ORG - 10:04, Friday 03 July 2015 (19437)CAL
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.
darkhan.tuyenbayev@LIGO.ORG - 10:33, Tuesday 07 July 2015 (19466)

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.

peter.shawhan@LIGO.ORG - 14:41, Sunday 12 July 2015 (19580)CAL, INJ
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.
H1 General
jim.warner@LIGO.ORG - posted 09:26, Wednesday 17 June 2015 (19192)
Morning meeting summary
ISC EX/EY TMS work done, new QPDs need tested
ETMX pitch offset de-biased, charge measurments/mitigation need to be done
Lots of model changes being done, trying make models the same between LLO/LHO
Vacuum ports at EX, venting HAM6, EY maybe closing today
Water leak possibly fixed at VPW
 
 
Safety: JohnW reminds everyone of LIGO stop work policy. You have the right to speak up / stop any activity if something looks amiss.
Be mindful of the heat
Fire hazard is high, no vehicles allowed offroad
 
Lots of new people on site, SURFS and others...
H1 AOS (DetChar)
keith.riles@LIGO.ORG - posted 22:48, Tuesday 16 June 2015 - last comment - 23:24, Tuesday 16 June 2015(19190)
Narrow lines in full ER7 data
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:
  • The bounce modes are better suppressed in the latter part of the run.
  • A comb with 0.1698-Hz spacing is now visible in its 41st through 59th harmonics
  • There is a newly apparent comb-on-comb structure with a fine spacing of 0.0884 Hz attached to a comb of 76.9426-Hz lines. Only the clusters up to the 3rd harmonic of 76.94 Hz are labeled on the spectra, but one can still see indications of the comb-on-comb up to at least the 12th harmonic at 923 Hz.
  • Something I overlooked before is that the OMC dither lines at 1675.1, 1700.1, 1725.1 and 1750.1 Hz are prominent on top of their induced up-conversion. This is in contrast to what I usually see in L1 data, where the dither lines themselves are servoed to near zero and are barely visible in the up-conversion they create.
  • In addition to the previously noted combs of 16 Hz and 64 Hz harmonics, one can now see a very sporadic set of 8-Hz lines. The more prominent ones are marked on the spectra and include 376, 552, 808, 1064, 1096, 1112, 1144, 1176, 1192, 1416, 1544, 1608, 1624, 1672, 1704, 1784, 1800, 1816, 1832, 1880 and 1896 Hz.
Figure 1 - Spectrum 0-2000 Hz with labeled lines Attachments: 1 - Line list 2 - zip file with 27 sub-band spectra
Images attached to this report
Non-image files attached to this report
Comments related to this report
daniel.hoak@LIGO.ORG - 23:24, Tuesday 16 June 2015 (19191)DetChar

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.  :)

H1 SYS (SUS, VE)
betsy.weaver@LIGO.ORG - posted 20:36, Tuesday 16 June 2015 (19188)
End Station Vent Status

As of COB today, we are on-schedule for the 4 day EX and EY vents.  So far no major surprises or issues.  Further dust monitor data to be posted later.

As per the schedule:

- The ISI's have been locked on both ETMx and ETMy.

- 2 CC witness samples have been pulled from each BSC9 and BSC10.

- The VE port work has finished at ETMy.

- The TMS work has finished at both stations.

- The ETMx debiasing has been completed (removed ~440 uRad of pitch mechanically at the suspension using the optical lever as the monitor.)  Bias is now at zero.  This is where commissioners should start looking for beams in a few weeks.  Yaw bias remains unchanged (and non-zero).

- Local charge measurements taken on ETMx with in-chamber equipment in prep for discharge procedures. 

- ESD feedthru swap has started.  Filiberto and Gerardo have pulled the flange and have it out and ready to reterminate with the new connector.

- Quick P and V TFs of ETMx show healthy suspension - Arnaud launched matlab overnight TFs of SUS-ETMx for further check.

 

First up tomorrow:

- Finish ETMx ESD feedthru work.

- Finish VE port work at ETMy.

- Move equipment to ETMy and Discharge ETMy.

- Close ETMy chamber.

H1 SEI
arnaud.pele@LIGO.ORG - posted 18:51, Tuesday 16 June 2015 - last comment - 15:14, Wednesday 17 June 2015(19187)
BSC-ISI models modified and restarted

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). 

Non-image files attached to this report
Comments related to this report
arnaud.pele@LIGO.ORG - 15:14, Wednesday 17 June 2015 (19199)

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

M       h1isietmx.mdl
M       h1isietmy.mdl
M       h1isiitmx.mdl
M       h1isiitmy.mdl
M       h1isibs.mdl
 
arnaud.pele@opsws7:/opt/rtcds/userapps/release/isi/common/models$ svn st
M       gnd_sts_library_EX.mdl
M       gnd_sts_library_EY.mdl
M       isi2stagemaster.mdl
M       gnd_sts_library_IY.mdl
 
 
arnaud.pele@opsws7:/opt/rtcds/userapps/release/isi/common/medm/bscisi$ svn st
 
?       ISI_CUST_CHAMBER_ST1_SUSINF_ALL.adl
M       ISI_CUST_CHAMBER_ST2_SUSINF_ALL.adl
M       ISI_CUST_CHAMBER_OVERVIEW.adl
Images attached to this comment
H1 DAQ
david.barker@LIGO.ORG - posted 18:09, Tuesday 16 June 2015 (19185)
DAQ restart to support OAF and ISI model changes

18:02 PDT: DAQ restarted to sync with new INI files for BSC-ISI and OAF.

H1 ISC
keita.kawabe@LIGO.ORG - posted 16:10, Tuesday 16 June 2015 - last comment - 11:55, Monday 22 June 2015(19175)
Done with TMSY (Corey, Kiwamu, Keita)

ISI was locked by Jim in the morning.

Before doing anything, EY alignment slider [PIT, YAW] = [142.0, -75.1], TMSY = [116.6, -20.0], EY OPLEV=[-39, -15]-ish.

Transitioned to laser hazard, moved EY such that the green return beam hits the center of the relf PD: EY [PIT, YAW]=[207.4, -75.1]

- Krytox on beam diverter in situ: Good.

Everything went well as per yesterday.

- QPD strain relief: Good-ish.

Unlike TMSX, it turns out that all QPDs were already equipped with a make-shift strain relief using stainless steel cable clamps, the same clamps used for fixing the cables on the TMS ISC table, but the cables were without kapton tubes. We decided to install the right strain relief anyway.

In the end, we were able to install the right ones on three out of four QPDs. As for the remaining one (Green QPDB), we weren't able to install it as the 1/4-20 Allen key to attach the PEEK strain relief to the QPD base would have interfered with the YAW knob of one of the QPD sled mirror holders (M102 in D1201458).  The stainless steel strain relief was left as is.

After this work, we checked if QPDs still work and they did (used green beam for the green QPDs and a flashlight for IR QPDs).

- TMS balancing: Good.

After the work, we checked the balace of the TMS table with the green light injected to the chamber. The vertical alignment was found to be already good and therefore we did not make any mechanical adjustment. Similarly, the horizontal was also good and giving an extra digital bias of +13 urad (resulting in -7.0 urad in OPTICALIGN_OFFSET) made the return beam well-centered on ALS-REFL_PD. So the balance is good.

 

After everything was done: EY slider [PIT, YAW] = [142.0, -75.1] (back to the original), TMSY = [116.6, -7.0], EY OPLEV=[-24, -31]-ish.

Seems like EY moves around by 15urad-ish both in  PIT and YAW, so TMS alignment could be only as good as 15urad-ish.

Comments related to this report
corey.gray@LIGO.ORG - 21:31, Tuesday 16 June 2015 (19189)

Here are photos from EY TMS work today:  https://ligoimages.mit.edu/?c=1616

keita.kawabe@LIGO.ORG - 09:19, Monday 22 June 2015 (19269)
jameson.rollins@LIGO.ORG - 11:55, Monday 22 June 2015 (19274)

The certificate for ligoimages.mit.edu has expired, so this site is currently not accessible.

H1 ISC
corey.gray@LIGO.ORG - posted 12:14, Tuesday 16 June 2015 - last comment - 10:13, Wednesday 17 June 2015(19168)
EX TMS tasks done

Corey, Keita, Kiwamu,

We conituned working on the remaining tasks for the TMSX in chamber (see alog 19157 from yesterday).

[Strain Relief for QPDs]

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.

[Balancing of the table]

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.

[Addendum]

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.

EX is now Laser Safe.

(And ready for the SUS crew to take over.)

Comments related to this report
keita.kawabe@LIGO.ORG - 10:13, Wednesday 17 June 2015 (19193)

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.

LHO General
thomas.shaffer@LIGO.ORG - posted 00:55, Sunday 14 June 2015 - last comment - 15:14, Wednesday 17 June 2015(19132)
Ops Report

(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

Comments related to this report
kiwamu.izumi@LIGO.ORG - 15:14, Wednesday 17 June 2015 (19200)CAL

The transfer functions that TJ measured for us have been renamed to be more obvious names as follows:

  • 2015-06-14_H1_DARM_OLGTF_LHOaLOG19132_ETMYL3LPOFF_17W.xml
  • 2015-06-14_H1PCALEY_2_DARM_LHOaLOG19132.xml

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.

H1 DetChar (DetChar)
paul.altin@LIGO.ORG - posted 00:24, Sunday 14 June 2015 - last comment - 08:08, Wednesday 19 August 2015(19131)
DQ shift summary: LHO 1117843216 - 1118102415 (June 9 - 11)

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.

Non-image files attached to this report
Comments related to this report
nutsinee.kijbunchoo@LIGO.ORG - 14:35, Wednesday 17 June 2015 (19197)

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.

Images attached to this comment
edward.daw@LIGO.ORG - 08:08, Wednesday 19 August 2015 (20676)
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. 

Non-image files attached to this comment
H1 ISC (CDS)
evan.hall@LIGO.ORG - posted 22:36, Friday 12 June 2015 - last comment - 17:01, Tuesday 16 June 2015(19110)
The EY ESD bias was stuck negative since 22 May

Richard, Evan

Summary

It appears that the EY ESD bias was stuck at −430 V ever since the installation of the low-voltage driver in May. It became unstuck on 11 June, when Richard reset the driver.

Since we have always requested a positive bias for EY in the digital system (using SUS-ETMY_L3_LOCK_BIAS), this means that the reset on 11 June flipped the sign of the EY ESD actuation, causing the transition of DARM from EX to EY to fail (as TJ found).

To fix the transition, the EY bias is now requested to be negative in the digital system, thereby restoring the sign (but not the magnitude) of the true analog bias that we have had since 22 May. Of course, if the magnitude of the L3 actuation has changed, this will affect the accuracy of the calibration in the region dominated by the control signal.

Details

First, let us enumerate some of the mysteries surrounding the EY ESD:

  1. After the low-voltage driver was installed (i.e., after 2015-05-22), we found that we had to flip the sign of the L3 actuation from positive to negative. This is despite the fact that both the low-voltage driver and the high-range driver supposedly have positive polarity at dc (so we should not expect to have to compensate for an analog sign flip).
  2. After the low-voltage driver was installed, we found that the dc actuation strength of EY L3 was 50 times weaker than EX L3. We expect only a factor of 20×1.25 = 25. The factor of 20 comes from the difference in dc gain between the high-range driver and the low-noise driver (40 V/V versus 2 V/V). The factor of 1.25 is what Kiwamu had previously found necessary to match the dc strengths of EX L3 and EY L3 when they were both driven by the high-range drivers.
  3. After the low-voltage driver was installed, the analog readbacks for the high-range driver (bias line and 4 quadrants) were stuck at −15000 ct.
  4. After Richard reset the high-range EY driver for the charge measurements (2015-06-11, circa 21:00:00 UTC), there has not been a successful transition of DARM from EX to EY (although there have been only four trials, according to the summary pages).

We hypothesize that mysteries (1), (3), and (4) are explained by the EY ESD bias being stuck at −430 V between 2015-05-22 and 2015-06-11, and the driver's readbacks being nonresponsive. Mystery 2 is still unsolved.

When Richard went to EY on the 11th, he found the high-range driver putting out −430 V on all five lines, and the driver's analog readbacks were frozen at −15000 ct or so. According to him, this is a known failure mode of the driver's microcontroller. After he reset the driver, the analog readbacks became functional again.

The attached plot shows a trend of the analog readback of the EY ESD bias. It is stuck at about −15000 ct from 2015-05-22 (when the low-voltage driver installation was finished) to 2016-06-11 21:00:00ish UTC (when Richard reset the driver). The natural conclusion from this is that the EY ESD bias has been railed at −430 V between these two dates (even though we thought we were giving +380 V of bias).

I flipped the requested bias so that it is now (I think) −380 V, which is the most negative bias that can be requested from the driver when it is operating properly. I was able to transition control of DARM from EX to EY by hand following the steps in the guardian.

Images attached to this report
Comments related to this report
evan.hall@LIGO.ORG - 23:02, Friday 12 June 2015 (19111)

Also, Travis and I are hearing ETMY saturations every so often. The rms drive to EY L2 is 40000 ct or so, which is higher than the 15000 ct that we measured when we first started using EY L2. (Could it just be wind?)

If you, like us, don't like it when your suspensions saturate in full lock, then we suggest trying out a higher L1/L2 crossover. Engage FM9 in H1:SUS-ETMY_L1_LOCK_L, and turn up the gain from 0.16 to 0.31.

Images attached to this comment
rich.abbott@LIGO.ORG - 15:04, Tuesday 16 June 2015 (19179)ISC, SUS
Per Jeff's request, here is an excerpt from an email I sent to Evan and Jeff:

Some architectures used in amplifiers suffer from a phenomenon known as Phase Reversal wherein the feedback sign of the amplifier can actually change on certain saturation events.  I have not looked to see if that is whatsoever possible with the HV ESD amplifiers.

Something that bothers me here is that if you are running in low voltage mode, there is no way the high voltage drive signals for the quadrants can make it to the reaction mass.  A relay disconnects them.  This makes me somewhat puzzled about potential HV/LV interactions causing any sort of actuation force reduction.  The actual applied bias could be changing by the time it makes it through the non-trivial series resistance associated with the bias filters (~70kohms), but there would have to be a low impedance on the bias terminal to created the necessary voltage divider.

As for the sign flip, I have no answer there.  I will check (again) that I didn't do something dumb and make a typo on the + and - wires.
rich.abbott@LIGO.ORG - 17:01, Tuesday 16 June 2015 (19184)ISC, SUS
Following up on the notion of phase reversal, I checked all the chips used in the HV ESD Driver signal chain.  Here's the result:

LT1124 - Input receiver, these are the same architecture as the ubiquitous LT1125 we use everywhere at LIGO, so I'm not too suspicious here.
LT1007 - Second stage of input receiver, no mention of immunity to phase reversal in data sheet.  This is often a bragging point among chip designers, so I can't eliminate this chip from the list of suspects.
OP-97 - Front end chip for the HV output stage, Vcm = +/-13.5V min, this is a possible culprit as the input architecture appears to be jfet based, and it's used in a feedback loop, which is a double whammy for phase reversal.
PA-95 - HV driver chip.  No mention of phase reversal immunity.  Definitely jfet based, used in a feedback loop, and is not grounded on the positive pin.  Triple whammy for phase reversal, although it would be hard to exceed the input common mode voltage with +/-430V rails...

Mostly pseudo science here, but my two cents.
Displaying reports 64361-64380 of 83069.Go to page Start 3215 3216 3217 3218 3219 3220 3221 3222 3223 End