Displaying reports 69241-69260 of 83146.Go to page Start 3459 3460 3461 3462 3463 3464 3465 3466 3467 End
Reports until 18:30, Friday 03 October 2014
H1 ISC
sheila.dwyer@LIGO.ORG - posted 18:30, Friday 03 October 2014 - last comment - 19:16, Friday 03 October 2014(14296)
IR WFS Y-arm alignment

Alexa, Sheila, Gabriele

 

We closed the servo  loops for the relf wfs IR  y-arm centering. The error signals are fed back to the test masses as follows:

  Pitch Error Sig Pitch Gain Yaw Error Sig Yaw Gain Filter Bank
ETMY RELF_B_RF9_I -0.001 RELF_B_RF9_I 0.005 DHARD
ITMY REFL_A_RF9_I -0.001 REFL_A_RF9_I -0.003 DSOFT

The DC centering must be on; these were unchanged. I have also taken a screen shot just in case (the input/output matrices are the same for pitch and yaw).

Images attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 19:16, Friday 03 October 2014 (14297)

I wrote a python script that implements the same angular loops, but actuating directly on the alignment offsets. In this way it is not necessary to offload the servo output at the end of the alignment. The loops operates only if the arm transmitted power is above a threshold. They continue to operate as long as the error signals are larger than another threshold value. The check on the error signal is perfomed with a running average, to smooth their noise. All parameters are set at the beginning of the script.

As shown in the attached figure, the loops are working well. Maybe the gains are still a bit low.

To ease the implementation of this alignment techniques into the guardians, I'm not using anymore the threaded trigservo loops as at Livingston, since it was not clear to me how to terminate the threads from inside the guardian. Now everything is local to the main thread. The script is attached. It should be easily configurable to any other configuration and number of degrees of freedom

Images attached to this comment
Non-image files attached to this comment
H1 SUS (AOS, DetChar, ISC, SEI)
jeffrey.kissel@LIGO.ORG - posted 16:50, Friday 03 October 2014 (14265)
Refining ITMX and ITMY Alignment Slider Calibration
J. Kissel, J. Driggers

There's been some confusion about why the ITM ISIs are performing so differently. This resurrected memories of mistrust in the optical lever calibration, that I'd talked to Thomas about in June (see LHO aLOG 12216). That aLOG leaves it at "we should confirm the calibrations once we have arms again." The idea will be to cross-check the calibration  using the alignment sliders, which can be precised calibrated using the green beam and baffle PDs as a 4 [km] optical lever. The details of the process are below, but in summary, the refined calibration of the sliders is
IX P = 15.589 [ct/urad]
IX Y = 43.835 [ct/urad]
IY P = 19.920 [ct/urad]
IY Y = 46.700 [ct/urad]
which, for IX P is a ~50% correction, but the rest is a ~10-20% correction.

We have updated both the OPTICALIGN [ct/urad] gains, and corrected the "cal" [ct/urad] FM0 in the M0 LOCK P and Y filter banks, saved the newly corrected alignment offsets, and confirmed that the refinement of gain and slider value brings the optic to the same place.

DETIALS
------------

Currently, the alignment slider calibration gains are
P  23.219 [ct/"urad"]
Y  51.689 [ct/"urad"]
based on dead-reckoned knowledge of the actuation chain (see LHO aLOG 4730).

Keita, Alexa, and Shiela recently went through the exercise of finding the green beam down the arms (see LHO aLOG 14201 for ITMX, and LHO aLOG 14161 for ITMY) using baffle PDs and the SUS alignment sliders. 

From these aLOGs, we know that the ETMY baffle PDs, and ETMX ERM Pattern are at the following ITM alignment slider values:
                 P ["urad"]     Y ["urad"]
ETMX Top Stop     65.2     
ETMX Bot Stop     84.2
ETMX Lef Stop               -20.2
ETMX Rig Stop                3.8
ETMY PD1          165      -105.3
ETMY PD4          197       -139
for displacement claimed by the sliders of
      delta ["urad"]
EX P   -19 * 2 = -38
EX Y   -24 * 2 = -48
EY P   -32 * 2 = -64
EY Y   33.7* 2 = 67.4 
where the factor of 2 comes from the single bounce, optical lever effect.

