### OBSDATE ### 20120825 ### LOGDATE ### 120825 ### OBSERVERS ### ACR ### WEATHER ### partly cloudy ### LOCATION ### MQ ### PROGRAM ### Tau-Sco and other Sco-Cen member orbits. ### SIDEROSTATS ### n3 s3 ### TARGETS ### Started early and checked the autocol positions of N3 and S3 again, slight shift from the previous night but pretty much in the same place so I didn't change anything. Since it was still daytime I checked the S1 autocol position as well, since XH had trouble acquiring last night. It look fine also. Pi-Sco (cal) poor fringes found at -300um after a few search passes, definitely cloud at this point. Tau-Sco fringes at -320, sky cleared briefly for this obs and got a very good, quick(less than 3 mins) 100 seconds. Eta-Lup (cal) fringes at -350, poor fringes again. Tau-lib noted that cart speeds of ~380 are definitely an issue, cart oscillation amplitudes up to a 3rd of the "Servoplot" window height. Fringes at -320, very poor to start with but variable, cloud is probably the issue. Pi-Sco (cal) fringes at -300um cart oscillating again. Tau-Sco fringes at -320um not great, clouds are back. Eta-Lup (cal) fringes at -370um, variable. Del-Sco fringes at -340um, they are ok but again, variable. Cart rates of 500 don't seem to cause oscillations. Pi-Sco (cal) fringes at -340um. Variable, but ok when they are there. Tau-Sco fringes at -330um. Variable, and with cart oscillations (at cart rate 375-400). Eta-Lup (cal) fringes at -400um. Tau-lib couldn't find fringes, it just got way cloudier than earlier. Del-Sco fringes at -360um Pi-Sco (cal) fringes at -350um only got 75 seconds. Lots of cloud came over and lost star. Waiting or a bit for the clouds to lighten up ### QUALITY ### Average ### PROBLEMS ### No issues tonight other than the minor points below. The system worked quite well tonight, other than a few slew fails which are quickly fixed with sb + track. Had taskmaster do the whole job for some targets. 1.One strange issue where PAVO got into the "OFF" state when really it should be in the "AOFF" state. Fixed with a single command. !!MIKE!! can you reply to this email with the command to fix this? I forgot to write it down. 2.Cloud. The "Rat" number didn't really get above 0.2. V^2 on PAVO got to 0.1-0.15 sometimes but was mostly below 0.1. If it wasn't cloudy I would have clicked "very good". 3. N3 does some sort of overshoot sometimes in the elevation position when slewing (5 degrees or so) it seems to get to where it's going eventually. 4. Twice the shutter server went down during shutter sequences, but rebooted successfully, 5. K108 issue when i tried to close roofs. The error was: Sat Aug 25 17:04:42 2012 ERROR: Failed to identify host. Blocking socket. ... this came from you I believe. From when I tried to connect via roofgtk, I got: Sat Aug 25 20:51:15 2012 ERROR: Failed to identify host. Blocking socket. fixed by restarting the server. An Observation: When fringes aren't found where they are known to be (e.g. you just did an obs of this star 30mins ago, or you just lost fringes) it seems that letting PAVO do the searching doesn't always work. I've seen PAVO search a range of positions more than once with no fringes, but if I then start my own fringe search the fringes will be there. One thing I didn't test was whether or not this occurred only hen there were significant cart oscillations.