Displaying reports 52881-52900 of 83308.Go to page Start 2641 2642 2643 2644 2645 2646 2647 2648 2649 End
Reports until 10:03, Monday 07 November 2016
H1 PEM (PEM)
corey.gray@LIGO.ORG - posted 10:03, Monday 07 November 2016 - last comment - 11:05, Monday 07 November 2016(31278)
H1 Dropped Out Of OBSERVING By Excitation!

This morning H1's Intent Bit was taken out of UNDISTURBED.  I quickly asked around for any activities going in the Control Room and no one admitted to anything.  I tooke it back to UNDISTURBED and about 30sec later we dropped out again!

For the 2nd drop, I happened to be watching the Guardian Overview & noticed the message:  "EXC:  pemmx excitation!" on the DIAG_EXC Guardian Node.  The Log for this node said we had this excitation at:

WHAT IS THIS??  

Is this an automated excitation?  

If this is an acceptable excitation, can we remove this as a channel SDF monitors to knock us out of UNDISTURBED?

Comments related to this report
james.batch@LIGO.ORG - 10:34, Monday 07 November 2016 (31281)
I did that, testing a diaggui issue.  The PEM-MX_CHAN channels are not connected to an AI chassis, so it has been a convenient place to run tests that can't disturb anything.  I'll refrain from doing so in the future.  
keita.kawabe@LIGO.ORG - 11:05, Monday 07 November 2016 (31284)

Corey, any excitations except calibration and hardware injections should (and in this case did) kick us out of observation. Don't remove this channel out of guardian's watch list.

H1 PSL (PSL)
patrick.thomas@LIGO.ORG - posted 09:09, Monday 07 November 2016 (31276)
PSL Weekly Report
Laser Status:
SysStat is good
Front End Power is 34.64W (should be around 30 W)
Front End Watch is GREEN
HPO Watch is GREEN
PMC:
It has been locked 1.0 days, 11.0 hr 50.0 minutes (should be days/weeks)
Reflected power is 26.42Watts and PowerSum = 125.8Watts.

FSS:
It has been locked for 0.0 days 10.0 hr and 37.0 min (should be days/weeks)
TPD[V] = 3.567V (min 0.9V)

ISS:
The diffracted power is around 3.384% (should be 5-9%)
Last saturation event was 0.0 days 10.0 hours and 37.0 minutes ago (should be days/weeks)

Possible Issues:
PMC reflected power is high
LHO General
corey.gray@LIGO.ORG - posted 08:55, Monday 07 November 2016 (31272)
Morning 8:30 Meeting Notes

Discussion of weekend's activities & then going through the subsystems.

Work Permit Review.

Tues Maintenance Outlook:

H1 General
jim.warner@LIGO.ORG - posted 08:02, Monday 07 November 2016 (31271)
Owl Shift Summary

TITLE: 11/07 Eve Shift: 08:00-016:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: NLN
SHIFT SUMMARY:  Locked all shift. PIs were a challenge at the beginning, but mode 27 finally settled down after turning the the gain from 5000 to 4000
LOG:

Locked all shift.

H1 General
travis.sadecki@LIGO.ORG - posted 00:00, Monday 07 November 2016 (31270)
OPS Eve Shift Summary

TITLE: 11/07 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Jim
SHIFT SUMMARY:  Locked on and off all shift.  No major issues other than PI modes ringing up.  At one point, I had 2 modes ring up simultaneously and could not effectively damp either one.  Microseism is trending down below 0.3 um/s.  Wind is calm.
LOG:

1:29 lockloss, HAM 6 ISI and OMC WD tripped

2:16 EX HEPI and ISI WD tripped, possibly due to 5.0 EQ in OK that rang up very quickly

3:16 Observing

3:26 Out of Observing to turn off SRC1 P loop and damping PI modes

4:30 Observing

4:44 lockloss

6:13 Observing

6:29 lockloss, 2 PI modes ringing up, could not damp either one

7:30 Observing

 

H1 ISC
stefan.ballmer@LIGO.ORG - posted 17:13, Sunday 06 November 2016 (31269)
TCS settings reverted at Nov 07 2016 01:11:00 UTC

Since we didn't see any benefoit from reverting to May TCS setting, I dialed back the November settings, namely:

