Displaying reports 62321-62340 of 85626.Go to page Start 3113 3114 3115 3116 3117 3118 3119 3120 3121 End
Reports until 16:03, Thursday 03 December 2015
H1 General
jeffrey.bartlett@LIGO.ORG - posted 16:03, Thursday 03 December 2015 (23938)
Ops Day Shift Summary
Activity Log: All Times in UTC (PT)

16:00 (08:00) Take over from JT
17:48 (09:48) Kyle – Going to X2-8 to recover equipment
19:29 (11:29) Kyle – Returning from X2-8
20:01 (12:01) Jodi – Going into High Bay to check for parts/equipment
21:18 (13:18) Kyle & John – Going to X2-8 to bring equipment back to CS
21:59 (13:59) Kyle & John – Back from X-Arm
22:26 (14:26) Kyle – Moving equipment to VPW. Then driving to Y2-8
23:31 (15:31) Kyle – Returning to CS from Y2-8 


End of Shift Summary:

Title: 12/03/2015, Day Shift 16:00 – 00:00 (08:00 – 16:00) All times in UTC (PT)

Support: None needed 
 
Incoming Operator: Travis

Shift Detail Summary: Overall a good observing shift. The IFO has been locked in Observing mode for the past 11.5 hours. Winds remain calm to light breeze (0-7mph). Seismic remains quiet. Microseism has flattened out and is showing a slight downward slope, but is still around 0.7um/s. 

There is a timing error flagged on H1SUSETMY. Will wait for the next time IFO is out of Observing mode to reset it.     

H1 AOS
min-a.cho@LIGO.ORG - posted 15:13, Thursday 03 December 2015 (23937)
Updates to approval processor logic
1. Approval Processor now checks for SegDB overflows, looking for overflow flags 30 seconds prior to and 5 seconds after the event gpstime. The program waits 180 seconds before it performs these checks to ensure that the proper SegDB files have been copied to the emfollow machine.

