Displaying reports 67701-67720 of 84537.Go to page Start 3382 3383 3384 3385 3386 3387 3388 3389 3390 End
Reports until 11:45, Tuesday 17 March 2015
H1 SEI
hugh.radkins@LIGO.ORG - posted 11:45, Tuesday 17 March 2015 (17299)
HEPI Corner Station Accumulators Charged

Checked and set all LVEA Supply Accumulators to 70psi; Return Accumulators set to 20-30psi.

Issues found at H(am)5R(eturn), H6S(upply), H5S, H4S, B(SC)3E(ast)S,B3W(est)S,B3WR,B2N(orth)S(unable to charge due to interference), B2NR, B1NS, B1SR, H3S, H1S, H1R, H2R.

Wow, maybe easier to list the ones that did not need some gas.  Most of the Supply units that needed charging where at 20psi or below. This should make a good improvement in pump pressure fluctuation coupling into to platform motion.  I expect next check should see a much shorter list.

H1 SEI
hugh.radkins@LIGO.ORG - posted 11:24, Tuesday 17 March 2015 (17298)
HEPI Drain Valve found open under BSC1--No Leak

Found that someone had decided to store unused 2" Angle Cable Tray Support Assemblies under BSC1.  Sliding these in, the Feet on the Assembly was just the right height to hit the valve knob and turn it.  Fortunately, the drain exit is capped and no leak occurred.  Please mind the caution tape and be aware of the pushing and pulling things in and around the low dark places where HEPI resides.

H1 AOS
hugh.radkins@LIGO.ORG - posted 11:19, Tuesday 17 March 2015 (17297)
SR3 OpLev Transmitter Pier is Touched by Piping

Noticed that the Vacuum Pipe, Instrument Air Piping and Conduit are all contacting the SR3 OpLev Transmitter Pier near its base.  This is just East of HAM4 on the North Side.

H1 AOS
jeffrey.bartlett@LIGO.ORG - posted 11:14, Tuesday 17 March 2015 (17296)
Reset of HEPI L4C Accumulated WD Counters
Reset the watchdog counters for HAM2, HAM3, HAM5, ITMX, and ITMY
H1 SEI
jim.warner@LIGO.ORG - posted 10:57, Tuesday 17 March 2015 (17295)
Modified blend filter for BSC St2 works

I got a chance to test the modified blend filter that JeffK and I came up with on Friday(alog 17256). It looks like it most does what we expected. Attached plots show X, Y and Z dofs for both stages., dashed lines are the before, solid lines are after, red is St1, blue is St2. I don't show it, but there was no change in performance below 1 hz.  I think we might be able to push the elliptical filter down a little more, get some improvements closer to 5hz, but that will have to wait while I run down other projects.

I've installed this on ETMY, ITMY and ITMX, but it's only running on the Y arm chambers, for now.

A side note, the blend filter banks for the BSC's are getting a little weedy. It's probably getting to be time to do a little clean up and make things more consistent between chambers.

Images attached to this report
H1 ISC
kiwamu.izumi@LIGO.ORG - posted 09:49, Tuesday 17 March 2015 - last comment - 12:10, Monday 23 March 2015(17293)
Roll mode damping on ITMX and ETMY with AS WFS

Dan, Kiwamu,

At one point last night, we noticed that a roll mode rang up at ~14 Hz. The peak height in the DARM spectrum (ffted with a 0.1 Hz BW) exhibited a anomalously high value of more than 10-12 m/sqrt Hz.

So we worked on damping the peak, this time with the AS_WFS_A_45Q signal (alog 16864) which is a state-of-the-art Livingston technique. We were successfully able to damp the mode to an ordinary height of about 10-14 m/sqrt Hz level in the DARM spectrum.

 


(Identification process)

First of all, see how terrible the roll mode was:

The red curve is from Mar-17-2015 8:51:00 UTC and we were intentionally stayed on the rf DARM rather than the DC readout to combat the roll mode. Even though there was some confusion in identifying which suspension had been rang up, eventually we confirmed that the roll mode was from ITMX by taking coherence between AS_WFS_A_45Q and the OPLEV_PIT signal of each test mass. In fact, the ITMX oplev was able to see the roll mode in its spectrum with a peak ~ 10 times higher than the noise floor while the rest of the oplevs did not see a visible peak.

In addition, after the successful damping on ITMX, the AS_WFS_A still showed a bit high peak but with a slightly lower frequency (~ 200 mHz ) than that of ITMX. We then identified that this was in turn from ETMY by looking at the coherence again. This lead us to another damping work on ETMY which we were also able to damp.

 

