Displaying reports 79601-79620 of 83254.Go to page Start 3977 3978 3979 3980 3981 3982 3983 3984 3985 End
Reports until 12:49, Wednesday 08 August 2012
H2 SUS
szymon.steplewski@LIGO.ORG - posted 12:49, Wednesday 08 August 2012 (3748)
Suspension Coil Driver noise testing

Around 2:30 on August 7, 2012 I attached 5 grounding plugs to the "TEST IN" connections at the Y end station.  At this time, all ITMY and ETMY coil driver boxes (for TOP, UIM, and PUM) have grounding plugs connected to each of the TEST IN connections.  I then took some power spectra measurements of the coil driver NoiseMonitor channels to see what effect the grounding plugs have on the coil driver noise.

Starting with ETMY, the UIM driver board didn't exhibit any significant change between COIL IN and TEST IN configurations.  This is because the noise in the coil drivers is dominated by component noise, and selecting the TEST IN state allows one to see the component noise without the added DAC noise.

The ETMY PUM driver board is dominated by DAC noise, since the PUM driver is not filtered as much as the UIM board in the lowest noise mode.  Therefore when we switch to the TEST IN state, the expectation is that the noise in all coil drivers should drop to the component self-noise level.  This is what we are seeing now, as compared to Jeff K's alog #3111 when the noise levels increased and the frequency dependence was different for those channels.

https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=3111

For the ITMY, the UIM behavior is generally the same as on ETMY coil drivers.  However, the ITMY PUM driver shows an increase in noise after switching to the TEST INPUT with grounding plug attached.

Non-image files attached to this report
LHO General
patrick.thomas@LIGO.ORG - posted 11:38, Wednesday 08 August 2012 (3755)
dust monitor in clean room over HAM3 swapped
Due to a calibration error, the dust monitor at location 15 in the LVEA (in the clean room over HAM3) was swapped. It was removed around Aug. 8 17:20 UTC and the new one put in around Aug. 8 18:01 UTC.
H2 ISC
jaclyn.sanders@LIGO.ORG - posted 09:31, Wednesday 08 August 2012 - last comment - 08:05, Thursday 09 August 2012(3746)
Cavity Characterization: Preliminary Results

This is the transfer function between the phase-frequency discriminator and the FET IQ demodulator while the cavity is locked. The blue trace is "initial" conditions, i.e., with a well-aligned cavity and standard modulation sidebands. The green "sb shift" trace was taken with the RF modulation sideband frequency tuned 200 Hz higher than its initial value. The red "alignment shift" trace was taken with the ITM yaw misaligned. 

The FSR is 37.512 kHz, with a higher-order FSR peak at 75.018 kHz. Given this FSR, the cavity length is 3995.95 m.

The peaks due to the RF modulation sidebands are at 54.432 kHz and 58.098 kHz in the initial trace. These peaks shift 200 Hz in the green trace.

Additional structure is observed at 46.301 kHz, 55.325 kHz, 57.252 kHz, and 66.229 kHz. The peaks at 46.301 kHz and 66.229 kHz increase for the case of yaw misalignment and are thus likely to be (1,0) modes. 

The separations between these peaks are:

75.018 - 66.229 = 8.789 kHz

66.229 - 57.252 = 8.977 kHz

46.301 - 37.512 = 8.784 kHz

55.325 - 46.301 = 9.024 kHz

The mean modal spacing is 8.8935 kHz.

From this modal spacing, the g-factor is 0.540532, corresponding to approximate mirror radius of curvature of 2302.86 m. 

The FWHM of the FSR peak is approximately 94 Hz. Finesse is thus 37512/94 = 399.064. This would occur for a reflectivity of about 99.2%.

There's a follow-up of this in the works for characterizing cavity properties during ring heater use.

Images attached to this report
Non-image files attached to this report
Comments related to this report
daniel.sigg@LIGO.ORG - 08:05, Thursday 09 August 2012 (3772)
The RF frequency is 24.515730 MHz and was shifted to 24.515930 MHz for the second measurement. Making the ansatz

f_SB = (N - 1) * f_FSR + f_mease 

with f_FSR ~ 37.51kHz, N an integer, and f_meas = 58.098 kHz, we determine 

N = 653

Now, we can go back and recalculate f_FSR = 37511.71 Hz with a few ppm precision. This then yields L_arm = 3995.985m.
H1 TCS
aidan.brooks@LIGO.ORG - posted 09:01, Wednesday 08 August 2012 (3754)
ETMY Ring Heater set to ~30W

I turned on the ETMY RH, requesting 630mA from each ring heater segment. This equates to roughly 30W of power input into the ETM. I'm monitoring the Hartmann sensor signal to check for a response.

