Scott L. Chris S. Tyler G.

While DOT's battle to regain SR 240 post "tumblegeddon" has past, it would seem our fight has only begun.

Beginning Jan 2, the facilities team has focused its efforts on mitigating the considerable impedance that the tumbleweeds have imposed on traveling along the X and Y arms. But, to no avail. Our efforts on Jan 2 & 3 along the x arm were quickly undone when another wind storm came through on Sat, Jan 4. 

With delivers and site walkthroughs being performed on and around our regularly scheduled Tuesday maintenance window we shifted our priority for tumbleweed processing from the X arm to the Y. By 1pm local time we had the Y arm mostly cleared and absolutely passable. By 3pm, the Y arm was once again obstructed.

At this time, facilities is discouraging any attempt to travel along the Y arm between now and tomorrow morning. The X arm is absolutely NOT passable and will likely remain in this state for most of the week and maybe longer.

Based on the forecast in front of me, we are likely to see some intermittent winds through Wednesday. We will continue making our best effort to keep high priority areas outside of the corner station accessible but progress may be slow.  

To reiterate my point from this morning's all hands meeting: Please don't run over tumbleweed piles in the cars. As the arms are (slowly) opened up for travel no low clearance vehicles should be driven down the arms as running large piles over can and will rearrange and damage the undercarriages of the cars and in some extreme cases will high center the vehicle.


Attached photos are of the X arm looking at the mid station. These are the worst areas we've encountered to this point. For reference, the harvester is approximately 13' tall.

More photos/videos available upon request.

TITLE: 01/06 Day Shift 16:00 – 00:00 (08:00-16:00), all times posted in UTC

STATE of H1: Locking

INCOMING OPERATOR: Corey

SHIFT SUMMARY: High wind/microseism caused us range issues until we lost lock. Been attempting to re-lock since then, got as far as MOVE_SPOTS.

LOG:

16:53 (08:53) Tyler driving tractor from EX to EY

17:40 (09:40) Coffee/refrigeration onsite

18:52 (10:52) Coffee/refrigeration leaving site

22:03 (14:03) Lockloss due to seismic/wind conditions

22:12 (14:12) Gerardo to LVEA -- check ion pump

22:25 (14:25) Gerardo out of LVEA

22:56 (14:56) Chandra to MY

23:19 (15:19) Chandra back from MY

It's pretty breezy out, and the microseism is creeping up above our 90th percentile.  As a result, we have pretty terrible range.  Sheila pointed out that a simpler way to test whether the scattering that Robert postulates (in alog 54298) does indeed come from scatter between the end test masses and reaction masses is to change the angle of the end reaction masses.  If we can affect the scatter by changing the angle between the etm and reaction mass, then it points to Robert being correct that this relative displacement is a source of scatter. 

Keita okay-ed this work to happen during Observation while the environment is bad, as long as the ramp times for moving the reaction chains are long.  In order to do this in Observe, Niko unmonitored R0 offset and tramp channels for the optic align sliders for both ETMs. 

I started moving both the ETM reaction chains at the same time, only in pitch, up to about 8 urad from their nominal positions.  I was getting some pretty bad glitches (which I think were due to increasing wind), so just in case, I moved them both back to their nominal positions.  About 80 seconds after those ramps finished, we lost lock.  I attach a screenshot of my ndscope, but mostly as a reminder to myself what channels I was looking at.  I don't think I had moved enough yet to see anything difinitive.  I had been hoping to move a few tens of urad, both in pitch and in yaw, and then do a series of ~10 min new positions, 10 min old positions, 10 min new, etc. to see if the angle really makes a change.

I wonder however if I was moving the ETMs by moving the reaction chain, and since the glitches are loud enough to drown out the ADS lines, the ETMs weren't really following.  Something to try when we get relocked will be to turn up the ADS line amplitudes to get better signals, and make sure that the SOFT angular degrees of freedom are doing what they need to do.

DQ Shifter: Yanyan Zheng
Email:zytfc@umsystem.edu

Fellow(s):Ethan

Duty cycle and BNS range:

• The duty cycle of observing is (94.4+49.8+0+83.8+89+90.8+94.4)/7=71.74%
  • On Wednesday, out of observation for the whole day, due to the computer crash and heavy wind(alog54224)
  • Seveal lockloss due to the corner station models crashed (alog54187),a High Voltage trip at HAM6 (alog54280)and the connection error in Beckhoff/Slow Controls land (alog 54320), Lockloss on Monday without reason(alog 54173).
• The BNS range ~115Mpc.
  • On Friday and Sunday the BNS range are ~120Mpc. The rest of the days are ~110Mpc

Glitches:

• On Wednesday, Thursday and Saturday and Sunday, the wind speed were very high. It caused the excess noise at 10-60Hz.
• Earthquake and high microseism on Sunday caused excess noise at 10-60Hz.
• Vilion modes at 500Hz and 1000Hz presented most time of the week.

Dechar

• Hveto:
  • H1:ASC-AS_A_RF45_Q_YAW_OUT_DQ is the 1st round winner on Saturday. It picked most excess noise that may be caused by the wind and earthquake.
  • H1:LSC-POP_A_LF_OUT_DQ is the 1st round winner in the rest days of the week.

Pcal

• No pcal X and Y image on Wednesday due to out of observation all the day
• Nothing unnormal during the week

Spectra

