### OBSDATE ###
20120112

### LOGDATE ###
120113

### OBSERVERS ###
MJI, JGR

### WEATHER ###
Clear

### LOCATION ###
ROCS

### PROGRAM ###
Test, update wiki instructions, training (for JGR)

### SIDEROSTATS ###
n1   s1 s2  

### TARGETS ###
HR 2326
HR 3207
HR 3117
HR 3165

### QUALITY ###
 Average 

### PROBLEMS ###
After typing star name in taskmaster, N1 hung 'Failed to read enough data from server'.  We couldn't re-compile the sidcon initially because Ben hadn't committed the include directory in arksidcon. Running the code in gdb (debug mode) caused the entire ARK computer to hang (then could not be pinged) and it had to be power cycled. ARK was in a confused state and needed reboot. But got 'Failed to read enough data from server' and 'Failed to allocate message memory' again. We tried continuing past these errors.

S1 continually reports 'Failed to run message job' - about once every second. Where is this coming from? S1 fails on azimuth 179.00 degrees. Can't make S1 work, even manually entering azimuth. Changed to S2.

Re N1 failure: "client_read_socket" in the cliserv library was called with a request to read 83991669 bytes from the socket. Clearly, this will take a while. This faulty message is being read from skymon. It is fixed by closing skymon

Note: tg on HR 2326 produced an air offset of -1 (metres of air).

Bug found in PAVO group delay search; it put zero at left hand side of search and plot. Fixed.

S2 server died twice - both times at the end of a shutter sequence (or start of next)

Experimented with PAVO servo gain: sgain 0.3 is default, sgain 2 is borderline in causing oscillation/loss of fringes (in tonight's quite good seeing conditions).

We had 128 microns offset at end of night in zeroset.