Evan G., Chris B., Rick S.

Summary:
We started the INJ_TRANS guardian node, but due to a time zone issue in the gpstime python module, we couldn't schedule injections to verify the code was doing the right thing. We will come back to make the final tests once the time zone issue is sorted out. 

Details:
To do this test, we logged into the guardian machine and updated the guardian SVN to get the latest and greatest updates from Chris.

Then, because the guardian node for INJ_TRANS was not running, we started it by
$ guardctrl create INJ_TRANS; guardctrl start INJ_TRANS

We added a test injection to the new schedule file, set an injection time in the near future, and verified it by the following:
$ PYTHONPATH=/opt/rtcds/userapps/release/cal/common/guardian:${PYTHONPATH}
$ CAL_USER_APPS=/opt/rtcds/userapps/release/cal/common
$ python ${CAL_USER_APPS}/scripts/guardian_inj_schedule_validation.py --schedule ${CAL_USER_APPS}/guardian/schedule/schedule_1160692574.txt --min-cadence 300 --ifos H1

The state of the guardian never changed as it should have, so after some debugging, we found the difference in the GPS time the node thinks it is versus what GPS time it really is, is about 7 hours. It is likely due to the fact we got the following warning when starting the guardian node:
/ligo/apps/linux-x86_64/gpstime/lib/python2.7/site-packages/gpstime-0.1.2-py2.7.egg/gpstime/__init__.py:220: RuntimeWarning: GPS converstion requires timezone info.  Assuming local time...
  RuntimeWarning).

Chris is going to investigate how to set the time zone info for the GPS module before we try again to fully test the infrastructure