### OBSDATE ###
20120110

### LOGDATE ###
120110

### OBSERVERS ###
MJI

### WEATHER ###
Partly cloudy, little wind

### LOCATION ###
SUSI

### PROGRAM ###
See if I've fixed the weird PAVO dispersion bug

### SIDEROSTATS ###
n1 n3  s1   

### TARGETS ###
canopus

### QUALITY ###
  Quite bad (no/almost no useful data

### PROBLEMS ###
Things to be fixed in daytime:

1) The s1 and n3 server had a continuous display of "Failed to run message job"

2) PAVO couldn't connect to the n1 server, and then had a memory allocation error. 

The n3 beam really was horrible. Faint and bad quality with speckles. Really needs comparison to n1 data to see what is going on here.

S beam t/t appeared to have fringes across it.  This has happened often in the past and is I think (?) nothing to worry about. Plausibly could be speckles/seeing.

Independent of old or new PAVO code , there was a noise peak intermittently at the left of the group delay plot. I saved a little data to help diagnose this... but when I clicked save, the problem wasn't at its worst.

The cart lost its position (laser heater current out of range, needs reset). Due to clouds I didn't bother with this.

N3 had an offset of  221, -123

Certainly the PAVO noise peaks were generally at zero dispersion rather than -5m, but I can't definitively say that anything was fixed. Code commited anyway.