Displaying reports 72861-72880 of 83254.Go to page Start 3640 3641 3642 3643 3644 3645 3646 3647 3648 End
Reports until 10:23, Wednesday 12 March 2014
H1 SEI (INS, ISC)
hugh.radkins@LIGO.ORG - posted 10:23, Wednesday 12 March 2014 (10710)
H1 ETMY HEPI Medm Screens Populated

They weren't empty but they were wrong.  The IPS raw signals only became useful Monday after we finished the final alignments after the Actuator connection.  So if you care (likely not) about the ETM HEPI position before now (0955pdt) you'll have to look at the local coordinates.  Now you can look at the cartesian values for positions.  Remember, I zero'd (<50 counts, 655cts.0.001" or 38.8nm/ct) Monday.  The raw IPS are all running under 300cts now (HEPI is still unlocked) but the ACB weight decreased slightly yesterday and I'm not surprised to see a little drift as well.  The cartesian are all running under 10um or urad and most much less.  The nominal position for control will be zero.

H1 INS
michael.landry@LIGO.ORG - posted 08:14, Wednesday 12 March 2014 (10709)
HAM4 closed temporarily
Yesterday we tacked both doors on HAM4 with four bolts.  We did not complete a chamber closeout checklist: we are not going to pump down on this volume until after we revisit alignment of the SR2 there, i.e. we cannot pump down until going back in and completing the closeout.  
H1 ISC
sheila.dwyer@LIGO.ORG - posted 01:34, Wednesday 12 March 2014 - last comment - 05:22, Wednesday 12 March 2014(10707)
measurement left running on ETMX

I started to try to commision the slow feedback to ETMX again.  (We previously had this working, but had never charachterized it, and it was causing pitch problems.  I would like to have a feedback to both HEPI and the top mass, and Arnaud has been working on L2P decoupling.)

It seems like the L2P filter right now is unstable, the optic is pitched around alot everytime I try to engage it.  Currently I have a X arm gain of -0.8, the notch in MO_LOCK_L, and no boost.  The feedback is stable, but the UGF is low.  The guardian is set up to set these settings, and running tonight.

From the transfer function measurements I've made (none of which have verry good coherence) it seems like we should be able to increase the gain, the problem is that we start to excite pitch too much and loose lock.

If opwsws4 has not crashed by morning, would someone from the red team hit save on my dtt session, please?  Thank you.

Comments related to this report
yuta.michimura@LIGO.ORG - 05:22, Wednesday 12 March 2014 (10708)

Your data is saved and ETMX is misaligned now.

H1 ISC
sheila.dwyer@LIGO.ORG - posted 22:08, Tuesday 11 March 2014 (10706)
LSC model

Although Adam warned me about making sure we fixed all the connections in the LSC model, I miscommunicated with Dave and we installed it with out fixing the connections.  Daniel and I now fixed the connections, restarted the model, and commited it to svn. 

H1 SUS
arnaud.pele@LIGO.ORG - posted 21:59, Tuesday 11 March 2014 (10705)
TOP mass Y2Y filters installed

The Y2Y filters for ETMX ITMX and ITMY were installed today in the top mass drivealign matrix. The ITMX filter has been copied from ITMY and the design method is the same as in alog 10610.

The open loop (top mass yaw drive to test mass yaw through the invY2Y filter) (should) give a single pendulum transfer function with a resonant Q of 3 @ 0.6Hz, for the 3 quads.

The design scripts are living in :

/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGM0/Scripts/itmy_Y2Y_inversion.m

/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMX/SAGM0/Scripts/etmx_Y2Y_inversion.m

And the measured data is from the dtt templates :

/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGM0/Data/2014-03-03_H1SUSITMY_M0_YtoPY_WhiteNoise_0p1to10Hz.xml

/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMX/SAGM0/Data/2014-03-10_H1SUSETMX_M0_YtoPY_WhiteNoise_0p1to10Hz.xml

 

Images attached to this report
H1 ISC
sheila.dwyer@LIGO.ORG - posted 20:30, Tuesday 11 March 2014 (10703)
Locking COMM tonight

Alexa, Sheila

We have been unable to lock ALS COMM for more than about 5 minutes tonight, I'm not sure if this is because of high seismic, or for some other reason.  (The microseism is around (or just below) the 90th percentile, and we have convoys of trucks) We have made a few measurements of spectra, not with the WFS engaged.  The attached screen shot shows two spectra, the red trace was taken with a gain of 8dB on in 1 of the common mode board, the green trace with 19 dB.  We wanted to reproduce that the high gain loop really has lower noise, but keep dropping lock. 

