TITLE: 06/11 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC STATE of H1: Observing at 63Mpc INCOMING OPERATOR: Travis SHIFT SUMMARY: Remained in observing the entire shift. No issues. Not even a PI mode to damp. Locked almost 44 hours. LOG: No events to note.
Have remained in observing. No issues.
TITLE: 06/11 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 64Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
Wind: 7mph Gusts, 6mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.20 μm/s
QUICK SUMMARY:
Locked for over 36 hours. No known issues.
TITLE: 06/11 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 64Mpc
INCOMING OPERATOR: Patrick
SHIFT SUMMARY:
H1 locked for ~ 36hrs. Nothing to report. Handing of to Patrick
LOG:
TITLE: 06/10 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 65Mpc
OUTGOING OPERATOR: Travis
CURRENT ENVIRONMENT:
Wind: 16mph Gusts, 10mph 5min avg
Primary useism: 0.05 μm/s
Secondary useism: 0.17 μm/s
QUICK SUMMARY:
This is posted a bit late.
ETMX is incoherent to about .73 @ 13-15Hz. LLO operator was informed.
23:31UTC Intention bit "Undisturbed"
Before and after screen caps below:
TITLE: 06/10 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 61Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY: Locked for my entire shift and 28 hours total so far. We did drop out of Observe a couple of times due to TCS ITMx laser losing lock (see aLog 36777), but it relocked itself without issue. Two large tour groups (50 people each) led by Mike and Betsy from ~20:00-21:00 UTC.
LOG: Nothing not previously logged.
TCS_ITMX_CO2 caused us to drop out of Observing for ~1 minute due to the laser losing lock.
And again from 22:08-22:11 UTC.
The whole story is in the title. Per Keita's request.
Was it reported by Terramon, USGS, SEISMON? Yes, Yes, No
Magnitude (according to Terramon, USGS, SEISMON): 5.1, 5.1, NA
Location: 72km WSW of Puerto Madero, Mexico; LAT: 14.4, LON: -93.0
Starting time of event (ie. when BLRMS started to increase on DMT on the wall): 18:54 UTC
Lock status? H1 rode it out with a glitch showing up in the BNS inspiral range plot. LLO lost lock possibly coincident with the EQ.
EQ reported by Terramon BEFORE it actually arrived? Not sure.
No issues thus far. H1 has been locked for 24 hours.
Rolf, Keith, Carlos, Dave:
During the CDS Face2Face meeting at LHO June 6-9, we worked on the LHO DTS:
JoeH from LLO called at 16:34 UTC to ask if we had receieved a GRB alert. We did not. He said that they also only got a single alarm, not the typical repetitive alarm that requires acknoledgement.
TITLE: 06/10 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 61Mpc
OUTGOING OPERATOR: Patrick
CURRENT ENVIRONMENT:
Wind: 6mph Gusts, 4mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.14 μm/s
QUICK SUMMARY: No issues were handed off and H1 has been locked for 20+ hours. Bubba is leaving the site as of 15:14 UTC and reports that the door lock issue has been resolved.
TITLE: 06/10 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC STATE of H1: Observing at 61Mpc INCOMING OPERATOR: Travis SHIFT SUMMARY: Observing entire shift. No issues. LOG: 13:19 UTC Bubba to LSB
Have remained in observing. No issues to report.
TITLE: 06/10 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 64Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
Wind: 10mph Gusts, 7mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.10 μm/s
QUICK SUMMARY:
INJ_TRANS guardian node is not set (see previous alog). No other known issues.
The INJ_TRANS guardian node has a request of NONE and is in the INIT state. Should the request be changed to INJECT_SUCCESS or INJECT_KILL?
Jenne and I reviewed the ISS status this morning. Jenne noticed that the RIN of the 2nd loop out-of-loop PD array shows increased coherence between 7~30Hz. I continued to investigate the comparison of the ISS state between now (6/8 19:00 UTC) and May 1st (5/1 1:00 UTC).
The 2nd loop out-of-loop floor level shows the stability of 1e-8 [1/rtHz] for both cases. However, the stability below 30Hz is worse than the one on May 1st. (Attachment 1. The blue curves are the current, and the red curves are the ones on May 1st.)
Attachment 2 shows the ISS QPD pointing. The yaw shows the shift from 0 to +0.3 while the pitch stayed ~-0.7. (Is that Okay?)
The 2nd loop PDs (inner/outer) exhibited 5~7% decrease, while the input power was also decreased 5%. So there looks some real decrease of the incident power on the PD exist. (Note tthat the QPD sum decreased -6.5%).
Can we change the features in the power spectrum by realigning the ISS PDs?
Rick sent me a couple of reference alogs regarding the ISS QPD centering:
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=30915
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=29583
It seems that the last ISS QPD centering was done on Oct 27, 2016. (Attachment 1)
I've checked the ISS QPD pointing since this last centering (Attachment 2). The pointing gradually drifted out from the center in the pitch diection during the first two months. There was no yaw drift. After the vent, there was no big change in pitch, but was in yaw.
I took the in-loop/out-of-loop spectra of the invac ISS array outputs right after the last centering (Attachment 3). The spectra were basically the same as the ones seen before the vent, and thus were better than the current level.
Because there was no intentional offset on the QPD pointing, we should try to center the beam on the ISS QPD (in the next possible occasion) to see if this helps to reduce the residual intensity noise at the low freq band.
