Displaying reports 63481-63500 of 77237.Go to page Start 3171 3172 3173 3174 3175 3176 3177 3178 3179 End
Reports until 11:31, Thursday 25 September 2014
H1 ISC
kiwamu.izumi@LIGO.ORG - posted 11:31, Thursday 25 September 2014 (14137)
locking activity last night

Summary of the activities from the last night:

 

Below are some details:


(X arm locking)

The PSL light was locked to the X arm by feeding the signal back to MC2. This configuration gives us a situation where we can steer IM4 and PR2 such that the input pointing matches the cavity axis of the X arm. In prior, I moved the bounce and roll filters in MC2 from ISCINF to M2_LOCK_L such that the notches are applied only to the M2 stage. This is a suggestion from Ryan of LLO in order for a HSTS suspension to avoid ringing up the modes without sacrificing the length control bandwidth. This seemed to help the stability a lot. I did not see a too-prominent peak at these bounce and roll frequencies when it was locked. Good.

I followed the procedure described in a previous alog (alog 13747) except for the sensor. This time I used ASAIR_RF45_I instead of a REFL detector because ASAIR seemed to have a larger signal level without extra whitening amplifications. Also I tailored the demodulation phase to -98.6 deg which maximized the in-phase signal. The LSC gain needed to be 0.01 in this case which gave a UGF of 50 Hz. Measuring the open loop transfer function, I found that the phase margin at around the UGF was about 10 deg or so. So I put a lead filter in FM5 of LSC_XARM to bring the phase up by approximately 30 deg around the UGF. The measured open loop with the lead filter on is attached below.

Though, I still don't understand why the phase had been so bad in the first place. According to the digital filters we have, the phase between 40 and ~200 Hz should be about 90 deg as it falls as 1/f. But the open loop looked falling as 1/f2.

 

(POPAIR realignment)

After I touched up IM4 and PR2 (mainly in pitch), I could not get reasonable signals from both POPAIR_A and _B at all. I went to ISCT1 and checked the beam in the path. Indeed the beam was off from both diodes. Similarly to the other day (alog 14055), I could not precisely evaluate the beam position on the top periscope mirror. The beam was too high on the bottom periscope mirror while the horizontal looked centered. I steered the top periscope mirror and realign the down-stream again. Also, I moved the POP camera position to a point close to the last steering mirror in order to get a bigger beam image.

After the realignment, I did not see an apparent sign of clipping in the POP beam image. Good.

 

(Michelson free swing)

See the attached below:

Note that the incident power on IMC at this point was 10 W.

Images attached to this report
H1 SUS
keita.kawabe@LIGO.ORG - posted 11:04, Thursday 25 September 2014 - last comment - 14:14, Thursday 25 September 2014(14144)
OL sign convention

Daniel and I have found that the optical lever sign convention for ETMs and ITMs was changed in May/2013, and now it's opposite of what I remember.

I'd like to know why it is/was a good idea.

Right now, the dot on the screen goes up when the OL beam goes down.

Comments related to this report
thomas.vo@LIGO.ORG - 14:14, Thursday 25 September 2014 (14149)

It probably was changed so that the convention matches the SUS coordinate system so that positive pitch in the OSEMS should read positive pitch in the OLs, if this isn't the case then it's an error.

LHO FMCS (FMP)
richard.mccarthy@LIGO.ORG - posted 10:43, Thursday 25 September 2014 (14142)
Supply Fan 5 Motor Starter
The circuit breaker for the motor starter on Supply Fan 5 was replaced. This fan is the cold deck fan for the OSB lab area.  The breaker failed to turn on after shutting it off for greasing of the fans.  This is an odd failure for a Circuit breaker but not unheard of.
H1 PSL (PSL)
peter.king@LIGO.ORG - posted 10:02, Thursday 25 September 2014 (14141)
ISS PD Array Picomotor Cable Pulled
The in-air cable for the Picomotor (PM5) was pulled.  Labelled H1PSL-ISS_PM5.  Goes from HAM2 flange D6-F12 to Picomotor controller #5, channels 5-8.

This Picomotor steers the beam before the mode matching telescope to the ISS photodetector array.

See D1002873 for flange nomenclature.

