Displaying reports 67241-67260 of 83004.Go to page Start 3359 3360 3361 3362 3363 3364 3365 3366 3367 End
Reports until 01:24, Thursday 22 January 2015
H1 ISC
sheila.dwyer@LIGO.ORG - posted 01:24, Thursday 22 January 2015 (16199)
locking tonight

Alexa, Evan, Sheila, Koji, Rana

We have been locking the arms tonight, with DRMI on 3F and trying to transition CARM to sqrt(TRX+TRY).  

So far no success, although we found several setings which were wrong.  

We tried moving the CARM offset (using the COMM VCO) to -200 Hz (green), and adding a small amount of gain, 1/10 of our nominal gain.  Rana saw that this adds a lot of high frequency noise to CARM.  

H1 ISC
alexan.staley@LIGO.ORG - posted 00:50, Thursday 22 January 2015 (16198)
Lock Acquisition Investigation (sort of)

Sheila, Kiwamu, Rana, Evan, Daniel, Alexa

We had hope to explore the phase-space of DRMI and improve the lock acquistion time; however, we did not get very far. 

We began with DRMI+arms off resonance under the nominal gaurdian configuration. We acquired the lock 5 times, and found the following acquisition times:

  Lock time (Jan 22, 2015 UTC) Acquisition Duration
1 00:43:02 8 min
2 00:49:40 3 min
3 00:52:53 3 min
4 00:57:28 4.5 min
5 01:19:30 7 min

At this point we checked the demod phases for the 1f signal, and decided to adjust the REFL45 phase from 137 deg to 142 deg. We also changed the MICH upper trigger to 5.0 from 10.0. and touched up the alignment (this probably ruins the validaty of our test). With this configuration, we repeated the above and found:

  Lock time (Jan 22, 2015 UTC) Acquisition Duration
1 02:00:00 1.5 min
2 02:00:57 0.5 min
3 02:04:00 2 min
4 02:05:30 10 sec
5 02:44:29 10 min*

* flipped CARM offset at one point. 

 

Overall this test was pretty inconclusive, but I thought I would post the lock aquisition times. This evening, we have been running with the MICH upper trigger threshold at 5.0 and it takes about 15 min or so to lock again ... 

H1 ISC (ISC)
rana.adhikari@LIGO.ORG - posted 00:44, Thursday 22 January 2015 (16197)
MICH filter changes

A few filter changes for the MICH / BS tonight:

  1. Moved the Butterfly stop band filter from the M2 COIL filter banks into the M2 LOCK, so that we only have to use 1 filter. I think there's no danger of the  mode getting rung up by the OL loops.
  2.  Removed the 300 Hz notch for the BS Violin and replaced it with a 10 Hz wide 80 dB stopband filter. There is no appreciable phase lag at the MICH UGF of 10 Hz. This catches not only the 299,5 Hz BS violin mode (which was ringing up and saturating tonight), but also a couple peaks at 302 and 303 Hz which were dominating the BS DAC range when the DRMI was locked on the 1f signals.
  3. The MICH loop phase margin is only ~25 deg, due to the low freq boosts and the elliptic low pass at 40 Hz. I have made a RLP65 to replace the ELP40. This has approximately the same phase lag, but better attenuation around 100 Hz. During the 3f lock the RMS at the DAC was ~33000 counts (out of 131000). This was ~8-10x more than during the 1f locks and mostly comes from the low SNR of the BBPD used to acquire the REFL 3F signals.

My guess from the noise that we hear in the speakers is that the BS coil driver DAC channels has been lightly saturating whenever we reduce the CARM offset. Its pretty close to the rails before we start and the signals are only noisier when we're on the side of the CARM fringe.

The first attachment compares the ELP40 with the RLP65.

The second attachment compares the M2 LOCK signal with 1f lock (PURPLE), 3f lock (BROWN), and 3f lock with the new filter (BLUE). The new filter gives us a 3-4x reduction in the RMS. I think this should give us a more smooth 3f lock and a smoother CARM reduction.

