Displaying reports 45801-45820 of 86550.Go to page Start 2287 2288 2289 2290 2291 2292 2293 2294 2295 End
Reports until 09:35, Friday 11 May 2018
H1 AOS (DetChar)
ronaldas.macas@LIGO.ORG - posted 09:35, Friday 11 May 2018 (41949)
Live noise budget: speculative bullseye sensor noise contribution to DARM

Sheila, Ronaldas

Sheila suggested to investigate bullseye sensor noise contribution to DARM. It is basically a coherence based projection of jitter from the bullseye sensor upstream of the PMC, which was contributing to the DARM noise from 30Hz-1 kHz in this lock stretch (4th of July).

Bullseye sensor readings seem to be coherent with DARM signal on YAW and PIT d.o.f., see 'bullseye_yaw_pit_coherence.jpg'.

This sensor measures jitter that we believe is driven by the turbulent flow of water over the crystals in the high power oscillator. The acoustic or PZT injections in the PSL which can reproduce the jitter peaks seen by sensors downstream of the PMC cannot explain the level of noise coupling that the coherence suggests for jitter sensors before the PMC. We are relying on the observed coherence between this sensor and DARM to estimate the noise contribution.  

Nonetheless we tried the following:
1) choose maximum coherence d.o.f. for bullseye sensor (either YAW or PIT)
2) if coherence with DARM is bigger than 0.01 for a frequency bin, include it as a noise
3) then the bullseye noise is simply sqrt(coherence) * DARM

Result can be seen in 'bullseye_sensor_coherence_noise.jpg'. This noise contributes quite a lot for f>100Hz and improves noise budget, see 'compact_nb.jpg' and 'full_nb.jpg' [cyan dots in the plot]. For a comparison, previous noise budget plot can be found here (previous noise budget).

While the result seems encouraging, we need to investigate it for other locks. This coherence projection was done for 4th of July, 2017 (GPS time: 1183190418, duration: 600s), before the earthquake. Note that we expect this noise source to be reduced for commissioning/O3 because the high power oscillator has been replaced with the 70W amplifier.  

Images attached to this report
H1 SUS (AOS, SUS)
keita.kawabe@LIGO.ORG - posted 18:41, Thursday 10 May 2018 (41942)
TMSX SUS cage needs to be physically rotated by ~-250 urad YAW. (Travis, Betsy, Keita)

Summary

TMSX needs to be YAWed by about -250 urad (YAW slider from -329 urad of Feb/06 X arm peek to -585 urad today) to make the ALS X beam retro reflect by ETMX.

Old ERMX wedge seems to have been about ~590 urad, thus deflection should have been (1.46-1)*590=270 urad horizontally, but now the wedge is entirely gone.

We know that ETMX angle is pretty good as of now within ~+-80urad or so from PCal reflected beam. We know that TMSX suspension didn't change angle by O(100urad) since February.

Unfortunately, with the new offset TMSX suspension DAC is already railing, so we need a physical rotation to relieve it.

Old ERM wedge

Old ERM spec is pretty loose, 0.04+0.04-0.03 deg = 700+700-500 urad (in horizontal direction, it seems).

In the case of old ERMX, which is ERM-02, the Vendor report (C1001321) shows that the edge at 180deg position is 0.2mm thicker than the reference edge at 0deg, so I'd guess the wedge is 0.2mm/340mm =590 urad. The same report says something about parallelism of 0.02mm but I don't know what it means. There is also GariLynn's transmission data E1200019 but I don't know if Zernike Tilt coefficients on the report represent the wedge or not.

IF the wedge was indeed ~590urad, using n~1.46 at 532nm, the deflection should have been 271urad before ERM replacement.

(For ERMY 0.25mm/340mm~735urad, deflection ~340urad, on the same order as ERMX, Vendor report C1001320).

What was done

After Betsy and Travis are done with ETMX oplev and confirmed that PCAL beam reflection is right on the detector within +-1mm or so (which means that the ETMX angle is good within of  ~+-1mm/6m/2=+-80mrad), I fired up the ALSX laser, turned on the QPD centering, went in to the chamber, removed the ERM cover, came out and changed the TMSX alignment offset to obtain retro-reflection. I had to basically rail F2 and F3 coil that are used for YAW.

  Arm peak on Feb/06 Now
PIT OFFSET [urad] 74 91
YAW OFFSET [urad] -329 -585

