Displaying reports 73861-73880 of 77380.Go to page Start 3690 3691 3692 3693 3694 3695 3696 3697 3698 End
Reports until 19:02, Thursday 26 July 2012
LHO General
patrick.thomas@LIGO.ORG - posted 19:02, Thursday 26 July 2012 (3617)
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 ISC
eleanor.king@LIGO.ORG - posted 18:13, Thursday 26 July 2012 (3616)
Optimising ALS green laser doubler crystal temperature

Bram, Alberto, Elli.  We set the green laser doubler crystal temperature to maximise the green laser power output.  The laser diode current was 1.725A and the 1064 laser crystal was 42.05 degrees C.  We varied the doubler crystal temperature and measured the power output.  Attached is a plot of these measurements.  The green laser power was maximised when the doubler crystal temperature was set to 34.37 degrees C.

 

When the doubler crystal temp was 34.37 degrees C:

(with 1.725A input current, 42.05 degrees C crystal temp)

-The laser power output was measured at 41.9mW

-GR_PWR_MON read 8400 counts

-REFL_PWR_MON read 15500 counts, and we measured 1.22mW, 4.8V, and a gain setting of 20dB at this PD.

Images attached to this report
H2 SEI
fabrice.matichard@LIGO.ORG - posted 17:50, Thursday 26 July 2012 (3615)
ETMY ISolation, Comparison with ITMY
The work done on ITMY in the last few days has been duplicated to ETMY. It was very straight forward. The exact same blend filters are being used on both units and provide similar isolation. See attached plot where:

- Red curve is ITMY, BSC-ISI control off  
- Blue curve is ETMY, BSC-ISI control off
- Green curve is ITMY, BSC-ISI control on
- Brown curve is ETMY, BSC-ISI control on   


The data can be found in the DTT file seismic/BSC-ISI/H2/ETMY/Data/Spectra/Isolated/ETMY

Contol off: UTC time 23:52:36, 15 averages, df=50mHz
Contol on:  UTC time 23:45:51, 15 averages, df=50mHz



---------------------------------------------------------------------------

For our records, I am posting the details of what was done to implement this on ETMY:


1) Damping Loops

Our Damping loops were DC coupled. A DC offset was visible when turning the loops on. I added:
- two zeros at DC
- two poles at 25 mhZ: pair(0.025,65)

To do that:
- I modified the cutoff filters in Step_5_Damping_Loops_ST2_LHO_ISI_BSC6.m
- Run Step_6_Damping_Loops_ST1_LHO_ISI_BSC6.m
- Run Step_7_C2D_Damping_Filters_LHO_ISI_BSC6.m
- Updated the foton file


2) Output Filters

Installed the new output filters, which includes the low pass at high frequency to limit the "glitches" when the control is turned ON.

For that:
- Run aLIGO_BSC_ISI_Output_Filters.m
- Run aLIGO_BSC_ISI_Filters_Digitalization.m
- Updated the foton file


3) Blend Filters

- Created the following folders:
/ligo/svncommon/SeiSVN/seismic/BSC-ISI/H2/ETMY/Scripts/Complementary_Filters
/ligo/svncommon/SeiSVN/seismic/BSC-ISI/H2/ETMY/Filters/Complementary

- In Complementary_Filters, copied the ITMY complementary filters file:

Complementary_Filters_Stage12_750mHz_2012_07_25.m
Complementary_Filters_Stage12_250mHz_2012_07_25.m
Complementary_Filters_Stage1_100mHz_2012_07_25.m

Run these three files that create the complementary filters, store them in .mat files saved in Filters/complementary.


4) Control_Scripts

Step_8_Blend_Filters_LHO_ISI_BSC6.m:
- Modified Step_8 to load the good complementary filters
- line 41 and 42 modified the blend_frequency value and index (commented the changes in the m file)


Step_9_C2D_Blend_Filters_LHO_ISI_BSC6.m:
- added teh continuous/digital filters comparison
- modified it to generate the filters necessary to make the blend switching work (T240 and NXT)

Run Step 8 and Step 9 for each of the three blend filters
Updated the foton file

