The dust monitor in the Diode Room is hung, (no response to remote commands). When into Diode Room and power cycled the unit. Ran zero count test and flow rate check. Both tests are within spec. After the power recycle of the dust monitor the unit is still hung up. Need to recycle the comptroller to recover remote communications. Fillberto will power cycle the comptroller during Tuesdays window.
Attached are spectra for HAM and BSC ISI CPS sensors.
The xterm window did not display any that were over threshold.
Commissioning: Mostly done, but there is some remaining ASC work. (Keita & Sheila?)
Tues Maintenance Plans: See photo for list for tomorrow.
Would like Maintenance to be over by noon to allow for LHO All Hands Meeting.
Weekend Summary: Relatively successful weekend with coincident running for Virgo's Engineering Run (which should now be over, awaiting email). Here are summary points from Keita:
Laser Status:
SysStat is good
Front End Power is 33.98W (should be around 30 W)
HPO Output Power is 157.3W
Front End Watch is GREEN
HPO Watch is GREEN
PMC:
It has been locked 4 days, 3 hr 15 minutes (should be days/weeks)
Reflected power = 16.56Watts
Transmitted power = 56.13Watts
PowerSum = 72.69Watts.
FSS:
It has been locked for 0 days 3 hr and 5 min (should be days/weeks)
TPD[V] = 3.142V (min 0.9V)
ISS:
The diffracted power is around 4.3% (should be 3-5%)
Last saturation event was 0 days 3 hours and 14 minutes ago (should be days/weeks)
Possible Issues:
I don't see anything from the report.
TITLE: 06/26 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 65Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
Wind: 13mph Gusts, 10mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.16 μm/s
useism took a quick step up between 22:00 - 3:00 to just above the 50th percentile (still low). See an odd jump up for EY low freq seismic noise at about 14:30utc (no incursions seen on Access System & winds...well, there is a small increase up to 15mph...that is probably it: local EY wind event.
QUICK SUMMARY:
Ed passed on some PRMI alignment tweeks he tried last night. L1 has just rejoined us. Virgo has been down for 7hrs (perhaps their Engineering run is over?).
TITLE: 06/26 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 65Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY:
LOG:
7:25 First locking attempt resulted in NLN for about 5 seconds
7:41 Second attempt: Lockloss at CARM_ON_TR
8:18 Third attempt: After much diddling with PRMI and, basically all PRC optics, I got a better alignment which resulted in A good NLN lock.
8:30 Large glitch
8:33 Bounce modes are still above 10e-15 but coming down. However, there are abnormally high resonances between 10Hz and slightly above roll mode freqs.
08:20 Intention bit Undisturbed
12:56 Lockloss. Nothing obvious
13:43 H1 back into Observing mode
14:34 Spoke to Jeremy at LLO. They're getting aligned and ready to re-lock.
12:56UTC Lockloss
13:43 H1 back to Observing
H1 locked and observing fort 2hr58min @ 65Mpc. There were a couple of glitches. Everything looks fine.
9:39UTC confirmed with Danny at Livingston.
08:20UTC 66.2Mpc
TITLE: 06/26 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
Wind: 4mph Gusts, 3mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.17 μm/s
QUICK SUMMARY:
TITLE: 06/26 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ed
SHIFT SUMMARY: A weird instability started a little into my shift. I think an initial alignment fixed this, but now I am still having trouble locking. It doesn't seem to be dropping at any particular place, and it has been difficult to get past DRMI. Passing it off to Ed with DRMI locked.
LOG:
Not the same issue as last time, no obvious reasons why at this point.
Same as last one, I'll try an initial alignment since DRMI wasn't great ast time.
Doing and initial alignment seemed to help, but it broke as I reached NOMINAL_LOW_NOISE. Time to try again.
Observing 03:35 UTC
The control signals started ringing up for the past 40min or so. They got to the point where I felt like we were going to lose it any second. CSOFT P and CHARD P seemed to be rung up the most, so in an act of desperation I went to ramp down the gain on those one at a time. It didn't work.
There are no obvious clues to me as to why the control loops started to ring up. I attached the lockloss plot and some trends
Back to Observing 01:09 UTC
The instability continues, but doesn't seem to be getting worse to the point of lock loss. It is hurting our range as we are now down to 56Mpc.
Summary: H1 Remained Locked, L1 Broke lock, Virgo was already down before EQ
H1 rode through this decent-sized EQ from the South Pacific. The green ITMY Z EQ BLRMS signal approached 1000nm, but never got there (instructions say to take it to LARGE_EQ, which I assume is LARGE_EQ_NOBRSXY [I'm assuming even when locked?], but we never reached the threshold).
Play By Play Of Signals/Tools/Monitors As EQ Approaches/Passes:
The last conversation that I had with Jim left me the understanding that switching to Large EQ anything is done after the lock is broken and is to simply keep the tripping under control. Unless I misunderstood, I don't think switching in-situ is going to help. Am I wrong? anyone?
Ed's right, the only intent of the large eq state is to keep the tables from tripping when the low frequency ground motion is large. Going to this state outside of some narrow circumstances will probably break the lock. The other eq states might work better, but the transition isn't fast enough and will also probably break the lock.
To remind everyone what the response is during an earthquake: While the IFO is locked, do nothing. AFTER the IFO goes down, if the earhtquake is big (probably like a mag 7+, but depends on distance) switch to the large eq state. When .03-.1 hz blrms are somewhere below 1 micron, switch back to the windy state. This is just to prevent tables from tripping, saving time and steps in recovery. The hope is that if the tables don't trip, you're less likely to have to do an initial alignment.
If you like resetting watchdogs and running through initial alignment, feel free to ignore these directions.