There apparently was a big YAW shift, but I don't see any M0 stage jump nor drift since February. I and Corey moved LF, RT and F1 BOSEMs at some point, but the actuation of a BOSEM should have much smaller dependence on the magnet depth than the sensing, and anyway these shouldn't and didn't affect YAW. See attached.

After this ERM cover was put back on, ALSY was turned off, and EY station was put back in laser safe.

Betsy reported that they ran a quick transfer function and saw no touching/rubbing.

What about Y?

TMSY Yaw offset used to be pretty small (between 0 and +10urad last year when ALSY was regularly locked), but after ERMY swap we had to set the YAW offset to -217 urad (40793). As was noted above, IF the wedge could be read off of the thickness measurement by the vendor the deflection should have been 340 urad. Not as satisfying an agreement as X, but still on the same order.

 

Images attached to this report
H1 SUS (ISC)
georgia.mansell@LIGO.ORG - posted 18:33, Thursday 10 May 2018 (41946)
Towards measurement of ESD actuation co-efficients using optical lever coupling
Sheila, Georgia
 
Just an update: I’ve been working towards some scripts to measure the alpha, beta, beta_2, and gamma co-efficients of test masses using the optical lever. This is similar to the measurements Sheila has done longitudinally, see lho alog 38656. This measurement will give more information than the usual Veff measurements, which is one combination of these four parameters, and will help us localise charge (eventually) quadrant-by-quadrant. 
 
By driving different combinations of the signal electrodes and bias electrodes, with and without signal and bias offsets, we think we can work out all 4 parameters for pitch and yaw, helping us localise charge on the optic. We can drive these electrodes hard enough to see a signal on the optical lever. Stay tuned for an alog full of maths about how we calculate the parameters.
 
The scripts I’m working on are works in progress, and are not fit to be run at the moment, but reside in /userapps/sus/common/scripts/quad/opLevChargeMeasurements
 
I’ve been testing the scripts out on ETMY. Note: to avoid driving the LR quadrant and introducing coupling between pitch and yaw I’ve changed the EUL2ESD matrix. Normally this is:
 
P = sqrt(2) UL + sqrt(2) UR - sqrt(2) LL - sqrt(2) LR
Y = - sqrt(2) UL + sqrt(2) UR - sqrt(2) LL - sqrt(2) LR
 
I’ve made the LL and LR elements 0 for pitch, and the UR and LR elements 0 for yaw. I assume we'll want to leave it this way until the LR quadrant is fixed.
LHO VE
kyle.ryan@LIGO.ORG - posted 18:27, Thursday 10 May 2018 (41945)
Dismanteling of CP4 bake-out components begun

Ken D., Tyler G. and Mark D.

The power cords connecting the 480 VAC manual variac, duct heaters and recirculating fan from their respective control panels were disconnected.  Now the variac and heater control panel can be moved out of the way.  Also, all of the added foam insulation board, aluminum foil and "rock wool" insulation has been removed from the VEA. 

LHO VE
kyle.ryan@LIGO.ORG - posted 18:15, Thursday 10 May 2018 (41944)
Elevated temprerature scan of CP4

Scan taken this morning (see attached).   This is "unofficial" but is promising. 

Non-image files attached to this report
LHO VE (VE)
gerardo.moreno@LIGO.ORG - posted 17:15, Thursday 10 May 2018 - last comment - 09:21, Friday 11 May 2018(41943)
Leak Test of IP gate valves, HAM2, HAM5 and BSC2 Viewports/blanks

(Kyle R, Gerardo M)

Today after lunch we removed all aux cart equipment used to pump down BSC1 and BSC3 annulus systems, then we moved to do a gross leak check of disturbed joint conflats, background for the entire procedure remained under 10-09 torr*L/sec.
Helium leak tested the viewports/blanks installed on HAM2 and HAM5, and the new installed ion pump gate valves (IP1 and IP2).  Kyle noted a couple of viewports that had tape indicating that needed testing on BSC2, leak checked those as well, and removed the tape.  No gross leaks found.

Comments related to this report
kyle.ryan@LIGO.ORG - 09:21, Friday 11 May 2018 (41948)