From an older aLOG when Keita had performed a similar calibration (see attachment to 9087), we know the ETMX baffle PDs are a distance 11.76 [inches] = 0.2987 [m] apart in vertical, and 11.77 [inches] = 0.29895 [m] in horizontal. From D0900949, we know the pattern has an inner-most diameter of 226 [mm] = 0.226 [m]. The length of the arms is 3994.5 [m], confirmed by older measurements during the HIFO days (see LHO aLOG 9635 and 11611).
That means the physical displacements are
EX P   0.226 [m] / 3994.5 [m] = 56.6 [urad]
EX Y   0.226 [m] / 3994.5 [m] = 56.6 [urad]
EX P   0.298 [m] / 3994.5 [m] = 74.6 [urad]
EX Y   0.298 [m] / 3994.5 [m] = 74.6 [urad]

Hence the slider gains should be corrected by
IX P   56.6 / 38   = 1.49 [urad / "urad"]
IX Y   56.6 / 48   = 1.18 [urad / "urad"]
IY P   74.6 / 64   = 1.17 [urad / "urad"]
IY Y   74.6 / 67.4 = 1.11 [urad / "urad"]
or
IX P  0.67138 ["urad"/urad]
IX Y  0.84806 ["urad"/urad] 
IY P  0.85791 ["urad"/urad]
IY Y  0.90349 ["urad"/urad]



The new slider gains are therefore
IX P   23.219 [ct/"urad"] * 0.67139 ["urad"/urad] = 15.589 [ct/urad]
IX Y   51.689 [ct/"urad"] * 0.84806 ["urad"/urad] = 43.835 [ct/urad]
IY P   23.219 [ct/"urad"] * 0.85791 ["urad"/urad] = 19.920 [ct/urad]
IY Y   51.689 [ct/"urad"] * 0.90349 ["urad"/urad] = 46.700 [ct/urad]

Which means the former alignment values, in ["urad"],
                     P               Y
IX Aligned         75.4            -7.6
IX Misaligned        0            -52.75
IY Aligned         182.4          -116.6
IY Misaligned        0               0
now become (["urad"] slider value * [urad/"urad"] = [urad] slider value)

                      P            Y
IX Aligned         112.35       -8.968
IX Misaligned        0         -62.245
IY Aligned         213.41     -129.43
IY Misaligned        0           0   

We have updated both the OPTICALIGN [ct/urad] gains, and corrected the "cal" [ct/urad] FM0 in the M0 LOCK P and Y filter banks, saved the newly corrected alignment offsets, and confirmed that the refinement of gain and slider value brings the optic to the same place.
H1 TCS (TCS)
greg.grabeel@LIGO.ORG - posted 16:47, Friday 03 October 2014 (14295)
HWS Light Pipes Attached
After it was decided that the existing design for the TCS HWS table light pipes was insufficient to protect the vacuum envelope we decided to use what everyone else uses, some 10" self sealing flanges and the lexan viewport assemblies. Anyhoo, the commissioners should be happy I won't need to be thumping around on HAM4 any longer.
Images attached to this report
H1 TCS (TCS)
greg.grabeel@LIGO.ORG - posted 16:22, Friday 03 October 2014 (14294)
TCS ITMy Rotation stage fixed?
The rotation stage on ITMy had become unresponsive last week after some cable dressing was done. Restarting Beckhoff had proven ineffective and Fil was unable to find any lose cables. Unplugging and replugging the interlock bypass on the D1300131 box. This possibly had the effect of resetting the relay that blocks communication to the relay stage. Whatever happened the rotation stage is working again.
LHO General
patrick.thomas@LIGO.ORG - posted 16:05, Friday 03 October 2014 (14293)
Ops Summary
Andres covered from 10:00 - 11:00. Thank you Andres.

