In trending the PSL Enclosure temperatures for the past few days, I remembered about the AD590-based sensor on the table near the exit of the reference cavity chamber. There's a sudden jump in the temperature reading. Not sure why this would be the case. The reference cavity was locked at the time.
H1 is locked and Observing for 19hours43min.
Range is vacillating between 63 and 73Mpc. (as per the range medm screen)
The 1009.5 vioin mode has neither rung down nor up.
Environmental conditions are nominally good
All seismic BLRMS show downward trending
Below are trends from the past two days. I can see a definite correlation between wind speed and the .3u particle count in the PSL 101 dust monitor ~ two days ago. It's hard to tell about the most current one. The particle count is definitly high enough to set off the alarm but can wind speeds under 10mph be to blame?
I don't see any aLogs about VEA environmental changes at EY so I don't quite know what is going on with dust monitor 1. Again, I see wind speeds ≤ 10mph
TITLE: 12/12 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 71.8Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY:
All shifts should be like this....weekend! Cheryl handed off a locked H1 & it is approaching 16hrs of lock. The range looks very good on this stretch: flat, no glitch drops. useism is just under the 90percentile and winds are low.
1st Harmonic of Violins (~1kHz) are high (1x^-15). Perhaps we should address damping these guys down at some point when L1 is down?
Tonight Amber Henry was my copilot at the operator helm. Walked her through some of the basics.
Plot attached:
Thanks. FYI we no longer need to log PI damping changes (unless of course something goes wrong/abnormal).
TITLE: 12/11 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 70.4106Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY:
(Gray, Kawabe, Vorvick)
Wanted to close the loop here (mainly wanted to confirm there were no other channels we had to worry about).
Today Cheryl took care of UNMONITORING the channel (H1:ALS-Y_FIBR_LOCK_TEMPERATURECONTROLS_ON) we observed knocking us out of OBSERVING the last two days.
I went ahead & followed Keita's instructions for checking ALL the channels for this frontend (h1sysecaty1plc2), which Cheryl posted (here), to make sure there were no other channels in h1sysecaty1plc2 we might be missing. The [15] channel list files are at: /ligo/home/keita.kawabe/LockLoss/SDFERRORS/h1sysecaty1plc2 & I ran a lockloss script on all of these files for both OBSERVING drops which happened during Cheryl's shifts (GPS time: 1165432802 & 1165531183) & for both of these times, the channel noted above is the only one which makes an obvious change (see attachment #1 & #2 for both times).
So we should now be good (unless a new channel makes a change on us).
Terra called in to check on H1. I hadn't looked outside, so wasn't aware that we'd had sleet this morning after I got here, and she's telling me that road conditions in town are not good. She and I talked about H1 and it's running well, so she did not come to the site. She emailed Keita, so he's aware.
Local time translates into 15:00UTC yesterday to 21:00 today.
After reading Keita's alog 32025, I used the template to passively look at coherance over this lock, and pitch is at 0.9 and has been and this was not in the previous lock, interestingly enough, though yaw was worse at the end of the last lock.
Going out of Observe now to reduce the coherance made sense in light of the long lock we just had.
paasive a2l checks:
Here's what's odd - pitch and yaw coherances are better an hour after running a2l, but the entire region 10Hz to 40Hz is elevated, and the range has gone down.
Plot start time is 20:32:06UTC.
New plot - start time 20:43:21 - coherence is higher but 10-40Hz is not elevated.
Smaller coherence with larger DARM noise at 20Hz means that the excess noise is not due to a2l coupling. When something other than a2l coupling dominates the noise at 20Hz, running or not running a2l is irrelevant, so please don't run it.
Again I'll say this, it's a perfect project for a fellow to write a script to plot the coherence and DARM BRMS for 15-25Hz or so VS time. With such a script it would be easy for operators to determine (and show to others) if running a2l would be beneficial or not.
Anyway, going out of OBSERVE to run a2l script is OK when all of below are satisfied.
Do it sparingly, single IFO data is still valuable for CW.
(Added later at 13:30 local time: If the coherence is super bad like Cheryl's "before" plot for PIT, there's not much point in waiting hours to run a2l, but make sure that the alignment itself is not suspect.)