Committed the changes to the svn

 
Non-image files attached to this report
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
H2 SUS
jeffrey.kissel@LIGO.ORG - posted 16:56, Thursday 26 July 2012 (3613)
H2 SUS ITMY Oplev Signals re-ordered
Optical lever QPD's analog signals from each segment/quadrant come into the ADC in numerical order (1, 2, 3, 4) where the segments are defined as

   +-------+
   | 1 | 3 |  ^
   |---+---|  | This way up
   | 4 | 2 |  |
   +---+---+

(staring at the face of QPD, as though you were an incident laser beam). The QUAD MASTER model absorbs these signals as channels

$(IFO):SUS-$(OPTIC)_L3_OPLEV_SEG1
$(IFO):SUS-$(OPTIC)_L3_OPLEV_SEG2
$(IFO):SUS-$(OPTIC)_L3_OPLEV_SEG3
$(IFO):SUS-$(OPTIC)_L3_OPLEV_SEG4


However, up until this model change, the top level ITMY model had been re-ordering these signals as

Analog Signal    ADC Channel      SEG#
1                1_0              SEG2
2                1_1              SEG1
3                1_2              SEG4
4                1_3              SEG3


I have now re-ordered them in a sane fashion, as the ETMY had already been ordered:

Analog Signal    ADC Channel      SEG#
1                1_0              SEG1
2                1_1              SEG2
3                1_2              SEG3
4                1_3              SEG4


The updated model,
${userapps}/release/sus/h2/models/h1susitmy.mdl
has been committed to the repo, and I've recompiled, reinstalled, restarted, and restored H2SUSITMY.
X1 SEI
hugo.paris@LIGO.ORG - posted 12:05, Thursday 26 July 2012 (3610)
HAM-ISI Unit #6 - Assembly Validation Complete

The Assembly Validation testing of HAM-ISI Unit #6 is complete. HAM-ISI Unit #6 - Assembly Validation report was posted under the DCC, and validated. We can now store this Unit in a container.

HAM-ISI Unit #7 will be the last HAM-ISI built at LHO. Assembly is approching completion. Assembly Validation testing will follow.

Reports regading the Assembly validation of previous units at LHO are available in the DCC:
HAM-ISI Unit #1 - Assembly Validation
HAM-ISI Unit #2 - Assembly Validation
HAM-ISI Unit #3 - Assembly Validation
HAM-ISI Unit #4 - Assembly Validation
HAM-ISI Unit #5 - Assembly Validation