2. We've doubled the far thresholds respectively for each pipeline.
H1 DetChar (DetChar)
keith.riles@LIGO.ORG - posted 14:00, Thursday 03 December 2015 (23935)
How long does it take to see the narrow H1 lines below 100 Hz?
Prompted by a plot I showed at todays JRPC call of the forest of narrow lines visible below 100 Hz in a typical
daily FSscan normalized spectrum (based on a day's worth of 30-minute FFTs), Jeff asked me 
how much data one needs to see these lines when trying to investigate them. Below are some
ldvw spectra from this week for a variety of total observation times and FFT coherence times,
starting with long times and moving toward shorter times. From these spectra, I would say
that 15 minutes of observing time with 1- or 5-minute FFTs could be adequate to see if a
particular change has made the stronger lines go away completely, but one would need
to go to longer times to quantify small relative changes in strength.

To see weaker lines, one can go to longer observation times and longer coherence times
(see last figure).

Figures:
1 - 2 hours of 15-min FFTs
2 - 1 hour of 15-min FFTs
3 - 30 minutes of 15-min FFTs
4 - 30 minutes of 5-min FFTs
5 - 15 minutes of 5-min FFTs
6 - 15 minutes of 1-min FFTs
7 - 5 minutes of a 5-min FFT
8 - 5 minutes of 1-min FFTS
9 - 8 hours of 30-min FFTs
Images attached to this report
H1 General
jeffrey.bartlett@LIGO.ORG - posted 12:42, Thursday 03 December 2015 (23936)
Ops Day Mid-Shift Summary
   The IFO has been in Observing mode for the past 8 hours. Range has been between upper 70s to 80Mpc. Wind is calm to a light breeze (0 - 4mph). Seismic activity is quiet and well below 0.1um/s. Miscroseism has been building for the past 6 hours, but is starting flatten out at around 0.8um/s. There are storms along the North Pacific coast (data buoys reporting waves 12 to 16.5 feet, winds 22 to 37 knots, pressure at 29.2 inches and falling). 

   There have been two ETM-Y saturations.  
H1 General (SUS)
vincent.roma@LIGO.ORG - posted 11:14, Thursday 03 December 2015 (23934)
Strange Behavior of ITMX Oplev Diode

When looking at the optical lever diodes recently I noticed that the ITMX diode sum seemed to be dropping and rising very regularly, with a period of approximately 6 seconds.  The attached image shows two minutes of data for the four indivual ITMX diode segments along with their sum.  It was not obvious to my eyes that the four segments would add up to equal the sum (it seemed unlikely) but Keita added the four signals together and it did in fact result in the sum as we see it on the plots.  So the sum channel is being added properly, however we still do not know why it is rising and dropping as it is.  I looked at old data to try and see when this behavior started it and it looks like this has been happening for a long time.  This pattern was visible in the data for all of 2015.  It can be clearly seen in data back from January of this year.  I did not see this behavior in the other optical lever diode channels.

Images attached to this report
LHO VE
john.worden@LIGO.ORG - posted 10:43, Thursday 03 December 2015 (23933)
ION pump on X2 module

Kyle and Gerardo now have the beam tube ion pump open to the tube. The pressure at XEND has fallen by ~ 1/2.

Two days shown on the plot.

Images attached to this report
H1 General
jeffrey.bartlett@LIGO.ORG - posted 08:44, Thursday 03 December 2015 (23932)
Ops Day Shift Transition
           Transition Summary:
Title:  12/03/2015, Evening Shift 16:00 – 00:00 (08:00 – 16:00) All times in UTC (PT)
	
State of H1: 08:00 (16:00), The IFO locked at NOMINAL_LOW_NOISE, 22.2w, 75Mpc.  

Outgoing Operator: TJ

Quick Summary:  IFO locked in Observing mode for the past 4 hours. Environmental conditions are mixed – wind is calm (0-3mph), seismic activity is quiet. Microseism has been intensifying for the past 4 hours, and is now at 0.8um/s.     

LHO General
thomas.shaffer@LIGO.ORG - posted 08:00, Thursday 03 December 2015 (23930)
Ops Owl Shift Summery
H1 CDS
thomas.shaffer@LIGO.ORG - posted 07:36, Thursday 03 December 2015 (23931)
Can't log into the workstations in the control room

Peter King arrived and couldn't log in so I tried my account on two different machines with no luck. LLO isn't having this issue so must be a local problem, but I don't think it should be related to the full file system.

H1 General
peter.king@LIGO.ORG - posted 04:44, Thursday 03 December 2015 (23929)
remote MEDM screens
As per TJ's note on some hard disc space being filled.  The remote screens
and control room shots are amiss.  Having said that a number of the HEPI and
ISI ones are still available, if that helps debug the issue.
H1 CDS (OpsInfo)
thomas.shaffer@LIGO.ORG - posted 04:42, Thursday 03 December 2015 (23928)
/ligo system is full again I think

I'm seeing signs very similar to last time this happened (alog23006).

I first noticed something was up when I couldn't get the Lockloss tool to work due to an IOError of no space left on drive, and then the Lock Clock died. The clock works similarly to the reservation system where it will repeatedly write a new file with the updated times and delete the old one, so when the system gets full it can't write a new one.

I have deleted some stuff in my folder in hopes that it would help, but I don't really have any large files that would make a big dent.

Operators: VerbalAlarms has also crashed because it cannot write its notifications. I started it up on the Alarm Handler computer without the "-w" option so it will still run for now, but none of its notifications are being recorded. Please stop this process and start a new one when the issue is fixed. Same startup as before, type "VerbalAlarms" into the AH computer terminal (the -w and -l options are already aliased in).

LHO General
thomas.shaffer@LIGO.ORG - posted 04:26, Thursday 03 December 2015 (23927)
Back in Observing

Back at 12:21 UTC. Had to run thourhg an initial alignment, where I struggled with locking ALSX. I couldn't seem to get the power above 0.5, similar to what Corey was going through on Nov 29 (alog23805). I'm not sure how I fixed it. I fiddled with the ETMX, ITMX, and a tiny bit of TMSX, but when the power suddenly shot up near 1.0 I swear it was at values that I had already passed through for all three.

LHO General (Lockloss)
thomas.shaffer@LIGO.ORG - posted 02:21, Thursday 03 December 2015 - last comment - 02:40, Thursday 03 December 2015(23925)
Lockloss 10:17 UTC

Not sure of the cause yet. Control signal Striptools didn't show any signs of struggle. Seismic looks calm, no wind.

Comments related to this report
thomas.shaffer@LIGO.ORG - 02:40, Thursday 03 December 2015 (23926)

HEPI tidal seems to have been good (1st attachment).

Lockloss tool is failing due to "IOError: [Error 28] No space left on device"

 

Looks like I am going to have to do an initial alignment, pretty much everything seems very misaligned...odd.

Images attached to this comment
LHO General
thomas.shaffer@LIGO.ORG - posted 00:01, Thursday 03 December 2015 (23924)
Ops Owl Shift Transition
H1 General
travis.sadecki@LIGO.ORG - posted 00:00, Thursday 03 December 2015 (23923)
OPS Eve shift summary

Title: 12/2 Eve Shift 0:00-8:00 UTC (16:00-24:00 PST).  All times in UTC.

State of H1: Observing

Shift Summary: Another very quiet shift.  Only 4 ETMy saturations.  Going on 31 hours of lock.

Incoming operator: TJ

Activity log:

0:45 Commissioning mode for Hugh to change HEPI limits (~1 min.)

0:49 Commissioning mode for Evan to change tidal limits (~1 min.)

H1 General
evan.goetz@LIGO.ORG - posted 22:42, Wednesday 02 December 2015 (23922)
LISA Pathfinder launch online outreach

Evan G, Travis S, Nutsinee K

 

Congratulations to the LISA Pathfinder team for the succesful launch today! The LHO and LLO control rooms both took part in a Google Hangouts interactive live-stream in the leadup and following the launch of LISA Pathfinder. Besides a few technical difficulties with Google Hangouts/YouTube, I think it was a nice experience. We were able to answer a few questions how LIGO and LISA are different, our current operational status, etc. We now look forward to the interesting scientific output from the mission!

Congratulations again! :)

