03:05UTC USGS reports 5.6 near Chile at 2:43UTC. Seismon hasn't reported it as of 3:12UTC
3:40UTC first signs of ground motion on EQ BLRMS .3um/s. Terramon still not updated. Seismon isn't either.
1:19:45UTC Got this error. Have no idea what this is. It doesn't seem to have broke anything o my present knowldege.
Full data plots of H1:SYS-TIMING_Y_GPS_A_ERROR_FLAG and H1:SYS-TIMING_Y_GPS_A_ERROR_CODE for the last 8 hours are attached. The error code momentarily went to 4. From the medm I might guess this is decoded as 'Waiting for GPS lock'. This seems familiar: alog 35111.
@ 00:21
I, however, did not get the alert. I checked the INJ_TRANS node and it was still in the nominal 'wait' mode. I then called Keita inquiring as to wether I should manually KILL injections to which he agreed I should.
Node was reset at 2:09UTC.
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 66Mpc
OUTGOING OPERATOR: Travis
CURRENT ENVIRONMENT:
Wind: 13mph Gusts, 10mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.18 μm/s
QUICK SUMMARY:
Dick in control room with a new SERF student and his family. H1 humming along as quietly as it can.
TITLE: 06/11 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 65Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY: No issues to report. Lock is ~52 hours old.
LOG: None
Locked for 48 hours currently. No issues to report.
Had a friendly local stop by the site for a lunchtime snack. Apparently Robert isn't the only one who likes the berries on the trees. See pics.
TITLE: 06/11 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 63Mpc
OUTGOING OPERATOR: Patrick
CURRENT ENVIRONMENT:
Wind: 2mph Gusts, 1mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.23 μm/s
QUICK SUMMARY: No issues handed off. Locked for 44+ hours.
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.
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.
