cheryl.vorvick@LIGO.ORG - posted 19:45, Monday 03 July 2017 - last comment - 00:57, Tuesday 04 July 2017(37300)
Corrected H1 glitching with alignment of TMSX and TMSY
First attachment:
- 23:56-00:29UTC - corrected the glitching with aligning TMSX and TMSY
- left most plot
- 00:29:20-0045:50UTC - a2l is running during this plot
- left of center plot
- 0045:50-00:50:49UTC - checked TMSX and TMSY alignments
- right of center plot
- 00:50:49UTC - H1 back in Observe
- 00:50:59-00:58:26UTC - the first 8 minutes of Observe
- right most plot
Second attachment:
- 23:29-00:58:26UTC - total time span matches the first attachment (all on one plot)
- left most plot
- easier to see how OMC_DCPD_A changed
- 00:58:26-1:43UTC - showing the first big glitch in H1, which coincides with the arrival of an EQ
- middle plot
- 03:06-01:06UTC - July 3rd to 4th - showing entire lock
- right most plot
- shows ASC-X and ASC-Y qpd sum values were lower at the beginning of the lock that after I'd adjusted TMSX/Y
- shows the effect of aligning and a2l on OMC-DCPD_A amplitude
Total time out of Observe = 54 minutes.
Images attached to this report
Comments related to this report
Nice!
- TMSX and TMSY went more than 3 days and 4 locks with the same alignment.
- I believe this alignment was good enough to lock, but the arms as defined by the ITM and ETM moved, and possibly TMS drifted as well, and then TMS was no longer optimally aligned to the arm.
- Since going back to Observe, there has been at least one EQ that degraded the range, other large glitches have been in the bucket, and I'm not sure from what, but the glitches before aligning TMSX/Y were lower frequency.
Images attached to this comment
09 January 2016: O1 alog where aligning TMS saved the lock.