H1:TCS-ITMX_CO2_LASERPOWER_POWER_REQUEST => 0.3
H1:TCS-ITMY_CO2_LASERPOWER_POWER_REQUEST => 0.0
H1:TCS-ITMX_RH_SETUPPERPOWER => 0.25
H1:TCS-ITMX_RH_SETLOWERPOWER => 0.25
H1:TCS-ETMX_RH_SETUPPERPOWER => 0.75
H1:TCS-ETMX_RH_SETLOWERPOWER => 0.75
H1:TCS-ITMY_RH_SETUPPERPOWER => 0.25
H1:TCS-ITMY_RH_SETLOWERPOWER => 0.25
H1:TCS-ETMY_RH_SETUPPERPOWER => 0.75
H1:TCS-ETMY_RH_SETLOWERPOWER => 0.75
H1:TCS-ITMX_CO2_LASERPOWER_COMMAND => 2
H1:TCS-ITMY_CO2_LASERPOWER_COMMAND => 2
 

This happened at at Nov 07 2016 01:11:00 UTC

H1 ISC
stefan.ballmer@LIGO.ORG - posted 16:45, Sunday 06 November 2016 (31268)
back on REFL WFS and beam diverter closed (again)

Noticed that the guardian left us on POP_X with the POP Beam Diverter open. We know this makes us susceptable to scatter, so we are back on REFL WFS.

The Guardian was checked into SVN.

H1 ISC (DetChar, ISC)
hang.yu@LIGO.ORG - posted 16:13, Sunday 06 November 2016 (31267)
searching ASC modulation of the range fluctuations

We did a bit more analysis on the range drop reported in alog 30790

We computed the DARM (using GDS-CALIB_STRAIN) asd every 16 sec and recorded the height of each freqency bin (width = 1 Hz per bin) from 30-1000 Hz. At the same time, we also recorded the mean value of ASC control signals for that 16 sec segment. Then we correlated the darm high frequency peaks with the low frequency ASC control signals to see if we could id. the channels that modulated darm, which might further help the id. of scattering position. 

We used the data starting from Oct 24 11:00:00 UTC for ~2 hr (8096 sec), which should cover the entire period of the range drop. The darm peaks we focused on were the 48 Hz one and the 84 Hz one. 

For the 48 +- 0.5 Hz darm bin, the ASC channels showed most coherence were: OMC_B_PIT, MICH_Y, AS_C_PIT, SRC2_P.

For the 84 +- 0.5 Hz bin, the most interesting channels were: PRC2_Y, MICH_P, AS_C_PIT, SRC1_P

Images attached to this report
LHO General
corey.gray@LIGO.ORG - posted 16:11, Sunday 06 November 2016 (31258)
Ops Day Shift Summary

TITLE: 11/06 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Travis
SHIFT SUMMARY:

Spent most of the day attempting locks with the ITM Ring Heaters OFF (I took a step back by turning them on a couple of times).  Stefan still has us in this configuration--one note is that MODE27 rings up fast in this state!  Currently, taking its gain to 0 slows it down (& then finding a better gain is the current recipe to address this MODE).

LOG:

H1 ISC
stefan.ballmer@LIGO.ORG - posted 15:36, Sunday 06 November 2016 (31266)
Running with May 15 TCS settings (Ring heaters and CO2)

The ITM ring heaters were switched off on 2016/11/06 13:55 UTC (with two accidental short streches reangaging them 17:27-17:38, and 18:48-18:53 UTC).

The ETM ring heaters were set to 0.5W per segment (1W total) [from 0.75W/segement - 1.5W total] on 2016/11/06 19:14 UTC

Additionally, we set the in-lock CO2 TCS settings to 0.268W (X-arm) and 0.068 (Y-arm).

This corresponds to the setting we had during the 5h long nice lock at 25W with hardly any couplings at higher frequencies.

Operationally, the main difference were:

 - Our current PI settings drive mode 27 unstable - just shutting off the feed-back prevents runaway.

 - the SRC1 ASC loop goes unstable about 1h into the lock. THis behaviour is familiar for past operation. For our noise test we can simply shut SRC1 down temporarily.

 

 

Attached are plots of calibrated DARM, as well as DCPD cross power spectra (not corrected fro the closed-loop gain).

Note that the TCS revert did NOT result in lower noise couplings above 200Hz. (In fact, it seems somewhat worse than the November settings - but that might just be due to more duning in the November state).

Bottom line: It is still a mystery to me why the jitter noise above 200Hz was 3x to 5x better in May.

Images attached to this report
H1 AOS
robert.schofield@LIGO.ORG - posted 13:38, Sunday 06 November 2016 (31264)
80 Hz peak

The 80 Hz peak was not present in any of the spectra I looked at before the last lock on the 31st of Oct. UTC. Starting with the next lock on Nov. 2, it was always present in spectra that I looked at.  Possible sources of changes in the alog include PMC and ILC modifications, PSL polarizer work, problems associated with CO2Y, changes in PMC locking electronics, and, of course, alignment changes. I did a quick re-check for new scattering sites from alignment changes, but found nothing.

