Displaying reports 68621-68640 of 85883.Go to page Start 3428 3429 3430 3431 3432 3433 3434 3435 3436 End
Reports until 17:21, Tuesday 07 April 2015
H1 AOS
eleanor.king@LIGO.ORG - posted 17:21, Tuesday 07 April 2015 (17734)
HWS alignment at end stations

Nutsinee, Aidan, Elli

Today we worked at both end-X and end-Y, working on moving the HWS camera to the image plane of the ETMs.  In the morning we were at EY and in the afternoon we were at EX.  We were planning to make only a small adjustment to the HWS location, but after taking some measurements we decided that we will have make bigger changes to the HWS path.  Most likely we will move the lenses on the HWS path.We have measured the current optic locations and we plan to move the HWS lenses tomorrow.

 

Details:

We located the image plane by applying a 0.05mHz, 2 microradian yaw to H1:SUS-ETMX/Y_M0_OPTICALIGN_Y_EXC .  We took 200 images with the HWS camera at .5 second intervals.  The images are located in /ligo/home/eleanor.king/HWS_Pictures/HWS_image_plane_X and /ligo/home/eleanor.king/HWS_Pictures/HWS_image_plane_Y.   We plotted the centroid of the beam vs time the images using the script 'find_image_plane2.m', which is attached.  We need to move the camera to where the centroid of the beam moves by and amplitude less than 0.2 pixels.  With the current lens locations, we would need to move the cameras by ~0.5m, which we don't have the room to do.  Instead we plan to move the lenses on the HWS table to move the conjugate plane.

Curernt HWS optic locations:

EY table layout with optics names as per https://dcc.ligo.org/D1400241
-All units are in cm.
-M3 was measured from the back face of the optic.
The distances between the optics at EY are:
BS1:M1    10.7 (cm)
M1:L1       7.7
L1:L2        61.0
L2:M2      12.3
M2:M3     9.6    
M3:M4     82.5
M4:M5     6.3
M5:L3      8.5
L3:M6      55.9
M6:CCD1 33.9

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

EX table layout is not the same as that in https://dcc.ligo.org/D1201448.
-  The lenses L1 and L2 are in different positions.  L1 is between M1 and L2, L2 is between L1 and M2, L3 is as drawn in D1201448.
-All units are in cm.
-BS1 is measured from the front face.  BS2 is measured from the back face.  M5 is measured from the front face.
The distances between the optics at EX are:
ALS-M11:BS1 6.5 (cm)
BS1:M1      32.7
M1:L1        10.6
L1:L2          62.6
L2:M2         20.1
M2:BS2      11.3
BS2:L3        62.9
L3:M3         11.2
M3:M4        10.2
M4:M5        63.3
M5:M6        31.1
M6:M7        9.9
M7:CCD1    11.5

Non-image files attached to this report
H1 ISC
daniel.sigg@LIGO.ORG - posted 17:09, Tuesday 07 April 2015 (17727)
Slow controls software update

The tidal code has been changed by adding a delay trigger to the red lock trigger and by requiring a lock condition to go into the red lock state. This should avoid the problem where the tidal state machine keeps switching states upon cavity flashes after a lock loss.

Prepared a change in the LSC/IMC model to enable the common tidal from MC_F using a switch after the MC_F filter module. This way we can switch on the common tidal feedback independently when the tidal state machine is in the transition state.

New slow controls code was loaded into the remaining EtherCAT systems to support automatic screen generation.

A new feature was added to the auxiliary library to allow momentary switching of its binary outputs. This has been implemented for the ESD power on/off channel to avoid the problem with the 4 second auto-reset when the channel was left in the high state by mistake. A high transition will now generate a one second long pulse which returns to low automatically.

LHO VE
bubba.gateley@LIGO.ORG - posted 16:42, Tuesday 07 April 2015 (17732)
Beam Tube Washing
Scott L. Ed P. Chris S.

Relocated lights and equipment to X-1-8 double doors north towards mid station yesterday.

Tested 8 sections as opposed to the normal 6 as this is the last and somewhat longer section from the double doors to mid station. Vacuumed beam tube supports and cleaned those same floor areas. Heavily soiled areas.  Able to clean only 6 meters yesterday and 64 meters of tube today.
Beam tube pressures monitored by control room operator during cleaning operations.  
LHO VE
kyle.ryan@LIGO.ORG - posted 16:38, Tuesday 07 April 2015 (17733)
HAM6 vent
(Kyle, Gerardo, Bubba, Jeff B., Betsy, Richard M.)

