We don't seem to be ablke to use the lockloss tool tonight, I get this message. I'm not sure if this is realted to bug 834, or to some maintence activity today.
sheila.dwyer@opsws4:~/Desktop/Locklosses$ lockloss select
Traceback (most recent call last):
File "/ligo/cds/userscripts/lockloss", line 288, in <module>
args.func(args)
File "/ligo/cds/userscripts/lockloss", line 199, in cmd_select
selected = select_lockloss_time(index=args.index)
File "/ligo/cds/userscripts/lockloss", line 106, in select_lockloss_time
times = list(get_guard_lockloss_events())[::-1]
File "/ligo/cds/userscripts/lockloss", line 93, in get_guard_lockloss_events
time = parse_guard_timestring(line[0])
File "/ligo/cds/userscripts/lockloss", line 76, in parse_guard_timestring
return gpstime.strptime(string, format)
File "/usr/lib/python2.7/_strptime.py", line 325, in _strptime
(data_string, format))
ValueError: time data '2015-05-06T02:27:30.12109' does not match format '%Y-%m-%dT%H:%M:%S.%fZ'
This was the result of the guardian log time stamp change, which slightly changed the format of the time stamps in the logs.
It should be fixed now.
thanks