Work permit 4868.


Fil, Peter
X1 DTS (CDS)
james.batch@LIGO.ORG - posted 09:36, Thursday 25 September 2014 (14140)
Rebooted x1work, install new software
The x1work computer has been rebooted following patches for the bash security bug. It hung on reboot, and shows a tendency to not want to mount partitions in a timely manner.

New software:  A new version of root 5.34.00 has been installed as the default which has the python interface enabled.  Also a new version of gds tools, branch gds-2.16.12.2, is installed as the default for testing.  These software packages are for Ubuntu 12.04.  
H1 PSL (PSL)
peter.king@LIGO.ORG - posted 08:20, Thursday 25 September 2014 (14139)
ISS fluctuations
For the past few days the ISS actuator has been swinging around more than it should.  This was remedied by adjusting the
REFSIGNAL slider.  This setpoint indirectly sets the power incident on the PMC.  in some sense there should be no reason
to change the setting unless the power out of the laser has increased or decreased.

The REFSIGNAL slider was adjusted from -2.03 to -1.98.  Which implies a 2.5% decrease in power ((2.03 - 1.98) / 2.03 x 100).
Prior to that the output power of the laser only decreased by less than 1%.  The power transmitted by the PMC varied by ~2.8%.
The reference cavity transmission decreased by ~14%.  We already know there is a drift in the optical path to the reference
cavity.  The ISS railings are due to fluctuations in the PMC transmission.

We should examine the performance of the PMC more closely to see if we can decrease the power fluctuations out of the PMC.
Alternatively we can diffract more light to compensate for the drifts in PMC transmission.
Images attached to this report
H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 07:47, Thursday 25 September 2014 (14138)
CDS model and DAQ restart report, Wednesday 24th September 2014

model restarts logged for Wed 24/Sep/2014
2014_09_24 09:41 h1hpibs
2014_09_24 09:41 h1iopseib2
2014_09_24 09:41 h1isibs

2014_09_24 13:41 h1fw0
2014_09_24 14:27 h1fw1

restart of h1seib2 after unexpected crash. unexpected restarts of h1fw[0,1]

H1 SEI (ISC)
kiwamu.izumi@LIGO.ORG - posted 21:18, Wednesday 24 September 2014 (14136)
HAM5 ISI tripped at 1095626448 and affected the beam at the dark port

Looking at the dark port camera, I found that the infrared beam looked clippy and also off from the center by half of its beam size toward right in the camera view.

Then I found that the HAM5 had been tripped most of the time today. I untripped it. It looks like GS13s triggered the watichdog.Untripping the HAM5 ISI steered the beam toward the center. The ITMX reflection still looks bit off toward right, and the ITMY is apparently too low by half of its beam size. The attached is the python plot of the trigger event.

Images attached to this report
H1 AOS (AOS, ISC, SUS)
sheila.dwyer@LIGO.ORG - posted 20:54, Wednesday 24 September 2014 - last comment - 14:29, Thursday 25 September 2014(14134)
Y arm initial alingment

Keita, Sheila, Gabrielle

Now, in chronological order:

result of TMSY to IMTY baffle PD search:

PD label in epics

PIT YAW V gain (dB)
ITMY PD1 2.2 7.3 3.6 20
ITMY PD2 -72.5 -70 4.3 20
ITMY PD3 -153.5 -1.6   20
ITMY PD4 -97.8 74 3.6 20

Based on D1200657-v4, (assuming the view shown is looking at it from the BS), this does not make sense with the arrangement of baffle PDs.  These votlages are low compared to what we see on the X arm, so we suspected that this was a second bounce or ghost beam, however, they do not move when the ITM or ETM are moved, so they are not reflections off of those optics.  If we think that if these are the real beam, the baffle PDs are mislabeled somewhere, so we used the TMS suspension alingment sliders to try to figure out which PD is which.  (Unfortuately, the TMS alignment slider also seems to be wrong.)

