### OBSDATE ### 20120815 ### LOGDATE ### 120816 ### OBSERVERS ### XH ### WEATHER ### Cloudy at the beggining, clear after, RH < 70% ### LOCATION ### ROCS (Sydney) ### PROGRAM ### Looking at Be star disks, and also binary stars. ### SIDEROSTATS ### n1 s2 ### TARGETS ### hr322/hr100 ### QUALITY ### Average ### PROBLEMS ### I find the new opcon gtk pretty convenient. The cart behaved quite nicely all night long. As Ben said, RH indicates 0% in the environment monitor. When launching pavogtk, error windows "Got PAVO_CAMERA_STATUS with wrong data." appear endlessly even after restarting the server... I tried to stop and start the camera again from the control menu but it didn't change. Ben fixed it with the new version of pavo gtk. Then the display didn't work saying "the width and height of the image is too large 512 512". Mike says it is a consequence of tweaking the camera menu that I did just before. He fixed it. At this point, S2 server crashed and I had the message " Warning: Could not send elevation the absolute position. Giving up" and "WARNING : elevation not indexed" although the Alt and El looked fine previously. So I indexed it. Went from Bet Cru to Delta SCo but clouds. Didn't find the star. Went to zet sgr, acquisition went smoothlty but when trying to find the fringes, S2 server crashed After that acqlabjack doesn t want to center the star and the white cross. Solution: reopen (from Yitping). Acqlabjack probably lost track of the sids that are being used. The ldc went to limit meanwhile...so I did what is in the bugshooting page. After that, I can't explain why I didn't find the fringes. I searched from -3000 to 3000 with step of 3, several times... I changed target and finally found fringes on Hr 322 (binary) at -800. On a calibrator (hr 100), they were at -850. Took a couple of frames on these two and stopped at twilight. During this last part of the night, putting the HR number in the taskmaster and staying around the fringes position were the only tasks I had to do, nice.