Kyle -> Soft-closed GV5 and GV7 

Kyle, Gerardo -> Connected pump cart to HAM5 annulus -> Vented HAM5/6 annulus volume 

Kyle, Gerardo -> Vented HAM6

Richard M. -> Troubleshot and fixed cabling to PT110A 

Kyle, Gerardo, Bubba, Jeff B., Betsy -> Removed HAM6 East door
H1 General
travis.sadecki@LIGO.ORG - posted 16:00, Tuesday 07 April 2015 (17726)
OPS Shift Summary

8:05 Kyle closing gate valves in vertex

8:10 Gerardo to LVEA assisting Kyle

8:12 Jim loading new isolation filters on HAM 2,3,4

8:21 Fil to EX, EY working on OpLev wiring

8:25 Vern and Richard to LVEA

8:28 Doug to LVEA OpLev test bed, moving to EX

8:33 Elli to EY HWS work

8:33 Jeff B to LVEA dessicant cabinet work

8:35 Hugh to HAM1 for L4C work

8:48 HAM6 picomotors shutdown for vent

9:20 Peter K to H1 PSL enclosure with Corey

9:31 Richard to LVEA checking Pirani gauge

9:33 Jeff B done

9:43 Vern out

9:49 Porta potty service on site

9:49 Betsy to LVEA

10:02 Jeff B to HAM6

10:13 Corey out

10:20 Hanford FD to LVEA

10:27 Cris and Karn to ends

10:52 Koji, Dan, Ross to HAM6

10:54 OMC and OMs to SAFE, HAM6 ISI to OFFLINE

10:55 PR3 light pipe install and align

11:01 Andres to West bay

11:05 Peter K done in H1 PSL, moving to H2 PSL

11:08 Andres done

11:37 Peter K done

11:58 Doug and Jason done at PR3 OpLev

12:03 Hugh done

12:05 HAM6 open for business

12:07 Elli done at EY

12:20 Dan, Koji, Keita, Corey to HAM6

12:37 Fil installing dewpoint cabling LVEA

12:47 Elli to EX for HWS work

12:58 Betsy to HAM6

13:08 Richard to LVEA

13:09 Betsy out

13:33 Sudarshan to EY for PEM work

13:40 Jeff B to HAM6

14:30 Doug and Jason to EY for OpLev work

14:45 Fil to LVEA retreiving tools

H1 General
jeffrey.bartlett@LIGO.ORG - posted 15:27, Tuesday 07 April 2015 (17728)
Particle Counts HAM6 Door Removal
   Attached below are the particle counts taken during the removal of the HAM6 East door. Counts were in line with expectations and in chamber counts below expectations. Checks with people working in and around the chamber all showed to be below the clean-100 levels. Last counts taken in the chamber this afternoon showed 10 0.3 micron and 0 for 0.5 and 1.0 micron particles. 
Images attached to this report
H1 General (PSL)
travis.sadecki@LIGO.ORG - posted 12:55, Tuesday 07 April 2015 (17725)
Diode room crystal chiller water level check

Checked the crystal chiller water level as per the OPS Tues. checklist.  Noted that it was filled on 4/3 (by Peter K, I assume) and that the level was midway between Min. and Max. level.  No water added.

H1 SEI (ISC)
hugh.radkins@LIGO.ORG - posted 12:41, Tuesday 07 April 2015 (17723)
WHAM1 HEPI H2 (SW Corner, Horizontal) L4C Exchanged

Replaced non-functioning L4C (L4-C) sn L41367 with L41365.  Looks okay, will continue testing.

How?  Deisolated platform.  Locked only corner2 foot to Caging brace (oh yeah, had to adjust rear caging brace to proper position) w/ ~5mil + bias from Ready state--the Actuators tend to pull a few mils (5-10) from the nominal shimmed position.  Disconnected Actuator from brackets but did not loosen brackets hoping this would help retain position.  This won't always work.  Shimmed and locked down actuator.  Disconnected Actuator from Foot.  Powered down Pier Pod, dewired, and removed it and the holder bracket (to get access to L4C Clamp bolts.)  Removed the two Horizontal Actuator Adapters.  Loosened the three L4C holder bolts, loosened the two L4C clamp bolts.  Left the L4C leveling shims in place since we really level the holder, not the L4C.  Pulled the L4C and clamped in the replacement.  Rewired to check spectra--looked okay.  Dewired again.  Reversed process: Actuator Adapters, Actuator to Foot (worked nicely, all the bolts went in smoothly,) Bolted Actuator to Brackets (Housing,) rewired Pier Pod.  Numbers look very similar to before.  Unlocked Actuator and removed shims.  Unlocked Foot--position within 200 counts of position before.  Reengaged Isolation, no problem.