Note that we had valved-out the YBM MTP so that all of the helium signal would be routed through the Vertex MTP which was backed by the leak detector.  Each joint got a minimum of 120 seconds of audible helium flow, 60 seconds at each 180 degree-separated test slot.  Also, following this exercise, we re-exposed the YBM MTP and added the XBM MTP.  Thus, the combined volumes of the Vertex+YBM+XBM are now pumped by the (3) MTPs.

LHO General
corey.gray@LIGO.ORG - posted 15:59, Thursday 10 May 2018 (41933)
DAY Operator Summary

TITLE: 05/10 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:

Started covering for Cheryl at 10amPDT.
LOG:

H1 SUS
betsy.weaver@LIGO.ORG - posted 12:56, Thursday 10 May 2018 (41937)
Updated ETMX OLV Offsets and Gains

ETMX OSEM Open Light Values (OLV) remeasured, offsets and gains adjusted:

Main Chain Top

BOSEM Location NEW OLV NEW OFFSET OLD OFFSET NEW GAIN OLD GAIN
F1 19500 -9750 -12009 1.538 1.249
F2 26900 -13450 -14727 1.115 1.019
F3 27100 -10685 -15330 1.107 0.978
LF 21370 -10950 -12256 1.404 1.224
RT 21900 -10950 -12362 1.370 1.213
SD 26000 -13000 -14259 1.154 1.052

Reaction Chain Top

BOSEM Location NEW OLV NEW OFFSET OLD OFFSET NEW GAIN OLD GAIN
F1 25500 -12750 -14461 1.176 1.037
F2 20430 -10215 -11507 1.468 1.304
F3 22870 -11435 -12858 1.312 1.167
LF 23350 -11675 -13331 1.285 1.125
RT 20380 -10190 -12194 1.472 1.230
SD 18810 -9405 -10980 1.595 1.366

L1 (UIM)

BOSEM Location NEW OLV NEW OFFSET OLD OFFSET NEW GAIN OLD GAIN
UL 21575 -10788 -12133 1.390 1.236
LL 22600 -11300 -13269 1.327 1.130
UR 22575 -11288 -12273 1.329 1.222
LR 22960 -11480 -13130 1.307 1.142

L2 (PUM) TBC...

All values updated in the SDF SAFE file

H1 ISC
jenne.driggers@LIGO.ORG - posted 12:51, Thursday 10 May 2018 - last comment - 10:50, Friday 11 May 2018(41938)
IMC locked, alignment not yet complete

[Sheila, Jenne]

When Sheila first opened the light pipe, we weren't seeing beam on IMC REFL camera.  We went to the table with a card and moved the PZT until we were back on the camera.  I had previously set the IMC optics back to the bottom stage OSEM positions from the last IMC lock.  This got us flashes.  The IMC is now locked, although the alignment is very poor - we'll continue to work on that after the meeting, but should be ready to send beam to HAM 6 this afternoon.

Comments related to this report
sheila.dwyer@LIGO.ORG - 18:08, Thursday 10 May 2018 (41940)

The IMC is locked with a build up slightly lower than what we had before this vent.  On April 26th we had 165 counts on MC2_TRANS_SUM with 2 Watts input, we now have 67 counts with 0.85 Watts of input power. Some of the things that we ran into:

Craig and I re-phased the length demodulator as his comment says, and flipped the sign.  We then added 219 degrees to the IMC WFS demod phases.  We found that the LSC power normalization was not up to date (probably a consequence of using the rotation stage medm rather than the guardian to set the power) the gain of the IMC WFS was very low.  We also reset the dark offsets for the MC WFS.  SDF screenshot attached. 

Keita found that there was angular feedback to M2 on MC2, which I don't think is correct.  This was set this way on Feb 17th and accepted in SDF, we set it back to M2 off and accepted that in SDF. 

We set the mode cleaner to offline for a jitter measurement using the IMC WFS DC starting at 1:04 UTC.  The PSL is in science mode and there is 8.9 Watts injected.  

On a small detour, I made some edits to the state generator for the OFFLOAD_ALIGNMENT_MANY state, bug fixes from the guardian re-work.  The motivation for this is that the offload MCWFS script doesn't turn off the loops so it misaligns the IMC which the slow MCWFS loops take a while to recover from.  I had intended to write a guardian state that uses this generator, however, this generic offload state relies on having the alignment intergators in the suspension top masses, which is not the case for the MCWFS.  We also would need to edit the state to deal with the IMC PZT.  There were a few bugs to work out with the generic offload script,    I added fast_ezca to the list of things that are imported by ISC_GEN_STATES, and removed two variables which were just renamed in the state ie: 

