Displaying reports 55961-55980 of 87439.Go to page Start 2795 2796 2797 2798 2799 2800 2801 2802 2803 End
Reports until 08:43, Thursday 08 December 2016
H1 General
jeffrey.bartlett@LIGO.ORG - posted 08:43, Thursday 08 December 2016 (32359)
Ops Day Shift Transition

Ops Shift Transition: 12/08/2016, Day Shift 16:00 – 00:00 (08:00 - 16:00) -  UTC (PT)

State of H1: IFO unlocked due to earthquake in California.
Intent Bit: Environment
Weather: Wind is a Gentle to Moderate Breeze (4- 12mph), cold and clear, snow expected
Primary 0.03 – 0.1Hz: Currently at 0.7um/s 
Secondary 0.1 – 0.3Hz: Currently at 0.5um/s
Quick Summary: IFO is unlocked due to Mag 6.8 earthquake in California. When the microseism clams down a bit more will start to relock.  
Outgoing Operator: TJ
LHO General
thomas.shaffer@LIGO.ORG - posted 08:07, Thursday 08 December 2016 (32347)
Ops Owl Shift Summary

TITLE: 12/08 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Earthquake
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: I had a few locklosses due to PIs, but I eventually wrangled them and got it locked for almost 2 hours before a 6.5M earthquake off of California knocked us out.
LOG:

LHO General
thomas.shaffer@LIGO.ORG - posted 06:56, Thursday 08 December 2016 - last comment - 06:58, Thursday 08 December 2016(32357)
Lockloss @ 14:52

A very nearby earthquake just tripped basically everything. It hasn't shown up on USGS yet, but the BLRMS are off the displays.

Comments related to this report
thomas.shaffer@LIGO.ORG - 06:58, Thursday 08 December 2016 (32358)
H1 SUS
thomas.shaffer@LIGO.ORG - posted 05:15, Thursday 08 December 2016 - last comment - 15:31, Friday 09 December 2016(32354)
PI slightly rung up modes that we are not damping

It seems like there are some PI modes that we are no longer damping that are slightly run up according to the dtt. I also wonder if the peaks at around 13000hz are modes that we had not had issues with before, or maybe something else entirely? I don't see any mention of them on the PI medm and they are currently the highest. I will try to damp some of the other ones if they get any higher.

The attached shows the PI dtt just after reaching low noise.

Images attached to this report
Comments related to this report
thomas.shaffer@LIGO.ORG - 06:01, Thursday 08 December 2016 (32356)

Well I think things are stable now. I ended up flipping the sign for the both the phase and gain on mode 27. Mode 26 also came up and changing the phase got it to, very slowly, go down. I took some screen shots of the dtt template at 20min, 26min, and 32min into the lock. The modes that the Striptools said were ringing up, didnt necessarily agree with the dtt. I dont remember how much the modes can shift in frequency, but it seems like some of them were off by a couple of hz. 

Images attached to this comment
terra.hardwick@LIGO.ORG - 11:58, Thursday 08 December 2016 (32364)OpsInfo

A couple things:

  • I'm not sure what you're referencing that seems 'a couple Hz off', could you elaborate? I checked the band pass filters against the frequency of the peaks at the times you listed and the most I found was Mode28 was off by 1 Hz. I have since changed the BP filter to account for this shift. 
  • Remember that if a peak's frequency in DTT is different than the bandpass filter frequency, you should switch to a different band pass. There are explicit directions in the PI Wiki (which you can open from the PI medm screen and which I just updated to make more clear) and I've walked through this process individually with each operator. If something is still unclear, you can always still call me at anytime (number on the whiteboard). This shouldn't be much of an issue these days but is worth checking if you're having damping problems.
  • Modes 27 and 29 have to be carefully watched during the first hour of lock. These have been successfully damped for weeks now but must be reacted to immediately. 
  • Again, if you lose lock from a PI, you must wait in DC readout to give that mode time to ring down. You can watch the ringdown in DTT. If you try locking again, the mode will still be rung up.
  • There are some modes that always have higher amp, such as the 13kHz modes TJ noted, that are not unstable - TJ that DTT from low noise you first posted is totally normal. You can always look at a reference from an eariler stable lock time to compare the amplitudes. I will add a good reference to the PI DTT in the background so it's easy to see what's 'good'
  • Regarding DTT and StripTool not seeming to match - we use different error signals for different modes, while the DTT is just looking at one of those signals. The result is that Modes 27,28 look very rung up on the StripTool but their peaks in the DTT dont look so high. This is done on purpose, because those modes need to be damped faster. 

Please any operator contact me at any time if help/explanations/etc is needed.