Reports regading the Chamber Side testing of other units at LHO are available in the DCC:
HAM2 (HAM-ISI Unit #4) - Chamber Side Testing
HAM3 (HAM-ISI Unit #5) - Chamber Side testing
H1 SUS
betsy.weaver@LIGO.ORG - posted 11:31, Thursday 26 July 2012 - last comment - 14:13, Thursday 26 July 2012(3608)
MC2 Roll adjustment

This morning we adjusted the 0.4mm roll out of the MC2 lowest stage via rolling the optic in the sling.  We were able to take the roll error from 0.4mm on each side to 0.003mm error, well within the 0.25mm guideline.

We reset the M3 stage AOSEMs and are now back to running TFs of MC2.

Comments related to this report
betsy.weaver@LIGO.ORG - 11:43, Thursday 26 July 2012 (3609)

July 24, 2012 Norna's email exchange of roll tolerance requirements:

Colleagues

I found the email exchange I had with Dave R about clocking, see below.

1.5 mrad corresponds to a height mismatch of ~ 0.2 mm (0.1 mm up on one side and 0.1 mm down on other, with 75 mm radius). This value was not a concern to him as you see. Betsy's 0.4 mm up on one side and down on other gives a clocking of ~ 5 mrad. So someone (Luke?) should check the Zemax to see if 5 mrad (for example)  is OK and then we should get a target value captured in a design requirement doc.

However Matt's practical advice and experience of getting it to 0.25mm sounds good for now.

Norna

betsy.weaver@LIGO.ORG - 14:13, Thursday 26 July 2012 (3611)

TFs from before the roll fix showed some small cross-coupling between T and L.  We fixed the roll of the optic and the modes are now degenerate as expected.   Plots and more details coming.

H1 CDS
jeffrey.kissel@LIGO.ORG - posted 11:24, Thursday 26 July 2012 (3607)
Updated SUS corner of H1 userapps repo
For the record, I've done the following:

  ~ $ cd /opt/rtcds/userapps/release/sus/
sus $ svn up

The "common" folder was what I was specifically looking to make sure was up to date (and now the folder has all the new quad changes, as well as the CD_STATE_MACHINE updates), but the update also received a whole bunch of (other) site specific stuff.
LHO VE
john.worden@LIGO.ORG - posted 10:50, Thursday 26 July 2012 (3606)
GV16 Annulus ion pump

 We received a text message from the alarm handler this morning regarding a signal associated with GV16 at the XMID station. After reviewing the signal in question we realized that this signal had fallen to zero on July 20 from a nominal 1ma  (scale of 1-10 mA)

This looks like the normal failure mode of the annulus ion pump power supply and will be investigated and hopefully repaired (depending on replacement parts) next week.

Signal is HVE-MX:GV16_II339

X1 SUS
james.batch@LIGO.ORG - posted 09:08, Thursday 26 July 2012 (3605)
Tripleteststand survived the night
The tripleteststand had the One-stop cable and cards (between the computer and the I/O chassis) replaced yesterday in an effort to solve the mystery of the models freezing and the cards in the I/O chassis becoming invisible.  The x1sushxts27 model was started Wednesday 7/25 at 14:06 PDT and is still running this morning.  
LHO VE
john.worden@LIGO.ORG - posted 08:21, Thursday 26 July 2012 (3604)
END X vented

The END X volume was vented yesterday so work may proceed at BSC9. During turbo pump startup we found that the QDP80 was rotating the wrong way. This was corrected and the turbo was spun up as a precaution.

LHO VE
john.worden@LIGO.ORG - posted 08:18, Thursday 26 July 2012 (3603)
Vertex volume pumping down.

I started pumping the LVEA vertex volume yesterday.  Roughing was paused overnight and will continue today. Pressure is currently 60  torr.

H2 ISC
bram.slagmolen@LIGO.ORG - posted 23:54, Wednesday 25 July 2012 (3601)
PLL servo

We looked into the PLL servo. First we checked the temperature feedback signals to the laser. They did seem ok, although the green had a 1mV offset (although not being written to it). We disconnected the green temp feedback.

The IR laser crystal temperature feedback was ok, but only after we managed to reset it to zero. Even the EPICS display was not showing all the digits (we got an intergrator gain of 1e-6). The EPICS screen displays voltage, which is good to know.

We had to adjust the temprature on the laser to find the beatnote, it was set back to 42.1 deg C. The knob on the front panel is very 'coarse', so the beatnote was within 10 MHz from the nominal 39.7 MHz. We engaged the temperature servo and we saw the beatnote move towards the 39.7 MHz. The Phase-Frequency Discriminator has a flat gain when the beatnote is far away from the LO frequency (39.7 MHz). Although not a problem, with low gain you do wait for it:) You can speed it up by engaging the CMB-A servo, which feedback to the PZT. Matter of fact, the temp signal is a plain copy of the PZT signal, which goes through the Beckhoff system and has it sown little servo.

We looked on an oscilloscope at the temperature feedback signal. There are a few ripples in the signal at ~1 micro second, ~5 microseconds and ~2 milli seconds. I think we should add an analog 10 Hz low pass filter at the output to remove these. The temperature feedback has a bandwidth of up ~0.5 Hz anyway.

Looking at the PZT feedback signal. It has ~1.5Vpp 'oscillations' with a ~10s period appearing and then fading away. This is of course the 'equivalent' noise the laser tries to follow. The PZT frequency to volts conversion is ~3 MHz/V, so that indicates that the laser frequency fluctuates by ~4.5 MHz!

Looking a the I-mon from the Phase-Freq Discriminator it is flat when locked (and around the 39.7 MHz). When further away the signal looks like 'pulse-widht-modulated' with an average voltage which correspond to how far away the beatnote is and is expected. I don't know how far the beatnote needs to drift, at which point the frequency discriminator takes over from the phase discriminator. All-in-all the I-mon doesn't seem to be bad or noisy.

H2 ISC
bram.slagmolen@LIGO.ORG - posted 19:30, Wednesday 25 July 2012 - last comment - 23:58, Wednesday 25 July 2012(3598)
Cavity lock with large VCO drift

We looked into the PLL which seemed to be ok (see other entry 3601). We didn't pay much attention to the RefCav yet, as we want to to make the cavity lock again. To make this happen we had to reset the ETMY HEPI, lucky Fabrice was here to help. The output on ISC BLEND_RZ was off. All is well.

We have fringes again, and the REFL_PWR_MON seems to be at its previous healthy ~11000 counts level. When engaging the cavity locking (CMB-B), it seemed to be ok until is starts the oscillation at 10-20 sec period. I turned the first boost filter off which didn't seem to help much. The VCO frequency drifts upto 39.78 MHz (from 39.603 MHz nominal). It almost looks like there is a sign wrong, it locks, fluctuates around 0 then creeps to the -10V limit. When you look at the VCO frequency it keep slowly climbing. At the same time the cavity power drops. Hmm, maybe still something in the PLL servo is not right.

We have two new indicator on the OAT screen, 'RefCav Trans (V)' and 'Beatnote at (Hz)'. The first one is nominal at 1.1 V (has a green box when above 0.8V, and a red box when <0.4V), and indicates if the RefCav is locked. The Beatnote shows the VCO frequency in Hz, nominal at 39.603 MHz.

I left the cavity unlocked, but the PLL engaged.

A good .snap time is Wed July 25 2012, 20:00h (and half hour from now).

Comments related to this report
bram.slagmolen@LIGO.ORG - 23:58, Wednesday 25 July 2012 (3602)

Could the 'pulse-width-modulation' effect (lack of a better discribtion), and the drift of the beatnote away from the LO, be the reason that the laser is behaving strange?

H2 PEM
bram.slagmolen@LIGO.ORG - posted 19:11, Wednesday 25 July 2012 (3600)
Dust monitor alarm

The H2 dust monitor alarm went off. Not sure what button to press, so I pressed silince for one hour ...

H1 AOS
thomas.vo@LIGO.ORG - posted 15:07, Monday 23 July 2012 - last comment - 08:50, Thursday 26 July 2012(3543)
H2 ETMY Optical Lever Calibration
I have taken the calibration data and analyzed it. The plot of the linear response curve is attached.

I used a polynomial fitting program in python to get these numbers.  This should give you the conversion from volts to micro-radians.

           Slope            Y-intercept
Pitch   [  1.01902201e+06   8.42886118e+00]
Yaw     [  9.83122943e+05  -1.19329010e+01]
Comments related to this report
thomas.vo@LIGO.ORG - 19:11, Monday 23 July 2012 (3550)
Please hold off on using these calibration parameters, it looks like the SUS readout channels that map out the quadrants on ETMY and ITMY were not correct and I will need to re-calculate if this is true. Updates soon to come.
thomas.vo@LIGO.ORG - 14:25, Tuesday 24 July 2012 (3564)
The QPD mapping did prove to be different than what was previously shown on the MEDM screens.

Here are the new values for the linear response curve. The units are micro-radians/volts. The lever arm is taken to be 6 meters still 

Pitch [ 1727.67131855    23.41350328]
Yaw   [ 1666.80728788   -33.14694715]


It is relevant to address that a positive pitch on the ETMY quad suspension MEDM on the m0 stage will yield a higher intensity on the two lower quadrants of the optical lever QPD, giving a negative pitch as viewed facing the QPD. 
Also, a positive yaw in the quad suspension MEDM will yield a higher intensity on the two left quadrants of the optical lever QPD, giving a negative yaw as viewed facing the QPD. For alignment purposes this will be important to note.  

The next step is to take measurements over the course of at least 2-6 hours and measure the drift as a function of time.
Images attached to this comment
thomas.vo@LIGO.ORG - 08:50, Thursday 26 July 2012 (3588)
I copy and pasted wrongly into the screen the pitch and yaw are reversed, this is signal(1/m) vs translation(micro-radians) which gives units of micro-radians*meters.
       Slope              Y-intercept
Pitch [1666.80728788   -33.14694715]
Yaw   1727.67131855    23.41350328]

