Displaying reports 67001-67020 of 77175.Go to page Start 3347 3348 3349 3350 3351 3352 3353 3354 3355 End
Reports until 22:17, Monday 03 March 2014
H1 ISC
keita.kawabe@LIGO.ORG - posted 22:17, Monday 03 March 2014 (10483)
Green WFS today (Alexa, Keita)

After Sheila and Alexa realigned the arm by hand (arm transmission ALS-C_TRX_LF_OUT about 700cts), we removed the dark offset of WFS demode output, confirned that RFAM is negligible by misaligning the ITM but aligning the ETM, then centered and engaged WFS, but it did not converge.

We had to refine alignment further (760 cts transmission), disable the PDH off-loading to the ETM (the length to angle coupling is large even at low DC),  recenter the WFS, engaged WFS, wait for a while, hold the WFS output, recenter the WFS, and it worked with all except one DOF (DOF2 PIT, which is the soft mode PIT).

For now the hard mode sensor for PIT and YAW are WFSB and WFSA, respectively, while the soft mode sensors for PIT and YAW are WFSB and WFSA. The WFSA and WFSB seem to be highly degenerate for PIT, and that's probably why it's very difficult to make both DOF1 and DOF2 PIT at the same time.

Anyway, after three DOFs are engaged the transmission went up to 860+ cts maximum. We left the arm with WFS on.

Note that it's still with very small bandwidth (basically just DC).

H1 AOS
yuta.michimura@LIGO.ORG - posted 21:33, Monday 03 March 2014 - last comment - 10:27, Tuesday 04 March 2014(10482)
Calibrated PRM actuation function and PRY signal challenge (factor of 2)

I calibrated PRM actuation transfer function measured in alog #10450.
Measured PRY error signal is smaller by factor of 2 from the calculation and suspension model. This means that demodulation phase is off by 60 deg, or PRY modematch(including misalignment) is 50%, or suspension model is off by factor of 2 (or combination of all of them).