(Damping setup)

The AS WFS_A signal was routed from the ASC model with a gain of +1 (in ASC_OUTMATRIX_TESTMASS_DAMP). I found that both were damped well with a positive gain in SUS-E(I)TMX(Y)_M0_DAMP_R.

As for ITMX, I ended up with FM3 (-100 dB), FM4 (bp13.9) and a gain of +40. Although I had to start from a gain of +1 in order not to saturate the DAC due ot the high amplitude in the roll mode. Then I gradually increased the gain as the DAC counts reduced. Once I went to a gain of more than 10, the mode was damped relatively quickly probably on a time scale of about a couple of minutes.

As for ETMY, I ended up with FM4 (bp13.9) and a gain of +0.0008. At one point I went to a gain of +0.005, but this actually started increasing the peak height. So I had to set the gain back to + 0.0008. This loop could damp out the mode on a time scale of a couple minutes as well.

 

(Why they rang up ?)

We don't know.  One observation is that before the modes rang up, Sheila was trying to increase the recycling gain by manually touching the ITMs.

Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 18:01, Tuesday 17 March 2015 (17318)DetChar, SUS
What's the exact frequency (or at least to ~0.01 [Hz] precision)?

Remember, I was able to distinguish two mode frequencies in LHO aLOG 16868: a 13.18 [Hz] mode or the 13.81 [Hz] mode, which I'd narrowed down to an ITM and an ETM mode respectively. It would be good to catalog is the ITMX mode you say rung up.

@DetChar -- you're more than welcome to answer this, if Dan or Kiwmau can't get back to it quickly. The time you should use is listed in the bottom corner of the DTT screen capture.
rana.adhikari@LIGO.ORG - 23:01, Tuesday 17 March 2015 (17323)

since the color of the Time text is the same as the reference, I guess that's not the right time. Better to use the time of the RED live trace.

andrew.lundgren@LIGO.ORG - 12:10, Monday 23 March 2015 (17398)
Looks like about 13.98 Hz, accurate to 0.01 Hz. I used 5 mins of data, 120 sec FFT, overlap of 0.9. I used the time mentioned in the log entry (8:45 UTC Mar 17) since the data didn't look right around the time in the DTT screen.

We don't have a nice tool for quickly marking the peaks in spectra. I'll look into making one.
Images attached to this comment
H1 General
jeffrey.bartlett@LIGO.ORG - posted 09:06, Tuesday 17 March 2015 (17294)
08:30 Meeting Minutes
Seismic:
	Hugh doing HEPI maintenance in corner station
	Jim performance testing on ETMX, & Filter work on ETMY
	Reboot of End-X BRS computer

3IFO:
	Jodi moving and labeling 3IFO items in the LVEA
	Bubba hooking up 3IFO Quad LS and BS storage boxes to N2 system
	Corey moving bins in and out of the LVEA

PSL:
	Work on RefCav alignment & TFs on FSS

CDS:
	Model and DAQ restarts
	Jim moving the NTP server

VAC/FMP:
	Swapping ion pumps at HAM1 & HAM2
	Tumble weed bailing 
	Hanford FD on site testing fire alarms
H1 ISC
sheila.dwyer@LIGO.ORG - posted 02:50, Tuesday 17 March 2015 (17292)
progress today

Dan, Kiwamu, Sheila

Today we made several gaurdian changes:

I looked for a signal from the QPDs which was insensitive to TMS angle.  For the X arm pitch I used TRX A - 0.5 TRB and for Y arm pitch 1TRY_A-0.65 TRY_B seemed good.  I closed a verry low bandwidth loop to ITMX using this signal, screen shot is attached.  

We found that we could increase the recycling gain from ~27 to ~33 by moving the ITMs with ASC lops closed on IM4, PR2, BS, common ETMs, and differential ETMs.  We had to move ITMX by as much as 5 urad to do this, and we found that we would loose the lock soon after getting a good recycling gain.  Kiwamu calcualted that by moving ITMX 5 urad, we are moving the spot on the test masses by 1 cm assuming that the ETM is controlled. This may be due to a problem with the DHARD loop. 

We also spent some time looking for a Transmon QPD signal that would be insensitive to motion of the transmon.  We closed a loop to ITMX pitch using TRX_A - 0.5 TRX_B, the attached screenshot shows the settings.  This loop was verry low bandwidth.  

Images attached to this report
H1 CDS
sheila.dwyer@LIGO.ORG - posted 21:01, Monday 16 March 2015 (17291)
ramping indicator stuck on

