Reports until 20:32, Saturday 08 August 2015
H1 ISC
jenne.driggers@LIGO.ORG - posted 20:32, Saturday 08 August 2015 - last comment - 00:01, Sunday 09 August 2015(20356)
Locking attempts with higher TCS power

[Jenne, Gabriele]

It's been quite a struggle to get the IFO relocked today.  Last night, Evan et al. ran a TCS tuning test, which left the TCSX CO2 power at 0.43 W.  Yesterday, it had been at 0.23 W. 

Just now (03:12:00-ish UTC) we returned the TCSX power to 0.23 W, and we're leaving it to re-equilibrate. 


Separately, although we don't think this affected our ability to lock, the SYS_DIAG guardian is dead.  It went into error at some point, and reloading it didn't clear the error.  Stefan tried to restart it, but it never came back up.  We await expert advice on fixing this.

It looks like (see log messages below) there is a syntax error somewhere, although no one (in the control room at least....) was editing it.  Perhaps we entered some "if" loop that doesn't usually get run, so that's why this hasn't been caught before?

2015-08-09T00:33:40.06923   File "/opt/rtcds/userapps/release/sys/h1/guardian/SYS_DIAG_tests.py", line 403
2015-08-09T00:33:40.06929     yield 'ISI {} WD saturation count is greater than 75% of max'.format(chamber)
2015-08-09T00:33:40.06932         ^
2015-08-09T00:33:40.06939 SyntaxError: invalid syntax
2015-08-09T00:33:40.09600 guardian process stopped: 255 0
 

Comments related to this report
evan.hall@LIGO.ORG - 23:58, Saturday 08 August 2015 (20357)GRD

There were some typos in the SEI_STATE test that were preventing the node from restarting.

I destroyed and created the node (probably unnecessary), and then started it.

Also, SYS_DIAG_tests.py had not been checked in to the SVN for quite some time.

jameson.rollins@LIGO.ORG - 00:01, Sunday 09 August 2015 (20358)

Thanks, Evan.  It was definitely unecessary to destroy/recreate the node, but it doesn't hurt anything.  Probably all you needed to do was just reload.