H1 AOS
robert.schofield@LIGO.ORG - posted 13:36, Sunday 06 November 2016 (31263)
Move of hot PZT box on PSL table

I did a preliminary test of the effect of hot electronics near the beam path on the PSL table (https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=31190). The plot shows an apparent increase in range after the move from close to the beam path to further away, with the move indicated by the spike on an accelerometer. I used a quick intrusion into the PSL, moving very quietly and with 50% fan speed and 100% makeup air, and we didn’t loose lock. There was a broad band decrease below 100 Hz, but also a decrease in a peak at about 65, so I am not completely convinced. I need to do multiple close/far cycles to be convinced, but we didn’t have time. In any case, I left the PZT power box in the far position.

Non-image files attached to this report
H1 PEM
robert.schofield@LIGO.ORG - posted 12:53, Sunday 06 November 2016 (31261)
Black glass at ETM port study

I studied the effect of black glass in the manifold ports at Y-end, comparing black glass in all six ports to no blocks in any port. I compared both with no injection, Figure 1, and with an acoustic injection that excited scattering peaks normally a little below the DARM floor, Figure 2. No effect was seen. I didn’t have time to do the complete multi-port study at X-end, but I had to excite more there to bring up scattering peaks, so I think there is somewhat less of a potential problem there. I left one of the new black glass blades in the Pcal camera port at each end station, though I had found no evidence of a problem at either station.

Images attached to this report
H1 General
corey.gray@LIGO.ORG - posted 10:39, Sunday 06 November 2016 - last comment - 10:45, Sunday 06 November 2016(31259)
4th Lock Attempt: Another PI#27/SRC Pit CONTROL Lockloss

For this lock, kept Ring Heaters OFF for the ITMs & went only to 25W.  Robert was optimistic and started to head out to EX (I transitioned the ISI_CONFIG to WINDY_NOBRSX).  For this lock the range was fairly noisy(between 50-70Mpc).  

Comments related to this report
corey.gray@LIGO.ORG - 10:45, Sunday 06 November 2016 (31260)

Turning ITM Ring Heaters back ON.

H1 General
corey.gray@LIGO.ORG - posted 09:43, Sunday 06 November 2016 - last comment - 10:31, Sunday 06 November 2016(31256)
3rd Lock Attempt So Far....Knock On Wood

For this current lock (15min so far):

Comments related to this report
corey.gray@LIGO.ORG - 10:31, Sunday 06 November 2016 (31257)

After 20 minutes, we dropped out of lock.  (ITMy did not oscillate after.)

Seconds prior to the lockloss:

  • VERBAL noted that PI Mode 27 was ringing up---& it was ringing up super-fast.  
  • Another possibly related effect was the the SRC 1 & 2 Pitch CONTROL signals were both trending up a few minutes before the PI Mode 27 started its ring up.
  • See attached StripTool!

Will attempt another lock with the ITM Ring Heaters OFF from the get-go.

Images attached to this comment
H1 PSL
sheila.dwyer@LIGO.ORG - posted 22:25, Saturday 05 November 2016 - last comment - 18:10, Tuesday 16 March 2021(31245)
ISS second loop offsets, DBB, PSL rack grounding problems?

Travis, Sheila

Tonight we saw more pathological behavoir in the PSL electronics.

Robert wanted to do a test of powering down the DBB, so he switched the power supply that sits on top of the DBB chassis off and unplaggued the DIN connector from the back.  After this, engaging the ISS second loop caused the diffracted power to drop from almost 5% to less than 0.5%, which caused locklosses as we tried to increase power. 

We tried to let the offset adjustment servo (30932) run for a while, but this didn't help. 

We plugged back in the DBB so we could get back to locking, but doing so tripped the PSL external shutter. 

Comments related to this report
sheila.dwyer@LIGO.ORG - 01:48, Sunday 06 November 2016 (31248)

We've continued having trouble with the ISS second loop introducing a large offset into the ISS, although it is not as bad with the DBB plugged back in. 

The attached screenshot shows the AC coupled ISS second loop moving the diffracted power by almost 2% as we power up, so we need to be able to keep the diffracted power high enough that we don't saturated while powering up.  Right now turning on the second loop decreases the diffracted power by about 4%, so we are just setting it high to start with.

Images attached to this comment
robert.schofield@LIGO.ORG - 08:17, Sunday 06 November 2016 (31252)