H1 General
travis.sadecki@LIGO.ORG - posted 21:21, Wednesday 02 December 2015 (23921)
OPS Eve mid-shift summary

Other than a brief excursion to Commissioning for updating HEPI drive limits (see aLog 23918), we have been locked in Observing for over 28 hours now.  Congrats to the LISA Pathfinder mission for a successful launch.

H1 CAL (COC, DetChar, SUS, VE)
jeffrey.kissel@LIGO.ORG - posted 14:24, Tuesday 01 December 2015 - last comment - 19:48, Wednesday 02 December 2015(23866)
Charge Measurement Update; Measurements Continue to Agree with Calibration Line Actuation Strength, ETMY Charge Slowing Down?
J. Kissel, S. Karki, B. Weaver, R. McCarthy, G. Merano, M. Landry

After gathering the weekly charge measurements, I've compared H1 SUS ETMY ESD's relative Pitch/Yaw actuation strength change (as measued by the optical levers) against the Longitundinal Actuation Strength (as measured by PCAL / ESD calibration lines). As has been shown previously (see LHO aLOG 22903), the pitch/yaw strength's slope trends very nicely along with the longituinal stength change -- if you take a quick glance. Upon closer investigation, here are things that one begins to question:
(1) We still don't understand why the optical level actuation strength assessments are offset from the longitunidal strength assessment after the ESD bias sign flip. 
(2) One *could* argue that, although prior to the flip the eye-ball-average of oplev measurements trackes the longitudinal strength, after the flip there are periods where two quadrants (magenta, in pitch, which is LR, from Oct 25 to Nov 8; black, in yaw, which is UR, from ~Nov 11 to Dec 06) track the longitudinal strength. As such, one *could* argue that the longitudinal actuation strength trend is dominated by a single quadrant's charge, instead of the average. Maybe.
(3) If you squint, you *could* say that the longitudinal actuation strength increase rate is slowly tapering off, where as the optical lever strength increase *may* be remaining constant. One could probably also say that the rate of strength increase is different between oplevs and cal lines (oplev P/Y strength is increasing faster that cal line L strength).
All this being said, we are still unsure whether we want to flip the ETMY ESD bias sign again before the observation run is out. Landry suggests we either do it mid-December (say the week of Dec 14), or not at all. So we'll continue to track via optical lever, and compare against the longitudinal estimate from cal lines.