The band semilog ration changed a little bit on Tuesday. Otherwise, nothing unnormal. 

More details can be seen at https://wiki.ligo.org/DetChar/DataQuality/DQShiftLHO20191230

Not sure how common this is, but the ISI_ETMX_ST1_SC Guardian briefly went into fault and then returned to its nominal state

Just an update that the fences are holding up to the 50+ mph winds we've been seeing, and seem clear of tumbleweeds (photos attached).

FAMIS 11525

TCSX chiller: added 280mL, there was an air bubble caught in the sock filter so it seems like more than usual. The sock filter is still in need of replacement, but I will wait for a time to turn off the chiller and wipe out and around where the filter seats.

TCSY chiller: added 100mL.

• VAC visitors this week
• End station work deferred (except for nitrogen delivery) for Maintenance due to tumbleweeds
• Lab fume hood work, no alone allowed on roof
• LVEA turbo work ongoing
• RF cable relabeling ongoing (PSL racks tomorrow)
• ALS Guardian work at 8am
• IMC WFS centering work
• PSL diode/PMC tweaking from CR

- IFO was observing with an average duty cycle of (71 + 73.3 + 67.2 + 93.8 + 93.6 + 88.2 + 91.9)/7 = 82.7% for the week.
- The BNS range hovered around 118Mpc on Monday and Tuesday, rest of the days it was around 115Mpc.
- Increased low frequency glitches (10-30Hz ) due to high microseism, especially Thursday onwards.
- Earthquakes and high microseism knocked the IFO out of lock a number of times throughout the week. Earthquakes alog 54061 alog 54014 alog 54111 alog 54157 microseism alog 54142
- On Saturday and Sunday, there was a lockloss due to unknown causes. alog 54160 alog 54167.
- Corner Station air compressor duty cycle reduced significantly to reduce the noise that it was creating. alog 54071.
- Issues with seismon on Friday, it was not updating. alog 54149
- Wandering Pcal X line in the high frequency region.

Link to the entire DQ Shift wiki page :https://wiki.ligo.org/DetChar/DataQuality/DQShiftLHO20191223

Ops Shift Transition: 01/06/2020, Day Shift 16:00–00:00 (08:00-16:00) - UTC (PT)

State of H1: Locked

Intent Bit: Observing

Weather: 10-40 mph wind

Primary 0.03 – 0.1Hz: 0.01 um/s

Secondary 0.1 – 0.3Hz: 0.4 um/s

Outgoing Operator: Camilla

Quick Summary: Locked and Observing for 3.5 hours, wind and microseism are both on the rise.

TITLE: 01/06 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 93Mpc
INCOMING OPERATOR: Niko
SHIFT SUMMARY: Wind is increasing (even more!) and the arms are pretty full of tumbleweeds.
LOG:

• 08:41 SEI_DIFF from FULL_DIFF_CPS to CORNER_DIFF_CPS which is now our nominal state.
  • Instantly reduced glitches in 20-30Hz band.
  • As shown in attached 1 hour plot of SEI_DIFF change (top plot), 20-30Hz BLRM (middle), wind (bottom)
• 10:49 SEI_CONF to EQ for incoming 5.7mag form Puerto-Rico
• 11:06 Lockloss
• 11:08 SEI_CONF to LARGE_EQ to help relocking
• 11:31 SEI_CONF to EQ (couldn't lock Green arms in LARGE EQ)
• 12:03 SEI_CONF to WINDY
• 12:40 NLN and Observing
• 15:15 SEI_CONF to EQ
• 15:20 Tyler taking the tractor from EX to Y arm to tackle this weekends tumbleweeds
• 15:28 SEI_CONF to WINDY

FAMIS 11251

Nothing has moved more than a few μrad in the last week. ITMY has moved 4μrad in the last month.

TITLE: 01/06 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 119Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_CONF state: WINDY
    Wind: 17mph Gusts, 13mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.52 μm/s
QUICK SUMMARY: Locked 14h30 with microseism on the rise and tumbleweeds blown against some buildings.

(Kyle R, Richard M, Gerardo M)

The HAM6 RGA ion pump system crashed, this caused the the HAM6 high voltage interlock to trip and take the IFO down.  The controller for the ion pump was found with a message on the main screen, message was "short", and the "short' remained after several attempts to start the controller.  We could not locate a direct replacement for such controller, and we have 2 different types, a negative and a positive (we need a positive type), due to time constraints the decision was to swap the cable for the high voltage interlock back to the nominal state, back to HAM6 Inficon gauge.  Attached is a plot of PT110 gauge pressure for the past 30 days.

FRS ticket 14014.

J. Kissel,

As we've done in O3A (see LHO aLOG 51245), I hold this space for documenting start times of high-frequency roaming calibration line sweeps to be used for estimating the sensing function uncertainty above 1 kHz.

(All times UTC)
2019-11-01 16:55:02 HIGH_FREQ_LINES guardian reinitialized for the Start of O3B, starting at 4001.3
2019-11-12 18:35:25 data not found on ndscope while only shortly at last data point, 1001.3,  [CAL EX / EY front-end models restarted, and filter coefficients updated; see LHO aLOG 53188 LHO aLOG 53210]
resumes at
2019-11-12 18:38:37 re-started at 4001.3 Hz
2019-11-21 00:49:47 re-started at 4001.3 Hz
2019-11-29 14:40:20 re-started at 4001.3 Hz (and not yet finished)