thomas.shaffer@LIGO.ORG - 15:31, Friday 09 December 2016 (32401)

For the couple hz off thing, I was mainly refering to the frequencies listed on the medm above the modes. I'm not sure how accurate these are suppose to be, but like mode 27 says 18041, and the dtt was saying that 18038 seemed to be more rung up (see second attached). I didn't remember how much they shifted, and I did not look at the actual filters themselves at the time.

I was able to make it work (on the second try) with just changing phase and gain so I didn't look into it too much after that. But, yes, following your instructions and changing the BP would have been next on the list.

In alog32385 you mention that you will put a reference trace to show what is normal and what is not. I would love this because I looked at the dtt picture that is on the wiki and saw that it was much different. Either way, it was a good learnign process for me since I have only ever had to change phases for PI modes.

H1 General
thomas.shaffer@LIGO.ORG - posted 03:11, Thursday 08 December 2016 - last comment - 05:10, Thursday 08 December 2016(32350)
Lockloss @ 11:07

PI mode 27. I damped mode 28 then, thinking that I defeated it, went to get a cup of water. When I returned, mode 27 was quickly rising and I got it to level out but couldn't damp it before it broke.

Comments related to this report
thomas.shaffer@LIGO.ORG - 03:46, Thursday 08 December 2016 (32351)

Back to Observing at 11:45

thomas.shaffer@LIGO.ORG - 04:13, Thursday 08 December 2016 (32352)

Another lockloss at 12:10 due to PI mode 27. I couldn't seem to get it to go down. I could get it to almost level out, but never bring it down. I did not try changing the gain, I will next time.

thomas.shaffer@LIGO.ORG - 05:10, Thursday 08 December 2016 (32353)

Observing again at 13:07. Range says 79Mpc!

H1 General
thomas.shaffer@LIGO.ORG - posted 02:12, Thursday 08 December 2016 - last comment - 02:45, Thursday 08 December 2016(32348)
Lockloss @09:54

It was very sudden. There was no indication form any of the FOMs that anything was, and the environment looks good. There may be the smallest bump on the BLRMS, but nothing that ever should have dropped it. SR3 lockloss template attached, doesn't seem to be the cause (I zoomed in this time unlike before). Also attached the generic lockloss plots, which I can't tell if any of it is out of the norm. Myabe MICH was a bit more active a few seconds before it dropped, but it does sometimes seem to do that normally.

IMC is having trouble staying locked, I should stop writing here and get back to that.

Images attached to this report
Comments related to this report
thomas.shaffer@LIGO.ORG - 02:45, Thursday 08 December 2016 (32349)

Back to Observing @ 10:45

LHO General
thomas.shaffer@LIGO.ORG - posted 00:06, Thursday 08 December 2016 (32346)
Ops Owl Shift Transition

TITLE: 12/08 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 75.5915Mpc
OUTGOING OPERATOR: Travis
CURRENT ENVIRONMENT:
    Wind: 11mph Gusts, 7mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.24 μm/s
QUICK SUMMARY: Travis delivers a locked IFO again after recovering from an earthquake in China. LLO is currently down. Snow expected in the morning sp be safe driving in.

H1 General
travis.sadecki@LIGO.ORG - posted 00:01, Thursday 08 December 2016 (32345)
Ops Eve Shift Summary

TITLE: 12/08 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 78.082Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:  Locked for most of the shift with ~1.5 hour downtime due to EQ.
LOG:

See previous logs for pertinent events.

 

H1 General
travis.sadecki@LIGO.ORG - posted 23:39, Wednesday 07 December 2016 (32344)
Observing at 7:39 UTC

No issues with IA or relocking.  Here we go again.

H1 DetChar (DetChar)
vincent.roma@LIGO.ORG - posted 22:50, Wednesday 07 December 2016 (32343)
Dec 1 - 4 LHO DQ Report

The DQ report for December 1 - 4 is online and can be found here.  It's being posted slightly later than normal due to some techincal issues.

Quick Summary:

H1 General
travis.sadecki@LIGO.ORG - posted 22:47, Wednesday 07 December 2016 (32342)
Starting Initial Alignment

IFO alignment looks pretty bad which is to be expected after such a long lock stretch.  Running through IA now.

H1 General
travis.sadecki@LIGO.ORG - posted 22:12, Wednesday 07 December 2016 - last comment - 22:32, Wednesday 07 December 2016(32340)
Lockloss 6:10 UTC

Most likely due to 5.9 EQ in China. 

Comments related to this report
travis.sadecki@LIGO.ORG - 22:32, Wednesday 07 December 2016 (32341)

This lock was 28 hours and 44 minutes.