Results continue to look encouraging for ETMX -- ever since we've had great duty cycle, and turned off the ETMX ESD Bias when we're in low-noise and/or when the IFO is down, the charging rate has decreased. Even though the actuation strength of ETMX doesn't matter at the few % level like it does for ETMY (because ETMX is not used as the DARM actuator in nominal low-noise, so it doesn't affect the IFO calibration), it's still good to know that we can get an appreciable effect by simply reducing the bias voltage and/or turning it off for estended periods of time. This again argues for going the LLO route of decreasing the ETMY bias by a factor of 2, which we should certianly consider doing after O1.

---------------
As usual, I've followed the instructions from the aWiki to take the measurements. I had much less trouble today than I had last week gathering data from NDS, which is encouraging. One thing I'd done differently was wait a litle longer before requesting the gathering and analysis (I waited until the *next* measurement had gone through -9.0 and -4.0 [V] bias voltage points and started the 0.0 [V] point, roughly 5 minutes after the measurement I wanted to analyze ended). As such, I was able to get 6 and 4 oplev data point to compose the average for ETMX and ETMY, respectively (as opposed to the 3 and 1 I got last week; see LHO aLOG 23717).

Once all data was analyzed, I created the usual optical-lever-only assessment using 
/ligo/svncommon/SusSVN/sus/trunk/QUAD/Common/Scripts/Long_Trend.m
and saved the data to here:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Results/CAL_PARAM/2015-12-01_H1SUSETMY_ChargeMeasResults.mat

However, I'd asked Sudarshan to gather the latest calibration line estimates of the ESD longitudinal actuation strength (aka kappa_TST), which he gathered from his matlab tool that gathers the output of the GDS function "Standard Line Monitor." (He's promised me an updated procedure and an aLOG so that anyone can do it). This is noteably *not* the output of the GDS pipeline, but the answers should be equivalent. His data lives here:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Results/CAL_PARAM/2015-12-01_Sep-Oct-Nov_ALLKappas.mat

Finally, I've made the comparison between oplev and cal live strength estimates using
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Scripts/CAL_PARAM/compare_chargevskappaTST_20151201.m
Images attached to this report
Non-image files attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 12:25, Wednesday 02 December 2015 (23906)SUS, SYS, VE
J. Kissel, G. Merano, J. Worden

In order to facilitate figuring out what's left on the chambers that might be charging the test masses (and also to compare against LLO who has a few bonkers quadrants that had suddenly gained charge), I attach a drawing (apologies for my out-of-date SolidWorks version) of what gauges remain around the end-station chambers. 

The "Inficon wide-range gauge" is the BPG402-Sx ATM to UHV Gauge,
and the "Gauge Pair" are separate units merged together by LIGO.

Also, PS -- we're valving in the ol' ion pumps today (in their new 250 [m]-from-the-test-masses locations). Kyle and Gerardo are valving in the X-arm today (stay tuned for details from them).
Images attached to this comment
john.worden@LIGO.ORG - 19:48, Wednesday 02 December 2015 (23920)