Apologies
Images attached to this comment
X1 SEI
hugo.paris@LIGO.ORG - posted 11:59, Monday 09 July 2012 - last comment - 14:54, Thursday 26 July 2012(3370)
HAM-ISI Unit #6 - CPS readout drifting

HAM-ISI Unit #6 was balanced, and CPS readouts were within acceptable range, on 07/03 when we left it for long TF measurments. When checked this morning, CPS readouts featured an offset of approximately +/-3000 counts:

 

   

    07/03

    07/09

    Difference

    H1

    -387.82

    2014.8

    2402.62

    H2

    -15.363

    2259.8

    2275.163

    H3

    291.12

    2534.3

    2243.18

    V1

    -80.917

    -3112.1

    -3031.183

    V2

    -38.773

    -3118.5

    -3079.727

    V3

    119.34

    -3054.5

    -3173.84

 

There is no drive/offset on MEDM channels.

Coil drivers were turned off. The CPS readouts remained unchanged.

CPS interface chassis were turned off, and then turned back on. The CPS readouts remained unchanged.

 

Dataviewer plots are attached. They show the drifting of the CPS readouts.

 

We experienced high temperatures over the last few days.

       2259.8       17.137
       2534.3       20.602
      -3112.1       26.775
      -3118.5       20.225
      -3054.5       31.743

 

      -387.82       15.522
      -15.363       16.733
       291.12       24.948
      -80.917       24.324
      -38.773       18.063
       119.34       25.563
      -387.82       15.522
      -15.363       16.733
       291.12       24.948
      -80.917       24.324
      -38.773       18.063
       119.34       25.563