The botom panel shows the coherence with the ISCT1 accelerometer that Robert moved onto the periscope today. 

Images attached to this report
H1 SUS (ISC)
jeffrey.kissel@LIGO.ORG - posted 20:01, Tuesday 11 March 2014 - last comment - 20:38, Tuesday 11 March 2014(10702)
All L1 and H1 HSTS M2 and M3 Stage Actuators are off by a Minus Sign
J. Kissel, A. Pele, A. Staley

All HSTS and HSTS at both sites have incorrect M2 and M3 coil/magnet COILOUTF gain signs.

While once again banging our heads against the IMC crossover measurements against Alexa's discrepant ALS COMM model, we had one more epiphany regarding the SUS -- RESPECT THE PHASE. Her lowest frequency cross-over, the M1-M2 crossover, which should have a phase of -180 [deg], was measured to have a phase of 0 [deg], but otherwise the magnitude matches exquisitely. Then I remembered her mentioning a month ago that LLO had to account for an unknown minus sign on there lower stages of MC2 to get models to match measurements. Having just recently found an AOSEM vs. BOSEM COILOUTF gain sign bugs on the QUADs during the coil balancing, it occurred to me to check that the M2 and M3 stages of the MC2 matched the PUM stage of a QUAD. They did not, and are indeed incorrect. BIFF!

Worried that it was a systematic flaw copied and pasted everywhere (and because green team need mode cleaner, but not PRM), I checked PRM. Also incorrect. To confirm that that sign orientation *is* in correct, we drove a DC offset on the lower stages of PRM, and indeed, a +L requested drive moves the suspension in -L (as measured by the OSEM sensors). I asked Arnaud to quickly plot the phase of the acceptance measurements that he had for one of these suspensions. ZLONK! +180 [deg] measured phase at DC, where we should expect (from any suspension on the planet) 0 [deg] phase at DC.

Sad about this, I then modified the acceptance measurement scripts to plot the phase of a random smattering all of the M2 and M3 acceptance measurements that have been taken of all HSTS at both sites. All have a phase of +180 [deg] -- see attached. POWIE!

The reason for the flaw in magnet compensating gains? AOSEMs and BOSEMs have coils wound in exactly opposite direction. So a positive current sent to a BOSEM coil will result in magnetic fields opposite in direction than the AOSEM coil. We realized this halfway through defining all of our suspensions' lower stage magnet signs, as is reflected by the poor quality of information in our sign convention documentation, T1200015, specifically the Cheat Sheet, where it shows a table of COILOUTF gains for "Any 4 OSEM Stage" as
    UL   -
    LL   +
    UR   +
    LR   -
which is the current sign distribution on the M2 and M3 stages for HSTSs. However, this table was created / determined assuming a BOSEM winding. You'll notice that the difference between -v2 and -v3 is "adding a AOSEM vs. BOSEM push/pull table," and the (unfinished!) statement that "AOSEM and BOSEM coils are wound exactly opposite in direct[[ion]]." CLANK-EST!

Naturally, because the HLTS EPICs values began as a copy-and-paste of the HSTS, any HLTS has this same flaw of its lower stages, but we haven't used them enough to notice.

Conclusions:
- All HSTS and HSTS at both sites have incorrect M2 and M3 coil/magnet COILOUTF gain signs. That's MC1, MC2, MC3, PRM, PR2, PR3, SR3, SR2, and SRM.

There signs should be:
    UL   +
    LL   -
    UR   -
    LR   +

- I blame myself.

- I clearly need to create a version 4 of T1200015.

- Of course this affects all IFO loops that use the HSTS, so I have not and will not change the signs unless I have whomever designed the ISC loops sitting next to me.
Non-image files attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 20:38, Tuesday 11 March 2014 (10704)
T1200015 has been updated to version 4 with explicit calls to the differences between an AOSEM and BOSEM, 4-OSEM stage.
H1 AOS
thomas.vo@LIGO.ORG - posted 17:18, Tuesday 11 March 2014 (10701)
03/11/2014 Ops Summary

- Hanford Fire Maintenance fixing hydrant 1 by the woodshop

- Jim and Cyrus at MY working on PEM card.

- Dave B. two DAQ reboots today.

- Jeff B. and Andres R. at HAM4

- Robert S. installing accelerometers on ISCT1L

- Apollo installing  both doors on HAM4 with 4 bolts

- CDS implementing LSC and ASC model changes

- SUS doing transfer functions at EY