Not sure what Jeff meant by "ol' ion pumps". Kyle and Gerardo valved in a "bran' new ion pump" at the 250m location. The ol ion pump remains mounted in the end station but valved out from the chamber. Only the Xarm pump has been valved in at the 250 m location. The Yarm pump has yet to be baked prior to opening to the tube.

https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=23916

H1 PSL (ISC, PSL)
evan.hall@LIGO.ORG - posted 00:31, Thursday 09 April 2015 - last comment - 15:39, Thursday 03 December 2015(17766)
Another 3 dB of FSS gain

Rick, Evan

Summary

This evening we went into the PSL and examined OLTF of the FSS.

Since we want to increase the FSS gain, but cannot turn the common gain slider up any further, we looked for other ways to squeeze more gain out of the loop.

Rick had the idea to try to increase the error signal slope by adjusting the demod phase using the delay line. Indeed, we were able to increase the loop gain uniformly by 3 dB. The phase remained more or less unchanged below 700 kHz.

We now have a UGF of about 350 kHz with 50° of phase. The gain margin is about 3 dB.

Details

Delay line switch positions (up/down) are as follows:

Delay (ns) Old New
1/16 D D
1/8 D U
1/4 D U
1/2 D U
1 D U
2 D U
4 D U
8 U D
16 U U
1/16 D D
1/8 D D
1/4 D D
1/2 D D
1 U D
2 U D
4 U D
8 D D
16 D D
Total 32.9 ns 40.0 ns

So the phase change at 21.5 MHz is 56°. That seems like quite a lot, so perhaps we should take a closer look at the error signal with the FSS unlocked to make sure it's reasonable.

Also, on the manual FSS MEDM screen, we found that the TEST2 enable/disable button didn't really work; we seemed to get a sensible transfer function no matter what.

Non-image files attached to this report
Comments related to this report
evan.hall@LIGO.ORG - 10:47, Friday 10 April 2015 (17792)

Peter K, Jeff B, Evan H

We did some FSS diagnostics today in and around the PSL:

  • We measured the LO going into the FSS tabletop box; it is 20.0 dBm.
  • We also measured the refcav powers: with 28.3 mW incident, we have 11.8 mW transmitted immediately after the refcav. The transmission PD voltage was 1.15 V. But I think this must have been during the time at which the ISS AOM was diffracting an anomalously high amount of power, since the best transmission PD voltage we've observed is more like 1.5 V.
  • By driving the NPRO PZT with a triangle wave, we took sweeps of the error signal, the cavity transmission, and the cavity reflection.
  • We were able to entirely remove the delay line phase shifter. We replaced it with about 20 cm of extra RG58.
  • For a stable lock with a >300 kHz UGF, we had to adjust the common (PZT+EOM) and fast (PZT) gains to 26 dB and 21 dB, respectively (they were 30 dB and 15 dB) before. As we were leaving we noticed the loop started to oscillate, so we backed off the common gain to 24 dB instead.

Originally there was 14.5 dBm of 21.5 MHz drive going into the delay line, and 8.1 dBm coming out (and thus going to the EOM). So we have won back almost 6 dB of drive to the EOM. That's roughly consisent with the extra headroom we now have on the common gain slider.

However, I do not understand why we had to adjust the fast gain after removing the delay line. With 26 dB common and 15 dB fast, we saw a broad peak in the transfer function around 50 kHz or so, and we increased the fast gain to 21 dB to suppress it. So perhaps removing the delay line shifted the crossover frequency.

A new OLTF is attached (at 26 dB of common gain), along with the error signal and cavity sweeps that we took (which are now outdated).

Non-image files attached to this comment
evan.hall@LIGO.ORG - 15:39, Thursday 03 December 2015 (23910)

Using data (scope_7.csv) in the above attachment, we find that the PSL NPRO PZT actuation coefficient is 1.3 MHz/V [ = 21.5 MHz / (7.11 V + 9.09 V)].

Displaying reports 62321-62340 of 85626.Go to page Start 3113 3114 3115 3116 3117 3118 3119 3120 3121 End