Grabbing the opportunity to dither-up while Livingston is still in the process of re-joining the search.
IFO has been locked in Observing for the past 15.5 hours. Need to damp the 4735 Hz violin mode and run the A2L script at the next opportunity. No other problems or issues noted.
Ops Shift Transition: 01/27/2017, Owl Shift 08:00 – 16:00 (00:00 - 08:00) - UTC (PT)
TITLE: 01/27 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 67Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Locked and Observe the entire shift. The 4735Hz has been ringing up slowly, been waiting for LLO to go down to damp it.
16:32 Kyle, with Apollo, on site.
17:22 Operator Checklist
21:00 Weekly Meeting (see minutes in aLog)
22:10 Fil and Mark to MY
22:18 Corey to MY
22:40 Corey to MX
Attached is the 3IFO and spare parts desiccant cabinet relative humidity data with the last few months appended. Looks near zero except when I've opened the cabinets to look for items or take the RH reading.
BRSY shows drift as one of the photodiode spots works it;s way of the photodiode. The large spike is when the box was opened to install the STS. The downward trend following thermalization shows signs of decreasing. Next weeks maintenance will be to re-center and re-zero the STS that is co-mounted to the BRS. The margin of the drift still remains good between the defined thresholds.
For Next Tuesday's Maintenance:
VAC - Kyle will be running roughing pumps in he mechanical room next Tuesday. Gerardo will be modifying an ion pump power supply for HAM6. He will also be going to MX for purge air maintenance.
SEI - the sei team would like to re-center and re-zero the masses on the STS that is co-mounted to the BRS at EY. They would also like to begin model changes to the ISIs. They will begin with BSCs and the Output arm only as trips to input arms could potentially be to costly to chance at this time.
CDS ELE - The addresses need o be set on the Beckhoff interlock modules for the safety system. They would also like to take a look at the illuminator on ETMY.
REMINDER:Benton County Sheriff will now be making routine visites to the site during evening and owl shift times. It would help to carry proper site related ID on your person.
19:41UTC Lockloss. No immediately apparent cause
20:39 Back to Observing
Attached is a 30 day trend of the ITMs and BS SUS vertical and Pitch drifts, along with the BSC3 external temp sensor. Recall that the LVEA temperature control was a bit wild for a few weeks during extreme cold in our region which ended up apparently raising the temp as seen by the test mass suspensions. This was remedied around 6 days ago and the BSC3 temp channel reports a cooling trend. Subsequently, the TM and BS suspensions have been drifting back up.
Ignore the first channel on the plot, the BSC1 external temp sensor jumps around with offsets periodically for some unknown reason.
Message: ETMY_ST2CPSINF_H3 high freq noise is high!
These plots were generated by Jim's new script launcher that he asked my to try out.
These plots are made by two scripts launched from the OPS -> WEEKLIES screen (BSC CPS PYTHON & HAM CPS PYTHON), unfortunately they only work from the Debian machines (the Ubuntu signal python libraries don't have Welch!? ). The message Ed posted comes from some warnings that the scripts post to the xterm launcher window. If operators use these scripts to do the CPS famis, they should include that output, if any this comes up.
For this task, corrective action is generally only required when either 1.) a single sensor is close to a factor of 10 above the CPS spec noise around 100 hz (I haven't added the noise spec to the plots yet, coming soon), or 2.) multiple sensors on a stage are a factor of a few above the spec noise. This is usually not urgent (exceptions being the HAM5 incident in December, the ISI wouldn't re-isolate), and can wait to be addressed on a maintenance day.
TITLE: 01/26 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC STATE of H1: Observing at 68Mpc INCOMING OPERATOR: Ed SHIFT SUMMARY: Observing the entire night. Ed pointed out that the 4735 Hz line is rung up. I was paying attention to the wrong line and did not notice it. LOG: 08:45 UTC Diag reset H1IOPASC0 to clear timing error 11:31 UTC GRB. LLO is down.
Have remained in observing. H1IOPASC0 reported a timing error. I hit diag reset and cleared it. No other issues to report.
I've opened FRS7244 to investigate these infrequent high cpu processing times on h1iopasc0
Krishna
I took a quick look at the data from the PEM STS at EndY, which is mounted on the BRSY platform. The channels are mentioned in 33533.
First plot shows the GND STS (used by SEI) and the PEM STS converted to angle units (by multiplying by w^2/g) in comparison to the BRSY - rX. The wind-speed during this time was less than 2-3 m/s. The GND STS sees less signal than the BRS below ~50 mHz, but the PEM STS sees a lot more. The second plot shows the coherence between some channels and the third plot shows the X-direction signal. The Z channel is not recorded so I can't access it through ligodv-web.
The source of extra noise in the PEM STS could be - a) Insufficient mass centering or b) Extra temperature noise either on the STS case or the table it sits on; more insulation to the table and the STS case might help...
When allowed (Tuesday?) we could go check the centering and center it up as needed--Hugh
On Tuesday went to EndY to Check on and Center the PEM STS Masses
Upon arrival checked the mass measurements right away: U V & W were -3.7 -1.8 & -12V. The X axis is generated from U V & W but the Y signal comes just from V & W. See manual for axis mapping.
While the W mass is clearly out to lunch, U is also high >2volts. However, as W contributes to both X & Y signals (but with different weightings) you'd think both X & Y signals would be noisy. One might even argue that Y(North on STS Manual) would be even worse than X.
This morning, Thursday ~0930pst, with an IFO Lockloss, we went to the VEA again to check and found the U V & W masses exactly where I recorded them almost two days ago after nearly two hours of centering attempts: 9.9 12.9 & -13.5V. After recording the voltages this morning, we hit the centering button and left the VEA.
Now see the attached 60 hours of minute trends. Before the Tuesday mass centering activity, the X & Y time series values suggest fairly zero'd signals; I did zoomed in and they are. During the interum ~2 days before this morning's look, the Y signal was pined to a rail. Noting my U V & W voltages, before Tuesday just W was on it's rail but after Tuesday, essentially all 3 masses were at or near a rail. This further suggests you can not just look at the X Y & Z signals to assess the mass centering.
So, clearly, waiting for the masses to come off their rail did not yield results. In addition, it appears there is a higher frequency noise on the channels showing up on X after Tuesday and now on Y after this morning's centering.. We will go measure the mass voltages when allowed. I did leave some leads hanging off the monitor port for voltage measuring but they are mostly insulated and I don't think they are causing noise. However, we'll remove these next time just in case.
Meanwhile, the positive glitches seen on the time series (average is still under the min trace but the max [black] is way higher than the average) are not continuous. I guess these show up as the 1/f noise starting around 40Hz on the spectra, second attachment. The reference traces are 1200utc 31 Jan (before the Tuesday activities.) Note the higher noise on the X (pink) trace compared to the Y signal (cyan.) I checked the wind, it did not seem to be an issue at that time.
I have to just throw this in and run.
Here is a comparison of the SEI Ground STS and the the PEM unit on the BRS. These have some gain difference I don't understand yet but I made them the same by multiplying by the ratio at the useism. At this BW, the PEM is not happy.
The pending leap second LED cleared at 16:00 PST indicating the leap second was applied correctly. Disappointingly I did not see the seconds indicator do the 58, 59, 60, 00, 01 sequence, it looks like it stayed on 00 for two seconds.
It did what it was supposed to do, programmed that way to stay on for 2 seconds.
H1 back into Observe