Non-image files attached to this report
H1 SEI
jeffrey.kissel@LIGO.ORG - posted 18:43, Wednesday 21 January 2015 (16196)
HAM3 Performance, with 250 [mHz] Blends -- Not so good a compromise
J. Kissel, A. Pele

While Seb suggests that moving the HAM3 blends to the "250mHz" configuration is a good configuration to "solve" the 0.6 [Hz] feature (see LHO aLOG 16100), we argue that it would be better to live with a 0.6 [Hz], digitally-sharp, peak than to increase the X motion by the factor of several. OR we should find a different set of blend filters for RY that *don't* increase the low frequency motion.

I attach 2 supporting documents:
(1) 16196_20150121183131_H1-SEI_QUIET_3C14C7_SPECTRUM-1105747216-86400.png
The performance comparison between all HAM platforms from the Jan 20th summary pages. On this day, HAMs 2, 4, 5,and 6 are in the "nominal" LHO configuration, all using "01_28" blends on all degrees of freedom, with sensor correction ON for all DOFs, GS13s in high-gain mode, with newly improved isolation loops. HAM3 however, was in Seb's suggested configuration -- the same as the other HAMs *except* for the RY blend filter, which has been changed from "01_28" to "250mHz."

(2) 2015-01-21_H1vL1_BlendFilter_Comparison.pdf
A comparison between the H1 "01_28," H1 "250 mHz", and L1 "400" RY blend filters, as well as the H1 "01_28" and L1 "250" X blends. This shows that 
   (a) In RY, 
       (i) the H1 "01_28" and L1 "400" are virtually identical, as expected. To be precise, for some reason, the L1 GS13 filters are 8% higher in gain, but otherwise identical.
       (ii) The H1 "250mHz" blend is actually *lower* in blend frequency than the H1 "01_28" filters. This means the low-frequency roll-off of the GS13 high pass is much slower for the "250mHz" than for the "01_28".
   (b) In X, 
       (i) there is a good bit of difference in the 0.2 - 4 [Hz] region. We suspect this is because the H1 "01_28" filters were copied over from LLO in Oct 2013, before Ryan had made further tweaks to these blend filters to improve performance around the SUS resonances. The performance is most different at 0.75 [Hz], where the displacement sensor low-pass is lower by a factor of 10.
       (ii) it's concerning that the GS13 high-pass -- though 19% different in overall gain -- does *not* differ between the two site's versions of the filter. This must be what Ryan means when he suggests his filters are "almost" complementary.

While all points are interesting with respect to the sociology and history of the SEI commissioning, point (2)(a)(ii) is the key for HAM3. Because the RY GS13 filter rolls off slower and lower for the "250mHz" blends, the differential vertical GS13 noise is reinjected into the RY loop. This excess residual RY motion couples to X via tilt-horizontal coupling, which degrades the low-frequency noise performance in the same frequency region. Bad. We'd discovered this nasty cross-coupling path as far back as The Stone Ages.

We should find/design an RY filter for HAM3 that *increases* the blend frequency from the H1 "01_28" filters, if we intend to run for a while in such an odd configuration. We may try copying over a few other L1 blend filters. This is all still lower priority compared to the *rest* of the to-do list, but Arnaud and I are worried that the excess low-frequency motion in HAM3 alone might be causing problems with cavity motion.
Images attached to this report
Non-image files attached to this report
H1 General
travis.sadecki@LIGO.ORG - posted 16:01, Wednesday 21 January 2015 (16193)
OPS shift summary

8:51 Kiwamu to IOT2L

9:05 Bubba to EX

9:06 Karen to EY

9:08 Corey to Squeezer Bay working on 3IFO ISC

9:15 Cris to MX

9:37 Corey to EY looking at ALS optics on table

9:38 Andres working on 3IFO storage cleanup in LVEA

9:44 Kiwamu done in LVEA