- Patrick T. doing a CONLOG update

- Karen at EY to clean

H1 SEI
sebastien.biscans@LIGO.ORG - posted 17:17, Tuesday 11 March 2014 (10700)
Procedure to turn the BSC-ISIs back on

Until the guardian installation, I've been asked to write a quick procedure on how to turn back the BSC-ISIs on after a trip.

 

Right now, the best configuration for BS, ITMX, ITMY and ETMX is the same: lvl3 controller on ST1 and ST2, Tcrappy blend filters on ST1 and ST2. No sensor correction.

- Reset the watchdogs

- Check that HEPI position loops are still on

- Open the ST1 CART BIAS screen and click on Reset CPS offset then Store target offsets

- Open the commands screen and click on !Isolate <CHAMBER> lvl3

- A black xterm window will show up. While this pop-up window is there, don't touch anything.

- The isolation loops are now on. Next step is to switch to the good blend filters. Wait for the T240 signals to go down! The overview T240 indicator has to be ALL GREEN before doing anything.

- When you think the platform has settled down, open ST1 BLEND screen -> SWITCH ALL and select Tcrappy.

- If this process makes the ISI trips, that means you haven't waited long enough. Restart the all process. A trick that could work is to start switching the vertical blend filters (Z, RX and RY) first, then the horizontal ones (X, Y, RZ).

- Repeat the same process with ST2 BLEND.

 

Remember that we are dealing with seismic signal and very low frequency instruments. Be patient!

H1 SUS
jeffrey.bartlett@LIGO.ORG - posted 16:29, Tuesday 11 March 2014 (10699)
H1-SR3 Magnet Repair
Andres & Jeff 

   Using a 3 axis translation stage on an optics post (see photos) we glued a new magnet/dumbbell assembly to the UR side of the SR3 optic, to replace the one that was knocked off on Monday. The process is straight forward and was completed in a couple of hours.
 
Procedure: 
1) Lock the Intermediate Mass in its level hanging position; then lock the Optic in its level hanging position.  
2) Adjust the placement  and X, Y, Z location of the 3 axis translation setup so the magnet flag holder is aligned on top of the ring of glue left from the original magnet/dumbbell assembly. 
3) Lock the Z and Y axis stages of the 3 axis translation setup in place so they cannot shift.
4) Retract the X axis stage as far as it can go to pull back the magnet flag holder away from the Optic face.
5) Using Acetone and Alpha swabs carefully clean the old glue from the face of the Optic. It helps to hold an Acetone soaked swab against the glue spot for several minutes to soften the old EP-30. Then with a second swab gently rub the glue spot. If the glue does not start to come off hold the Acetone swab against the glue spot for a few more minutes. 
6) Repeat the wetting and swabbing process until all the old EP-30 has been removed. 
7) Mount a new magnet/dumbbell assembly into the flag holder and apply a dab of EP-30 to the dumbbell. 
8) Slowly turn in the X axis stage until the dumbbell makes contact with the face of the Optic. 
9) Lock the X axis stage so it cannot shift while the glue dries.           
Images attached to this report
X1 DTS
james.batch@LIGO.ORG - posted 16:17, Tuesday 11 March 2014 (10698)
Removed Jenkins access via http
Jonathan Hanks, Jim Batch, David Barker

Reconfigured the badger.ligo-wa.caltech.edu web server to no longer accept http access using a common login.  Replaced with https LIGO.ORG authenticated service, which displays the Jenkins service running on x1boot.  Existing users may notice cached links to http pages need to recache as https 
H1 CDS (CDS)
patrick.thomas@LIGO.ORG - posted 16:09, Tuesday 11 March 2014 (10697)
conlog updated from 1.1.0 to 1.3.0
Dave B., Jim B., Patrick T.

WP 4487

This was done primarily to match what Livingston is running. It adds:

1.1.0 -> 1.2.0
1. A reduced rate on the keep alive updates
2. A minor bug fix in the printing of startup messages

1.2.0 -> 1.3.0
1. A cron job to check for and mail information on frequently changing channels
2. A javascript datetime picker to the webpage
3. A link to the bugzilla for conlog to the webpage
4. Abbreviations for the timezone in the query results

Note that the code was restarted to run 1.3.0 before the channel list updates reported today by Dave.