We had a second incident of a permanently ramping slider today, earlier we saw this with SR2 Yaw and just now (3:56:20 UTC) we saw it again with SR2 pitch.  The offset had ramped to the correct value (probably in the 10 second ramp time), but the ramping indicator stayed on.  This wouldn't be a problem except that we are using .is_ramping in the guardians, and they get confused by this situation. 

Again I changed the ramp time, and Dan moved the slider one click and moved it back again, and the ramping indicator went off. 

Dave investigated this earlier in the day when we saw it with yaw.

LHO VE
bubba.gateley@LIGO.ORG - posted 17:24, Monday 16 March 2015 (17284)
Beam Tube Washing
Scott L. Ed P. Chris S.

The crew relocated lights and equipment this morning. We will be starting at the single door between X-1-5 and X-1-6 double doors and working toward the Mid station. We started vacuuming beam tube supports this afternoon and took dirty samples on the tube. Results posted on this entry. These are some of the dirtiest areas we have seen so far.
A new generator was purchased Friday, however it still needs to be shipped here. A rental generator was picked up this morning to get us by until the new unit arrives. 
Non-image files attached to this report
H1 ISC
daniel.sigg@LIGO.ORG - posted 17:16, Monday 16 March 2015 (17288)
REFL_A_RF9 RF phase

This is a reminder that the RF phase of the REFL_A_RF9 and REFLAIR_A_RF9 signals should always be adjusted using the delay line phase shifter. The analog phase shift is applied to the LO signal and therefore effects both analog and digital feedback paths. On the other hand, the phase rotation in the real-time system only changes the digital path. It should always be set to 0°, if the error signal of the REFL servo uses the I output of the demodulator, and to ±90°, if it uses the Q output. One other caveat is that the delay line phase shifter may be in local mode, meaning one has to use the physical toggle switches at the chassis. In local mode the digital settings are getting completely ignored and there is no readback.

Images attached to this report
H1 CDS
david.barker@LIGO.ORG - posted 16:24, Monday 16 March 2015 - last comment - 11:28, Friday 20 March 2015(17286)
MEDM changed to move Print button to prevent accidental printing

Jamie, Dave, Jim:

Jamie reported that the location of the MEDM Print selection, being at the top of the right-mouse pull-down menu, has resulted in many accidental printer jobs. This explains the printouts of things like the sitemap screen with no data content and no one picking the print-outs up.

Jim modified the LHO CDS MEDM this afternoon to move the print section from the top to second from the bottom of the pull down menu. Please see the attached before and after images.

During tomorrow's maintenance we will stop all old MEDMs in the control room so the new feature will be picked up. This is only a linux change, it was not applied to Mac OS.

Images attached to this report
Comments related to this report
jameson.rollins@LIGO.ORG - 11:28, Friday 20 March 2015 (17368)

Awesome.  Thanks, Jim and Dave.  The forests thank you.

H1 General
jeffrey.bartlett@LIGO.ORG - posted 16:07, Monday 16 March 2015 (17285)
Ops Day Shift Summary
LVEA: Laser Hazard
Observation Bit: Commissioning   

07:00 Karen & Cris – Cleaning in the LVEA
07:45 Bubba – Chiller delivery from LLO, Bubba unloading truck at Mid-X
08:15 HFD – On site with Richard at Mid-X
08:25 Adjust ISS diffracted power from 5.5% to 8.2% 
08:43 Corey – Going into Squeezer bay for 3IFO work
08:50 Filiberto – IN LVEA making a survey of racks
09:00 Corey – Out of squeezer bay
10:00 Corey – Going into squeezer bay for 3IFO work
10:10 Bubba – Finished unloading truck at Mid-X – Big Red has been parked
10:30 Corey – Out of squeezer bay
11:15 Ken – Working on CER
12:47 HFD on site for fire alarm maintenance
14:20 Richard – Going to Mid-X
14:35 HFD finished testing the OSB fire alarms
H1 SEI
hugh.radkins@LIGO.ORG - posted 15:29, Monday 16 March 2015 - last comment - 16:43, Monday 16 March 2015(17283)
H1 BS Stage2 Trip from Medium Isolated when Mich/DRMI Drops

Even though the threshold is set to 32k, the Stage2 tripped when the Actuators only hit 30k.  Is this just from the 512k downsampled data?

The attached trend plots shows the full data and although it gets close, it doesn't appear to reach the threshold.  Shame we get shut down for such a short transient.

Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 16:43, Monday 16 March 2015 (17287)
Hugh means 512 [Hz], because the _DQ channel he's posted is down sampled from the native user model rate of 16384 [Hz] to 512 [Hz] before it sent out for frame storage. 