Now the position could actually be different but I really don't think by much (a few mils at the worst) and I don't think ISC is that sensitive here.  But, feel free to drive it to where it is needed.

H1 AOS
jason.oberling@LIGO.ORG - posted 12:28, Tuesday 07 April 2015 - last comment - 16:27, Tuesday 07 April 2015(17722)
Optical Lever Maintenance

D. Cook, J. Oberling

ETMx

We moved the recently tweaked oplev laser (SN 197) from our testbed at HAM3 to ETMx.  This laser will thermally stabilize over the course of the afternoon, then we will start monitoring it to perform, if necessary, the final tweaks.  While we were at End X we installed the 50 lb. lead damper assembly onto the ETMx receiver pylon.  Due to the laser swap and the damper install, the oplev needed to be realigned, so we did that as well.

PR3

At the request of commissioners we realigned the PR3 optical lever.  While out there, we installed the light pipe support assembly (see attached picture) to keep the light pipe on the receiver from sagging.

Images attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 12:53, Tuesday 07 April 2015 (17724)

great!  that will make life easier.

jason.oberling@LIGO.ORG - 16:27, Tuesday 07 April 2015 (17731)

ETMy

We also finished tweaking another laser and considering the ongoing HAM6 work, and with commissioner approval, installed that in ETMy (SN 138-2).  We also installed the lead damper (see attached picture) and realigned the oplev (like ETMx, the laser swap and the damper installation changed the alignment of the oplev).  We will monitor this one as well as ETMx to see if we need to make any small tweaks to the laser power to maintain stability.

Images attached to this comment
H1 SEI
jim.warner@LIGO.ORG - posted 10:57, Tuesday 07 April 2015 (17720)
HAM ISI and restoring cart bias

I was taking HAM's 2-4 down this morning to install higher gain control loops. HAM's 2 and 4 went down and came right back up. HAM3 refused to re-isolate, and it took a while to figure it out. It turns out that HAM3 is restoring a large pitch (RY) offset, and Guardian is restoring this offset at roughly the same time it tries to engage the horizontal iso loops. When it does this it sends a large tilt to the GS13's and trips the ISI. Eventually I got around this by switching the GS13s to low gain, and the ISI came right up, whereupon I switched the GS13s back to high gain. A couple thoughts:

1. We should restore fewer DOFs on the HAM's. It wouldn't have prevented this particular problem, but the ISI doesn't wander much, the HAM's don't trip often. I also think that the commissioners probably only care about a few angular DOF's (sadly RY on HAM3 is probably one) and keeping  historical  x/y offsets only make isolating/de-isolating the ISI's and troubleshooting more difficult.

2. HAM3 is restoring a 4000 nrad offset. We should try to offload this to HEPI. Isolating and de-isolating HAM3 ISI is made more difficult by servoing to this position because it sends a big tilt to the GS-13s, which see it as translation.

