C. Cahillane I have included systematic error in our Nominal ER8 Models. From here on out I will call the ER8 Model with the systematic error corrections the Systematic Model. The most notable thing about the Systematic Model is the extremely low level of uncertainty. This is because I only include statistical uncertainty for the Systematic Model, and our coherence requirements for measurements is typically very high (0.99 or 0.98), making uncertainty low. More analysis to come. Plot 1 is the money plot. It is the direct comparison of the uncertainty associated with the Nominal model (uncertainty which included systematics) and the Systematic model, which is only statistical uncertainty. Plot 2 is the Response function direct comparison for Nominal vs Systematic. Plots 3-6 are the Nominal uncertainty components squared and their square roots Plots 7-10 are the Systematic version of the same thing.
Several of us noticed helicopter flyovers last week. From the online Tri-City Herald, 9/18/15: "A helicopter that has been flying low over the Columbia River several times a day is conducting work on a Hanford project, according to the Department of Energy. The flights, which circle over the Columbia River four to six times each day, are expected to continue until about Oct. 1."
Title: 9/20 Day Shift 15:00-23:00 UTC (8:00-16:00 PDT). All time posted in UTC.
State of H1: Observing
Outgoing Operator: Jeff Bartlett
Summary: Locked in Observing since my previous shift. Elli and Miguel here on Fellows shift.
Activity Log: All Times in UTC (PT) 07:00 (00:00) Take over from TJ 07:00 (00:00) IFO locked at NOMINAL_LOW_NOISE, 22.9W, 69Mpc 07:14 (00:14) ETMY saturation 08:30 (01:30) ETMY saturation 09:14 (02:14) Craig left the site 09:59 (02:59) ETMY saturation 13:31 (06:31) ETMY saturation 14:17 (07:17) ETMY saturation 14:31 (07:31) ETMY saturation 14:46 (07:46) ETMY saturation 14:59 (07:59) ETMY saturation 15:02 (08:02) Turn over to Travis End of Shift Summary: Title: 09/20/2015, Evening Shift 07:00 – 15:00 (00:00 – 08:00) All times in UTC (PT) Support: None needed Incoming Operator: Travis Shift Summary: - IFO has been in Observing mode for past 20 hours. Environmental conditions have been quiet all morning. The only exceptions were eight (8) ETMY saturation notices.
A quiet first half of the shift. The IFO has been locked in Observing mode at NOMINAL_LOW_NOISE, 22.9W, and currently 72.Mpc for the past 17 hours. There have been three (3) glitches and four (4) ETMY saturation events reported since the start of the shift.
Transition Summary: Title: 09/20/2015, Owl Shift 07:00 – 15:00 (00:00 – 08:00) All times in UTC State of H1: Locked at NOMINAL_LOW_NOISE, 22.9W, 69Mpc, Intent bit set to Observing Outgoing Operator: TJ Quick Summary: IFO has been locked for the past 12 plus hours; wind is light, Seismic activity is low.
TITLE: 09/19 Eve Shift 23:00-7:00 UTC (16:00-0:00 PST)
STATE Of H1: Observing, 72 Mpc Range, 9 hours locked.
SHIFT SUMMARY: Locked my entire shift, with no saturations for the first half. FMCS alarm at 2:15 UTC (see alog) that just seemed to pass though.
INCOMING OPERATOR: Jeff B.
ACTIVITY LOG:
ETMY Saturations (in UTC): 3:25, 3:48, 3:58, 4:28, 6:01, 6:28, 6:36
Locked in Nominal Low Noise and Observing. Minimal glitches, no saturations so far, and the environment seems calm.
At 19:14 PST there was a critical alarm on H0:FMC-EX_CY_H2O_SUP_DEGF. By the time I got to it it was no longer in alarm. The EX chiller medm seemed to look normal to me, but trending the previously mentioned channel did show an odd flat spot in the supply temperature for the past ~3 hours (See attachments below). The tempurature began to increase again at 19:07 and seems to have gone back into its normal rythme.
First screenshot: A 12hour trend from today
Second screenshot: A 12hour trend from yesterday
I will continue to montior this.
State of H1: Observation Mode at 73Mpc for the last 5 hours.
Outgoing Operator: Travis S.
Quick Summary: Travis recovered from an earthquake and then has had it locked for the past ~5hours.
Title: 9/19 Day Shift 15:00-23:00 UTC (8:00-16:00 PST). All times in UTC.
State of H1: Observing
Shift Summary: After a few false starts at lock stretches of significant length, H1 has been locked in Observing Mode for the last ~5 hours of my shift. A few glitches related to ETMy saturations, but otherwise stable. Environment: calm.
Incoming operator: TJ
Activity log:
18:43 Evan arrives on site
DCS copies the H1_R raw science frames from CDS to the LDAS archive and the H1_C commissioning frames from CDS to the LDAS scratch filesystems. Currently the commissiong frames are also being copied to the LDAS archive. To fix a load issue on the LDAS side which was causing archiving of the science frame to fall behind, this latter process has been switch to primarily get its data from fw1. LDAS is getting the science frames from fw0, but now is getting commissiong frame for both scratch and archive from fw1. This should not affect CDS.
Once again back to Observing @ 18:11 UTC.
Lost lock again @ 17:47. ITMx saturation, but again not obvious enviromental culprits.
I had a look at both of the last locklosses (UTC 16:40 / GPS 116715542 and UTC 17:14 / GPS 112672005). The lockloss plots look very similar. Signals spike in AS_A_RF45, AS_B_RF45, AS_C and ASC-OMC wavefront sensors, and the signals quickly runaway. The ITMY and ITMX suspensions both saturate, followed by HAM6 ISI, OM1, OM2, MC2, OMC, in order. Attached is a plot of the first lockloss, showing growing ASC signals.
Locked Nominal Low Noise @ 17:40, set to Observing Mode.
H1 has been relocked and set to Observing Mode at ~76 MPc. I had to accept 2 SDF Diffs (H1:ALS-Y_WFS_DOF_3_P_GAIN and H1:ALS-Y_WFS_DOF_3_Y_GAIN) in order to go to Observing Mode. There is still a notification present about SPM Diffs for SEI HAM5 (H1:HPI-HAM5_MASTER_SWITCH and H1:ISI-HAM5_MASTERSWITCH), but these did not prevent me from going to Observing, so I am ignoring them.
Also, going through the checklist before setting Observing Mode, I had a question about sweeping the LVEA. I couldn't find an aLog about this being done, so I called Corey. He stated that this was being postponed until next Tuesday and that I could safely ignore this for now. Nevertheless, the lights in the LVEA and PSL are all off and no one is on site besides Elli and Miguel who are in the CR.
Update: Just after posting this, we have just lost lock again @ 16:32 UTC (ITMY saturation). Nothing obvious on the seismic or wind front.
I trended the H1:ALS-Y gains against the range channel, and noticed that the gains were changed during a stretch when we were not locked. I asked Evan about this and he had no good reason for these to change. These are not used in full lock, so they are inconsequential to the data. I will revert and re-accept them back to their old values when we are not locked, or leave a note for subsequent operators to do so.