In addition to electronics problems, there is also a chance that there might be alignment differences in the beam path next to the DBB when it is shut off since it is 4 degrees warmer than the table.

daniel.sigg@LIGO.ORG - 12:57, Sunday 06 November 2016 (31262)

How to adjust the diffraction power (when out of lock):

  • Make sure the second loop is in its down state. This means only the input switch is off. The output switch is on as well as its input into the first loop board.
  • Make sure the excitation input is enabled and the AC coupling servo switch is on (shouldn't do anything, since the input switch is off).
  • In this state, the output offset should be continuously zeroed by the offset servo. Just check that the second loop output readback reads near zero.
  • Adjust the REFSIGNAL of the first ISS loop, so that you roughly have 4% diffracted power.
  • Turn second loop on with the input switch (the IMC needs to be locked).
  • In the AC Coupling medm screen there is an input offset (top left). Adjust it so that the diffracted power stays at 4%.
  • Toggle the input switch and make sure that the diffracted power doesn't change.
jeffrey.kissel@LIGO.ORG - 18:06, Monday 28 November 2016 (31942)IOO, OpsInfo
 How to adjust the diffraction power (when out of lock) -- translated with screenshots of the relevant MEDM screens, and with the language color coded to match the colored highlighted boxes on the screenshots:

   - Make sure the second loop is in its down state. This means only the input switch is off. The output switch is on as well as its input into the first loop board.
   - Make sure the excitation input is enabled and the AC coupling servo switches are on (shouldn't do anything, since the input switch is off).
   - In this state, the output offset should be continuously zeroed by the offset servo. Just check that the second loop output readback reads near zero.
   - Adjust the REFSIGNAL of the first ISS loop, so that you roughly have 4% diffracted power.
   - Turn second loop on with the input switch (the IMC needs to be locked).
   - In the AC Coupling medm screen there is an input offset (top left). Adjust it so that the diffracted power stays at 4%.
   - Toggle the input switch and make sure that the diffracted power doesn't change.
Images attached to this comment
jenne.driggers@LIGO.ORG - 18:10, Tuesday 16 March 2021 (58265)

These instructions are outdated.  The ISS second loop board has been modified since these were written.  Please see new instructions at alog 58264.

H1 AOS
robert.schofield@LIGO.ORG - posted 21:30, Saturday 05 November 2016 - last comment - 13:41, Sunday 06 November 2016(31243)
More CP movements

I don't think I had focussed the input arm cameras yet when Sheila made this log about moving CPs, https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=30979, so I offset CPY to see if I could see where the light was hitting. I could see a moving spot on an apparent table weight in front of the PR2 scraper baffle (screenshots show nominal and pitch of -150 on CPY, bright spot is at the very bottom of nominal image). However, I could not see it on the "swiss chese" baffle in front of HAM2 when I looked through a viewport, so it is likely dumped on the vacuum enclosure near HAM3 or the "eye" baffle between HAM3 and the long IMC tube, and from there reflects onto HAM3. Sheila's 0.1 Hz excitations did not show that this was a current problem. Nevertheless, from looking at the camera, I agree with her that a lower-scatter parking place is at CPY pitch < -70. This might also give us even more head room for some of the ~100 Hz scattering associated with vibration excitation of the input arm vacuum enclosure.

Images attached to this report
Comments related to this report
robert.schofield@LIGO.ORG - 13:41, Sunday 06 November 2016 (31265)

The reason I dont think it is a simple path off of PR3 is that the spot is quite large and diffuse.

H1 OpsInfo
edmond.merilh@LIGO.ORG - posted 17:25, Thursday 03 November 2016 - last comment - 08:41, Friday 18 November 2016(31182)
Running a2l scriptS now

There are now THREE a2l scripts that we will be running once during EACH lockstretch. Patrick mentioned them in his time log. I'm tagging Opsinfo with the information again.

cd /opt/rtcds/userapps/release/isc/common/scripts/decoup

./a2l_min_LHO.py

./a2l_min_PR2.py

./a2l_min_PR3.py

that is all :)

Comments related to this report
corey.gray@LIGO.ORG - 10:34, Monday 07 November 2016 (31280)

A note on the (3) A2L measurements.  

  1. The ...LHO.py file can improve H1 performance.
  2. The ...PR2 & PR3.py files are for data-taking purposes (Jenne alignment study).
corey.gray@LIGO.ORG - 08:41, Friday 18 November 2016 (31586)OpsInfo

As of this week, we want to run the ...LHO.py file at the beginning of locks (i.e. right after we reach NLN).  It takes on the order of 10min.  

Sometimes you might not want to run it.  If the DARM specrtra looks good around 20Hz, then you are good.  It's a judgement call, but in general, this helps with sensitivity.  Will put this in the Ops Sticky Note wiki & should get in the Ops Checksheet soon.

(Thanks to Jenne & Ed for sharing the alogs about this!)

H1 CAL (DetChar, SUS)
jeffrey.kissel@LIGO.ORG - posted 16:42, Thursday 03 November 2016 - last comment - 22:07, Monday 07 November 2016(31179)
Increased Amplitude of H1SUSETMY L1/L2 Temporary Calibration Lines
J. Kissel, D. Tuyenbayev

We're still not getting the IFO duty cycle to get the desired uncertainty on the single-frequency actuation strength scale factor measurement of the UIM and PUM stage and we're running out of time, so I've increased the SNR of these temporary lines by another factor of ~3 over yesterday's increase (see LHO aLOG 31108).

Oscillator       Freq (Hz)      Old Amp (ct)   New Amp (ct)
ETMY UIM          33.7           180            500
ETMY PUM          34.7            81            300

Hopefully Robert's activities tonight won't impact the ~30 Hz region of the sensitivity, and we can turn things off soon.
Images attached to this report
Comments related to this report
darkhan.tuyenbayev@LIGO.ORG - 18:18, Thursday 03 November 2016 (31183)CAL

Jeff K, Darkahn T,

We calculated actuation strengths of L1 (UIM), L2 (PUM) and L3 (TST) actuation stages using calibration lines from 6 lock stretches in the last two days.

Preliminary results are given in the attached plots. Standard deviation on estimations of AU and AP are ~1.2% and for AT is ~0.4%.

Data points were taken at GPS times with HOFT_OK_BIT = 1 (segments are listed below).

# seg    start           stop            duration
0        1162123790.0    1162124750.0    960.000
1        1162124840.0    1162125190.0    350.000
2        1162125280.0    1162125480.0    200.000
3        1162127120.0    1162129210.0    2090.000
4        1162134280.0    1162137150.0    2870.000
5        1162162170.0    1162163370.0    1200.000

Increased line amplitudes will hopefully allow us to get AU and AP actuation strengths with subpercent 1-sigma error bounds.

Images attached to this comment
darkhan.tuyenbayev@LIGO.ORG - 09:04, Monday 07 November 2016 (31275)CAL

Jeff K, Greg M, Darkhan T,

After the L1 and L2 line amplitude increase it seems that we got better uncertainties in the esitamtions of the sus. stage actuation strengths.

This time we filtered the data using the IFO range channel, we used 50 MPC as a threshold. And from the remaining data we made historams of three different time intervals. We did not yet investiage why the noise levels of the lines are different at each of these intervals. The uncertainties for A{U,P,T} are given for the least noisy interval (blue data points).

Non-image files attached to this comment
darkhan.tuyenbayev@LIGO.ORG - 22:07, Monday 07 November 2016 (31302)CAL

Jeff K, Greg M, Darkhan T,

We calculated [N/ct] actuation force factors calculated from the ~35 Hz independent L1, L2 and L3 lines:

KU = 8.012-8 +/- 3.873-10 N/ct   ( std(KU) / |KU| = 0.0048 )

KP = 6.482-10 +/- 2.748-12 N/ct   ( std(KP) / |KP| = 0.0042 )

KT = 4.253-12 +/- 1.679-14 N/ct   ( std(KT) / |KT| = 0.0039 )

During a Nov. 4 lock stretch we got a factor of 3 improvement of the standard deviations compared to the previous day (blue data points vs. green).

In most recent 2 days we got more data with longer lock stretches, which can help us to better bound the uncertainties. Analysis of this data would require including an updated DARM digital filters, the IFO response changed on Nov. 5 (see LHO alog 31201) which can bias on our calculations if not taken into account.

The outliers were removed in a following way:

- Took >= 50 MPC data and removed data points that fall outside of 2-sigma std. deviation (some large outliers were not filtered by this step);

- one more time calculated std. and mean in the remaining data points and removed 2-sigma outliers (this step helped to remove large outliers).

- The mean and 2std. of these data points were shown with black solid line and dashed lines.

The final reported mean values and standard deviations were taken from the blue data points ( GPS [1162252470, 1162271230] ), L1 and L2 data was least noisy during this period. This mean value and its std. were shown with blue solid and dashed lines.

Non-image files attached to this comment
Displaying reports 52881-52900 of 83308.Go to page Start 2641 2642 2643 2644 2645 2646 2647 2648 2649 End