09:15 Betsy to LVEA West bay to work on 3IFO SUS
10:43 Aaron pulling cables between HAM1 and the PSL closet
11:17 Kiwamu to end Y to align optics on the ISCT table
11:56 Corey walking around IMC for ~ 5 minutes
12:00 Chris to end X to check on moth situation
12:04 Aaron pulling cables over HAM1 and HAM2
12:36 Sheila, Kiwamu at end Y
12:40 Aaron done pulling cables over HAM1 and HAM2
12:44 Chris back from end X
14:08 Andres to TMSX lab to look for parts
14:42 Andres back from TMSX lab
H1 PSL
gabriele.vajente@LIGO.ORG - posted 15:08, Friday 03 October 2014 (14291)
Status of the ISS second loop

Peter K, Gabriele

Loop performance, excess sensing noise

As reported yesterday, the second loop servo didn't have enough gain, so this morning we modified one switchable stage of the board to include a x10 gain. Unfortunately, that stage is an inverting one, so we can't really switch it on and off with the ISS second loop closed. This stage is controlled by H1:PSL-ISS_SECONDLOOP_ADD_GAIN.

Using everything we have in the board (maximum gain at +40dB, x10 stage, integrator and boost) we could engage the second loop and get the performance shown in the first attached plot. The red and blue traces are the in-loop and out-of-loop signals, calibrated in RIN, when the second loop is open. The green and maroon traces are again the same signals, with the loop engaged with maximum gain. The cyan and magenta traces correspond to the integrator and boost switched on. We're getting a bandwith of about 1 kHz.

We can see that the out-of-loop signal shows an excess of noise with respect to the in-loop signal, up to about 60 Hz. The out-of-loop RIN is about 1e-6 at 10 Hz and 2e-7 at 60-70 Hz. We can conclude that our ISS second loop photodiodes are limited by sensing noise of some kind at this level.

The second plot shows a comparison of the error signals (sum of photodiodes 1-4 and sum of photodiodes 5-8) with one or the other in loop. The performance is very similar in the two cases, so the amouint of excess sensing noise is about the same in both sets of sensors.

The last plot shows that there is some coherence between the out-of-loop signal and the ISS QPDs. This is true at least at low frequency, below 10 Hz. The QPD signals show a structure at ~18 Hz which is very similar to the one visible in the out-of-loop signal, altough there is no coherence. It might be due to a highly non stationary coupling, but we're not sure of that. So it is likely that at least some of the excess sensing noise is due to beam jitter to intensity noise coupling at the ISS array. to imrpove this, we should try to move the beam using the picomotors and looking at the out-of-loop signal noise in the 10-60 Hz region.

How to switch on the ISS second loop

The medm screen of the second loop is wrong, in the sense that the buttons are connected to the wrong switches. I created a new screen for the second loop, which for the moment is living in /ligo/home/controls/gabriele/SecondLoop.adl. Once finalized, we should move it to the right place.

  1. Switch off the connection between second loop and first loop (H1:PSL-ISS_SECONDLOOP_CLOSED to low level)
  2. Ensure that the additional gain path is on (H1:PSL-ISS_SECONDLOOP_ADD_GAIN to high)
  3. Move the loop gain to 0 dB (H1:PSL-ISS_SECONDLOOP_GAIN)
  4. Engage the second loop servo (H1:PSL-ISS_SECONDLOOP_SERVO_ON to high) and tune the reference level (H1:PSL-ISS_SECONDLOOP_REF_SIGNAL_ANA) to move the sencond loop output signal (H1:PSL-ISS_SECONDLOOP_SIGNAL_OUTMON) as close as possible to zero. You won't be able to get zero, just ensure that it is oscillating with a rough zero mean. You might need to tune the reference signal at the mV level.
  5. Switch on the connection between second loop and first loop (H1:PSL-ISS_SECONDLOOP_CLOSED to high level). Some times this kicks the first loop out of lock, but usually it is able to recover withtin few seconds. Watch the diffracted power, since any small error in the reference signal for the second loop will have a large impact. You might have to retune the reference signal
  6. Increase the gain to the maximum (+40 dB) and engage boost (H1:PSL-ISS_SECONDLOOP_BOOST_ON) and integrator (H1:PSL-ISS_SECONDLOOP_INT_ON)

To do

  1. automate the whole switch on procedure, including th zeroing of the second loop output tuning the reference signal
  2. when the IMC drops lock, we should automatically switch off the ISS second loop
  3. try to move the beam into the array using the picomotors, to minimize the out-of-loop noise