3-Jul 9-Jul Difference
H1 -387.82 2014.8 2402.62
H2 -15.363 2259.8 2275.163
H3 291.12 2534.3 2243.18
V1 -80.917 -3112.1 -3031.183
V2 -38.773 -3118.5 -3079.727
V3 119.34 -3054.5 -3173.84
3-Jul 9-Jul Difference
H1 -387.82 2014.8 2402.62
H2 -15.363 2259.8 2275.163
H3 291.12 2534.3 2243.18
V1 -80.917 -3112.1 -3031.183
V2 -38.773 -3118.5 -3079.727
V3 119.34 -3054.5 -3173.84
Non-image files attached to this report
Comments related to this report
hugo.paris@LIGO.ORG - 13:04, Monday 09 July 2012 (3371)

The ISI was re-blanced this morning. Reasonable values were obtained along Z. 

However, re-balancing the ISI did not correct the out-of-specification offset observed on horizontal CPSs.

CPS readouts, after re-balancing this morning, are presented below:

H1 1901.6
H2 2268.7
H3 2417
V1 -34.45
V2 47.896
V3 -201.18
hugo.paris@LIGO.ORG - 17:51, Monday 09 July 2012 (3375)

In order to get a better understanding of what was happening, we collected data from GS13/L4C pressure sensors. Data shows:

  • Pressure increased for the past 4 days (+3 kPa, fig, 1). Pressure data is well correlated between sensors.
  • CPS readout drifting is highly correlated to pressure variations. (Fig. 2) 
  • Pressure is still high: 103-4kPa (Fig. 3, just measured)
  • Figure 4 shows the pressure/CPS-readout evolution over 2 days. From 7am to 7am.

Notes

  • Dataviewer time = PT+7h
  • Mean values displayed. Fluctuations due to runnning excitations.
Non-image files attached to this comment
hugo.paris@LIGO.ORG - 15:04, Tuesday 10 July 2012 (3390)

The ISI was locked. CPS readouts are within expected range. 

H1 -348.96
H2 297.36
H3 -156.01
V1 252.29
V2 155.3
V3 323.62

The drifting we observed was not caused by a malfunctioning of the CPSs.

john.worden@LIGO.ORG - 14:54, Thursday 26 July 2012 (3612)

We later found that one circuit of our air conditioning had failed and therefore we could not maintain normal conditions in the staging building. There is no record of the indoor temperatures during this event  but I estimate that the temperature excursions were on the order of 5-10 degrees F. Normal excursions (night-day) are probably 2-3F and perhaps closer to 1F during the day only (if you exclude the cooling overnight.

Displaying reports 73861-73880 of 77380.Go to page Start 3690 3691 3692 3693 3694 3695 3696 3697 3698 End