There are still some configuration differences with Livingston that need to be worked out, but we are now closer.
H1 INS
jeffrey.bartlett@LIGO.ORG - posted 15:55, Tuesday 11 March 2014 (10696)
HAM4 Door Installation Dust Counts
   I monitored the dust counts during the installation of the HAM4 North & South doors. In general the particle counts under the cleanroom area were 0. Occasionally there were 0.3µ counts of 1 to 3 particles per 20 second sample time. I saw very few counts for larger particles.
 
   During the actual door installation dust counts were in the 1 to 5 particles per 20 second sample time. Many times during the operation the counts were 0. The highest counts on the North side were in the 75-80 0.3µ particles per 20 seconds sample time, during the removal of the two soft covers. The highest particle counts on the South side were in the 70-77 0.3µ particles per 20 second sample time, while the flange was being wiped down with alcohol. In both of these cases the counts returned to the 0 to 3 count range, in a few minutes.      
H1 SEI
sebastien.biscans@LIGO.ORG - posted 15:14, Tuesday 11 March 2014 (10694)
New cart bias screen installed for ISIs

New cart bias screens have been installed for the BSC-ISIs and the HAM-ISIs.

The goal of this update is to make the cart bias clearer to non-SEI commssioners. Let us know if it doesn't and we'll take in account your remarks.

Images attached to this report
H1 CDS
david.barker@LIGO.ORG - posted 14:30, Tuesday 11 March 2014 (10693)
LHO Conlog channel list regenerated and installed

Patrick and Dave

following our instuctions in the wiki page https://lhocds.ligo-wa.caltech.edu/wiki/ConlogChannelConfiguration as a test we regenerated the conlog channel list after the latest Beckhoff autoBurt.req were added and new models installed.

539 channels inserted

197 channels removed

+342 nett gain of channels

H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 13:52, Tuesday 11 March 2014 (10691)
h1pemmy

I have added h1pemmy to the CDS overview MEDM screens. It is also added to the DAQ configuration files, which will be impemented on the next DAQ restart.

H1 AOS (ISC)
corey.gray@LIGO.ORG - posted 12:37, Tuesday 11 March 2014 - last comment - 14:17, Tuesday 11 March 2014(10684)
EY TMS Cable Connector Note

Several of the TMS Cable connectors are missing screws to attach to the vacuum feedthru plugs.  Have discussed with Keita and because these connectors are a tight fit into the feedthrus as they are, we will not worry about installing these screws in the connectors.

Comments related to this report
justin.bergman@LIGO.ORG - 14:17, Tuesday 11 March 2014 (10692)

Mitchell had a reservoir of spare connector screws at one point.

H1 ISC
yuta.michimura@LIGO.ORG - posted 09:55, Tuesday 11 March 2014 - last comment - 16:54, Wednesday 12 March 2014(10674)
BS and PRM actuation balancing - MICH to PRCL supressed by factor of 4