H1 ISC (DetChar)
keith.riles@LIGO.ORG - posted 21:28, Tuesday 06 December 2016 - last comment - 05:48, Thursday 08 December 2016(32289)
Narrow lines in H1 ER10 data
As a benchmark against which to compare upcoming O2 data, I have compiled a list
of narrow lines seen in the H1 DARM spectrum up to 2000 Hz, using 107 hours of
ER10 FScan 30-minute SFTs. There are no big surprises relative to the lines and combs
Ansel and I have reported on previously from ER9 and later data, but below are some
observations. 

Attached figures show  selected band spectra, and a zipped attachment
contains a much larger set of bands. Also attached for reference is a plaintext list of combs, 
isolated lines, PEM-associated lines. etc. In the attached spectra, the red curve is the
ER10 data, and the black curve is the full-O1 data. The label annotations are keyed to
the height of the red curve, but in some cases, those labels refer to lines in the O1 data
that are not (yet) visible in accumulated current data. For the most part, lines seen in 
O1 that don't show up in ER10 nonetheless remain for now in the lines list and still
have labels on the graphs that end up in the red fuzz. If they fail to emerge in O2
data, they will be deleted from future line lists.

Observations:
  • As noted previously, the 8-Hz / 16-Hz combs seen in O1 are blessedly gone
  • Thanks to interventions to upgrade timing electronics firmware, the previously dominant low-frequency comb with 1-Hz spacing and 0.5-Hz offset is greatly reduced (but not eliminated)
  • Compared to O1, the non-linear upconversion around quad violin modes and harmonics is much worse in ER10, and it appears that at least some violin mode excitations are affecting the low frequency band in that one sees there a multitude of sparsely distributed doublets, triples and quadruplets of lines with a spacing of about 0.0468 Hz. Andy Lundgren pointed out that this spacing coincides closely with a beat between two 2nd-harmonic violin modes he reported on last week. If I measure / eyeball those frequencies as seen in the ER10 data set, I get 1009.4414 and 1009.4881 Hz, giving a beat of 0.0467 Hz (but with an uncertainty of a few tenths of a mHz), consistent with the explanation. Further credence comes from the proliferation of such doublets / triplets / quadruplets seen in the wings of the quad harmonics (fundamental and higher).
  • There are so many upconverted lines around the quad harmonics that I didn't bother cataloguing them in those regions on the assumption that they will go away in O2 with improved damping (but cataloguing can be revisited later, if needed).
  • With the exception of the violin mode regions, the higher frequency spectrum is generally free of narrow lines (unlike the region below 100 Hz), but one disturbing feature is the presence of non-Gaussian broad disturbances that were not visible in O1. The infamous region around 1083 Hz is one example, as is the 100-200 Hz band.
Figures: [ER10 in red and O1 in black; labels are attached to peaks in the ER10 data] Fig 1 - 0-1000 Hz Fig 2 - 1000-2000 Hz Fig 3 - 2-20 Hz Fig 4 - 20-50 Hz Fig 5 - 50-100 Hz Fig 6 - 100-200 Hz Fig 7 - 490-535 Hz Fig 8 - 1000-1000 Hz Fig 9 - 1800-1900 Hz Other attachments: * zipped file with full set of sub-band spectra * Lines list with label definitions
Images attached to this report
Non-image files attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 12:39, Wednesday 07 December 2016 (32311)DetChar

Here is a plot of the violin mode harmonics around 1kHz, comparing the amplitudes today to the amplitudes right after the damping efforts of Nov 30th. 

We don't actively damp these by default, only when someone manually engages damping do they get damped.   Durring the first part of ER10 ISI trips caused by tidal problems were ringing them up, but that problem is fixed now and most modes are ringing down.  ETMX modes (between 1003 and 1006Hz) have increased in amplitude since the 30th.  

The largest peak here is the pair on ETMY that Keith points out, we have settings that work to damp both of these modes using the mode9 filter bank on ETMY, and it would not be difficult to turn this damping on automatically in the guardian.  

Our question for Keith and detchar is is this (the current spectrum) good enough?  Or should we continue to try to add automatic damping for some of these modes?  

Images attached to this comment
keith.riles@LIGO.ORG - 05:48, Thursday 08 December 2016 (32355)
Automatically damping the violin modes would reduce up-conversion contamination at the starts of
lock stretches, making more data usable for CW searches. Even small excess powers in narrow bins
leads to unnecessary outliers in analysis that waste computing and manpower. Unless there is a 
downside to such damping, it seems warranted.

thanks,
Keith
Displaying reports 55961-55980 of 87439.Go to page Start 2795 2796 2797 2798 2799 2800 2801 2802 2803 End