No way to confirm your suspicion Hugh, with the data that's currently stored.

Brian says "We should store that stuff faster." I agree, especially if we add "if we *actually* want to know for these super-high-frequency glitch-type trips," because most people probably don't, they just want it not to happen. #TriggerECR

Have y'all reduced the high-frequency roll-off of these loops yet? That's the real solution...
H1 General
jeffrey.bartlett@LIGO.ORG - posted 15:10, Monday 16 March 2015 (17281)
24 Hour OpLev Trends
These are the 24 hour OpLev trends. Will look into the drops in PR3 and the BS.
Images attached to this report
H1 PSL
jeffrey.bartlett@LIGO.ORG - posted 13:33, Monday 16 March 2015 (17279)
PSL Weekly Status
PSL Status: 
SysStat: All Green, except VB program offline 
Output power: 31.9w  
Frontend Watch: Green
HPO Watch: Red

PMC:
Locked: 13 days, 2 hours, 34 minutes
Reflected power:    2.1w
Transmitted power: 22.5w 
Total Power:       24.6w 

ISS:
Diffracted power: 9.2%
Last saturation event: 0 days, 0 hours, 28 minutes 

FSS:
Locked: 0 days, 0 hours, 5 minutes
Trans PD: 1.347v
 

H1 SEI
hugh.radkins@LIGO.ORG - posted 12:05, Monday 16 March 2015 - last comment - 15:20, Monday 16 March 2015(17276)
SEI ETMX (Only One) BRS appears Crashed/Dead--It must be kept alive!

See the attached for trends of the BRS for health assessment.  It has been down since ~22 Feb.

The first plot is the minute trend of H1:ISI-GND_BRS_ETMX_RY_INMON.  This is 100 days of just the mean and the flat lined sections are BRS in trouble areas.  The 2nd attachment is a 60 minute second trend.  This shows the healthy 9mhz signal of the BRS.

Images attached to this report
Comments related to this report
krishna.venkateswara@LIGO.ORG - 15:20, Monday 16 March 2015 (17282)

Thanks Hugh. Some comments: The BRS was turned off around Dec. 18th for the ETMX vent and restored after things normalized again in EX VEA. The 'spikes' in the BRS data are mostly the disturbances from people in it's vicinity, which is damped quickly (in ~10 mins). Therefore in the normal/good state BRS_RY_INMON shows between 5-50 count amplitude and 9 mHz oscillations, as Hugh showed. When the BRS software crashes, the output remains flat and shows <2 count variation.

Currently the software crashes once in 2-3 weeks. A preventive restart (which takes <10-15 minutes) once in two weeks would be useful till a better solution can be found.

H1 AOS
robert.schofield@LIGO.ORG - posted 14:53, Sunday 15 March 2015 - last comment - 19:06, Monday 16 March 2015(17273)
Scattering shelf reaching past 100 Hz produced by large motion of OMC relative to table

More details on the scattering Dan mentioned on Friday, with some new and re-interpreted details (the responsible motion is horizontal) that became clear after further investigation.

This last Monday, DARM spectra showed a double scattering shelf occasionally reaching 60 Hz and 120 Hz (Figure 1) and even higher.  I searched for the source of the scattering path length variation by looking for motion sensors that detected maximum motion at the times that the higher frequency scattering shelf reached its highest frequency.  The top trace of Figure 2 is a 700s time series of DARM, band passed between 90 and 145 Hz. Each of the spikes in the time series was produced when the scattering shelf reached into this band. The lower plot shows that the maxima in one of the OMC OSEM signals coincides with the spikes in the DARM plot above it. All OMC OSEMs show this correlation except the side sensor (on the short side). I found no other GS13 or OSEM channels that showed this correlation; most importantly, it was not in the GS13 signals from HAM6. Figure 3 is a zoom in to one of the clusters of scattering spikes, showing that the scattering spikes appear to occur at the steepest part of the OSEM signals (when velocity would be highest), and that the time spacing between DARM spikes agreed with the resonant frequencies of the OMCS. Beating between 2 of the suspension modes seems to cause the variation in motion.

Using the 1 um/count calibration of the OSEM OUT channels, I obtained average velocity spetra that, for some OSEMs, reached 10 um/s (Figure 4).

In order to produce a shelf out to 60 Hz, the rate of path length change for a single bounce would have to reach about 30 um/s. The OSEMs measure displacement of the top mass, M1, and the OMC hangs below it. At the resonant frequencies of this suspension, the motion of the OMC, while damped, would still be greater than the top mass. Also, the 10 um/s figure is only an average rms. Thus the OMC motion can account for the 60Hz shelf with a single reflection. 