Images attached to this report
H1 SUS
jeffrey.bartlett@LIGO.ORG - posted 14:54, Friday 03 October 2014 (14292)
Quad-09 Phase1b TFs
After fixing the not taking Damped TF problem and the channel list mismatch problem, we took a full set of transfer functions for 3IFO Quad-09. The results data are posted below and have been added to the SVN repository. There are a couple of anomalies in the data. 

(1). The last peak of the Damped M0 data in "Y", "R", and "L" are shifted up. 
(2). The R0 "Y" DOF appears to not be damped where as the other 5 DOFs are.  

Note: The staging building test stand hardware and software are somewhat down level to the H1 & L1 test stands.   
Non-image files attached to this report
H1 SEI
jim.warner@LIGO.ORG - posted 10:27, Friday 03 October 2014 (14288)
Re: ITMX troubles from yesterday

Yesterday, Fabrice and I transferred the Livingston blend filters from the ITMY ISI to all the other BSC's. When I went to turn on ITMX, the ISI starting ringing up dramatically when I tried to engage the horizontal loops. Because we had to transfer the filters by hand, I immediately suspected I had screwed up a filter somewhere. I compared the blends between ITMY and ITMX, and found no difference. I did a diff between the a couple of archived foton files and the installed filters and found no differences beyond what I had to do to install the filters (i.e. no changes in any filters other than the blend filters I installed). When I started a rolling DTT spectra of the isolation loops (the ISO outs), I found that there was an instability in the Y isolation loop at 730 hz. When I looked at the filters I designedin matlab, I saw that there was indeed feature there, but I had sufficiently suppressed the feature. When I took an open loop measurement of the plant, however, the feature had evolved and was now a magnitued of 3 higher. I also found, looking at the foton digital filter, that there was again mismatch at 730 hz of about a factor of 5. At the time Fabrice and I decided that there must have been a change in the plant, added a notch and moved on.

This morning with, Jeff's help, we've found a few more interesting details:

        1. the foton filter does not agree with my matlab design (foton is in the first png, matlab design is my second figure). Up to about 400 hz, they agree well enough, but I have 2 high frequency notches that are not in the same place in foton. The notch I put at 730 hz has been shifted down to more like 660 hz.

         2. Looking more closely at the plant measurement I took on the 16th and the DTT measurement yesterday, we have less gain margin at high frequency than we thought we did. The comparison is show in my third plot(pdf), provided by JeffK. The green line is the measurement used in matlab, blue is the DTT measurement from yesterday. The difference is explained by a downsampling filter between the DQ channels we used to measure matlab tfs and the higher data rate channels we measured in DTT, shown on the bottom of Jeff's plot.

Images attached to this report
Non-image files attached to this report
H1 PSL (PSL)
peter.king@LIGO.ORG - posted 09:34, Friday 03 October 2014 (14287)
laser shutter closed
Whilst inserting/removing the second loop power stabilisation servo card, the laser shutter closed with
EPICSALARM highlighted on the PSL Beckhoff computer.  I reset the shutter and flow sensors from the
control room and opened the shutter (from the diode room).  Laser and servos came back by the time I
made it back to the control room.
LHO General
patrick.thomas@LIGO.ORG - posted 09:01, Friday 03 October 2014 (14286)
Morning meeting notes
SEI: TBD

SUS:
optical lever calibration
DRMI commissioning

Test stand:
review transfer functions
TMS builds

PSL:
modifications to 2nd loop ISS board

Commissioning:
DRMI
AS WFS
IR arm locking

CDS:
Running fibers
TCS X arm rotation stage
H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 08:26, Friday 03 October 2014 (14285)
CDS model and DAQ restart report, Thursday 2nd October 2014

