We have been locked for 5.5 hours. LLO is still currently down and struggling with some mystery noise after the commissioning period today.
I was informed by the Norco delivery driver that the mechanical level gauge (LI105A) at the X-end dewar was not responding to changes in the LN2 level, i.e., it was stuck @ 205" WC. I investigated and confirmed his observation. In doing so, I also discovered that the valve connecting the High and Low lines to this gauge (V-7) was open. This valve is normally closed and shorts out both the mechanical level gauge, as well as, the CDS level transducer which shares these lines and is connected in parallel to the mechanical gauge -> I will repair or replace the mechanical gauge on Tuesday. For now, I closed V-7. This should correct the "noisy" level signal that Chandra had noticed on CDS.
Begin 1 hour standdown.
TITLE: 04/12 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 63Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
Wind: 9mph Gusts, 6mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.14 μm/s
QUICK SUMMARY: No issues handed off. Locked for ~1.5 hours.
Accepted the following SDF Diffs to go back into Observing
for some cameras their EPICS values were no longer updating, even after restarting their processes via monit. We took the opportunity to patch and reboot the machines h1digivideo[0,1,2]
Accept SDF diff for IMC-REFL_SERVO_IN1GAIN setpoint -6 to -8
444 channels added 25 channels removed Differences, new channel list and blacklisted channel list (frequently changing channels not marked read only in burt files) attached.
To support any future LN2 dewar low-level alarms, I've started a strip tool on the virtual stripshooter server which plots a 7 day trend of all eight dewars. It is accessible from the LHO CDS home page via 'VAC (screen shots)' -> 'dewar.stp-current.png'
Attachment shows the stiptool image after it has been back-filling for one day.
I mistakenly did not make all of the states all caps in the SEI configuration nodes, sticking with the Guardian standard. This finally bit me in the butt when jim pointed out that the SEI_CONF node was not able to get to the full SC off state because of some state name confusion. Today I went through and changed all of the state names to be in all caps, and then reloaded the necessary nodes. I tested one node and went through some of the states, all went well.
Starting CP3 fill. LLCV enabled. LLCV set to manual control. LLCV set to 50% open. Fill completed in 136 seconds. TC A did not register fill. LLCV set back to 20.0% open. Starting CP4 fill. LLCV enabled. LLCV set to manual control. LLCV set to 70% open. Fill completed in 542 seconds. LLCV set back to 37.0% open.
I committed the following files to the SVN repository: /opt/rtcds/userapps/trunk/sus/h1/burtfiles/h1susmc2_down.snap /opt/rtcds/userapps/trunk/sus/h1/burtfiles/h1susetmx_down.snap /opt/rtcds/userapps/trunk/sus/h1/burtfiles/h1susetmy_down.snap /opt/rtcds/userapps/trunk/pem/h1/burtfiles/h1pemcs_safe.snap /opt/rtcds/userapps/trunk/cal/h1/burtfiles/h1calcs_safe.snap /opt/rtcds/userapps/trunk/sus/h1/burtfiles/h1susmc2_observe.snap /opt/rtcds/userapps/trunk/sus/h1/burtfiles/h1susetmy_observe.snap /opt/rtcds/userapps/trunk/psl/h1/burtfiles/iss/h1psliss_OBSERVE.snap /opt/rtcds/userapps/trunk/pem/h1/burtfiles/h1pemcs_safe.snap /opt/rtcds/userapps/trunk/cal/h1/burtfiles/h1calcs_OBSERVE.snap There are a few Guardian items, which is addressing. No other differences found.
Should say: TJ is addressing the Guardian differences.
model restarts logged for Tue 11/Apr/2017
2017_04_11 10:57 h1pemcs
2017_04_11 10:59 h1calcs
2017_04_11 11:45 h1broadcast0
2017_04_11 11:45 h1dc0
2017_04_11 11:45 h1fw0
2017_04_11 11:45 h1fw1
2017_04_11 11:45 h1fw2
2017_04_11 11:45 h1nds0
2017_04_11 11:45 h1nds1
2017_04_11 11:45 h1tw1
2017_04_11 11:46 h1nds0
2017_04_11 13:01 h1calcs
2017_04_11 13:03 h1broadcast0
2017_04_11 13:03 h1dc0
2017_04_11 13:03 h1fw0
2017_04_11 13:03 h1fw2
2017_04_11 13:03 h1nds0
2017_04_11 13:03 h1nds1
2017_04_11 13:03 h1tw1
2017_04_11 13:04 h1fw1
Maintenance day. New calcs and pemcs code, added chans to broadcaster, added seismon edcu. Two DAQ restarts
model restarts logged for Wed 05/Apr/2017 - Mon 10/Apr/2017 No restarts reported
model restarts logged for Tue 04/Apr/2017
2017_04_04 14:46 h1broadcast0
maintenance day, added channels to GDS/DMT broadcaster.
model restarts logged for Wed 29/Mar/2017 - Mon 03/Apr/2017 No restarts reported
FAMIS #6518 Added 100 mL H2O to the crystal chiller. There were no errors on either chiller. The canister filters appeared clear.
Main task at LHO is Robert's PEM test to distinguish between the Swiss cheese and the eye baffle as a source of 100 Hz noise in DARM from the HVAC, trucks, and other 8-18 Hz vibration as well as the transient 12 Hz combs.
A2L Pitch above 0.4 and Yaw is around 0.8. Ran the A2L repair script while in the commissioning window.
[Vaishali, JimW, Jenne]
During maintenance, while no one needed the IMC, we tried out our new L2A decoupling filter for MC2. Recall that Jim found that it would be helpful in alog 35330, and we measured and fit TFs for it in alog 35397.
We found that (a) the pre-existing L2A decoupling was in fact worse than doing nothing at all, and (b) that our new filter works well.
In the attached screenshot, the upper left corner is the Foton Bode plot of our decoupling filter. In the other 3 DTT panels we have the coherence and transfer functions of 3 different MC2 L2A configurations. For these measurements, the IMC was unlocked, but MC2 still aligned. The red traces in all panels are with no L2A decoupling at all. The blue traces are with the old L2A "decoupling" gain. That was a flat gain, and clearly was making things worse than doing nothing at all, over a pretty broad frequency range. The green traces are with our new L2A decoupling filter on, and we win almost 20dB of isolation below a few hundred mHz.
We have accepted the new L2A settings for MC2 in the safe and observe SDF files, so they should always be on now.
I've looked at the coherence between MC2 M1 length drive and the two pitch witnesses (MC2 Trans qpd and MC2 M1 Pit) during locks before and after the install of the new L2P feedforward, and things look better. Attached plot shows the coherence between MC2 M1 L and MC2Trans (top plot, blue is before, red after) and MC2 M1 L and MC2 M1 P (bottom plot, blue is before, red after). Below .1 hz the coherence is much better, which should help for wind and earthquakes, which is what I was looking at originally anyways. Above .1hz the coherence is pretty much unchanged, not sure why, maybe the motion is dominated by the table motion at those frequencies?
Always useful to actually post promised plots...
PI mode 19 started to ring up a bit to cause the SUS_PI node to change some of the PLL filters causing an SDF diff. Mode 19 is not one of the modes that we regularly damp while at 30W, but it may have been excited from the wind. I went to clear the SDF diff but just trying to click the unmonitor button would not work, there was an exclamation point next to the "MON" but I'm not quite sure if that was suppose pop up a screen for me that didn't work remotely, or if it was something else. I managed to select the unmonitor all, with only that channel having an FM3 diff, and getting it to accept it that way. I'm worried that this may have accepted the entire filter bank, and there was another screen that I couldn't see that would allow me to choose what parts on that filter bank to monitor.
We are back to Observing and there is a screenshot below of the SDF diff.
I brought this back to how it was before I unmonitored this entire bank, but I unmonitored the FMs since the PI Guardian can change them. I was correct that I was suppose to get another screen for the filter bank when clicking the !MON button, but I could not get this remotely.
