Displaying reports 55921-55940 of 83394.Go to page Start 2793 2794 2795 2796 2797 2798 2799 2800 2801 End
Reports until 14:48, Thursday 07 July 2016
H1 ISC (ISC)
carl.blair@LIGO.ORG - posted 14:48, Thursday 07 July 2016 (28243)
Switched OMC PI damping to DCPD HF

Due to the inability so far to damp the 18040Hz mode I have switch the PI damping to the DCPD HF path.

H1 CDS (OpsInfo)
thomas.shaffer@LIGO.ORG - posted 12:02, Thursday 07 July 2016 (28237)
Newest "Version" of VerbalAlarms is now running

I changed up a few things such as:

If there is any problem with this version, please don't hesitate to go back one revision.

H1 PSL (PSL)
peter.king@LIGO.ORG - posted 11:09, Thursday 07 July 2016 (28226)
FSS transfer functions
Attached are plots of the transfer functions measured this morning.  The input modecleaner
was disabled whilst these measurements were obtained.

    Note the frequency servo schematic is D040105

C20F22-1.tif: common gain = 20 dB, fast gain = 22 dB
C20F16-1.tif: common gain = 20 dB, fast gain = 16 dB

C20F22FastMon.jpg: transfer function measured at TP10
C20F22PCMon.jpg: transfer function measured at TP9
C20F22TP8.jpg: transfer function measured at TP8 (should be 10X greater than TP9 measurement)
               common gain = 20 dB, fast gain = 22 dB

C16F22TP8.jpg: transfer function measured at TP8, common gain = 20 dB, fast gain = 22 dB
C16F22TP9.jpg: transfer function measured at TP9, common gain = 20 dB, fast gain = 22 dB

C20F16TP9.jpg: transfer function measured at TP9, common gain = 20 dB, fast gain = 16 dB
C20F16TP8.jpg: transfer function measured at TP8, common gain = 20 dB, fast gain = 16 dB

C20F16TP3Spectrum.jpg: noise measured at TP3 (the mixer monitor, or error point)
                       common gain = 20 dB, fast gain = 16 dB
C20F22TP3Spectrum.jpg: noise measured at TP3, common gain = 20 dB, fast gain = 22 dB

CrossoverSpectrum.jpg: has the two noise spectra overlapped for a visual comparison.
Images attached to this report
H1 General
cheryl.vorvick@LIGO.ORG - posted 11:08, Thursday 07 July 2016 (28233)
running alog on status of H1 is alog 28222
LHO VE
chandra.romel@LIGO.ORG - posted 11:05, Thursday 07 July 2016 - last comment - 11:07, Thursday 07 July 2016(28229)
CP smoothing factor
The smoothing factor was set to 0.999 on all CPs. To confirm that the device is still active and responding and not in an "inactive state" (which happens if smoothing factor is set to its limit of 1.0), the LLCV trends over 30 days are posted for the seven CPs (CP3 excluded).

The smoothing factor algorithm (from EPICS integrated into Beckhoff):

if SMOO is 0 or INIT is True, VAL = val
else VAL = val * (1 - SMOO) + Previous_vale * SMOO

*this implements a first-order infinite impulse response (IIR) digital filter with z-plane pole at tau=-T/ln(SMOO), where T is the time between record processing

Images attached to this report
Comments related to this report
chandra.romel@LIGO.ORG - 11:07, Thursday 07 July 2016 (28232)


		
		
Images attached to this comment
H1 General (AOS, SEI, SUS)
travis.sadecki@LIGO.ORG - posted 09:36, Thursday 07 July 2016 (28224)
Optical Lever 7 Day Trends

Attached are screenshots for the past 7 days of optical lever trends for PIT, YAW, and SUM.

This completes FAMIS request 4683.

Images attached to this report
H1 General
cheryl.vorvick@LIGO.ORG - posted 09:15, Thursday 07 July 2016 - last comment - 14:53, Thursday 07 July 2016(28222)
H1 Update: work on laser is done, locking full IFO resumes

Peter was in the PSL enclosure and looking at the FSS - his alog will give details.

He's done so I'm starting to lock.

Comments related to this report
cheryl.vorvick@LIGO.ORG - 09:36, Thursday 07 July 2016 (28223)

DRMI locked at 16:36UTC

cheryl.vorvick@LIGO.ORG - 09:46, Thursday 07 July 2016 (28225)

POP X PZT railed, but POP signal is still centered on the QPD, so this is on the "to be fixed" list, but does not prevent locking. POP X is accessable from the ASC overview screen.

cheryl.vorvick@LIGO.ORG - 10:18, Thursday 07 July 2016 (28227)

in DC READOUT TRANSITION, OMC guardian was stuck in DOWN, and was unstuck by running it through INIT.

cheryl.vorvick@LIGO.ORG - 10:35, Thursday 07 July 2016 (28228)

I unintentionally killed the lock by requesting the INCREASE POWER state in ISC_LOCK.  

I thought this would just stop the ISC_LOCK guardian in this state, keeping the input power at 38W.

Instead it reran the code for INCREASE POWER from the beginning and lowered the input power to 10W, killing the lock.

cheryl.vorvick@LIGO.ORG - 10:52, Thursday 07 July 2016 (28230)

Broken:

So I thought the power was going to increase to 50W, based on what the LASER_POWER guardian main screen was showing, however TJ explained that the guardian can only request so many states, so the power was going to stop at 40W but the guardian could not show that because 40W was not a requestable state.

Fixed:

TJ rewrote the LASER_POWER guardian to make 40W a requestable state, so when we're going to 40W it will show this.

TJ also set the ISC_LOCK to stop at 25W input power on out next lock.

cheryl.vorvick@LIGO.ORG - 11:07, Thursday 07 July 2016 (28231)

Currently, we have the IMC locked and at 40W input power.

Keita is looking at the ISS Second Loop and measuring the correct offset for 40W.

cheryl.vorvick@LIGO.ORG - 11:32, Thursday 07 July 2016 (28234)

18:32UTC - adjustments made for running at 25W are complete - now relocking H1

cheryl.vorvick@LIGO.ORG - 11:43, Thursday 07 July 2016 (28235)

DRMI locked at 18:43UTC

cheryl.vorvick@LIGO.ORG - 12:13, Thursday 07 July 2016 (28238)

19:12UTC - H1 in DC readout and heading to ENGAGE ISS 2nd loop

cheryl.vorvick@LIGO.ORG - 12:59, Thursday 07 July 2016 (28239)

19:58UTC -------------

H1 made it to ENGAGE ISS 2ND LOOP which is good, because getting to the point where we could engage the 2nd loop is progress, however engaging the loop revealed an issue which broke the lock.  

Jenne and Keita are looking into it.

******** my estimate of having H1 in Observer was a bit optomistic - 4PM today (23:00UTC) is more likely.

cheryl.vorvick@LIGO.ORG - 14:06, Thursday 07 July 2016 (28240)

21:04UTC - locked and going to ENGAGE_ISS2ND_LOOP without engaging the loop, to do measurements

cheryl.vorvick@LIGO.ORG - 14:13, Thursday 07 July 2016 (28241)

lockloss

cheryl.vorvick@LIGO.ORG - 14:53, Thursday 07 July 2016 (28244)

last entry for this log:

21:52UTC - H1 is back in ENGAGE ISS 2ND LOOP with the ISS 2nd loop disabled.

Keita and Jenne are looking for a fix, so H1 can go to Observe.

Displaying reports 55921-55940 of 83394.Go to page Start 2793 2794 2795 2796 2797 2798 2799 2800 2801 End