9:53 Gerardo X beam tube ion pump work

10:11 Kiwamu and Elli to ISCT6

10:11 Corey back from EY

10:24 Karen done at EY

10:27 Bubba done at EX

10:43 Corey back to Squeezer Bay

10:47 Andres out of LVEA

11:02 Jeff and Andres to LVEA for more cleanup

11:10 Rick and Sudarshan to LVEA PSL area

11:20 Jodi to LVEA taking pics

11:22 Jeff and Andres out of LVEA

11:32 Jodi out of LVEA

12:02 Gerardo out of LVEA

12:22 Corey out of Squeezer Bay/LVEA

14:02 Corey back to Squeezer Bay for 20 min.

LHO VE (VE)
gerardo.moreno@LIGO.ORG - posted 15:14, Wednesday 21 January 2015 - last comment - 17:53, Wednesday 21 January 2015(16192)
XBM annulus ion pump

(Kyle R, Gerardo M)

The new ion pump became railed sometime after decoupling the pump cart yesterday, and remained railed overnight.
This morning after pumping down the annulus system with the pump cart, we determined that the main valve was leaking.
So, to minimize exposure of the annulus system to atmosphere, we decided to add another valve in series with the leaky valve.
After pumping down on the system for about 25 minutes, the Ion pump started operating as it should, and is currently at 1.5 amps.

Comments related to this report
john.worden@LIGO.ORG - 17:53, Wednesday 21 January 2015 (16195)

or perhaps 1.5 mA

H1 SEI
hugh.radkins@LIGO.ORG - posted 14:49, Wednesday 21 January 2015 (16191)
ETMY BSC10 EndY HEPI Guardian reload for all dof restore

Just like ETMX earlier, restarted the HEPI guardian at ETMY to restore the same position for all dofs.  No problems again.  Attached is similar plot showing how different the alignment is after the restart.  Again, the HEPI is exactly the same, cause we made it so.  And the ISI, even though it restores no dofs, holds to its previous position to within 1 urad ( worst is RX=Pitch at ETMY,) all other dofs much less.

Images attached to this report
H1 TCS
kiwamu.izumi@LIGO.ORG - posted 13:50, Wednesday 21 January 2015 (16189)
TCSX calibration filter was off, we switched it back on

As a part of the DRMI investigation, we checked the laser power of CO2X and found that the power had dropped by a factor of two or so a week ago. However it turned out that this was due to a calibration filter (FM2 of TCS-ITMX_CO2_LSRPWR_MTR) which had turned off at that time for some reason. We switched it back on and also edited safe.snap accordingly. The attached is a 100days trend of relevant channels. As shown, the input of the monitor channel stayed at a constant value approximately in the past month or so while the output suddenly changed a week ago, indicating that the calibration filter was taken out.

Images attached to this report
H1 SEI (SEI)
sebastien.biscans@LIGO.ORG - posted 13:07, Wednesday 21 January 2015 (16187)
Script for the sensor correction gain calculation fixed

I found a small mistake in the HAM_gain_matching_calculation script.

The Q of the GS13 model was wrong by a factor a few, causing a slight phase delay around the frequencies that matter for the sensor correction ([0.1Hz-0.4Hz]).  The overall amplitude was thus altered.

This has been fixed and committed into the SVN:

/ligo/svncommon/SeiSVN/seismic/HAM-ISI/Common/Misc/HAM_gain_matching_calculation.m

 

Here's the correct values that we have so far (I though we had done HAM2 as well, but I can't find a good set of data):

  HAM4 HAM5 HAM6
X 0.945 1.001 1.035
Y 0.929 0.991 1.027
Z 0.918 1.039 1.103

 

We still need to do HAM2&3, plus all the BSCs. Don't forget to put the ISI in high blend mode with sensor correction OFF when you want to calculate the gain.