The ITMY YAW was set to zero (from 717.81 counts) to keep the cavity from resonating or flashing during this measurement.

The time constant of the ring heater is several hours, so we will run this at least until noon.

H2 ISC
bram.slagmolen@LIGO.ORG - posted 23:21, Tuesday 07 August 2012 (3752)
OAT Locking

I locked the arm and did a dither alignment (>8000 on the REFL diode) and engaged the off laod at 23:10h local time, so good times are from 23:15pm.

With the work on the RefCav I will be keen to see the noise at higher frequencies. Vincent reinstalled the boosts on the ISI isolation, so all should be nice.

Should be good for the night.

LHO General
patrick.thomas@LIGO.ORG - posted 19:30, Tuesday 07 August 2012 (3751)
plots of dust counts
Attached are plots of dust counts > .5 microns in particles per cubic foot. The dust monitor in the clean room over HAM 3 (location 15) has a calibration failure. I'm not sure when it started, but I think it was sometime today.
Non-image files attached to this report
LHO VE
kyle.ryan@LIGO.ORG - posted 18:02, Tuesday 07 August 2012 (3750)
Added ~5 quarts turbine oil to Kobelco purge-air compressor


			
			
LHO VE
kyle.ryan@LIGO.ORG - posted 17:59, Tuesday 07 August 2012 (3749)
Lots-0-Leaks
I was only able to test ~20 joints today on the Vertex due to leaks.  Aaaargh!  At this rate, I'll need two or more additional days to finish!  A few of the leaks were on "legacy" joints circa 1998 but most were on new aLIGO joints.  I was able to retorque and get most of these to seal but this wastes time and is "not on the schedule" - better to do it right the first time!
H2 ISC
bram.slagmolen@LIGO.ORG - posted 13:15, Tuesday 07 August 2012 (3745)
OAT RefCav

During the reboots I took the opportunity to have another look into the OAT RefCav in the optics lab.

I removed the 50/50 beam pslitter infront of the RF LSC diode, so now ~30 mW of power is incident. In addition in optimised the HWP infront of the PM to reduce the AM, 2f_sb = < -80dB.

The few irises in the beam path are closed down, I looked with the viewer and reduced the iris so it was just not clipping.

I didn't find a low enough ND filter to o the paracitic interfernce hunt.

The cavity locks stable with a UGF ~300kHz, the settings are

Coarse Fine Common Fast Offset
351 420 350 540 293

The Laser temperature on the controller displays: T+40.991, the slow output (T-ed to the laser slow input and the oscilloscope) is at -620 mV.

Once we get the cavity locked again we can see if we gained anything.

H2 SEI
vincent.lhuillier@LIGO.ORG - posted 09:28, Tuesday 07 August 2012 - last comment - 14:14, Tuesday 07 August 2012(3744)
Boost filters back in FM10

I put the boost filters back in FM10 of the ISO filter bank on BSC6 and BSC8. They switch when crossing zero but I have changed the tolerance (300 to 50 counts) and the time out (2s to 20s).

Comments related to this report
vincent.lhuillier@LIGO.ORG - 14:14, Tuesday 07 August 2012 (3747)

Instead of engaging the filters when zerocrossing, the ramp (10s) is used.

H2 ISC
bram.slagmolen@LIGO.ORG - posted 20:57, Monday 06 August 2012 (3743)
OAT WFS demod phase

Elli and Bram

We went to the EY and injected a sine wave at 2280 Hz, 200 mVpp into the CMB-B (PDH), Exc A input. Then we used ddt to measure the tranfer coefficients of the SegX_Ix/SegX_Qx. We optimised the demodulation phase and maximised the transfer coeeficient. Although we could not zero the Q-phase, we got a factor of ~30x between the I and Q phase for all segments in both WFS-A and WFS-B.

in between the measurements we aligned the beams onto the WFS but adjusting the picomotor mounts. We actually did this manual and did NOT use the picomotor driver, which would be nice in the future ...

Now we can use the WFS for alignment feedback to the Quads, well at least measure the TFs.

LHO General
patrick.thomas@LIGO.ORG - posted 19:43, Monday 06 August 2012 (3742)
plots of dust counts
Attached are plots of dust counts > .5 microns in particles per cubic foot.
Non-image files attached to this report
H2 SUS
szymon.steplewski@LIGO.ORG - posted 16:48, Monday 06 August 2012 (3741)
Grounding Plugs for ITMY coil drivers

I attached 5 grounding plugs to the ITMY coil drivers Test Input this afternoon ~ 4:30 pm.  Three were connected at the top stage driver, and one each for UIM and PUM drivers.  I plan on doing the same for ETMY tomorrow before making measurements of the coil driver noise.

