corey.gray@LIGO.ORG - posted 21:25, Friday 11 September 2015 - last comment - 00:08, Saturday 12 September 2015(21418)
H1 Lockloss at 3:22UTC (8:22pmPST)
9/11 EVE Shift: 23:00-7:00UTC (16:00-0:00PDT), all times posted in UTC
3:22 H1 lockloss. "ITMY Saturation" on VerbalAlarm. Terramon said a 4.5 Japan quake within a minute of this, but we don't see any seismic evidence.
- Lock Attempt#1: Slight tweaks on ETMx for ALS & then H1 went on its way. DRMI took about 6min. Dropped out at RF DARM.
- Attempt#2: During this attempt, I noticed I had accidentally tweaked TMSx instead of the ETMx(!) in Attempt#1. So with Evan's suggestion, I paused at DC_READOUT, and then carefully tweaked the TMSx back (accidentally took it to 40.085, and returned it to its nominal 41.485). I returned TMSx with no issues.
- 4:06 H1 back up to NOMINAL_LOW_NOISE.
- 4:07 Evan going to start Noise Budget Injections (so this is why the range will look wonky from 4:15 & on....
I also talked with LLO (William on shift), and he said they were fighting roll modes. When they get it back, Anamaria/Robert would like to do PEM Injections (they said it was late, so they might only wait it out a little longer). So Evan will be opportunistic (WP5467) with H1 in the meantime.
Because of the pointing change to TMSX noted above, there was now an SDF Diff for the pitch offset for TMSX, so I added this channel to the Not Monitored list (NOTE: yaw was already not-monitored, not really sure why pitch was left out). Sounds like this is left to Operators to take care of Not Monitoring these pit/yaw biases as we go through alignments in the future (which is a bit of a rare thing nowadys with aLIGO H1).
The more indepth story is that I had to move TMSX a little. SDF had a setpoint value of 41.5848. When I used conlog to get the value, it didn't list the original value, it lists the first change from the original value. So, the first change was 41.4848, and I thought that is where I had to go to, but since SDF showed me that difference, I knew I was off by 0.1 and moved the TMSX pit to 41.5848. But it still had a diff (an issue with decimal points between values). So at this point, I chose to NOT MONITOR this channel.