def gen_OFFLOAD_ALIGNMENT_MANY(dof,tramp,optics):
    class OFFLOAD_ALIGNMENT(GuardState):
        request = False
        redirect = False     
        tramp = ramptime
        optics = opticList

became

def gen_OFFLOAD_ALIGNMENT_MANY(dof,ramptime,opticList):
    class OFFLOAD_ALIGNMENT(GuardState):
        request = False
        redirect = False 

Images attached to this comment
Non-image files attached to this comment
craig.cahillane@LIGO.ORG - 16:13, Thursday 10 May 2018 (41941)ISC
Craig, Sheila

Sheila and I added 4.5 nanoseconds of delay to the IMC PDH error signal.  The PDH modulation frequency is 24.078 MHz.  This corresponds to a +39 degree phase shift in the PDH error signal.
Images attached to this comment
sheila.dwyer@LIGO.ORG - 23:23, Thursday 10 May 2018 (41947)

Attached are data taken with the IMC unlocked with 8.5Watts input power, compared to the data attached to 39434 which was taken with the HPO and the IMC unlocked. Both are calibrated into beam diameters (normalized pit and yaw *sqrt(pi/8)).  The 70W amplifier has lower jitter below 50Hz, but not above.  This might be due to the high noise on the PSL table and periscope and the floor that Terra and Anamaria have pointed out (41707 and comments).  

Images attached to this comment
terra.hardwick@LIGO.ORG - 10:50, Friday 11 May 2018 (41950)

I did a quick summary page look at the HAM1 ground motion and PSL table motion from November jitter data timeframe and today. I also compared with LLO (used PSL table data from before install started, so August). Floor motion at LHO is slightly lower in the hundreds of Hz region now compared to Nov.

first plot: HAM1 ground, LHO on left, LLO on right

second plot: PSL table motion, LHO on left, LLO on right

Images attached to this comment
H1 General
cheryl.vorvick@LIGO.ORG - posted 09:49, Thursday 10 May 2018 (41932)
Morning Activities:
H1 General
cheryl.vorvick@LIGO.ORG - posted 09:36, Thursday 10 May 2018 (41931)
Morning Meeting:

Work, by group:

Work, by building:

H1 OpsInfo
jeffrey.bartlett@LIGO.ORG - posted 08:41, Thursday 10 May 2018 (41930)
Shutdown Post-Vent Dust Monitors
   Have shutdown dust monitors LVEA #5 and End-Y VEA #2 and removed them from the check_dust_monitors_are_working script. Dust monitors remaining in the check_dust_monitors_are_working script are in use and should be monitored by Ops per the checklist.  
H1 PSL (IOO, PSL)
keita.kawabe@LIGO.ORG - posted 23:47, Wednesday 09 May 2018 - last comment - 10:18, Thursday 10 May 2018(41924)
PSL main beam path done (ALS path later) (Cheryl, Sheila, Keita)

We iterated between IO_MB_1 and IO_MB_2 without moving EOM as planned. One difference from the plan was that it was my misunderstanding that Cheryl had two irises on the main beam path (there was only one), so we used EOM and iris as our fiducial.

As expected this made ALS path totally misaligned such that it doesn't clear Faraday, that will be adjusted later.

Comments related to this report
kyle.ryan@LIGO.ORG - 07:01, Thursday 10 May 2018 (41927)

Ooopps!  This is potentially a worst case scenario.  I made log entry 41922 @ 21:21 hrs. local intended for the Thursday morning 0900 meeting audience thinking that anyone who might potentially energize any of the High Volts had left for the day.  I hadn't seen anyone in the Control Room, LVEA or OSB offices for hours.  Is this log entry just a late recording of activities from earlier in the day, or, where people in the PSL "chomping at the bit" awaiting the "go ahead" from me confirming that we were on turbo pumping?  If so, and if any High Volts had been energized last night after my entry, then we may have risked Paschen arcing! 

Regardless, people, I think this situation (or potential situation) is symptomatic of a culture that is developing that is going to "bite" us sooner or later.  If I had my druthers, we would slow down the pace a little.  In the past, I didn't feel time pressure to make this hand-off to the next interested party.  Typically, we would pump with the turbos for a day or more before declaring it okay to resume IFO work. 

 