Based on our reinterpreation of the labels, we thought that the beam should be roughly centered on the optic when TMS is at -35 PIT, -31 Yaw.  However, we saw no sign of our beam at this location, nothing on ISCT1 and nothing returning to the ETM when we scan the ITM.  Keita trended the old values, and we saw the beam go by on SRM when he restored them.  Gabriele and I went to ICT1, and found a badly clipped beam by exciting the BS.  Later Keita and I returned and moved the TMSY alignment to get a somewhat better beam, with a TMS alignment of -87 PIT and -51.4 YAW and BS at 187 PIT and -258 YAW, we have 10 uW on ISCT1.  this was the same in the spring (alog 11296)  giving us some confidence that we really have the single shot beam on ISCT1.  (This is our first clue that the TMS alingment slider is wrong)

We went through the baffle PD game by moving ITMY and looking at the ETMY baffle PDs, using this TMS pointing which isn't necessarily centered on ITMY:

PD label PIT YAW V gain (dB)
PD1 140 -106 almost 2V 20
PD2 112 -135.9 2 20
PD3 140.3 -170 2 20
PD4 173 -140 2

20

This seems to make sense, but the power is low again.  We think this beam should be roughly centered on the ETM with the ITM slider at 156.5 PIT -123 Yaw. 

Since exciting the ETM (around its saved alignment) and watching on the MC1 camera and at ISCT1 didn't show us any return beam, we redid the baffle PDs for the ETM pointing:

PD label PIT YAW V gain (dB)
PD1 11.3 -26.3 0.17 0
PD2 42.0 -60.4 0.21 0
PD3 72.3 -26.6 0.17 0
PD4 48.5 8.8 0.18 0

This beam also did not make sense with the baffle PD arrangement, or our interpretation of the actual PD arrangement based on the TMS alingment sliders.  This means that either ETMY or TMSY has a sign flip in the pitch alignment slider (our second clue): 

label reality according to TMSY reality according to ETMY (I think this is the correct case)
PD1 PD4 PD2
PD2 PD1 PD1
PD3 PD2 PD4
PD4 PD3 PD3

Once we understood this I decided that our ETMY interpretation of the cabling must be the correct one, since the TMS pointing that actually gets a beam through the optic is very different in pitch than the pointing we calculated based on the baffle PDs.  Using this information, our original TMSY centered pointing should have been -113 PIT, -35 Yaw.  Indeed, this pointing does result in a beam that doesn't look clipped on ISCT1.  I can also see two other beams on ISCT1 which come from the ETM, but haven't been able to easily align the arm cavity.  Although I see some fringing, the mutliple bounce beams seem to get clipped as I try to align them.  I think the next step is to start fresh with baffle PDs, now that we think we know which one is which.

Images attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 10:51, Thursday 25 September 2014 (14143)

The root of the sign flip for TMSY is the transition from H2 to H1.

H2 TMSY used to have the same sign convention as the H1 TMXS as far as the bias sliders are concerned.

However, when it was moved to new H1 TMXY position, the top cage needed to be rotated by 180 degrees. This changed the PIT sign convention but not YAW.

See D0900419 (H2 TMSY) and D0902168 (H1 TMXY).

daniel.sigg@LIGO.ORG - 11:42, Thursday 25 September 2014 (14145)

Here are the ITMX baffle drawing and ITMY baffle diode drawing.

keita.kawabe@LIGO.ORG - 12:06, Thursday 25 September 2014 (14147)

For your convenience, the attached is the relative position of the ITMY baffle diodes viewed from the ITMY according to the TMSY and ETMY slider bias.

To the left of the plot is the drawing of the said baffle viewed from ITMY (D0900435).

ETMY plot (bottom plot) agrees well with the drawing assuming the cross cabling mentioned by Sheila. If you flip the TMSY plot vertically it also agrees with ETMY and the drawing.

Images attached to this comment
sheila.dwyer@LIGO.ORG - 14:29, Thursday 25 September 2014 (14150)

Now I've swapped tha cables at the baffle PD amplifier box, so the labels should be correct.  For the record I swapped PD1 and PD2 cables, and PD 3 and PD4 cables.  This is what we think will give correct labels in epics, based on the ETMY alignment sliders. 

H1 TCS (TCS)
aidan.brooks@LIGO.ORG - posted 17:48, Wednesday 24 September 2014 (14135)
HWS ups and downs. HWSX return beam success. HWSY in-vacuum lens is not correct

Aidan. Greg.