H1 PSL (DetChar)
edmond.merilh@LIGO.ORG - posted 13:05, Wednesday 21 January 2015 (16186)
PSL Diagnostic Breadboard Reports w/ISS RPN
Non-image files attached to this report
H1 SEI
hugh.radkins@LIGO.ORG - posted 12:24, Wednesday 21 January 2015 (16183)
EndX ETMX BSC9 HEPI Guardian restarted wp 5019

Using the Guardian manager, brought down the entire ETMX SEI after capturing the current held position for HEPI.  The Guardian code has been changed to restore all 8 dofs on HEPI to reduce or nearly eliminate alignment changes from lock to lock.  Before HEPI only restored the RZ and Pitch at the ETMs.

The Guardian smoothly brought the system down with no trips.  Restarted the Guardian code and then went directly to fully isolated first time.  No problems with the idea then.  I'll step this through all the platforms as commissioners allow.

Of note, none of the DOFs on the BSC-ISI are restored like this (As opposed to the HAM-ISI where all dofs are restored.)  So, I attach a plot showing the before and after of this morning's restart.  The op-levs are shown and the HEPI RZ.  Additionally, all the rotational dofs of the two ETMX ISI stagesare show to reveal at least one lock to lock alignment change on the ISI.  All the SEI channels are in nano units, Oplevs are urads I believe.  The Stage1pitch is worst at 600nrad tilt, all others are much smaller.

Images attached to this report
H1 General
travis.sadecki@LIGO.ORG - posted 11:30, Wednesday 21 January 2015 (16182)
Morning meeting notes
H1 PSL (DetChar)
edmond.merilh@LIGO.ORG - posted 10:53, Wednesday 21 January 2015 (16181)
PSL Weekly Report
Images attached to this report
H1 PSL
edmond.merilh@LIGO.ORG - posted 10:33, Wednesday 21 January 2015 (16180)
PSL Chiller Water

250ml of water added to chiller.

H1 IOO (ISC)
kiwamu.izumi@LIGO.ORG - posted 10:01, Wednesday 21 January 2015 (16179)
a lens inserted in IMC refl camera on IOT2L

As we found that the beam was too big on the IMC refl camera (alog 16166), I inserted a focusing lens (PLCX-25.4-20.6-UV) in front of it in order to obtain a better and wider view. The belows are pictures before and after the lens insertion.

Before

After

Both pictures were taken with the nominal exposure time of 19444 usec. In the second image, the main 00 mode is seen at the lower right. I am not sure whether if the upper part of the image is explainable by spatial higher order modes. It maybe a ghost beam. Note that this ghost-ish structure was visible with a laser card.

Images attached to this report
H1 ISC
sheila.dwyer@LIGO.ORG - posted 00:27, Wednesday 21 January 2015 - last comment - 12:36, Wednesday 21 January 2015(16175)
DRMI +arms tonight

Alexa, Evan, Koji, Arnaud, Sheila, Rana

The good news is that ALS is quite stable tonight, staying locked for up to 2 hours.  

We have been having trouble transitioning to 3F tonight.  We can transition MICH and PRCL fine, but we have seen a lot of noise at 300 Hz when we try to transition SRCL to 3F.  When we try to transition we see noise at 23.5Hz.  

ALS lock loss times: (all Jan 21st UTC) 0:03:02, 0:34:26

ALS lock loss +HEPI, ISI and sus trips: 7:30:15, 5:15:26 

Lockloss and bad misalingment of IMC due to DOF4: 6:35

Images attached to this report
Comments related to this report
alexan.staley@LIGO.ORG - 00:33, Wednesday 21 January 2015 (16176)

DRMI  + arms off resonance lock loss due to SRCL 3f transition at 01/21/14 08:06:00 UTC

sheila.dwyer@LIGO.ORG - 12:36, Wednesday 21 January 2015 (16185)

Keita, Sheila, Daniel, Alexa