H1 SUS
betsy.weaver@LIGO.ORG - posted 16:25, Monday 06 August 2012 (3740)
H1 MC2 installed in HAM3

(Betsy, Travis, Deepak, Cheryl, Dale on the camera)

All the prep work paid off and the MC2 was installed into the chamber relatively easy this afternoon.  Using the genie, we hoisted it up to the elevator which was attached to the arm, attached the spacer to the bottom of the suspesnion, and then used the arm to swing it into place on the ISI table against the cookie cutter.  We added a few dog clamps to make sure it doesn't walk away overnight.  Tomorrow we continue adding dog clamps, hooking up cables, etc.

LHO General
gerardo.moreno@LIGO.ORG - posted 16:09, Monday 06 August 2012 (3739)
Ops Summary

Report of site activities:

H2 SUS
szymon.steplewski@LIGO.ORG - posted 15:29, Monday 06 August 2012 (3735)
QUAD SUS OSEM sensor diagonalization

During the past few weeks I have been working on calibrating the sensor readouts from the Quad Suspension OSEMs on all four stages: main chain top M0, reaction chain top R0, upper intermediate mass (L1 stage or UIM), and penultimate mass (L2 stage or PUM).  One way to check the OSEM readouts is to measure their response to an excitation of the top mass, and then compare this to the response predicted by the 20120601TMproductionTMrehang mathematical model.  The Quad Suspension has a 0.43 Hertz mostly "Longitudinal" mode, and exciting this mode by shaking the main chain top mass will result in peaks at 0.43 Hz for all OSEM sensor spectra (M0F1 spectrum attached as an example).  Comparing the peak height data of each OSEM at 0.43 Hz to the data predicted by the model should show any dissimilarity between the predicted behavior of the OSEM sensors and what is actually seen.  

The file OSEMsensorplot.pdf shows the magnitude of the OSEM sensor readouts (vertical axis) for each OSEM ID(horizontal axis) scaled so that the magnitude of the Main Chain F1 OSEM is always one.  I tried a few different methods of measuring the power spectra that generate this plot, and they are labeled on the side of each plot.  In each case damping of the top stage reaction and main chains was OFF.

The model prediction is the sensor response at the 0.43 Hz peak for each OSEM derived from the mathematical model of the quadruple suspension.  The measurements labeled "White Noise" are from excitations of white noise into all Main Chain TOP degrees of freedom (Longitudinal, Transverse, Vertical, Roll, Pitch, and Yaw).  These white noise power spectra were collected WHILE the excitation was being performed.  In the 7/3/2012 White Noise measurement the coherence in the L2 stage OSEMs was terrible, and so these data points are not reliable.  The measurements labeled "Offset" are derived from an excitation where each main chain TOP degree of freedom was displaced with a static offset value after a turn-on ramp time of 10 seconds, then this static offset was instantly changed to zero to let the suspension swing freely.  Lastly the measurements labeled "Sine Relax" were taken by exciting the main chain TOP mass Longitudinal DOF with a 0.43 Hz sine wave drive for about five minutes, then the drive was turned off and the suspension allowed to swing freely for about 2 minutes before the power spectra were taken.

The sensor plot shows that the different measurement approaches lead to consistent OSEM data, but we see immediately that the lower stages have some problems.  The L1 stage magnitudes on each suspension appear slightly lower than predicted, but only ITMY OSEM L1LL is way off.  This could be a problem with the L1LL alignment or an electronic issue that fails to correctly communicate the position of the flag on that sensor.

The L2 stage is troubled with multiple symptoms, each OSEM is well below the model prediction.  I am still struggling to understand why the response is so small.  One glaring problem is that the L2UR sensors on both ETMY and ITMY are practically zero compared to the other L2 OSEMs.  I suspect that these specific sensors dead or barely working, but will need to check this somehow.

Images attached to this report
Non-image files attached to this report
H2 CDS
david.barker@LIGO.ORG - posted 13:05, Monday 06 August 2012 (3738)
h2tcsl0 install TCS ITMY model, H2 DAQ restart

I replaced the H2GDSAWGL0 model with H2TCSITMY on h2tcsl0 following the install of a second ADC card in this front end. The front end now has 2 ADC and 1 DAC cards. PEM uses the first ADC, TCS uses the second ADC and the DAC card.

The H2 DAQ was restarted with the new configuration.

The h2tcsl0 restart invalidated all the front end data. After the DAQ restart I had to restart the data streamers on each model, so the H2 data gap was longer than anticipated at about 10 minutes.