Good news first:

Using the periscope, we got the green ALS beam aligned to the on-table irises that were pre-aligned to the HWS probe beam. This, nominally, mated the in-vacuum and in-air axes. To test this, we turned on the probe beam and recorded a frame with the HWS camera to see if there was a return beam. And ...

There was a return beam from ITMX. It looks clean (as clean as possible with the Hartmann plate on). The next steps are to remove the plate and

1. Tweak the position of the probe beam on the ITM using the shadow of the baffles as a guide.

2. Move the HWS along the optical axis until it is imaging the ITMX HR surface.

Bad news second:

The in-vacuum lens for the Y-arm Hartmann sensor is not correct (I'm 99% sure of this). It appears to be a concave lens when it should, in fact be a convex lens (PLCX-50.8-360.6-UV). There are two things that indicate this.

1. The green ALS leakge field is quite large (vs the X arm green beam which is quite small). The beams are designed to be small coming out of the viewports and should be, roughly, the same size.

2. The lens is close to the viewport and you can see objects through it. For instance, the SR2 triple, about 3 or 4 feet away) can be seen through the lens off-axis. It appears smaller when viewed through the lens. We I take a spare PLCX-50.8-360.6 (what should be in there) and look through it, objects that are 3 or 4 feet away look bigger.

So I'm pretty convinced the in-vacuum lens is concave when it should be convex. We'll continue investigating how occured (it looks like some typos in a design change have propagated through a few documents). The more important thing is what to do about it. We won't get it working this week, but it may be possible to correct this using additional in-air optics in, what Eric G has dubbed, a Hubble Space Telescope optical fix.

FYI: Livingston has the correct lenses installed in the vacuum system.

Images attached to this report
H1 SEI
hugh.radkins@LIGO.ORG - posted 16:57, Wednesday 24 September 2014 (14133)
WHAM6 HEPI low Freq TF will start ~0300 Thursday Running on opsws1
H1 CDS
cyrus.reed@LIGO.ORG - posted 16:52, Wednesday 24 September 2014 (14132)
h1digivideo2 Rebooted
I rebooted h1digivideo2 to add the new green ITM cameras to the config.  This is the quickest way to ensure that the cameras will continue to work in the future after unintended/intended restarts.
H1 SUS
jeffrey.bartlett@LIGO.ORG - posted 16:01, Wednesday 24 September 2014 - last comment - 14:01, Friday 21 November 2014(14130)
Phase 1B Test Results for Quad-09
Ran a first set of TFs for 3IFO-QUAD09. The undamped plots look OK (pitch is a bit off). The damped plots measurements do not match the model between .1 and 20Hz very well, for both the Main and Reaction chains. Will investigate the cause. Plots are attached.  

As Betsy noted in aLOG 14128 the second pitch mode shift is present as for the other 3IFO Quads tested to date. 

All files, plots, and scripts have been commited to SVN.     
Non-image files attached to this report
Comments related to this report
travis.sadecki@LIGO.ORG - 14:01, Friday 21 November 2014 (15230)

Spectra for this quad attached.

Non-image files attached to this comment
H1 SUS
betsy.weaver@LIGO.ORG - posted 15:06, Wednesday 24 September 2014 (14128)
3IFO QUAD 09 Phase 1B testing

Jeff and Andres finished the transfer functions of the 3IFO Q9 QUAD.  Attached is the TF plot compared to the other 2 3IFO QUADs.  Infact, this unit ALSO has the elusive 2nd pitch mode shifted up in frequency.  In summary, so far all 3 of the 3IFO all-metal QUAD builds have this "feature".

Non-image files attached to this report
LHO VE
kyle.ryan@LIGO.ORG - posted 14:23, Wednesday 24 September 2014 (14127)
~1340 - 1405 hrs. local -> climbed on and around HAM6 to disconnect annulus pump system


			
			
H1 SEI
hugh.radkins@LIGO.ORG - posted 12:26, Wednesday 24 September 2014 (14126)
WHAM6 HEPI IPS Sensors Adjusted

Continuing the HAM6 HEPI Trouble shoot.  Checked sensor readings against visual position and raange of motion.  2 vertical sensors readings where offset wrt their actual positoin enough to allow the sensor to touch its flag.  This had to be corrected so I did that.