[Motivation]
We wanted to check the PRCL loop signal chain (We have done this for MICH loop already; see alog #10213).
Also, we need calibrated actuation TF for designing the compensation filter which does not saturate DAC.

[Method]
1. Made PRY simulink model (It lives in /ligo/svncommon/NbSVN/aligonoisebudget/trunk/PRMI/H1).

2. Change optical gain from PRM motion to REFLAIR_A_RF45_I to match the measured OLTF (which was measured in alog #10450).

3. Use this optical gain to calibrate PRM actuation transfer function.


[Result]
1. OLTF_PRCL_1077847156.png: OLTF compared with model and measured. Flat gain is fitted in the model and this gives the optical gain. The measured optical gain was 1.3e3 W/m.

2. From the REFLAIR signal chain in alog #10213, calibration factor for REFLAIR_A_RF45_I_ERR in PRY is 3.4e11 counts/m.

3. ActTF_PRM_1077847156.png: Calibrated PRM actuation transfer function. Red curve is plotted using zpk from LISO fitting of the measured TF (alog #10450) and divided by 3.4e11 counts/m for calibration. Blue/Cyan curve is from the suspension model using /ligo/svncommon/SusSVN/sus/trunk/Common/MatlabTools/TripleModel_Production/generate_Triple_Model_Production.m and calibrated using the numbers from ./MatlabTools/make_OSEM_filter_model.m (or LIGO-T1000061). M3 and M2 crossover and measurement look healthy. Note that the overall gain of the measurement agrees with model just because we don't have independent measurement of the optical gain. Even so, crossover frequency doesn't change.


[Discussion on optical gain]
Theoretical expression for PDH signal is

dPmod/dL = 2*8*pi/lambda*Peff*J0(beta)*J1(beta)*(t1**2*r2)/(1-r1*r2)

With

Effective input power: Peff = 7.3 uW * 4 /Tprm**2 = 0.032 W  (alog #10213; incident power on REFLAIR_A was 7.4uW when PRM and ITMY is misaligned)
Modulation depth beta=0.07 (alog #9395)
Amplitude reflectivity/transmissivity of PRM: t1 = sqrt(0.03)
Amplitude reflectivity of BS/ITMY compound: r2 = rBS*rBS*rITMY = 0.50

This gives dPmod/dL = 3.1e3 W/m (+/- ~10%). Here, Pmod is RF modulation amplitude of laser power, and dL is one-way length change of PRC, which equals to PRM motion. (Optickle gives 1.5e3 W/m since Optickle assumes demodulation gain of 1/2).

Even if I include the loss of the cable we measured(alog #10213), theoretical value is 2.5e3 W/m (= 3.1e3 W/m * 0.81), or 6.5e11 counts/m at I_ERR. This is factor of 2 larger than the measured.

Since theoretical value assumes perfect modematching and demodulation phase, actual value might be smaller. Also, note that measured optical gain is derived from the model which assumes that suspension model is acurate enough.

[How to solve this challenge]
 - Calibrate BS actuation transfer function using simple Michelson, and compare it using the measurement done in PRY. This will be an independent measurement of PRY optical gain.
 - Measure PRY modematching

Images attached to this report
Comments related to this report
yuta.michimura@LIGO.ORG - 10:27, Tuesday 04 March 2014 (10491)

From OLTF measurement in simple Michelson, we know that the BS suspension model is quite accurate (within ~10%; see alog #10127).
So, by comparing the actuation transfer function model and measurements done in PRY (alog #10450), we can estimate PRY optical gain independent of PRM suspension model.
Attached is the comparison of the measurement and model. This gives calibration factor for REFLAIR_A_RF45_I_ERR in PRY to be 4.3e11 counts/m.
This is different by factor of 1.3 from estimation using PRM.

This means that PRM suspension model is off by ~30% or calibration factor changed during BS measurement and PRM measurement. Still, 4.3e11 counts/m is significantly smaller than the theoretical value calculated above.

Note that BS changes PRY length by sqrt(2) * (BS longitudinal motion). Attached plot is counts (at H1:SUS-BS_M3_ISCINF_L_IN1) to PRY length change, not counts to BS longitudinal motion.

Images attached to this comment
H1 AOS
yuta.michimura@LIGO.ORG - posted 19:45, Monday 03 March 2014 (10481)
PRCL and MICH coupling investigation in PRMI

Stefan, Kiwamu, Yuta

Dip at ~13Hz in PRCL OLTF (see alog #10441) was from 40 Hz bandstop filter in PRM_M2_LOCK_L filter bank. When we turned this filter off, PRCL OLTF got much better. We still need a diagonalization of output matrix since we currently use only the BS to lock MICH. To do this, we measured BS and PRM actuation transfer functions (see alog #10450 for more detail) because they have different frequency response. We are now trying to make a conpensation filter to balance BS and PRM actuation from this measurement.

[PRCL and MICH OLTF]
OLTFs after removing the 40Hz bandstop filter are attached. The bandstop filter at 40Hz had -30 deg of phase and it seems like this filter was to blame for PRCL OLTF dip at ~13Hz. This filter was removed.
Demodulation phase of REFLAIR_A was re-tuned to 146.2 deg from 142.7 deg (H1:LSC-REFLAIR_A_RF45_PHASE_R) by minimizing the PRCL to MICH coupling. The LSC guardian is updated accordingly.
MICH to PRCL coupling is unavoidable in the current configuration.

The gain of the MICH to PRCL coupling was fitted with model with coupling at sensing matrix. The parameters I used to fit was 1. optical gain of BS to MICH error signal, 2. BS to PRCL, 3. PR2/PRM to PRCL, and 4. demodulation phase. The parameters I got to fit the measured curve was:

        BS     PR2+PRM
REFL_Q  1.8e2    0
REFL_I -4.9e5  -1.9e6    W/m

and demod phase of -17 deg (when perfect, it will be 0 deg).
But I think it is unlikely that the demod phase is off by 17 deg. So, we need actual sensing matrix measurement after output matrix diagonalization.
 

Images attached to this report
H1 ISC
stefan.ballmer@LIGO.ORG - posted 19:08, Monday 03 March 2014 (10480)
Observation intent bit
Fred, Jamie, Stefan

I was asked to install an "observation intend" bit that will be included in the interferometer state vector (ODC master). For now this is only intended to report that the IMC is ready.

What I did:
- Updated masks for the guardian input to ODC -right now there are only two bits: operator intent and guardian intend. The keep-alive is currently not used.
- Updated the IMC guardian to turn on its bit when it is done locking the IMC, and turn it off when it detects a lock loss.
- Added a user button on the Guardian main screen to report the operator intent (snap short).

With this, the H1 ODC master (H1:ODC-MASTER_CHANNEL_OUT_DQ) reports when the mode cleaner is locked, Guardian thinks so too, and a human being set the operator intent bit (or forgot to unset it...).

Obviously it will only be as good as the commissioners using it.





Images attached to this report
H1 SUS
brett.shapiro@LIGO.ORG - posted 18:47, Monday 03 March 2014 - last comment - 23:50, Monday 03 March 2014(10476)
Quad model wire length study
I have been investigating the wire length values used in the matlab model since the model fitting code results on ETMY from https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=10089 found a discrepancy in the UIM to PUM wire length. The value given by the model parameter file quadopt_fiber.m for this length is 
     330.8 mm. 
However, the model fitting code converged to 
     340.0 mm +- 2 mm.
About 9 mm longer.

I started investigating this discrepancy by looking at the drawings of the wire jig and the PUM assembly. Since the UIM to PUM wire is a loop, the equivalent length between the UIM and PUM needs to be backed out from these drawings. From these drawings, I calculate the length of wire between the UIM blade tip clamp and the PUM prism is 
     337.61 mm. 
The attached pdf, PUMwireLoopLength.pdf, contains the calculations and references for this number. The limiting assumption for this calculation is likely to be that the wire has an infinitely sharp bending radius going around the prism. In reality, a finite bending radius exists, which will tend to make this calculation a slight overestimate.

Still, the value is close but not quite there. Upon further investigation of the other wire lengths given by the model, I noticed that all the wire lengths are a few mm off from the values determined by the wire jig in D060516. My assumption has always been that the parameter file requires values referenced from the wire clamps (given by the wire jig), as it does for the d's. Thus, either all these values are out of date, or my understanding is incorrect. In particular, quadopt_fiber.m gives the top two stages of wire lengths as

pend.ln = 449.192 mm
pend.l1 = 308.585 mm

In contrast, the wire jig gives these as 

pend.ln = 453.0 mm
pend.l1 = 305.8 mm

Since the model predicts the measured longitudinal modes very well with the UIM-PUM fitting correction, I made the assumption that pend.ln and pend.l1 are correct as listed in the parameter file. Therefore, my previous assumption that the model file requires clamp-clamp lengths is wrong. So I searched for an algorithm (by guess and check more or less) that would take the clamp-clamp wire jig lengths and convert them to the listed numbers in the parameter file. What I found was this:

pend.ln = (wire jig length) + pend.dm/pend.cn  = 449.208
pend.l1 = (wire jig length) + (pend.dn + pend.d0)/pend.c1 = 308.521

The pend.d values are the distances from the wire clamps to the centers of mass. The pend.c values are the cosines of the wire angle from the vertical. With this, both lengths are within 10s of microns from the current quadopt_fiber.m values. Thus, this algorithm means that the wire lengths as given by the parameter file reference the center lines of the masses rather than the wire clamp positions.

Following this center line to center line convention for the UIM to PUM length, rather than clamp to prism we get:

pend.l2 = (clamp to prism length) + (pend.d1 + pend.d2)/pend.c3 = 337.61 + (pend.d1 + pend.d2)/pend.c3 = 338.924 mm

This value is about 1.1 mm from the value determined by the model fitting code, and it fits quite comfortably in the fitting code's +-2 mm error bar.

So, the good news is that the value determined by the model fitting code is consistent with the other metal wires under the assumption that the parameter file is working with center line to center line distances rather than clamp to clamp distances. 

However, ssmake4pv2eMB5f_fiber.m, which compiles the parameter file appears to be assuming the values are in fact clamp-clamp. For example, near the bottom of the ssmake script, the pend.stage2 corrections have 

ln = ln - 2*flexn/cn;
l1 = l1 - 2*flex1/c1;
l2 = l2 - 2*flex2/c2;
l3 = l3 - 2*flex3/c3;

where flex is the distance between the wire clamp and the effective flexure point and ln is equal to pend.ln (and so forth). Thus, it seems these corrections are assuming the parameter file references the clamp positions, not the center line positions. Additionally, higher up in the script around line 285 the vertical heights of the masses are calculated as

pend.tln = sqrt(pend.ln^2 - (pend.nn0-pend.nn1)^2) + pend.dm;
pend.tl1 = sqrt(pend.l1^2 - (pend.n0-pend.n1)^2) + pend.dn + pend.d0;
pend.tl2 = sqrt(pend.l2^2 - (pend.n2-pend.n3)^2) + pend.d1 + pend.d2;
pend.tl3 = sqrt(pend.l3^2 - (pend.n4-pend.n5)^2) + pend.d3 + pend.d4;

where the tl's are the 'true' vertical heights of the centers of mass, the n parameters represent the horizontal distance from the centers of mass of the wire clamps, and the d's again represent the clamp to center of mass distances. So for the top wire for example, 

sqrt(pend.ln^2 - (pend.nn0-pend.nn1)^2)

gives the vertical length of the top wire, and 

+ pend.dn + pend.d0

accounts for the clamp to center line distances for the stage above and below the wire. Thus, it seems again that the ssmake file is expecting clamp-clamp wire lengths from the parameter file.

However, putting clamp-clamp lengths into the parameter file does not provide the correct frequencies. So, the wire length mystery goes on...
Non-image files attached to this report
Comments related to this report
mark.barton@LIGO.ORG - 23:50, Monday 03 March 2014 (10484)

The intent for the ssmake file is very definitely that, when pend.stage2=1, all wire lengths are interpreted as clamp-to-clamp, and all d distances are interpreted as "physical" d's, i.e., COM-to-clamp. (The current quadopt_fiber.m that is under discussion does set this flag correctly.) Moreover this behaviour has been checked against the equivalent Mathematica model both for this parameter set specifically and more generally.

H1 SUS
arnaud.pele@LIGO.ORG - posted 16:50, Monday 03 March 2014 - last comment - 11:04, Wednesday 05 March 2014(10475)
ETMY TF

Started ETMY TF at gps 1077929299 on opsws0 for M0 and R0 in undamped and damped config. The measurement will be running for ~15 hours. This is to assess for rubbing after installation in chamber, and before tomorrow's alignment check.

Comments related to this report
arnaud.pele@LIGO.ORG - 11:04, Wednesday 05 March 2014 (10534)

The measurement returned 0 for all excitations data. I tried again yesterday night with SR2 as a guinea pig and it did the same thing. I suspected some awgstream issues, so I tried running the awgstream command we use in get_sch_TF_M0_v9DQ_sma.m from the terminal, and it returned some error, cf below. Jim is curently taking a look at it

awgSetChannel : failed awgnewchannel_1(chntype = 1,arg1 = 0,awg_clnt[41][0] =o) H1:SUS-SR2_M1_TEST_L_EXC
Error code from awgSetChannel : -5
Error while opening SIStream: Error setting up an awg slot for the channel

X1 SEI
hugh.radkins@LIGO.ORG - posted 16:49, Monday 03 March 2014 (10474)
ISI #6 (I3#1) de payloaded

Mitchell and I removed and bagged the 2200 lbs of dummy payload on the ISI #6 (I3#1.)  Will continue to prep that for storage.

H1 TCS (SUS, TCS)
greg.grabeel@LIGO.ORG - posted 16:41, Monday 03 March 2014 (10473)
ITMy Ring Heaters Installed
Thomas Vo, Greg Grabeel
The install of the ITMy Ring Heaters is finished. Everything went smoothly with the operation, and even the temperature sensor on the lower ring heater survived.

The lower ring heater resistance measured at 44.9 ohms, while the upper measured at 41.7 ohms, and the RTD measured at 109.6 ohms.
Images attached to this report
H1 ISC
kiwamu.izumi@LIGO.ORG - posted 16:21, Monday 03 March 2014 (10472)
Current recycling gain

Red Team

If we believe the recent calibration of the POPAIR_B_RF18 (see alog 10442), the current recycling gain is roughly 6 with the ITMY ring heater at 7 W.

The attached is a trend of the POPAIR_B_RF18 from this morning. It occasionally became a good alignment which gave us about 60 uW. This is greater by a factor of 3.6 than the one  when the ring heater was off (see alog 10448) -- remember that we used to have something like 16.5 uW at this diode.

Images attached to this report
H1 SUS
arnaud.pele@LIGO.ORG - posted 16:09, Monday 03 March 2014 - last comment - 16:09, Monday 03 March 2014(10460)
ITMY P2P

[Jeff Arnaud]

ITMY top mass pitch actuation to test mass pitch response measured by the optical lever was taken on friday afternoon using a "colored" white noise excitation. This method works fine for measuring main couplings (P2P for eg), but hasn't been tested for the cross couplings (L2P). The reason the white noise is filtered through a low pass is because, when increasing the overall amplitude of the signal, it would saturate the DAC at higher frequencies (because of the antiAcqFilter in the coilout filter bank which has a zero at 1Hz and a pole at 30Hz).
The measurement was fairly quick (less than one hour) and gives good coherence until 3Hz. I attached a comparison of the measurement against the "wirerehang" model.

Note that the model and the measurement are very well matching until 2 Hz, but slightly differs (~2%) for the 3rd and 4th pitch mode (2.5 and 2.8Hz). From 3Hz, the signal is two noisy to make any comparison. I added (from Jeff's advise) the top to top pitch TF (2nd attachement), to see how the pitch3 and pitch4 differs at the top level.

Note also that the sign of the oplev phase signal had to be flipped to match the model, so Pitch oplev sign convention differs than SUS.

The next step is to do the same comparison for L2P, then fit the measured (or modeled?) TFs in order to create the L2P decoupling filter.

Images attached to this report
Comments related to this report
arnaud.pele@LIGO.ORG - 14:50, Monday 03 March 2014 (10467)

Attached is the measured vs modeled Top mass Length to test mass Pitch transfer function. There is an extra zero in the measured TF at 0.18Hz, which is below the first QUAD resonnance (0.44Hz). I checked the same TF taken on ETMX, and it doesn't have the same feature, so it's unclear where it comes from.

Images attached to this comment
H1 General
andres.ramirez@LIGO.ORG - posted 16:00, Monday 03 March 2014 (10471)
Ops Summary
8:57 --> PSL Check List (OK)
9:30-11:15 Heading to MidY- Jodi
9:40-10:16 Searching for parts at MidY/EndX – Alexa/Jax
9:45-12:25 HAM4 HEPI attachment work – Huge/Mitchell
10:33-12:00 Going into LVEA West Bay area – Travis
10:45-10:56 Heading into LVEA to test a dust monitor – Richard
11:21-12:00 Going into LEVA – Thomas Vo
13:00-15:12 Heading to EndX/EndY (cleaning) - Cris
12:20-14:24 Back to MidY – Jodi
13:08-      Working on EndY ISC – Filiberto/Aaron
13:18-15:16 Work on ITM Y TCS (ring heater) – Thomas/Greg 
13:30-      Heading to End Y to unlock the quad – Travis
13:31-14:20 Going to End Y to install dust monitor #2 – Jeff B.
13:37-15:34 Working on End Y (fiber attachment) – Cyrus
14:05 ---> LVEA transitioned to Laser Hazard
H1 ISC
keita.kawabe@LIGO.ORG - posted 15:07, Monday 03 March 2014 (10470)
Silly WFS whitener/awhitener MEDM

First screenshot: Even though the left MEDM screen makes it look like STAGE1 whitener/awhitener pair is all green though the awhitener is off and mismatched with whitener. Also, "L1 ASC" label is hard coded.Silly.

Second screenshot: After a fix. MEDM is displaying the whitener and awhitener separately. "Off" and "On" buttons (which worked) still work on both at the same time. Also it says H1 when it's H1. Not silly.

Images attached to this report
H1 PEM (CDS, PEM)
patrick.thomas@LIGO.ORG - posted 11:29, Monday 03 March 2014 - last comment - 14:21, Monday 03 March 2014(10455)
errors on dust IOC for end Y
I telneted into the procServ IOC for end Y and saw the following error messages:

epics> attempting to connect to host: 10.1.3.64 port: 8003
Error: tcp_connect: socket: Too many open files
CAS: Client accept error was "Too many open files"
attempting to connect to host: 10.1.3.64 port: 8003
Error: tcp_connect: socket: Too many open files
attempting to connect to host: 10.1.3.64 port: 8003
Error: tcp_connect: socket: Too many open files
attempting to connect to host: 10.1.3.64 port: 8003
Error: tcp_connect: socket: Too many open files
CAS: Client accept error was "Too many open files"

I restarted the IOC, and the errors did not reappear, but none of the expected state reporting messages were shown. I tried pinging the Comtrol at 10.1.3.64 and did not get a response.
Comments related to this report
cyrus.reed@LIGO.ORG - 12:00, Monday 03 March 2014 (10456)

The switchport for the Comtrol has been down since Friday afternoon.  The Comtrol box is probably unplugged/powered off.

patrick.thomas@LIGO.ORG - 14:21, Monday 03 March 2014 (10466)
Jeff said the Comtrol was unplugged. He plugged it back in and I restarted the IOC. This time it worked.
H1 ISC
evan.hall@LIGO.ORG - posted 21:55, Sunday 02 March 2014 - last comment - 18:04, Monday 03 March 2014(10450)
PRM and BS actuation function measurement in PRY
Kiwamu, Yuta, Stefan

Since all our OLG functions in PRMI never really made any sense, we locked PRY and carefully measured the actuation functions from BS to REFL_45_I and from PRM to REFL_45_I.

Plot 1 shows both BS and PRM transfer functions in ctsREFL45 / cts ISCinf drive (i.e. total actuation function). Both are closed loop corrected.
The BS makes sense: it is almost 1/f^2. I don't understand the PRM - need to sleep over it.

Plot 2 shows the OLG and the CLG.

Plot 3 is a snapshot of (almost) all relevant settings.

The data is in ~controls/sballmer/20140302:
BSdrive.xml
PRMdrive.xml
data/BS2REFL_mag_rad.txt
data/PRM2REFL_mag_rad.txt
data/plotIt.m

To do next: 
-Understand PRM: for one we should check that the acquire mode TF of PRM M3 is as expected.
-Fit inverse actuation filters that make PRM and BS match
Images attached to this report
Comments related to this report
kiwamu.izumi@LIGO.ORG - 12:34, Monday 03 March 2014 (10459)

Stefan, Kiwamu

We then performed a fitting to get the zpk parameters out of the PRM actuator data. We used LISO. Here are the best parameters. We started from the HSTS suspension model, which was in the SUSsvn directory, as our initial guess. Since the data was not available at the low frequencies, we left the resonance at 68 mHz untouched.

=== fit parameters ===

zero 2.3327562304 7.4260090788  ### fitted (name = zero0)
zero 79.7052984298  ### fitted (name = zero1)
zero 7.1547795456  ### fitted (name = zero2)
zero 9.3953133943  ### fitted (name = zero3)

pole 2.8624375188 10.8992566943  ### fitted (name = pole0)
pole 1.6227455287 9.5958223237  ### fitted (name = pole1)
pole 6.839318e-01 2.754374e+01

factor 3.3153778483  ### fitted

Images attached to this comment
kiwamu.izumi@LIGO.ORG - 13:03, Monday 03 March 2014 (10462)

We did the same fitting business on BS. We left the resonance at 42 mHz untouched.

=== fit parameters ===


zero 1.5468779344 47.4044594423  ### fitted (name = zero0)

pole 1.5752161758 20.5781923052  ### fitted (name = pole0)
pole 1.1385114613 8.7983560598  ### fitted (name = pole1)

# from BSFM model
pole 4.201750e-01 3.057337e+01

# from foton
pole 37.5835 1.04298
pole 104.999 0.95652
pole 400
pole 100

zero 1.14018 0.814411
zero 112.186 1e7
zero 30

factor 47.5420319676  ### fitted

Images attached to this comment
kiwamu.izumi@LIGO.ORG - 14:43, Monday 03 March 2014 (10468)

Update on the PRM fitting:

We took some more data points of PRM at higher frequencies to make the fitting more accurate at the high frequencies. We extended the swept sine to about 250 Hz.

Here are the new set of parameters:

=======================================

zero 2.3228474583 7.4113193282  ### fitted (name = zero0)
zero 377.9190677283 41.5971099178m  ### fitted (name = zero1)
zero 15.9199488645  ### fitted (name = zero2)
zero 7.4012889472  ### fitted (name = zero3)

pole 2.8669608985 10.2813809068  ### fitted (name = pole0)
pole 1.6247562788 9.6336403562  ### fitted (name = pole1)
pole 144.4376381898 487.5251791891m  ### fitted (name = pole2)
pole 6.839318e-01 2.754374e+01

# foton poles and zeros
pole 314.966 0.95652


factor 3.3634583469  ### fitted

kiwamu.izumi@LIGO.ORG - 14:46, Monday 03 March 2014 (10469)

I forgot to attach the plot.

Images attached to this comment
stefan.ballmer@LIGO.ORG - 17:43, Monday 03 March 2014 (10477)
We resolved the the non-sensical Q's below 0.5, removed a meaningless pole-zero pair and refitted. This tie we also added a small delay:

=======================================

zero 2.3543597867 8.0633003881  ### fitted (name = zero0)
zero 16.3221439613 855.9042353766m  ### fitted (name = zero1)
zero 3.5808330704  ### fitted (name = zero2)

pole 2.8457926226 10.9197851152  ### fitted (name = pole0)
pole 1.6165053404 8.7715269619  ### fitted (name = pole1)
pole 37.2960505517  ### fitted (name = pole2)
pole 6.839318e-01 2.754374e+01

# foton poles and zeros
pole 314.966 0.95652

delay 120u

factor 3.2012088652  ### fitted

=======================================

In foton:
zpk([0.139329+i*2.35023;0.139329-i*2.35023;9.53503+i*13.2475;9.53503-i*13.2475;3.58083],
   [0.130304+i*2.84281;0.130304-i*2.84281;0.092145+i*1.61388;0.092145-i*1.61388;
   0.0124154+i*0.683819;0.0124154-i*0.683819;37.2961],1,"n")

Its inverse (including a Q=1, f=1 pendulum):
=======================================
zpk([0.130304+i*2.84281;0.130304-i*2.84281;0.092145+i*1.61388;0.092145-i*1.61388;
    0.0124154+i*0.683819;0.0124154-i*0.683819;37.2961],
    [0.139329+i*2.35023;0.139329-i*2.35023;9.53503+i*13.2475;9.53503-i*13.2475;3.58083;
    0.5+i*0.866025;0.5-i*0.866025],1,"n")




stefan.ballmer@LIGO.ORG - 18:04, Monday 03 March 2014 (10478)
Attached is a plot of measured and fitted actuation functions for BS and PRM. Plot 2 shows the residual relative gain of BS/PRM - certainly a lot better than before...

Also, for completeness, here are the foton filters for the BS plant:

zpk([0.0163157+i*1.54679;0.0163157-i*1.54679],
    [0.0382738+i*1.57475;0.0382738-i*1.57475;0.0647002+i*1.13667;0.0647002-i*1.13667;
    0.00687158+i*0.420119;0.00687158-i*0.420119],1,"n")

as well as the inverse plant. Again, it includes a f=1Hz, Q=1 pendulum. Since the BS is 1/f^4, this also includes two 300Hz real poles as roll-off:

zpk([0.0382738+i*1.57475;0.0382738-i*1.57475;0.0647002+i*1.13667;0.0647002-i*1.13667;
    0.00687158+i*0.420119;0.00687158-i*0.420119],[0.0163157+i*1.54679;0.0163157-i*1.54679],1,"n")
zpk([],[0.5+i*0.866025;0.5-i*0.866025],1,"n")zpk([],[300;300],1,"n")
Images attached to this comment
H1 SUS
brett.shapiro@LIGO.ORG - posted 02:47, Friday 14 February 2014 - last comment - 18:50, Monday 03 March 2014(10089)
ETMY Modeling Results
Results of my visit to LHO this week for system identification of the ETMY.

MOTIVATION:

Make better models for each particular suspension to aid control design and noise predictions.

The measured frequencies of the resonances are the most reliable data we have because they are not subject to errors in the sensors or actuators. There are also numerous resonances available for measurement, which can be used to adjust the model.

SETUP:

Resonance measurements were collected on ETMY main chain while on the test stand in the follow configuration with the following methods:
* full quad - top mass to top mass transfer functions using the OSEMs. This data was measured prior to my visit this week.
* triple hang - with the main chain top mass, reaction chain UIM and PUM masses locked on stops, spectra of the lower three main chain stages were measured with the UIM and PUM OSEMs and an optical lever on the test mass. No excitation is needed since the wind from the fans is more than enough. The process of locking the masses also misaligns the UIM and PUM OSEMs sufficiently that they are sensitive to vertical, roll, and transverse displacements of the stages. This allows us to measure more resonances with these OSEMs then we otherwise would. The optical lever isn't sensitive to any resonances the OSEMs miss, but it does add redundancy to help identify a forest of high Q pendulum resonances from spectra that include a lot of similarly shaped artifacts.
* double hang - with the main chain UIM and reaction chain PUM locked on stops, spectra of the main chain lower two stages were measured with the PUM OSEMs. In this case the optical lever would not stay in range, so the data is just the 4 PUM OSEMs.
* single hang - with the PUM on the teflon line stops, the test mass modes were measured with optically. This data was measured prior to my visit.

SUMMARY:

The data encompasses 56 resonance frequencies: 22 free quad, 16 triple hang, 12 double hang, and 6 single hang. See the attached plots and the summary of parameter changes below. In the attachment the black curves are the measured data, the blue the original model, and the red the new model. Pages 1-6 of the attachement show the diagonal top mass to top mass transfer functions. Pages 7-8 show L-P coupling and 9-10 T-R coupling. 11-13 are the frequencies of the triple, double, and single hangs respectively. 14 plots the mode frequency percent errors before the fit and 15 shows the same after the fit. The final page shows the convergence of the total error, where the error is calculated as

                  sum( [(measure mode - modeled mode)/(measured mode)]^2 ) 

The algorithm for fitting the data is Gauss-Newton, an approximation of Newton's method. The fitting code is on the svn at .../sus/trunk/QUAD/Common/MatlabTools/QuadModel_Fit/QuadPend_QuassNewton_fit_v2_H1ETMY.m.

Change in parameters from original model with the estimated convergence errors:
---------------------------------------
Inx (top mass roll inertia)                       : -1.0926 +- 2.6994 %
Iny (top mass pitch inertia)                    : 3.1636 +- 3.4396 %
Inz (top mass yaw inertia)                      : -0.86123 +- 0.65824 %
I1x (UIM roll inertia)                               : 3.9571 +- 0.77982 %
I1y (UIM pitch inertia)                             : 12.2729 +- 2.5078 %
I1z (UIM yaw inertia)                               : -0.10972 +- 0.55984 %
I2x (PUM roll inertia)                               : -2.9587 +- 0.85205 %
I2y (PUM pitch inertia)                            : 8.4597 +- 0.6904 %
I2z (PUM yaw inertia)                             : 0.011768 +- 0.3983 %
I3x (test mass roll inertia)                      : 2.2009 +- 0.77109 %
I3y (test mass pitch inertia)                    : -8.8738 +- 0.79819 %
I3z (test mass yaw inertia)                     : 0.44122 +- 0.5629 %
l2 (PUM wire loop length)                      : 8.6866 +- 1.1464 mm
l3 (fiber length)                                     : 22.1269 +- 2.6176 mm
kcn (top stage spring stiffness)              : 1.0719 +- 2.166 %
kc1 (top mass spring stiffness)              : 1.0935 +- 0.68178 %
kc2 (UIM spring stiffness)                      : 2.2795 +- 0.39067 %
kw3 (fiber bounce stiffness)                  : 9.4286 +- 0.4488 %
dn (top mass blade tip height)              : -0.20928 +- 0.303 mm
d1 (UIM blade tip height)                      : 1.8131 +- 0.56431 mm
d4 (effective fiber flexure at test mass): -4.8356 +- 0.23685 mm
---------------------------------------


DISCUSSION:

The fit of the original model was fairly descent already, except for pitch. The fit of the new model to this data is even better, especially for pitch. The worst mode frequency error decreases from 8.2% to 1.3%. Interestingly, even though only resonance frequencies were included in the fit, the shapes of the transfer functions (including zeros) all match well also. This goes for the cross coupling measurements as well. Note, the length to pitch measurement does not match the pitch to length. These should in theory be identical. Mismatches indicate measurement problems. Length to pitch has some low frequency notches that don't exist in pitch to length. Judging by the models (both before and after), I think it is likely that pitch to length is the more accurate measurement up to 4 Hz. I don't think we can believe either beyond 4 Hz. After the fit, the worst error in mode frequency corresponds to the first roll mode for both the free quad case and the triple hang case.

The inclusion of the extra resonance frequencies made a huge difference in the ability of the model to converge. In this case, a total of 21 parameters were floated. Normally, only a few at a time can be floated using just top mass data.

Many of the parameter changes produced by the fitting code seem quite reasonable. Some that are beyond what you would expect are the lengths of the fibers and the PUM wire loop. These changed by 22 mm and almost 9 mm respectively. Since the mass values are known, the only way to fit all 10 measured longitudinal modes is to adjust the wire lengths. This was achievable by floating both these wire/fiber lengths. I noticed that the default value in the original model for the PUM wire loop has the following comment: "% wire hang value - Mark Barton, 11/22/2011". I wonder if the entered value is no longer correct since the quad is not in the 'wire hang' configuration anymore. Regarding the fibers, the effective flexure length is rather complicated due to the geometry of the fibers. Perhaps some other error, like in fiber radius can mimic this. Note, the bounce mode stiffness moved by 9%.

The d4 change is also large. It is very likely this value is not physical because this parameter has significant degeneracy with both d3 and d2. Thus, the decrease of 5 mm could be spread out between all 3. d2 also has twice the sensitivity, so a small shift there can take up a fair bit of this 5 mm on its own. These degeneracies prevent the fitting code from floating these parameters simultaneously, so you simple have to pick one. d2 is sort of awkward because it is degenerate enough that it is difficult to float with either d3 or d4, but different enough that floating it instead of d3 or d4 yields different results.

DISCLAIMER:
As usual, the choice of parameters to float was made by experience and intuition. These parameter changes are not necessarily representative of reality. Though, with a fit that matches all 56 measurements to the 1% level, you might start to think that this thing is converging within some distance of reality.

COMPARISON WITH FUTURE MEASUREMENTS:
We should see how this new model holds up against L-P measurements at other stages and between stages.


NOTES:
The high frequency vertical and bounce modes were visible on the single hang and double hang measurements, but not the triple and free quad. If they were visible in all there would be 60 measured resonances. However, these modes are virtually the same from double hang to triple hang to free quad because they involve primarily displacement between the bottom two masses. Thus, the loss of information is negligible. In fact, we might be better off not including these extra bounce modes in case they emphasize bottom mass parameters over the upper masses since the same information would essentially be repeated 3 times.
Non-image files attached to this report
Comments related to this report
brett.shapiro@LIGO.ORG - 22:14, Monday 17 February 2014 (10125)
I found a typo in the model fitting code that explains the change in the fiber length. In the code the nominal d3 and d4 values, each 10 mm, were subtracted from the fiber length. The fitting code, doing what it is supposed to do, detected that the fiber length was incorrect and added 22 mm to compensate. The 2 mm difference is in the noise since the fiber length has a weak influence on the dynamics at the mm level. Note that the code did output a +-2.6 mm error bar for this fiber length change.

I'll take this as good news that the fitting code works.

The model fitting code has been updated on the svn with the bug fix.

The new parameter file is on the svn at:
/ligo/svncommon/SusSVN/sus/trunk/QUAD/Common/MatlabTools/QuadModel_Production/quadopt_fiber_H1ETMY.m
brett.shapiro@LIGO.ORG - 23:17, Monday 17 February 2014 (10126)
The following attachment shows that the new model is also a good match for L1ETMY.
Non-image files attached to this comment
brett.shapiro@LIGO.ORG - 18:50, Monday 03 March 2014 (10479)
A new alog entry at https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=10476
discusses the calculation of the UIM-PUM wire length required from the model based on the wire jig document and PUM drawings. These documents bring the wire length much closer to what the model fitting code found.
Displaying reports 67001-67020 of 77175.Go to page Start 3347 3348 3349 3350 3351 3352 3353 3354 3355 End