Displaying report 1-1 of 1.
Reports until 14:29, Wednesday 07 March 2018
H1 SUS
betsy.weaver@LIGO.ORG - posted 14:29, Wednesday 07 March 2018 - last comment - 13:34, Thursday 08 March 2018(40882)
ETMX SUS OPLEV trends - unexpected jump. Already.

This morning, Travis had to repoint the ETMX with some bias to get it back on the Oplev which I found odd.  The Oplev had been zeroed to the ETMX SUS last ~Monday reportedly by Jason.  However, besides that jump in the trend data, there is another jump on Tuesday.  I am guessing that the ISI EX model work/bootfest changed the pointing of the floating ISI/SUS.  Travis used the ETMX SUS to repoint back to zero.

This morning, Jim locked the ISI so hopefully there will be no more unexpected shifts due to anything ISIish.

Side note - try not to bump the OPLEV piers.  Ever. 

 

 

Images attached to this report
Comments related to this report
hugh.radkins@LIGO.ORG - 13:34, Thursday 08 March 2018 (40900)

Not that it isn't possible, but, it does not look to me like the reboots of the isi did anything to the OpLev readout.  Further, what can SEI do to pitch unless the optic is locked?  Based on everything I know and can see, I did not think the SEI could do this, it has only been DAMPED, READY or TRIPPED.

The attached 3 hour plot shows the OpLev Pitch, and WD, Guardian and CPS positions for the ETMX.  The step on the OpLev occurs at 1940 on Tuesday.  It is a full 14 minutes later that the Guardian is manipulated and 26 minutes later before the isietmx FE boot at 2006.  Below is the day boot start log--nothing is causal to the OpLev shift.  Meanwhile there is no hint of movement on the ISI (HEPI has been locked for more than a week) during the OpLev Pitch shift, (yaw is tiny) and none until the signals go to zero at 2005 at the start of the isi boot.  Just goes to show, sometimes you have to look closer.

hugh.radkins@opsws1:06 1$ more *.log
2018_03_06 11:13 h1asc
2018_03_06 11:13 h1omc
2018_03_06 11:13 h1sqzwfs
2018_03_06 11:15 h1susopo
2018_03_06 12:02 h1isiitmy
2018_03_06 12:04 h1oaf
2018_03_06 12:06 h1isietmx
2018_03_06 12:06 h1pemex
2018_03_06 12:13 h1alsex
2018_03_06 12:13 h1calex
2018_03_06 12:13 h1iopiscex
2018_03_06 12:13 h1iscex
2018_03_06 12:13 h1pemex
2018_03_06 12:24 h1oaf
2018_03_06 12:43 h1iopiscex
2018_03_06 12:43 h1pemex
2018_03_06 12:45 h1alsex
2018_03_06 12:45 h1calex
2018_03_06 12:45 h1iscex
2018_03_06 12:56 h1dc0
2018_03_06 12:57 h1dc0
2018_03_06 13:01 h1broadcast0
2018_03_06 13:01 h1dc0
2018_03_06 13:01 h1fw0
2018_03_06 13:01 h1fw1
2018_03_06 13:01 h1fw2
2018_03_06 13:01 h1nds0
2018_03_06 13:01 h1nds1
2018_03_06 13:01 h1tw1
2018_03_06 15:20 h1oaf
2018_03_06 15:20 h1pemcs
2018_03_06 22:03 h1fw0
2018_03_06 22:12 h1fw0
hugh.radkins@opsws1:06 0$ pwd
/opt/rtcds/lho/h1/data/startlog/2018/03/06
 

Images attached to this comment
Displaying report 1-1 of 1.