This shifted the computed cartesian position.  I looked before and after the adjustments (Loops open all through out) and then adjusted the Target positions appropriately.

WHAM6 is back to Position control but without boost.

The V2 IPS continues to behave and I even jiggled the wires a bit this morning--Periodic maintenance: unplug & plug in cables repeatedly, fun!

H1 SUS
betsy.weaver@LIGO.ORG - posted 10:58, Tuesday 23 September 2014 - last comment - 19:32, Tuesday 30 September 2014(14095)
3IFO QUAD 06 Phase 1B testing

QUAD 06 (Q6) Phase 1B transfer function plots are attached.   We had a hard time obtaining good coherence in the Transverse TF, so it is a bit hashy.  Will try again.  

 

Most notably is that, like Q8, the second pitch mode frequency is unexpectedly pushed upward on the main chain.  Recall, we never found the mechanism to fix it on Q8.  Interestingly, both the Q8 and Q6 assemblies are of the same batch of wires and are fresh builds, but by 2 different assembly teams, and on 2 different solid stack/test stand units.  Q8 is an ETM type of QUAD while Q6 is an ITM QUAD, but both main chains have the same pendulum parameters - both are detailed in the 'wireloop' model.

 

The Q6 data is plotted as QUADTST.

Non-image files attached to this report
Comments related to this report
betsy.weaver@LIGO.ORG - 15:14, Tuesday 23 September 2014 (14100)

We've checked that all wire diameters are as per the specs and that the wire segment clamps are seated properly on the masses.  We've also checked that the wire segments have been assembled with the proper assymetry as per specs (looking for something obvious).

 

Attached are pix of this unit, in case someone wants to look at them.  To me, they look just like the last few QUADs we've built, including Q8.

Images attached to this comment
brett.shapiro@LIGO.ORG - 17:20, Tuesday 23 September 2014 (14112)

Maybe this is a long shot, but we've exhausted all the simple causes...could the top wire be the wrong material? If the modulus of elasticity was higher, within a factor of 2 from where it is supposed to be, that would explain this strange pitch mode.

One way to test this is to measure the violin modes of the topmost wire in situ and see if it is right. Or maybe more simply, cut some wire from this wire stock, hang some wieght off of it, and measure its violin mode.

The correct 1.1 mm diameter wire should have a violin mode of 

frequency in Hz = sqrt(tension/0.0067)/(2*L)

where 0.0067 is the mass per unit length.

 

For example tungsten has a modulus about 2 times higher than what we are supposed to have. If for whatever reason we ended up with a tungsten wire, it would have an in-situ violin mode in the low 200s of Hz, rather than the 332 Hz spec (much denser than the usual piano wire).

brett.shapiro@LIGO.ORG - 17:52, Tuesday 23 September 2014 (14113)

Or even more simply, you could weigh some length of wire. The piano wire should be something close to 7 g/m. If you get different value from that, then the wire is the wrong material.

betsy.weaver@LIGO.ORG - 15:52, Wednesday 24 September 2014 (14129)

To confirm Brett's latest suggest regarding the wrong wire:  We have 2 rolls of 1.1mm diameter top wire here at LHO which could have possibly been used for QUAD builds.  Both are labeled as the correct stuff.  We weighed a 1m segment from each spool.  One measures 7.1g, the other measures 7.3g.

 

To be continued...

betsy.weaver@LIGO.ORG - 15:59, Wednesday 24 September 2014 (14131)

Another sanity check:

The Top Mass blade sets used for these 3 pitch-problematic QUADs are as follows:

Q6 - SET 10

Q8 - SET 8 - although I can't find the actual records

Q9 - SET 2

 

Q7 - SET 7 - still to be tested, unknown pitch frequency TFs

 

The SETs go from SET 1 being the most STIFF to SET 16 being the most SOFT.  So, the sets we are using for the 3IFO QUADs are somewhat scattered or in the middle of the pack.  They are not all clustered at the soft end, nor all at the stiff end...

betsy.weaver@LIGO.ORG - 14:43, Thursday 25 September 2014 (14151)

