Summarized H1 issues from last Fri/Sat & how we did over the weekend: Combination of environment & ALS glitching possible culprit for issues Fri/Sat. However we've been locked since about noon on Sat (going on 45hrs).
RF45 appears stable (will prob hold off on swapping cable until/if issue comes back & NOT address during Maintenance. Only address if needed).
Also discussion of "Freeze". Sounds like we are still in a partial freeze.
There was discussion about allowing Beam Tube repairs (will be discussed offline).
Commissioning & Any Invasive Activities:
Regular Tues Maintance Activities
There are activities which occur every week and these do not require a Work Permit, but need to be done on a recurring basis. A short list of these (also on whiteboard) is:
Ed is Operator on shift (& TJ is available as a secondary operator, if needed)
TITLE: 10/05 [OWL Shift]: 07:00-15:00 UTC (00:00-08:00 PDT), all times posted in UTC STATE Of H1: Observing, ~75 MPc SHIFT SUMMARY: Remained locked in observing for entire shift. A few SUS ETMY glitches. INCOMING OPERATOR: Corey ACTIVITY LOG: 07:54 - 07:59 UTC Stepped out of control room. SUS E_T_M_Y saturating (Mon Oct 5 8:52:2 UTC) SUS E_T_M_Y saturating (Mon Oct 5 8:52:4 UTC) SUS E_T_M_Y saturating (Mon Oct 5 14:56:49 UTC)
The SSD RAID has failed on h1tw0, so the trend writer has been halted. This will affect the ability of h1nds0 to get recent raw minute trend data.
Still locked in observing at ~ 78Mpc. A couple of SUS ETMY saturations.
TITLE: 10/05 [OWL Shift]: 07:00-15:00 UTC (00:00-08:00 PDT), all times posted in UTC STATE Of H1: Observing @ ~ 78 MPc. OUTGOING OPERATOR: Cheryl QUICK SUMMARY: From the cameras the lights are off in the LVEA, PSL enclosure, end X, end Y and mid X. I can not tell if they are off at mid Y. Seismic in 0.03 - 0.1 Hz band is around .015 um/s. Seismic in 0.1 - 0.3 Hz band is around .1 um/s. Winds are less than 5 mph. I noticed on the CDS DAQ Overview that tw0 restarted itself. I see that Corey noted this occurring on his shift as well.
TITLE: EVE Shift, Oct 4th-5th, 23:00:00UTC to 07:00:00UTC, 16:00PT-00:00PT.
STATE OF H1: locked since yesterday, 77Mpc
SUPPORT: MikeL
INCOMING OPERATOR: Patrick
SHIFT SUMMARY: quiet
IFO Activity:
Intention Bit: Undisturbed (Sun Oct 4 21:1:58 UTC)
SUS E_T_M_Y saturating (Sun Oct 4 21:22:44 UTC)
SUS E_T_M_Y saturating (Sun Oct 4 21:37:16 UTC)
SUS E_T_M_Y saturating (Sun Oct 5 0:18:31 UTC)
SUS E_T_M_Y saturating (Sun Oct 5 0:57:11 UTC)
SUS E_T_M_Y saturating (Sun Oct 5 2:30:11 UTC)
SUS E_T_M_Y saturating (Sun Oct 5 4:23:13 UTC)
SUS E_T_M_Y saturating (Sun Oct 5 4:34:1 UTC)
TITLE: 10/4 DAY Shift: 15:00-23:00UTC (08:00-16:00PDT), all times posted in UTC
STATE OF H1: In Observation Mode at 72Mpc
SUPPORT: Vinny, Robert
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY: Quiet shift with only small a small break for PEM injections.
Shift Activities:
Raw minute-trend writer, h1tw0, has been popping up medm message windows warning of "virtual circuit disconnects" (and h1tw0 boxes on the DAQ Detail go WHITE for a few seconds every few minutes).
LLO has had a GraceDB querying Failure for last few shifts/days.
Want to reiterate importance of contacting them whenever we receive an Alert on VerbalAlarms. The Alert/Trigger Site Response Checklist (L1500117), laminated at the Ops Work Station, states operator at each site must contact each the other to confirm they received the alarm (current state [LLO GraceDB Failure] is an example of the importance of this step).
Received GRB Alert at 18:11UTC. Going through the checklist (L1500117).
Yesterday when taking H1 to Observation Mode, Evan & I noticed a RED SDF on video0 (I think it was for PEMEX or EY), but we did not see it on our SDF screens on our work stations. I reopened the SDF and the RED went away. The medm was not frozen, because we were Accepting channels & it would go green before noticing this errant PEM RED. Just thought it was something interesting.
TITLE: 10/4 DAY Shift: 15:00-23:00UTC (00:00-8:00PDT), all times posted in UTC
STATE of H1: Observation Mode with Avg of 74Mpc
Outgoing Operator: JimW
Support: Vinny
Quick Summary: useism continues a slow trend down (at about 0.15um/sec). Winds hovering around 12mph.
Terramon has just come up with a RED warning of a 5.6 Peruvian earthquake who's Rayleigh wave is due here in a minute (0.7um/s), due at 15:30:38UTC. We'll see what happens.
L1 just went down at 15:30. Terramon said the EQ's Rayleigh waves (of 1.4um/s) would arrive there at 15:17UTC.
So we might not be out of the woods yet...watching 0.03-0.1Hz (all three axis have yet to move up at the same time and all are still under 0.1um/s...I've seen us drop out when all three go above that velocity...but that was a few weeks ago before the DHARD filter).
No signs of anything on tidal or ASC control strip tools either.
It's been 15min since the R-wave arrival estimate, I'm assuming we rode through the EQ. (it was barely observable in here on seismic bands, range, striptools). Time to make breakfast/coffee.
Title: 10/3 OWL Shift 7:00-15:00 UTC
State of H1: Low noise, observing 75 mpc
Shift Summary: Quiet night
Activity log:
Nothing happened. Quiet night, Corey's lock from yesterday made it through the night.
Quiet night at LHO. Wind ~10mph, seimic relatively low, lock from yesterday continues.
TITLE: 10/3 EVE Shift: 23:00-07:00UTC (Oct.4) (16:00-23:59PT), all times posted in UTC
STATE OF H1: Observation at 77Mpc
SUPPORT: Robert, Jordan, Sheila
INCOMING OPERATOR: Jim
SHIFT SUMMARY:
LLO is still having issues with useism.
Robert did one round of injections, and produced many ETMY saturations in 2 minutes - he may need to redo this measurement tomorrow night.
Jordan did one PEM measurement and would like to take another. The first was about 30 minutes and the second should be about this long as well.
Shift Activities:
00:00:42UTC, Oct. 4th - Robert's PEM injections start
01:34:37UTC - Robert's PEM injections end
03:35:37UTC - Jordan's PEM injections start
04:06:47UTC - Jordan's PEM injections end
Just in case you're wondering why LHO sees two noise bumps at 315 and 350Hz (attached, middle blue) but not at LLO, we don't fully understand either but here is the summary.
There are three things here, environmental noise level, PZT servo, and jitter coupling to DARM. Even though the former two explains a part of the LLO-LHO difference, they cannot explain all of it, and the coupling at LHO seems to be larger.
Reducing the PSL chiller flow will help but that's not a solution for the future.
Reimplementing PZT servo at LHO will help and this should be done. Squashing it all will be hard, though, as we are talking about the jitter between 300 and 370Hz and there's a resonance at 620Hz.
Reducing coupling is one area that was not well explored. Past attempts at LHO were on top of dubious IMC WFS quadrant gain imbalances.
1. Environmental difference
These bumps are supposed to be from the beam jitter caused by PSL periscope resonances (not from the PZT mirror resonances). In the attached you can see that the bumps in H1 (middle blue) correspond to the bumps in PSL periscope accelerometer (top blue). (Don't worry, we figured out which server we need to use for DTT to give us correct results.)
Because of the PSL chiller flow difference between LLO and LHO (LHO alog, couldn't find LLO alog but we have MattH's words), in general LLO periscope noise level is lower than LHO. However, the difference in the accelerometer signal is not enough to explain the difference in IFO.
For example, at 350Hz LHO PSL periscope is only a factor of 2 noisier than LLO. At 330Hz, LHO is quieter than LLO by more than a factor of 2. Yet we have a huge hump in DARM at LHO, it becomes larger and smaller in DARM but it never goes away, while LLO DARM is deat flat.
At LLO they do have a servo to supress noise at about 300Hz, but it shouldn't be doing much if any at 350Hz (see the next section).
So yes, it seems like environmental difference is one of the reasons why we have larger noise.
But the jitter to DARM coupling itself seems to be larger.
Turning down the chiller flow will help but that's not a solution for the future.
2. Servo difference
At LLO there's a servo to squash beam jitter in PIT at 300Hz. LHO used to have it but now it is disabled.
At LLO, IOOWFS_A_I_PIT signal is used to suppress PIT jitter targetting the 300Hz peak which was right on some mechanical resonance/notch structure in PZT PIT (which LHO also has), and the servo reduced the noise between about 270 and about 320Hz (LLO alog 19310).
Same servo was successfully copied to LHO with some modification, which also targeted 300Hz bump (except that YAW was more coherent than PIT and we used YAW signal), with somewhat less (but not much less) aggressive gain and bandwidth. At that time 300Hz bump was problematic together with 250Hz bump and 350Hz bump. Look at the plots from alog 20059 and 20093.
Somehow 250Hz and 300Hz subsided, and now LHO is suffering from 315Hz and 350Hz bumps (compare the attached with the above mentioned alog). Since we never had time to tune the servo filter to target either of the new bumps, and since turning the servo on without modification is going to make marginal improvement at 300Hz and will make 250Hz/350Hz somewhat worse due to gain peaking, it was disabled.
Reimplementing the servo to target 315 and 350Hz bumps will help. But it's not going to be easy to make this servo wide band enough to squash everything because of 620Hz resonance, which is probably something in the PZT mirror itself (look at the above mentioned alog 20059 for open loop transfer function of the current servo, for example). In principle we can go even wider band, but we'll need more than 2kHz sampling rate for that. We could stiffen the mount if 620Hz is indeed the mount.
3. Coupling difference
As I wrote in the environment difference, from the accelerometer data and IFO signal, it seems as if the coupling is larger at LHO.
There are many jitter coupling measurements at LHO but the best one to look at is this one. We should be able to make a direct comparison with LLO but I haven't looked.
Anyway, it is known that the coupling depends on IMC alignment and OMC alignment (and probably the IFO alignment).
At LHO, IMC WFS has offsets in PIT and YAW in an attempt to minimize the coupling. This is on top of dubious imbalances in IMC WFS quadrant gains at LHO (see alog 20065, the minimum quadrant gain is a factor of 16 larger smaller than the maximum). We should fix that before spending much time on studying the jitter coupling via alignment.
At LLO, there's no such imbalance and there's no such offset.
The coupling of these peaks into DARM appears to pass through a null near the beginning of each full-power lock stretch, perhaps indicating that this coupling can be suppressed through TCS heating.
Already from the summary pages one can see that at the beginning of each lock, these peaks are present in DARM, then they go away for about 20 minutes, and then they come back for the duration of the lock.
I looked at the coherence (both magnitude and phase) between DARM and the IMC WFS error signals at three different times during a lock stretch beginning on 2015-09-29 06:00:00 Z. Blue shows the signals 10 minutes before the sign flip, orange shows the signals near the null, and purple shows the signals 20 minutes after the sign flip.
One can also see that the peaks in the immediate vicinity of 300 Hz decay monotonically from the beginning of the lock strech onward; my guess is that these are generated by some interaction with the beamsplitter violin mode and have nothing to do with jitter.
Addendum:
alog 20051 shows the PZT to IMCWFS transfer function (without servo) for PIT and YAW. Easier to see which resonance is on which DOF.
We've both restarted our sessions on TeamSpeak (I rebooted computer since ours would not allow me to open anything. Upon reboot, TeamSpeak opened automatically [thanks, Ryan!].). We are both now re-connected.