Activity Log: All Times in UTC (PT) 00:00 (16:00) Take over from Corey 03:09 (19:09) Restarted VerbalAlarm 07:40 (23:40) Lockloss – Possible EQ in Victoria, CA. End of Shift Summary: Title: 12/29/2015, Evening Shift 00:00 – 08:00 (16:00 – 00:00) All times in UTC (PT) Support: Kiwamu, Mike L. Incoming Operator: Ed Shift Detail Summary: Good Observing shift until 07:40 (23:40) when lost lock possibly due to EQ in Victoria, CA. Started relocking when Ed came on shift.
In general a good first half of the shift. IFO status and environmental conditions remain as they were at the start of the shift. There were a couple of EQs that passed without any apparent issues. VerbalAlarms stopped working around the start of the shift (00:00 (16:00)). I restarted it (at 03:09 (19:29)) and notified the support group.
Transition Summary: Title: 12/29/2015, Evening Shift 00:00 – 08:00 (16:00 – 00:00) All times in UTC (PT) State of H1: 00:00 (16:00), The IFO has been in Observing mode for the past 3.5 hours, with power currently at 21.8W, and range at 80Mpc. Environmental conditions are good. The wind is up to a light breeze (2- 7mph). Seismic is flat at approximately 0.03um/s; microseism is also flat and centered around 0.3um/s. Outgoing Operator: Corey
Jeff, Sheila
We updated the Range integrand FOM, updating the reference which has been out of date for a while, and changed the scale.
TITLE: 12/29 DAY Shift: 16:00-00:00UTC (08:00-04:00PDT), all times posted in UTC
STATE of H1: NLN for 3+hrs at 80Mpc
Incoming Operator: Jeff B.
Support: Kissel on-site fellow, Sheila (Locking Commissioner)
Quick Summary:
Fairly light Maintenance Day (which occurred only because H1 dropped out of lock). Current lock looks noticeably less ratty (why??).
Shift Activities:
LVEA is still too warm and not under control. So I have set HC3B to off (4ma).
Maintenance Summary: 17:45 Lockloss --> 20:49 Undisturbed
Not clear why we had the lockloss (LN2 truck came 30min after lockloss).
17:47 - 18:53: Charge measurement, PSL WD Reset, LN2 at MY CP3
18:53 - 19:31: Initial Alignment. Here are two notable:
19:32 - 20:34: Lock Acquisition. Notes below:
Since I didn't get to align BS in MICH_DARK_LOCK, I selected LOCK_PRMI in ISC_LOCK guardian, but this apparently doesn't work. Sheila mentioned I should have selected PRMI_LOCKED instead. Sheila looked into making the guardian script handle what I did better, but DRMI eventually locked on its own! SOOOOO, I did NOT get to touch the alignment of the BS during Initial Alignment or PRMI.
For DC READOUT (or around there), we received a "Wrong Mode" message. It eventually went away on its own, but will need to figure out what an Operator should do if this message holds us up in the future.
20:41 - 20:48: Ran A2L (per Tues Regular Mainteance) & it took ~7min.
~1205 hrs. local Performed the daily manual overfill of CP3 (minutes after NORCO truck left site following LN2 delivery to CP3's dewar) -> Dewar vapor pressure ("head" pressure) after NORCO delivery has remained near nominal value of ~15 - 18 psi. -> CP3 exhaust line was exhausting GN2 when I arrived as if delivery (increase in LN2 column height in dewar) hadn't resulted in an over fill on its own though the exhaust line pressure was elevated when I arrived (1.5 psi) -> I reviewed the response of the LLCV %open from the previous NORCO delivery and have decided to leave the current manual %open value of 15% as is for now -> I may come in tonight to verify that CP3 isn't over filling on its own and adjust the manual LLCV %open value if needed.
J. Kissel, With only one more week to go on O1 "proper," (see JRPC Wiki), I think we've made the right gamble on not flipping the bias sign (as decided in the last two weeks, see LHO aLOG 24241, and 24383) -- the acceleration of the H1 SUS ETMY ESD's relative actuation strength accumulation in longitudinal is sufficiently negative that we will stay under the desired 10% systematic error in the calibration for at least another week or two (without correcting for the change, which we will do in the future). As usual, H1 SUS ETMX, (though inconsequential) shows a completely tolerable level of charge, and hasn't really moved since we've begun turning OFF the EX ESD Bias Voltage when its not needed. See attached trend plots. The new question is now "when and in what order do we make changes to the DARM loop?" We know we want to do the following (see G1501372): - Clean up the QUAD's longitudinal hierarchical control filters -- converting them all the distributed, and then chosing a better frequency distribution such that we don't need nearly as many violin mode notches, and which ever we do need don't impact the shpae of the over-all super actuator. - Jack up the boost on the DARM filter to get more low frequency suppression. - Reduce the EY Bias Voltage by 2 to reduce the rate of charge accumulation. - Flip the EY Bias to reduce whatever chare has accumulated over the course of the run, such that we hit zero at the start of O2 and stay there. - (maybe move to a true DARM drive?) Each of these tasks, once complete, will require a re-assessment of how close we are to saturations at each isolation stage. Further we should be sure to perform these changes slowly and methodically such that we understand the impact at every step and ensure that we retain IFO robustness (and *maybe* try to keep the DARM loop model and calibration up to date, if it's not too arduous). Part of slow and methodical is asking in what order we perform the above steps, and how much time should we use to reassess robustness in betweeen each step. Given that O2 prep is slated to begin mid-July (see G1501561), I think we can do these 4 (or 5) tasks over the course of a month and still have plenty of time to assess robustness. Further, since - it's unclear how much up-time we'll have during the commissioning period to measure the longitudinal strength change via PCAL, - there are also plans to make changes to the tracking of longitudinal actuation strength (see, e.g., Integration Issues 1138, 1170, and 1155) - making changes to the DARM loop as described above will mean that we'll need to get a new DARM model up and running before valid kappa's can be produced I suggest we continue to make these charge measurements once a week throughout the commissioning period. Though we've (sadly) shown that the optica lever charge assessments are not exactly proportional to the longitudinal assessments from PCAL, the assessment is still close enough that it'll do.
our backup machine cdsfs1 had stopped running on Dec 25th. It was not pingable, so I power cycled it remotely via IPMI at 10:30 PST. I have just started and disk-to-disk copy of /ligo from cdsfs0. I think this is the third crash of cdsfs1 this month. It is scheduled for replacement post O1.
H1 just dropped out of lock. Praxair is NOT on site, so not sure of lockloss reason. Sooooo....Took us to PREVENTATIVE MAINTENANCE, for these activities:
Humorously, as we dropped out, William P. called up to see how we were doing since they (L1) had just made it to Observing. :)
O1 day 102
model restarts logged for Mon 28/Dec/2015 No restarts reported
TITLE: 12/29 DAY Shift: 16:00-00:00UTC (08:00-04:00PDT), all times posted in UTC
STATE of H1: NLN hovering sort of above 70Mpc
Outgoing Operator: Ed
Quick Summary:
Maintenance Tuesday-Lite beginning. Kissel & I are at the helm. We were just sort of discussing a gameplan. Will stay locked as much as possible & also in Observing as much as possible. A Praxair delivery is due today. When/if that happens, I can perform a PSL Watchdog Reset (very quick and non-invasive maintenance task).
Kissel mentioned that our ratty range could be due to some MICH coupling into DARM (he saw a glitch on the running MICH live trace when he walked in); he's investigating.
No wind, and useism is about 0.5um/sec at LVEA.
LLO was up for about 90min a while ago (first time in last day+?). Chatted with William and he also expected a liquid Nitrogen tank delivery.
ISI Blend status:
My claims are unfounded regarding excess SRCL (or MICH) coupling. See attached -- I show the coherence between the current DELTA L EXTERNAL ASD and that of MICH & SRCL error signals, and one can see no excess coherence between MICH or SRCL to DARM in the frequency region where the red, 70-75 [Mpc] DELTAL ASD is above the gold, ~80 [Mpc] ASD. I'd shot from the hip when I saw the excess noise in the 60 to 200 [Hz] noise, because I've seen poor SRCL subtraction take that shape in the past when we were constantly tuning the subtraction (e.g. LHO aLOGs 19774, 18402). I'll keep looking, but I suspect whatever the problem is, it's what has been happening throughout this entire lock stretch (locked in nominal low-noise since Dec 29 2015 07:54:01 UTC). EDIT: Also not coherent with the EOM Driver's 45 MHz amplitude noise suppression loop's control signal (H1:LSC-MOD_RF45_AM_CTRL_OUT_DQ) so, it's also NOT "RF45" noise.
I ran BruCo on 10 minutes of data starting at 2015-Dec-29 16:14:47 UTC. The full report is available here:
https://ldas-jobs.ligo.caltech.edu/~gabriele.vajente/bruco_1135440904/
Unfortunately, in the region between 70 and 100 Hz, which seems the one thta got worse, there hardly is coherence with any channel.
At lower frequency, one can find the usual coherence with SRCL/MICH signals, but it seems too low to explain any excess of noise.
TITLE: Dec 29 OWL Shift 08:00-16:00UTC (00:00-08:00 PDT), all times posted in UTC
STATE Of H1: Observing
SUPPORT: N/A
INCOMING OPERATOR: Corey
SHIFT SUMMARY: IFO locked the entire shift. Range has been ≈ 76Mpc. Winds are ≤ 5mph. uSei has been ≈ 90th percentile range (mean). EQ bands are below .1µm/s except for a small spike from a quake in the Oklahoma area about 3.5 hours ago.
ACTIVITY LOG:
09:40 POP_A_LF_OUTPUT looks ratty and he range has diminished down into low 70-high 60 land. Going to try switching to 45mHz blends at EX. uSei is kinda high bu winds are low.
09:42 Intention bit set to commissioning by SDF when changes to blend made
09:52 Switching blends to 45mHz at ETMX (X) seems to have decreased the amplitude in DHARD_PITCH_OUTMON.
10:02 Intention bit set to Observe. 76Mpc
11:41 GRB alert
15:40 Got the go ahead from Corey to depart a little early :)
The LVEA temperatures are slightly out of control so I have lowered one heater HC1B from 11ma to 9ma on the control signal.
My previous entry about the PRMI branch in the ISC_LOCK guardian isn't as clear as it could be, so here is a newer version.
If you find that DRMI won't lock and seems to be missalinged (you see a lot of higher order modes on the AS camera, POP90 and POP18 flashes are low) you may want to lock PRMI to adjust alignment manually:
The transition from PRMI to DRMI only works sometimes, so this is probably best used only when the alignment is bad for now. (Its not a reliable way to speed up DRMI locking).
The above instructions have changed, only in that the name of the state to request is now PRMI_LOCKED:
If you find that DRMI won't lock and seems to be missalinged (you see a lot of higher order modes on the AS camera, POP90 and POP18 flashes are low) you may want to lock PRMI to adjust alignment manually:
The transition from PRMI to DRMI only works sometimes, so this is probably best used only when the alignment is bad for now. (Its not a reliable way to speed up DRMI locking).