Here is a screen shot of what happened that caused HEPI and ISI trips on DIFF lockloss last night.  First, the arms loose the green lock, at that time the DARM output becomes very large, the gaurdian ramps this down over ten seconds, durring which time the integrator in L1 is still integrating.  The guardian eventually clears this integrator.  Before the integrator was cleared, the arm cavity flashes, although the suspension was still swinging so this produced a momentary lock.  The tidal comes on, with a large output because the integrator in L1 has not been cleared yet.  

We have done 4 things to help prevent this in the future:

  • added a limiter of 3x10^6 in the DARM filter bank
  • added a limiter of 10 um in the LSC-X_TIDAL_ERR filter module (and Y)
  • fixed a mistake in the guardian that meant only one of the boosts in L1_LOCK_L was being turned off on a lock loss.
  • increased the speed of the ramping down of the DARM gain, so that the suspension history clearing will happen sooner.  

The last thing that we need to do is add a delay to the logic for the tidal feedback, so that it does not engage prematurely on these momentary locks.  

Images attached to this comment
H1 ISC (ISC)
rana.adhikari@LIGO.ORG - posted 20:05, Tuesday 20 January 2015 - last comment - 14:14, Wednesday 21 January 2015(16171)
UGF Servo math problem

Math puzzle: What's wrong with this UGF Servo?

its installed for use in the OMC and LSC at the moment, and could be used in the ASC if we find we want to hold the UGFs constant during TCS tuning.

Images attached to this report
Comments related to this report
nicolas.smith@LIGO.ORG - 12:59, Wednesday 21 January 2015 (16184)

loop diagram

We want to measure G. The algebra tells us that

b=frac{1}{1-G}e+n,

a=frac{G}{1-G}e+n.

When the excitation is sufficiently large that the noise is negligible, we get G=a/b.

a and b are complex quantities, and the real and imaginary parts are the I and Q outputs of the demods, or

a=a_I+i a_Q,

b=b_I+ib_Q.

In the version of the UGF servo that Rana posted, the phases would be chosen such that the imaginary (Q) outputs are zero, thus

G = frac{a}{b} = frac{a_I}{b_I}.

This is OK as long as G only ever changes in magnitude, otherwise G 
e frac{a_I}{b_I}.

To get the correct measurement in the case of a changing phase, one must do the following:

G = frac{a}{b} = frac{ab*}{|b|^2} = frac{a_I b_I+a_Q b_Q}{b_I^2+b_Q^2} + i frac{a_q b_I-a_I b_Q}{b_I^2+b_Q^2}=G_I+iG_Q

This is implemented in the attached simulink model.

simulink model

Images attached to this comment
Non-image files attached to this comment
koji.arai@LIGO.ORG - 13:40, Wednesday 21 January 2015 (16188)

(First of all I don't know the answer yet)

I believe G only changes the gain most of the case.

The problem was

a/e = G/(1-G) and b/e = 1/(1-G) change their phase as you change the gain of G. 

We usually don't care the phase of G, but only care the magnitude of G as the phase of G is fixed.

Therefore what we need is to take the ratio of the magnitude of a and b

|a| = |G|/|1-G|, |b| = 1/|1-G|

|a|/|b| = |G|, where |a| = sqrt(aI2+aQ2) and |b| = sqrt(bI2+bQ2)

(Ed: I'm suggesting to take SQRT(I^2+Q^2) to eliminate the frequently-omitted-effort of adjusting the demod phase correctly.)

william.korth@LIGO.ORG - 14:14, Wednesday 21 January 2015 (16190)

Meh, I say it's overkill. As Nic mentions, this works just fine if the UGF phase is not changing, so long as you set the demod phase correctly. As Koji mentions, the UGF phase should not be expected to change that much. It is already a second-order effect, so what is there now should be fine, unless we really want to accommodate wild loop phase fluctuations at the UGF. Is there a reason that's ever something we want?

Displaying reports 67241-67260 of 83004.Go to page Start 3359 3360 3361 3362 3363 3364 3365 3366 3367 End