Date: Thu, 7 Feb 2008 06:15:07 -0700 (MST) From: Jack Dembicky Subject: 3.5m Night Log 20080206 Apache Point Observatory 3.5m Telescope Night Log Wednesday, February 6, 2008 ACTUAL ASTRONOMER OBSERVER(S) INSTRUMENT START FINISH ------------------------------------------------------------------- T.Thuan T.Thuan Y.Izotov DIS 16:30 00:05 E.Hilton E.Hilton AGILE 00:05 06:25 INST SCHED(TWILIGHT) WEATH EQUIP OBS DAY NOT USED I/ROW/DN START FINISH D B D B D B USE D B --------------------------------------------------------------------- UV01/R 18:35 00:10 0 0 0 0 5.6 0 0 0 0 UW04/R 00:10 05:59 0.2 0 0.5 0 5.1 0 0 0 0 note: scheduled times listed include instrument change time ------------- ACTIVITY LOG -------------- Observing Specialists: J. Dembicky Running the new Rotator controller tonight for Fritz. Watching for problems. Slitviewer images 375-377 looked strange, like somebody had turned on a light, no light was on. I stopped the slitviewer (we were guiding with the NA2 guider at the time and just running the slitviewer in manual mode to keep track of the object on the slit). I then took 2-1 sec exposures (first one was messed up, second one not sure) then took a 10 sec exposure and things seemed fine again. I don't think it was a shutter problem, looked more like a problem with the camera, but not sure what (I could see what appeared to be the scratches on the slit like it was a real image). No time was lost since we were guiding with the NA2 guider. When I started AGILE (after stopping the telescope with the stop switches) the rotator stated a stop switch was still in (although the alt and az slewed fine. I did an axis stop and start and then tried rotating via tcc. that seemed to fix the problem and I had my observer slew again. Nimble crashed on us around 01:35. This may have had something to do with a bad param file Eric sent (He got a segmentation error earlier). We had to reboot Nimble a couple of times, but got it back up and running. Found out that having 2 users log in simultaneously to Nible is not a good idea (crashes the machine) or maybe we were both sending recovery commands that caused the 2nd crash? New rotator controller seemed to work fine, other than the glitch at the start of the night. At 05:45 the winds finally closed us down with sustained/gusts >40MPH. ------- FAILURE LOG ------- PROG INST FAILURE MODE TIME (SAEDFNVOG) TI/SHU START FINISH DESCRIPTION ---------------------------------------------------------------------- UW04 A I/H 01:35 02:05 Nimble crashed, rebooted ---------------- FOCUS LOG --------------- Time Instrument Focus Az El Temp Strc Prim Sec Air filt FWHM ----------------------------------------------------------------------- 18:06 DISslit 14(-320) 143 61 -3.8 -0.8 -1.2 -1.7 -2.9 -- 1.5 21:49 DISslit -61(-501) 82 38 -3.3 -3.6 -2.4 -3.9 -3.6 -- 2.3 00:23 AGILE -11(-897) -47 46 -4.1 -4.2 -3.8 -4.5 -4.1 B 1.5 ------------- WEATHER LOG ---------------- Wind Precip.or Time Temp F Dewp F MPH Direction Dust Sky Conditions ------------------------------------------------------------------- 16:00 31 -2 12 281 (W) 554 clear none 17:00 27 -2 13 306 (NW) 473 clear none 18:00 25 0 12 280 (W) 519 clear none 19:00 26 1 14 267 (W) 623 clear none 20:00 25 1 15 267 (W) 700 clear none 21:00 28 3 23 292 (WNW) 723 clear none 22:00 26 4 18 302 (WNW) 650 clear none 23:00 26 5 13 311 (NW) 532 clear none 00:00 25 7 16 325 (NW) 526 clear none 01:00 24 9 18 340 (NNW) 424 clear none 02:00 23 9 11 313 (NW) 377 clear none 03:00 22 9 17 4 (N) 453 clear none 04:00 20 9 15 357 (N) 459 clear none 05:00 20 9 24 21 (NNE) 450 clear none 06:00 22 4 39 21 (NNE) 517 clear none Note: the wind was coming from the azimuth listed. The convention used is north=0 degrees, east=90 degrees. The dust count is particles > 1u per 0.1 cubic feet. TELESCOPE STATUS Telescope drives operational. Current TCC version: 2.9.1 Current TUI version: TUI 1.4.4