model restarts logged for Thu 02/Oct/2014
2014_10_02 09:29 h1isibs
2014_10_02 09:33 h1hpiitmx
2014_10_02 09:33 h1hpiitmy
2014_10_02 09:35 h1isiitmy
2014_10_02 09:36 h1isiitmx
2014_10_02 09:42 h1hpibs
2014_10_02 09:44 h1isibs
2014_10_02 09:46 h1hpibs
2014_10_02 10:03 h1hpiham6
2014_10_02 10:03 h1isiham6
2014_10_02 10:10 h1hpiham1
2014_10_02 10:14 h1hpiham5
2014_10_02 10:14 h1isiham5
2014_10_02 10:16 h1hpiham2
2014_10_02 10:18 h1isiham2
2014_10_02 10:20 h1hpiham4
2014_10_02 10:20 h1isiham4
2014_10_02 10:27 h1isiham3
2014_10_02 10:29 h1hpiham3

2014_10_02 10:43 h1dc0
2014_10_02 10:45 h1broadcast0
2014_10_02 10:45 h1fw0
2014_10_02 10:45 h1fw1
2014_10_02 10:45 h1nds0
2014_10_02 10:45 h1nds1

2014_10_02 10:48 h1hpiham1
2014_10_02 11:53 h1ioppemmy
2014_10_02 11:53 h1pemmy

2014_10_02 11:53 h1sushtts
2014_10_02 16:38 h1pslfss
2014_10_02 16:55 h1psliss

2014_10_02 16:59 h1broadcast0
2014_10_02 16:59 h1dc0
2014_10_02 16:59 h1fw0
2014_10_02 16:59 h1fw1
2014_10_02 16:59 h1nds0
2014_10_02 16:59 h1nds1

2014_10_02 17:02 h1psliss

no unexpected restarts. Seismic and PSL model changes, with associated DAQ restarts. Recovery of h1pemmy after IO Chassis power supply swap.

H1 SEI
fabrice.matichard@LIGO.ORG - posted 19:50, Thursday 02 October 2014 (14284)
SEI Status

SEI Status:

- Motion measured on ITMY (ISI and optical lever) using the LLO configuration was good again last night, so we duplicated this configuration to all the BSC-ISI units

- As we re-started the units, Jim found an oscilation in ITMX. He fixed it. It is not correlated with the new blend configuration. More details on that to follow.

- Hugh worked on the Guardian. It is now fully updated to account for the new config (decribed below). Thanks a lot to Jamie for the remote support. The Guardian is now fully updated and running.

- All the units are up and running. We leave the sensor correction OFF for the night.

 

Configuration in use:

- LLO blends installed everywhere (excact same filters copied/pasted from the filter text file)

- Stage 1 RZ off on all units

- Only Stage 1 X and Y isolated on Stage 2 (all units except the BS)

- Stage 2 damped only on the BS

- Sensor correction is off for the night

 

 

H1 ISC
sheila.dwyer@LIGO.ORG - posted 19:19, Thursday 02 October 2014 (14283)
work today

Other than this we have been disrupted by ITMX this evening. 

Images attached to this report
H1 SUS
sheila.dwyer@LIGO.ORG - posted 17:12, Thursday 02 October 2014 (14282)
changes to h1sushtts model

Jenne, Alexa, Sheila

Since the asc had IPC senders for signals to OM1 and OM2, but the only revciever in the h1sushtts model were from the OMC model, we added new recievers.  Anamaria told us where to find the livingston model, and confirmed that it was up to date, so we copied what they had done there, just summing the inputs from the OMC model and ASC. 

Complied, installed, seems to be working, and we can now use the DC signals from our AS WFS for a centering servo.

H1 PSL
gabriele.vajente@LIGO.ORG - posted 17:10, Thursday 02 October 2014 (14281)
ISS second loop closed

Peter K, Gabriele

In brief, we finally managed to close the ISS second loop. The attached plot compares the intensity noise measured on the second loop photodiodes in different configurations: second loop open (green and maroon), loop closed withe the additional integrator (red and blue), loop closed with the additional boost (cyan and magenta).

Clearly, the boost doesn't do a very good job. With the integrator on, we get a loop bandwidth of the order of 200 Hz, and a gain at 10 Hz of something like 10-15.  We don't have enough gain to cope with our present large power noise after the IMC.

