Ops Shift Transition: 12/08/2016, Day Shift 16:00 – 00:00 (08:00 - 16:00) - UTC (PT)
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:
A very nearby earthquake just tripped basically everything. It hasn't shown up on USGS yet, but the BLRMS are off the displays.
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.
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.
A couple things:
Please any operator contact me at any time if help/explanations/etc is needed.
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.
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.
Back to Observing at 11:45
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.
Observing again at 13:07. Range says 79Mpc!
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.
Back to Observing @ 10:45
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.
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.
No issues with IA or relocking. Here we go again.
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:
IFO alignment looks pretty bad which is to be expected after such a long lock stretch. Running through IA now.
Most likely due to 5.9 EQ in China.
This lock was 28 hours and 44 minutes.
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:
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?
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
6.8M off the coast of Northern California