corey.gray@LIGO.ORG - 08:20, Thursday 10 May 2018 (41929)

This was an alog entered well after the work completed.  (Cheryl & Keita left the LVEA at ~4:45pmPDT.)

They were working on alignment in the H1 PSL Room.  The LVEA is Laser SAFE (so the light pipes for the ALS & PSL shutters are CLOSED).  

sheila.dwyer@LIGO.ORG - 10:18, Thursday 10 May 2018 (41934)

To re-enforce what Corey said, this was work that was done earlier during the day and confined to the PSL enclosure (no beams were sent into the chamber, no high voltage in chamber was used, and no viewport work.)

Before starting this, we measured the power before and after the EOM, which was 17.8mW at the input and 17.9mW at the output.  We changed the power up and down while we were working, and attempted to re-measure after the work was finished (9.08mW before the EOM, 9.5mW after).  We found that the scattered light from the high power beam dump that is near the EOM was showing up as significant errors in our power measurements, which probably explains why we found EOM transmissions greater than 100%.

H1 ISC
jenne.driggers@LIGO.ORG - posted 14:46, Monday 07 May 2018 - last comment - 10:56, Thursday 10 May 2018(41869)
First guess of new gains for 9 MHz and 45 MHz RF signals

I wanted a quick first guess of new gains to use for the RF locking signals, so that we know roughly where to start when trying to lock DRMI, since the drive levels are slightly different with the new EOM.  I'm using Koji's measured values from alog 41435.  Note that the drive levels are slightly different now, since the EOM drivers have been moved to outside the PSL enclosure (alog 41852), but they're pretty similar.  Our final gains will of course be set by measuring the loops, so this small discrepancy in the first round guess shouldn't really matter.

The amplitude of a PDH signal is proportional to J_0(Gamma)*J_1(Gamma), where J_n() is the Bessel function, and Gamma is the modulation depth in radians (see, for example, P1500001 appendix B for a derivation).  The ratio that we will want to apply to the old gains will be:

ratio = ( J_0(Gamma_old) * J_1(Gamma_old) ) / ( J_0(Gamma_new) * J_1(Gamma_new) ). 

For the 45 MHz channels (Gamma_old = 0.287, Gamma_new = 0.197), the ratio will be 1.43. For the 9 MHz channels (Gamma_old = 0.187, Gamma_new = 0.210) the ratio will be 0.89

Comments related to this report
jenne.driggers@LIGO.ORG - 10:56, Thursday 10 May 2018 (41935)

With the change out of the RF combiner for 45 MHz and 24 MHz (alog 41889), we now have a slighly higher modulation index for the 45 MHz signals.  Now Gamma_45MHz is 0.259, rather than 0.197.  This new value is much closer to the old EOM / RF driver combination from O2 of 0.287.

This means that the ratio defined in the above entry for 45 MHz is now 1.10.

H1 ISC (INS)
slawomir.gras@LIGO.ORG - posted 18:50, Thursday 03 May 2018 - last comment - 13:50, Thursday 10 May 2018(41835)
AMD installation on ITMs done
Betsy, Sebastien, Slawek


Work on installation of AMDs on ITMx and ITMy has been completed. 
Each test mass has now 4 AMDs glued to the suspension flats.  All AMDs on ITMy are glued slightly lower than the nominal AMD height position. It appears that quad suspension of ITMy is  ~5 mm longer than the ITMx quad. We have noticed it after AMD installation. This new AMD position should not cause any AMD performance degradation neither increase thermal noise according to our simulation.
Additionally, due to the scratches on the test masses flats we decided to move AMD 4 on ITMx and AMD 4 on ITMy. The exact gluing locations are shown in the attached drawing.
The curing dynamic test of the epoxy EPOTEK 302-3M of all batches was passed, see attached picture.  The bond between AMD and TM looks good for each AMD (see the back face image of the AMDs). 
We can call this installation 100% successful.
Non-image files attached to this report
Comments related to this report
sebastien.biscans@LIGO.ORG - 13:50, Thursday 10 May 2018 (41939)

The list of the different AMD modes are listed in the DCC document 'AMD_modes.pdf':

https://dcc.ligo.org/E1700356

 

Displaying reports 45801-45820 of 86550.Go to page Start 2287 2288 2289 2290 2291 2292 2293 2294 2295 End