3. If we can't risk shifting this offset, we should add GS-13 gain switching to the HAM's. Hugh found this sent an impulse to the BS, but that only mattered because it disturbed Mich. We only maybe need this on HAMs because of the need to restore ISI angular offsets (which we don't do on BSCs) and we don't need to switch while operating the IFO. The infrastructure exists, the SEI group may need to do a tiny bit of thought about how to implement it. We only need to switch when transitioning to and from isolated.

H1 SEI (SEI)
travis.sadecki@LIGO.ORG - posted 09:51, Tuesday 07 April 2015 (17719)
OPS: reset of HEPI L4C Accumulated WD Counters Tuesday 7 April 2015

I reset the accumulated WD counter for ITMX.  It had a count of 389.

H1 SUS
betsy.weaver@LIGO.ORG - posted 09:10, Tuesday 07 April 2015 - last comment - 13:36, Friday 10 April 2015(17635)
SR3 Acceptance TFs

Attached are the Phase 3b damped and undamped TFs of SR3 taken over the last few months.

 

The damped TFs of M1 are pretty squashed, but this is because there is some pretty heavy damping filtering engaged for commissioning.

Non-image files attached to this report
Comments related to this report
betsy.weaver@LIGO.ORG - 16:07, Thursday 09 April 2015 (17781)

Spectra are attached.

 

SR3 acceptance should be accepted.

Non-image files attached to this comment
stuart.aston@LIGO.ORG - 13:36, Friday 10 April 2015 (17802)
I've now added comparison plots for SR3 Phase 3b acceptance TFs measurements for each stage have been compared with similar L1 and H1 suspensions, as follows:-

- SR3 M1-M1 undamped & damped results (allhltss_2015-04-10_Phase3b_H1HLTSs_M1_D*_ALL_ZOOMED_TFs.pdf)
- SR3 M2-M2 undamped & damped results (allhltss_2015-04-10_Phase3b_H1HLTSs_M2_D*_ALL_ZOOMED_TFs.pdf)
- SR3 M3-M3 undamped & damped results (allhltss_2015-04-10_Phase3b_H1HLTSs_M3_D*_ALL_ZOOMED_TFs.pdf)

Summary:

M1-M1, undamped TFs are consistent with model and similar suspensions. Damped TFs demonstrate R, P & Y DOFs for H1 SR3 are the most aggressively damped of all HLTSs.

M2-M2, undamped TFs taken are consistent with model and similar suspensions. Damped TFs exhibit some expected deviation between sites.

M3-M3, undamped TFs suffering poor coherence below 0.5 Hz, both H1 HLTSs perform consistently. n.b. L1 SR3 can be seen to be weaker due to missing LL magnet (Integration Issue #175).

Therefore, these TFs raise no concerns for SR3.

All data, scripts and plots have been committed to the sus svn as of this entry.
Non-image files attached to this comment
H1 General
peter.king@LIGO.ORG - posted 07:28, Tuesday 07 April 2015 (17718)
LVEA Transition To LASER SAFE
07:28    The LVEA has transitioned to LASER SAFE to facilitate the removal of the doors from HAM6.
H1 ISC
evan.hall@LIGO.ORG - posted 04:45, Tuesday 07 April 2015 (17715)
Single bounce for HAM6

In preparation for today's work in HAM6, the inteferometer has been left in a single bounce configuration, with the spots in HAM6 centered on their respective QPDs.

I had to move the OMs a bit. The original slider values are as follows:

  P Y
OM1 -643.0 -484.0
OM2 899.0 656.0
OM3 -423.3 644.1

The new slider values are as follows:

  P Y
OM1 -575.0 -523.0
OM2 902.0 700.0
OM3 -414.3 631.1
H1 ISC (PSL)
evan.hall@LIGO.ORG - posted 03:45, Tuesday 07 April 2015 - last comment - 16:16, Tuesday 07 April 2015(17712)
35 kHz CARM UGF

Sheila, Evan

Summary

By increasing the gains on the common-mode and IMC boards, we pushed the CARM UGF up to 35 kHz and saw a reduction in the high-frequency noise floor of DARM.

Some further loop tuning is required to make this viable as a long-term change.

Details

Based on Sheila's earlier measurement of the IMC OLTF, we felt it was safe to increase the gain at the IMC error point (both the error signal and the AO) by 2 dB. Then we increased the CARM gain by 6 dB (using the IN2 slider on the CM board). These changes gave a UGF of 35 kHz with 25° of phase. [See plot and zip file.]

This gave a noticeable improvement in the frequency noise as seen by REFL_A 9I, which is currently the out-of-loop CARM sensor. [See plot.]

Consequently, there was a small but noticeable improvement in the high-frequency noise floor of the DARM spectrum. [See plot with red and gold, taken while still feeding DARM back to ETMX.] In the full locking configuration, the noise floor now touches the GWINC curve from 300 Hz to 3 kHz [See plot with purple.]

Obviously this CARM phase margin is quite thin, and we don't want to run like this as a matter of course. In order to win more phase, perhaps we need to look at the IMC loop and the FSS. Peter K last measured the FSS UGF to be 200 kHz with 30° of phase (on the low end of the phase bubble). In comparison, at LLO the FSS UGF is 500 kHz with 60° of phase.

More details

Nominal gains are 0 dB for CM IN2 [the CARM error signal], 5 dB for MC IN1 [the IMC error signal], and 0 dB for MC IN2 [the AO signal].

The gains used here are 6 dB for CM IN2, 7 dB for MC IN1, and 2 dB for MC IN2.

At the start of the evening, REFL_A 9I had no whitening filters engaged and 0 dB of whitening gain. It now has 1 stage of whitening, 21 dB of gain and a −21 dB filter engaged in FM4 (I and Q). There is some saturation during the lock acquisition, but in full lock the I and Q inputs are now at least a factor of 5 in ASD above the ADC noise floor everywhere. I also changed the digital phase rotation from 77° to 90°, as was hinted at earlier.

Images attached to this report
Non-image files attached to this report
Comments related to this report
evan.hall@LIGO.ORG - 04:18, Tuesday 07 April 2015 (17714)

The above work was done as usual with CARM controlled by REFLAIR.

However, in-vac REFL will also work for controlling CARM. The following screenshot shows the settings required and an OLTF of the CARM loop.

This has the unfortunate effect of making the DARM spectrum worse at high frequencies; a broad lump appears between 2 and 5 kHz. More investigation required.

Images attached to this comment
evan.hall@LIGO.ORG - 16:16, Tuesday 07 April 2015 (17730)

A noise budget of this morning's lock is attached, and includes intensity and frequency noise. For the coupling TFs I used what Koji and I measured previously.

This isn't our most sensitive lock in terms of inspiral range, in part because of the bump around 100 Hz. This is new as of a few days ago, and we are hoping it's just the HAM6 cleanroom.

The intensity noise is taken from IM4 trans, and the frequency noise from REFL_A 9I.

From the spectra shown in the parent entry, the noise in REFL_A 9I from 40 Hz to 2 kHz is mostly flat, and does not scale with CARM loop gain. It could be that the CARM loop is limited by sensor noise (e.g., from REFLAIR_A), or that it is just masked by noise in REFL_A. So the frequency noise trace in this plot should be taken as an upper limit between 40 Hz and 2 kHz.

In the future, when measuring intensity noise we should perhaps do what Alexa suggested and use the ISS second loop PD array as an out-of-loop sensor, since it is acquired faster than IM4 trans.

Non-image files attached to this comment
H1 AOS
betsy.weaver@LIGO.ORG - posted 16:46, Monday 06 April 2015 - last comment - 06:21, Tuesday 07 April 2015(17703)
SUS SDF update effort

Today I started hacking through the weeds that had grown up the SUS SDFs for the last 2 unattended weeks.  While I still have more pruning to do, I addressed:

- ODC DAMP GOOD state updates on medm and SDF where DIFFs were found - likely more tidy up needed per sus.

- Low noise BIO/COIL changes 17504 and 17478.

- Cleaned up SUS TEST banks (ignoring GAIN, OFFSET, TRAMP values, but continuing to watch SW1 and SW2 for when bank gets left on)

- Found lots of LIMITs engaged, so wrote their values into the safe.snap

- Set SDF to ignore SW2 of many LOCK and TEST banks which were in SDF DIFF state since now SUS GRD aligns and misaligns via these, alog 17259.  Reenabled SW1 monitoring in many cases where inputs will remain enabled now.  Where alignment offsets were written into TEST banks, I've written the values into the sus snap.safe.

- Zeroed out the R0 P TEST OFFSET of 200 that Keita put in a long time ago and inadvertently got written into the ETMx safe.snap and subsequently reenabled.  These should be off, 16865 - Today I turned the R0 P offset off, again.  Also, the R0 Y TEST bank offset (0.0) was enabled so I turned that off.  Our understanding is that no R0 chain offsets should be enabled.

Comments related to this report
jeffrey.kissel@LIGO.ORG - 06:21, Tuesday 07 April 2015 (17716)ISC, SEI
One more thing to highlight from this effort: all settings in the OMC and OMs in HAM6 have been captured, and there are no longer any differences with the table. Thus, this will be a reference point to get back to after the vent and/or we can monitor what has been done while in chamber such that we understand all that has changed during the vent.

Note, I attach the lists of channels that are currently *not* monitored by the SDF system so we're aware of what *won't* be tracked. 
Images attached to this comment
H1 SEI
jim.warner@LIGO.ORG - posted 13:30, Monday 06 April 2015 - last comment - 06:49, Tuesday 07 April 2015(17699)
ETMX ISI switched to windy configuration

Per JeffK's request, I have switched ETMX to the "windy" configuration. The ISI was already running the 90mhz blend since sometime this weekend. I've now also engaged the low frequency sensor correction on the X direction with the BRS turned on. I've been fiddling a little with the Z blend filters on St1, adding low pass filters to the 90mhz Z blend, but it doesn't seem to affect the St2 performance much. I'll post more on that in a bit.

Comments related to this report
jeffrey.kissel@LIGO.ORG - 14:39, Monday 06 April 2015 (17701)
Our goal is to prove that not only can this X DOF "windy" configuration (90 mHz blend, broadband, low-frequency sensor correction, with the BRS) replicate the performance of ISI in its "nominal" X DOF configuration (45 mHz blend, narrow-band 0.43 [Hz] sensor correction, no BRS), but it can do *better* than the nominal configuration during high winds.

As such, we want to compare three different configurations:
(1) Nominal ("45 mHz blend, derosa 0.43 Hz only sensor correction, no BRS") [we should already have plenty of this data]
(2) Windy when BRS doesn't work ("90 mHz blend, derosa 0.43 Hz only sensor correction, no BRS") [we may already have plenty of this data]
(3) Windy with a functional BRS ("90 mHz blend, mittleman broadband low-frequency sensor correction, BRS on") [what we'll get now, hopefully if the winds pick back up]

We've got some more of configuration (2) this morning, 
2015-04-06 16:00 UTC to 17:00 UTC -- winds were max ~25 [mph]
so that will be great fodder to compare what Jim's put the ETM ISI into now ( configuration (3) ).

And for the record, it was switched into this configuration (3) at 2015-04-06 21:10 UTC. Now we just need the winds to pick up again...
Images attached to this comment
jeffrey.kissel@LIGO.ORG - 06:49, Tuesday 07 April 2015 (17717)
Ask and ye shall receive!

Just after Jim switched to configuration (3) described above, the winds picked back up to > 20 [mph] for an hour or so -- see attached screenshot (note that I've plotted the mean minute trend over 24 hours; I would plot the max as well, but my remote trending abilities are limited). Thus, a good time to use in the above described comparison for config (3) is from 2015-04-06 21:30 UTC to about 23:30 UTC, plenty of time for several averages of a low frequency ASD.
Images attached to this comment
H1 AOS (AOS, IOO)
suresh.doravari@LIGO.ORG - posted 16:48, Friday 03 April 2015 - last comment - 12:18, Tuesday 07 April 2015(17676)
oplev laser installed in HAM3 Oplev for testing

[Ed. Merilh, Jason Oberling, Doug Cook, Suresh D]

 

Doug replaced the diode laser at the HAM3 oplev this morning after it was fixed for reducing glitching (SL No. 197) in the optics lab 2.   We wanted to let it settle for a while and reach thermal equilitbrium before adjustting the power level.  We did that around 12:30PM and I checked the results around 4PM.  The laser is still settling down  as seen in the attached plots.  We plan to monitor it for another day. 

Images attached to this report
Comments related to this report
suresh.doravari@LIGO.ORG - 15:22, Monday 06 April 2015 (17705)

Sl. No. 197 Diode laser  requires readjustment of power.

Please see the two attached plots.

1) The first shows short term trends of the laser power as obtained from the HAM3_OPLEV_SUM_IN1_DQ channel.  The first panel shows the RIN spectrum.  Note the two orders of increase in when we go below 1Hz towards 0.1Hz.  This indicates power instability at low frequencies  (A signature of glitching).  The second panel of this attachment shows hte time trend of this signal which shows gradual increase in glitch rate after the first hour or so.  The laser is moving from a low glitch rate to a high glitch rate power level due to thermal changes.  The third panel shows the same info in greater graphic detail with time evolution of the spectrum (spectrogram)

2) The second attachment is a long term 1s trend of the same SUM signal.   It shows that the initial power setting was okay and had few glitches if any.  However the power dropped over the following half a day and moved to an unstable zone.  It stabilised there and continued to glitch because it has landed at the edge of a stable zone and is now mode hopping.

 

Cure:  Increase power from 47900 SUM counts to  48500 counts.  Further one day of observation to see if it has worked.

Images attached to this comment
suresh.doravari@LIGO.ORG - 12:18, Tuesday 07 April 2015 (17721)

Oplev Laser Sl No. 197 has been shifted to ETMX oplev.

 

The diode laser Sl No. 197 which was under observation at HAM3 oplev has been performing well for the past six hours.  There were a few minor glitches after Tuesday morning maintenance started.  This could have been some heavy stuff moving around on the floor and disturbing the HAM3 Oplev Transciever.   The behaviour over six hours has been summarised in the attached plots of amplitude spectrum, time series and spectrogram.

Images attached to this comment
Displaying reports 68621-68640 of 85883.Go to page Start 3428 3429 3430 3431 3432 3433 3434 3435 3436 End