And here's the spectra of this Q6.  Note, the lowest stage (L2) does not have flags during the all-metal Phase 1 assembly, so the spectra plots of L2 are junk.

Non-image files attached to this comment
betsy.weaver@LIGO.ORG - 16:16, Thursday 25 September 2014 (14155)

And now attached are a damped TF from each R0 and M0.  As we all have noted in SUS - damped TFs on Phase 1 test stands are not useful since the damping is a function of the code on the out-dated test stands and the loops are not tuned very well.  Long story short, there is a little bit of damping evident, given whatever filters and gains are loaded, and we can see healthy excitations run through the suspension so all seems well with damping capabilities of Q6.

Non-image files attached to this comment
brett.shapiro@LIGO.ORG - 19:32, Tuesday 30 September 2014 (14235)
I ran the matlab model fitting code on the wireloop model for QUAD06. I used the measured top mass resonance frequencies, as well as the long-pitch frequencies from the triple hang data that Betsy collected. The latter was extremely helpful in refining the results beyond what top mass TFs provide on their own.
 
NOTABLE RESULTS:
 
* The top mass and UIM inertias converged to the same values obtained from the fiber H1ETMY fitting results (lho log 10089), within the error bars. This includes +12% on the UIM pitch inertia from what is given in the final quad design doc T1000286. Note, this means the same large shift has been found on two different configurations of different quads. So it is likely that the fitted value is correct. But great news for consistency on the suspensions.
 
* Some of the d's moved significantly. However, the move is noticebly less if you start from the previous fit to H1ETMY rather than the base model.
    -dn (top blade tip) increased by 1.25 mm relative to the H1ETMY fit. It is +2 mm relative to the base model. Note, one could alternatively shift dm instead.
    -d1 (uim blade tip) did not move significantly relative to the H1ETMY fit. However, it is +3 mm from the base model. Note, one could alternatively shift d0 instead.
    -d2 (PUM round prism, not part of fiber model) decreases by 1.25 mm.  This actuall could be due to errors in my previous estimate of what this value should be. In fact, this shift puts it about where it is supposed to be for the fiber quad.          Not sure if that is the intent with this prism.
 
* Still not clear what caused the shift in dn (or dm) relative to previous suspensions, like H1ETMY. The model fitting wouldn't say that though. All it can do is say that either dn or dm is off.
 
 
MORE DETAILS:
 
Plots of comparisons of the before/after models against the meadured data are attached. The first 6 pages show the top mass TFs. The 7th and final page merely shows the triple hang long-pitch frequencies since this data was pulled from an amplitude spectrum. In these plots, there are notable shifts in just 2 modes. The 2nd pitch mode (1.5ish Hz) on the top mass TF, and the first mode of the triple hang (0.4ish Hz), which is also pitch. The updated model shows pretty good agreement all around.
 
The parameter shifts required to make the match were originally rather large, for both the d's and the pitch moments of inertia. Interstingly, the moments of inertia for all the top two masses (didn't need to float the lower ones) consistently converged to the model fitting results from the fiber ETMY quad. Thus, I updated the wireloop model (update not committed to the svn yet) with the fitting results from H1ETMY for all the parameters of the top two masses (springs, inertias, d's). I then used this updated wireloop model as the staring point for the model fit.
 
The shifts in the parameters are below. The d's moved noticeably. The spring stiffnesses did not move a great deal, but were useful in fine-tuning the fit. The inertias did not need any further refinement from H1ETMY. I find this last point extremely exciting.
 
* mm shifts in the d's from H1ETMY fitting results
dn: 1.2438 +- 0.069243 mm   -> top mass blade spring tip
d1: 0.38916 +- 0.16088 mm   -> UIM blade spring tip
d2: -1.2815 +- 0.10267 mm    -> round PUM prism
 
* % shifts in the blade spring stiffnesses from H1ETMY fitting results
kcn: 2.1235 +- 1.8491 %         -> top-most blade stiffness
kc1: 0.56079 +- 0.45919 %     -> top-mass blade stiffness
kc2: -1.493 +- 0.58382 %        -> UIM blade stiffness
Non-image files attached to this comment
Displaying reports 63481-63500 of 77237.Go to page Start 3171 3172 3173 3174 3175 3176 3177 3178 3179 End