H2 AOS
thomas.vo@LIGO.ORG - posted 17:15, Thursday 26 July 2012 - last comment - 16:26, Wednesday 08 August 2012(3614)
H2 ITMY/ETMY Optical Lever Calibration
Jeff K. , Thomas V.

Below are the calibration parameters for the H2 ITMY Optical Lever:
        Slope          Y-intercept
Pitch [ 580.41229822  -11.51774017]
Yaw  [ 689.70532274  -13.3345144 ]


And here are the calibration parameters for the H2 ETMY Optical Lever:
         Slope           Y-intercept 
Pitch [ 1666.80728788   -33.14694715]
Yaw  [ 1727.67131855     23.41350328]

Both sets of calibrations were attained via the same process of moving the QPD along a translation stage and measuring the output signal.  All four sets of slopes are in units of radian*meters.
Images attached to this report
Comments related to this report
thomas.vo@LIGO.ORG - 14:40, Friday 03 August 2012 (3713)
Jeff K. Thomas V.

We have found a non-linear relationship between the way the translation stage moves and the way we were reading out the measurements.  We need to double check the calculations as well as the methodology on retrieving data.  This latter is difficult because even though there is a micrometer on the translation stage it is covered by the laser enclosures, which if we take off, it will introduce ambient light onto the QPD.  We are currently investigating solutions.
jeffrey.kissel@LIGO.ORG - 11:59, Monday 06 August 2012 (3736)
T. Vo, J. Kissel

Pulling out a spare translation stage and measuring the displacement response (in [mm]) to controller demands (in [ct]), we found the following attached relation. Immediately turned off by the non-linearity seen, from our experience with the controlers jolting the translation stage upon power on/off, and from Kissel's recollection of the controllers in i/eLIGO (of which these controls are the same), we've launched into a more sophisticated characterization of the controllers. Given that the non-linearity is roughly 1 [um] over the 1 [mm] range measured, we might be barking up the wrong tree and just be over-reacting, but it should be a quick round of measurements to assess it in more detail.

It should also be noted that the controller can demand from 0 to ~8600 [ct], and we've thus far only exercised it from 0 to 150, since we only need ~1 [mm] range given the size of the Oplev QPD.
Non-image files attached to this comment
jeffrey.kissel@LIGO.ORG - 13:03, Monday 06 August 2012 (3737)
T. Vo, J. Kissel

Here're the results from the more detailed characterization. It looks like, within a small range of operation the controller is indeed linear to the desired level. However, over the full range of the controller, there's certainly some non-linearities present.


Notes:
Linear UP -- commanding the stage to move from 0 (4000) up to 150 (4150), in linear 10 [ct] increments.
Linear DOWN -- commanding the stage to move from 0 (4000) up to 150 (4150), in linear 10 [ct] increments.
Random -- going to each data point in a random order

Each of these should yield the same answer if it's a truly linear system.
Non-image files attached to this comment
thomas.vo@LIGO.ORG - 16:26, Wednesday 08 August 2012 (3758)
Jeff Kissel Thomas Vo

After reviewing the linearity of the translation stage as shown in ALOG 3737, we found that the non-linear regime of the translation stage resides near the end of the rails of the stage but the approximate middle yielded linear results.  We're confident that the increments that we used to translate the stage during calibration for both test masses were small enough and far enough away from the edges so that the non-linearity would have a small affect on our results, this will require further testing to truly be valid (in progress).  That being said, after correcting some errors in the calculations and double checking our numbers, we used the original data to apply to the calibration.  

A noteworthy point: Jeff Kissel used the edrawing from the solidworks model in,

LHO Corner Station: D0901469-v5 
LHO EY Station: D0901467-v6 

to find a more accurate number for the lever arms than previously used, ITMY = 56.4m and ETMY = 6.6m, as opposed to 70m and 6m respectively.  This was taken into account for our last calculation.

Onto the good stuff, the values of the slopes below are in micro-radians*meters:

ITMY
        Slope         Y-Intercept
Pitch [ 25.93274501  -0.51461109]
Yaw   [ 30.81584154  -0.5957635 ]



ETMY
        Slope         Y-Intercept
Pitch [ 54.53112025  -1.01505634]
Yaw   [ 56.56393367   0.79879263]


Attached are the graphs of the linear response curves, the python fitting scripts and the EXCEL spreadsheets to help visualize the underlying calibration calculations. In particular, the excel spreadsheets shows the conversion from controller units into millimeters and then into meters and micro-radians.  Hope this is the last time we'll need to repeat this post, sorry for the troubles!
Images attached to this comment
Non-image files attached to this comment
Displaying reports 79601-79620 of 83254.Go to page Start 3977 3978 3979 3980 3981 3982 3983 3984 3985 End