Procedure to engage the second ISS loop

  1. All switches should be low (H1:PSL-ISS_SECONDLOOP_CLOSED, H1:PSL-ISS_SECONDLOOP_SERVO_ON, H1:PSL-ISS_SECONDLOOP_BOOST_ON, H1:PSL-ISS_SECONDLOOP_INT_ON)
  2. Move the second loop gain to the minimum (H1:PSL-ISS_SECONDLOOP_GAIN to 0)
  3. Switch on the second loop (H1:PSL-ISS_SECONDLOOP_SERVO_ON to high)
  4. Adjust the reference input H1:PSL-ISS_SECONDLOOP_REF_SIGNAL_ANA to move the output of the second loop as close as possible to zero (check H1:PSL-ISS_SECONDLOOP_SIGNAL_OUTMON)
  5. Switch on the additive path in the ISS inner loop (H1:PSL-ISS_SECONDLOOP_CLOSED to high)
  6. Increase the gain to maximum (H1:PSL-ISS_SECONDLOOP_GAIN to 40)
  7. Engage the integrator (H1:PSL-ISS_SECONDLOOP_INT_ON to high)

Some details

The input signals to the second loop servo board (the two sums of photodiodes) were not behaving correclty: they appeared to be choppen at the zero level, meaning that only the positive (or negative) part of the signal was present. We traced dow the problem to the OP27 which is used in the output stage of the transimpedance box. This OP27 was used to create a single ended monitoring of the box output, which was sent to the front panel and not used. For some reason we don't understand yet, this opamp was creating the problem. We removed it from the two boards and the sum output is now good.

We also modified the ISS model to wire in the two additional switches ADD_GAIN and ADD_PD_58_SUM. We plan to modify  the additional gain module to get an additional factor of ten in the gain.

Images attached to this report
LHO VE
kyle.ryan@LIGO.ORG - posted 16:32, Thursday 02 October 2014 (14280)
Restarted IP5 with help of pump cart (has been off since July(?)) -> Valved-in IP5


			
			
H1 General
travis.sadecki@LIGO.ORG - posted 16:27, Thursday 02 October 2014 (14279)
Ops shift summary

8:45 SEI bootfest of all CS ISI and HEPI

9:04 Aaron to EY to retreive AA chassis

9:19 Jodi to MY

9:22 Betsy and Corey to LVEA on 3IFO cable hunt

9:29 Jodi back from MY molesting tiltmeter

9:55 Peter King and Gabriele to PSL looking at ISS

9:55 McCarthy to LVEA looking for tools

10:05 McCarthy out of LVEA

10:24 Jeff and Andres to EX

10:34 JeffK to LVEA testing seismometers

10:43 Framebuilder restarted

10:48 Betsy, Kyle, Bubba to LVEA crane fest

10:50 Cris to EX

11:11 Karen to EY

12:20 Craning in LVEA complete

14:02 Jason to realign ITMy OpLev

14:28 Jason out of LVEA

15:00 Rick and Sudarshan to EX to mount PCal camera housing

16:20 Robert to BTE between MY and EY

H1 AOS
fabrice.matichard@LIGO.ORG - posted 15:51, Thursday 02 October 2014 (14278)
ITMX Pitch excess motion

Commisioners have reported excess pitch motion in ITMX for the past few nights. The plot attached shows the Optical lever motion (Top left is ASD, bottom left is RMS) , and the ground motion (Top right is ASD, bottom right is RMS). Measurement are taken every morning at 1am on Sunday (Red), Monday (Blue), Tuesday (Green), Wednesday (Brown) and Thursday (Magenta).

 

The numbers below show that the pitch motion has varied by as much as a factor of 5 from one night to another, but it is not necessarily directly correlated with the amplitude of the ground motion (worst pitch motion was yesterday though the mircro-seism was not higher than during the previous nights).

 

- Optical Lever RMS motion at 100 mHz, Sunday through Thursday at 1 am PT:

18 nRad / 44nRad / 63nRad / 42nRad / 100 Rad

 