I re-measured BS and PRM actuation transfer functions in PRY configuration after plant inversion done on Mar 5 (see alog #10559).
It seems like we succeeded in BS and PRM balancing within ~8 % and MICH to PRCL coupling is expected to be supressed by factor of ~4, compared with using only BS as an actuator.
For the sensing matrix measurment, the effect of residual MICH to PRCL coupling gives ~6 % error for MICH to REFL45Q element and ~16000 % error for MICH to REFL45I element.

[Motivation]
Before measuring the PRMI sensing matrix, we wanted to estimate how good output matrix diagonalization is.


[Method]
1. Lock PRY and measure open loop transfer function. Compare it with the model to derive optical gain.

2. Measure actuator transfer function of BS and PRM from ISCINF to REFLAIR_RF45_I_ERR in PRY (using the same template used in alog #10450). Calibrate these TFs into m/counts with the optical gain derived in step 1.

3. Closed loop correct TFs measured in step 2. TFs should look like 1/f^2 at 1-300 Hz (see comments on alog #10450). Since output matrix for MICH in PRMI are set to (BS,PRM)=(1,-0.5), these TFs should be equal (see alog #10559 and table below).

-table of actuation efficiency (optic motion to interferometer length change in m/m)-
      PRY      PRCL      MICH
BS    sqrt(2)  1/sqrt(2) sqrt(2)
PRM   1        1         0


4. Calculate expected actuator TFs for MICH to PRCL coupling using the measured TFs. BS ISCINF to PRC length change will be half as that of PRY. BS-0.5*PRM gives the residual MICH to PRCL coupling.


[Result]
1. OLTF_PRCL_1078572000.png: Openloop transfer function of PRY lock. By comparing with the model, this gives PRY optical gain of 1.8 W/m. So, the calibration factor for REFLAIR_RF45_I_ERR in PRY is 4.7e11 counts/m. Note that this calibration factor includes losses in the PD signal chain (e.g. loss from long cable). Also, note that PRM suspension model was 30 % off from the measurement (see #10482; measurement = 0.77 * SUS model). This correction factor is included in the model to derive the optical gain.

2. BSandPRMact_PRY.png: Measured actuator transfer functions for BS and PRM in PRY. x marks show raw measured TFs and dots show closed loop corrected ones. After closed loop correction, actuator TFs look like they follow 1/f^2. From the fit, BS actuator TF is 1.79e12 Hz^2/f^2 m/counts and PRM actuator TF is 1.93e12 Hz^2/f^2 m/counts for PRY. Considering the error bar from coherence and cavity build up fluctuation during the measurement, this 8% difference between BS and PRM is significant (error bars in TF magnitude are derived using the formula in alog #10506). We have done the balancing with the precision of ~10%, so this difference is reasonable.

3. BSandPRMact_MICH2PRCL.png: Estimated MICH to PRCL coupling from actuator diagonalization. Blue dots show BS ISCINF to PRC length change and red dots show BS and PRM combined actuator to PRC length change. Fitted lines show that MICH to PRCL coupling is expected to be supressed by factor of ~4 by actuator balancing. We can improve this supression ratio a little bit by changing the gain balancing between BS and PRM by 8%, but it's not easy to improve more and prove we did more.


[Is this enough?]
This means that our MICH actuator (BS - 0.5*PRM) changes MICH length by 1.79e12 Hz^2/f^2 m/counts and PRC length by 2.06e11 Hz^2/f^2 m/counts. According to Optickle simulation in LIGO-T1300328, sensing matrix for PRMI sideband is

            PRCL    MICH
REFL 45I    3.4e6   2.5e3
REFL 45Q    6.4e4   1.3e5  W/m


So, the estimated effect of residual MICH to PRCL coupling to the sensing matrix measurement is;

MICH to REFL45Q element:   6 % error (= 6.4e4/1.3e5/(1.79e12/2.06e11) )
MICH to REFL45I element: 16000 % error (= 3.4e6/2.5e3/(1.79e12/2.06e11) )

If we ignore MICH to REFL45I element, which is hard to measure anyway, I think this is acceptable.


[Next]
 - Update gain balancing factor between PRM and BS from 1/16 to 1/14.7 (FM5 in H1:SUS-BS_M3_LOCK_L)
 - Update IQ demod phase in H1:LSC-REFLAIR_A_RF45_PHASE_R to minimize PRCL to MICH coupling
 - Measure sensing matrix in PRMI

Images attached to this report
Comments related to this report
arnaud.pele@LIGO.ORG - 16:15, Tuesday 11 March 2014 (10695)

After talking with Yuta, I took a look at our PRM M3 to M3 transfer functions, measured with the osems as actuators and sensors, and compared it with the model. We see a factor difference of ~20% (model=1.18*measurement). This would mean the calibration error comes from the actuation chain (both of us are using T1000061 as a reference for calibrating actuation).

Images attached to this comment
yuta.michimura@LIGO.ORG - 16:54, Wednesday 12 March 2014 (10724)

I did the calibration of the error signal wrong.  The calibration factor 4.7e11 counts/m was correct, but I multiplied this number to the measured data in the script, instead of dividing.
Correct figures are attached. Actuator calibration from the fitting is as follows

BS to PRY: 8.13e-12 Hz^2/f^2 m/counts  (half of this is BS to PRCL in PRMI)
PRM to PRY: 8.79e-12 Hz^2/f^2 m/counts  (same as PRM to PRCL)
BS-0.5*PRM to MICH: 8.13e-12 Hz^2/f^2 m/counts (same as BS to PRY)
BS-0.5*PRM to PRCL: 9.28e-13 Hz^2/f^2 m/counts

Discussion about MICH to PRCL supression ratio and sensing matrix measurement error from actuation off diagonal element remain unchanged.

Also, note that my definition of MICH is one-way length difference between BS to ITMX and BS to ITMY. PRCL is PRC one-way length.

[Data and script]
Data and script used lives in ~/yutamich/BSPRMact/ folder.
./PRMdrive_complete.xml   (dtt of PRM actuation TF measurement)
./BSdrive_complete.xml   (dtt of BS actuation TF measurement)
./PRYoltf_complete1.xml    (dtt of PRY OLTF measurement)
./BSPRMact.py    (script for plotting and calibrating data)

Images attached to this comment
Displaying reports 72861-72880 of 83254.Go to page Start 3640 3641 3642 3643 3644 3645 3646 3647 3648 End