There are two shelves in Figure 1 spaced by a factor of 2 in frequency. The spectrogram in Figure 5 shows that the frequency spacing of the two shelves is always a factor of 2. The shelf at 120 Hz in figure 1 is about an order of magnitude below the shelf at 60 Hz. If this represents a scattered beam that reflects twice instead of once, then the reflectivities at each of the two extra surfaces would have to be very high. While there may be other mechanisms to generate the double shelf, it is probably worth looking for bright beam spots on highly reflective surfaces in HAM6.

Finally, it would be nice to reduce the motion of the OMC by a factor of ten, particularly, the side to side and rolling motion perpendicular to and about the line connecting the two suspension points of M1, motion detected by the LF, RT, T2 and T3 OSEMs.

Non-image files attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 11:26, Monday 16 March 2015 (17275)

It's likely the OMC ASC control (Kiwamu, Daniel, Keita)

Summary:

OMC BOSEMs are usually very quiet, but they show extremely big motion that Robert showed only when the IFO is in lock with DC. In-lock VS out-of-lock ratio is huge at about 3 orders of magnitude.

It turns out that this comes from OMC ASC control actuating on the OMC suspension.

OMC YAW has a large coupling to the distance between the OMC and the IFO because the rotation axis is fairly distant from the first steering mirror on the OMC breadboard, probably 18cm or so, and therefore is likely this is the main motion coupling to the scattering path modulation.

Apart from identifying the scattering source, there could be some mitigation tasks that we could do.

  • Stop using OMC SUS for alignment, and instead use to TTs for OMC. This will leave only one TT for AS AFS centering, but our guess is that it's going to be fine.
  • If we need to use OMC SUS, we could change the output matrix such that the OMC ASC YAW induce the rotation around the first steering mirror on the OMC.
  • Look at the S/N of the ASC, and see if the bandwidth of OMC ASC is appropriate.

We will test the two TT mitigation tomorrow.

Details:

Attached shows the same OMC BOSEM velocity signals that Robert used (the only difference is that this is calibrated in um/sec, not m/sec).

Solid lines are now, broken lines are when Robert took his measurement. At around big peaks, there's 3 orders of magnitude difference. It turns out that they're mostly like solid lines show, and becomes excited only when in DC-lock.

Kiwamu will fill in more details.

Images attached to this comment
kiwamu.izumi@LIGO.ORG - 14:17, Monday 16 March 2015 (17280)

I attatch a 24-hrs trend of some relevant channels from Mar-10-2015. As shown in the trend, it seems that every time the OMC-ASC loops are in action actuating on the OMC suspension, the OMC OSEMs read high fluctuation as weel as a big shift in the DC values. When the OMC ASC loops are not in action, the OSEM readouts are quiet.

Images attached to this comment
daniel.hoak@LIGO.ORG - 19:06, Monday 16 March 2015 (17290)

On Friday we reduced this scattering noise below the usual noise floor by reducing the OMC ASC gain by ~10x.  This reduced the UGF of the QPD loops down to 0.1Hz.  This is around the UGF of the dither loops, which explains why we only saw this noise recently, when the QPD loops were used in low-noise.  See the attached plot of the OMC SUS longitudinal signal: the blue traces are the QPD loops in a high-gain state, red is low-gain.  The purple traces are from March 4 when the OMC was aligned with the dither loops 9 (the dither signals are rolled off above 2Hz since the signal-to-noise above that frequency is not good).  The black traces are the quiescent OMC SUS noise without ASC feedback.  For the current noise floor between 10-100Hz, the motion of the red and purple traces are low enough to keep the scattering from being the limiting noise source.

That said, this scattering knowledge means that the experiment of feeding back alignment signals to the OMC SUS should end.  I've added OM3 to the ASC model, so we can feed back the DC centering signal from AS_B to OM1-3, along with the two degrees of freedom from the OMC.  This will give us a 3x3 control matrix for the HAM6 alignment, similar to what's being done at L1.  It ignores the centering on AS_A, but centering on AS_B should be sufficient.

Btw the dither loops need to be re-commissioned because I moved the dither lines up to ~1.7kHz.  This changed the sensing matrix, it needs to be remeasured and inverted for a new control matrix.  Tomorrow we will 1) switch the control topology to use the OMs rather than the OMC SUS, and 2) switch the sensing topology back to the dither for low-noise operations.

Images attached to this comment
Displaying reports 67701-67720 of 84537.Go to page Start 3382 3383 3384 3385 3386 3387 3388 3389 3390 End