- Ground instruments RMS motion at 100 mHz in nm/s (must check the units, but it's fair to compare the day to day relative motion), Sunday through Thursday at 1 am PT:

113  / 106 /  197 / 189 / 140

 

- Ratio in nRad/(nm/s):

0.16   0.41   0.32  0.22   0.71

Images attached to this report
H1 SUS
betsy.weaver@LIGO.ORG - posted 14:24, Wednesday 01 October 2014 - last comment - 14:43, Friday 03 October 2014(14247)
QUAD comparison plot for interested parties

For those interested in looking closer at QUAD model parameters, attached are plots comparing all of the QUAD Main Chains when suspended with wires and also when suspended with fibers.   Note, if QUAD data is missing for one of these configurations it's because there was no clean data available.  Between the 2 plotted configurations, all 12 (H1, L1, and 3IFO) QUADs are represented.  Note, I tried to chose data sets that had the same or similar environmental conditions, but it was difficult due to the fact that some QUADs were reworked on test stands and some were reworked in chamber.  In all cases they were mounted on Solid Stack Test Stands or Locked ISIs and in-air.

 

Data is committed to the svn and can be found at:

/ligo/svncommon/SusSVN/sus/trunk/QUAD/Common/Data/

There does not seem to be a pattern in the data of the 2nd pitch mode peak which are clustered by a specific type of suspension (ETM vs ITM, or wire segment hang vs wire loop hang).

Non-image files attached to this report
Comments related to this report
betsy.weaver@LIGO.ORG - 14:30, Wednesday 01 October 2014 (14248)

And now with some cursors and in a second format for Brett.

Non-image files attached to this comment
betsy.weaver@LIGO.ORG - 15:31, Wednesday 01 October 2014 (14254)

As suggested, I looked at the stiffnesses of the Top Mass blades to see if there is a correlation with the second pitch mode frequency shifts.  I don't see it.  In order of the peaks on the P to P plot, starting with the lowest frequency to the highest the blade sets used in each QUAD are:

H1ETMx - SET 9  (~1.28Hz)

L1ETMy - SET 13

L1 ETMx - ?

L1ITMx - SET 14/15

L1ITMy - SET 12

Q8 ETM - SET 8

Q9 ETM - SET 2

Q6 ITM - SET 10 (~1.531 Hz)

 

The blade sets go in order of stiffness from highest to lowest, so SET 2 is stiffer than SET 15.  SET 14/15 is a mixed SET with blades still of adjascent stiffness.

brett.shapiro@LIGO.ORG - 16:27, Wednesday 01 October 2014 (14257)

I took the two wireloop quads that have the highest and lowest 2nd pitch mode frequencies and made a fit to them. These measurements and their respective made-to-fit models are shown in the attached plot. QUAD06 (H1 QUADTST) is the highest,  X1 ETMX is the lowest.

I previously did a fit for QUAD06, see log 14235. The fit for X1 ETMX was made simply by taking the QUAD06 fit and subtracting 3 mm from dn, which works quite well.

Since the outliers are 3 mm apart on dn, the other quads seem to have an even spread between those, and no correlation with spring stffness is evident, then a possible explanation is that our tolerance on positioning the top mass blade tip height is +-1.5 mm.

Non-image files attached to this comment
brett.shapiro@LIGO.ORG - 11:14, Thursday 02 October 2014 (14274)

Attached is a prediction of what +-1.5 mm on dn would look like for the fiber quads.

The black is a model of H1ETMY (which has been the default fiber model for some time) where dn=1.78 mm; blue is the same model but with dn=0 mm; red is again the same model but with dn = 3 mm. Some data is included as well. The H1ETMY measurement is in orange, which matches well because of the previous fitting of H1ETMY. In purple is H1ETMX. I think H1ETMX corresponds to the wireloop quad X1ETMX, which was the low outlier on dn for the wireloop configuration. In that configuration a dn of 0 mm worked quite well to the fit model to the data. Here the same 0 mm dn makes almost as good of a fit. There is not data matching the dn=3mm. +3 mm was found to work well for the high dn outlier wireloop QUAD06, which is not yet a fiber quad.

So it seems that for the existing fiber quads, +-1 mm on dn explains the spread well. However, the most recent 3rd IFO quads, still with wireloops, are the stiffest yet in pitch, so they would be expected to bring this to +-1.5 mm and line up with the dn=3mm red curve.

Non-image files attached to this comment
brett.shapiro@LIGO.ORG - 14:43, Friday 03 October 2014 (14290)

Posting some notes from recent email converstions looking into the large apparent shifts in dn (top mass blade tip height) and d2 in the all metal build (PUM wire loop prism).

Attachement PUMCOMDetails.pdf is from Eddie Sanchez and is a drawing showing that the position of the PUM wire loop break off in the all metal build is basically the same as where it should be in the final fiber build. However, the model fitting suggests the actual break off is about 1.8 mm lower. So Betsy took some photos of this prism on a suspended metal quad. See image files 1445.jpg to 1447.jpg. Since the prism is round, it could be the wire does not have a clean break off. The pictures seem to indicate the wire has a significant length of a line contact. The 1.8 mm shift could be within this line contact.

The last image, 1449.jpg, shows a picture of the top mass blade spring tip in a suspended top mass. The spring looks pretty well centered, not consistent at all with +3 mm of apparent shift in dn for this quad. Quoting some numbers from Betsy:

"The top surface of the blade, as close to the tip as possible, is supposed to be at 9.6mm down from the top of the bridge notch.  The notch is 14.6mm wide, the blade is 5mm wide, therefore the bottom of the blade should line up with the bottom notch.  No gauge blocks needed.  From the picture, this looks very close to lining up."

PUMCOMDetails.pdf
Images attached to this comment
Non-image files attached to this comment
H1 ISC
corey.gray@LIGO.ORG - posted 13:12, Monday 21 October 2013 - last comment - 10:55, Friday 03 October 2014(8196)
Final Two TMS QPD In-Vac Cables Connected To Chamber

After consulting with Keita and TMS group, we finalized where we wanted the QPD cables to go [we have to be EXTREMELY careful with cabling the QPDs because if the wrong cable is connected to these guys we run the risk of frying the QPDs---several QPDs were damaged during the H2 TMS Installation].  Basically, we stuck with what the drawing (D1300007) calls out.  But I made sure to clearly label the external flanges to where the QPDs are connected (see photo).

Below is the latest cable run-thru with Flanges noted:

In-Air Cable

Chamber 

feed-thru

In-vac cable Cable Bracket In-Vac Cable

Cable Bracket

on TMS

In-Vac Component
H1:SUS_BSC9_TMONX-1("SUS1") .....|E6-7C1|..... D1000225 s/n S1106816 CB3, 1st floor D1000234 s/n V2-96-903 --- OSEMS:  Face1, Face2, Face3, Left
H1:SUS_BSC9_TMONX-4("SUS2") .....|E6-7C2|..... D1000225 s/n S1106771 CB3, 2nd floor D1000234 s/n V2-88-934 --- OSEMS:  Right, Side, ---, ---
: In-Air cable not run yet : .....|E4-2C1|..... D1000924 s/n S1104104 CB6, 1st floor D1000568 s/n S1104110 CB-primary, 1st floor Green QPD (D1000231 s/nS1202413)
: In-Air cable not run yet : .....|E4-1C2|..... D1000924 s/n S1203963 CB6, 2nd floor D1000568 s/n S1202739 CB-primary, 2nd floor Red QPD (D1000231 s/nS1202411)
: In-Air cable not run yet : .....|E4-1C1|..... D1000223 s/n S1202653 CB5, 1st floor D1000921 s/n S1104112* CB-entry, 2nd floor Picomotors (D1000238 s/n S1105218)
: In-Air cable not run yet : .....|E4-2C2|..... D1000223 s/n S1202656 CB5, 2nd floor D1000921 s/n S1104113 CB-entry, 1st floor Beam Diverter (D1000237 s/n S1202724)

 

 

	
in-vac cable cable bracket in-vac cable in-vac component
H1:SUS_BSC9_TMONX-1("SUS1")
in-vac cable cable bracket in-vac cable in-vac component
H1:SUS_BSC9_TMONX-1("SUS1")

 

 

Images attached to this report
Comments related to this report
corey.gray@LIGO.ORG - 10:55, Friday 03 October 2014 (14289)

ICS Note:  D1000225 s/n S1106771 is not in ICS :-/

Displaying reports 69241-69260 of 83146.Go to page Start 3459 3460 3461 3462 3463 3464 3465 3466 3467 End