Date: Sun, 14 Apr 2013 12:20:07 -0000 (UTC) Subject: 3.5m Night Log 20130413 From: mcmillan@apo.nmsu.edu Apache Point Observatory 3.5m Telescope Night Log Saturday, April 13, 2013 ACTUAL ASTRONOMER OBSERVER(S) INSTRUMENT START FINISH -------------------------------------------------------------------- T.Murphy R.McMillan APOLLO 19:30 20:25 B.Keeney J.Stocke,B.Keeney DIS 20:30 01:05 C.Churchill C.Churchill DIS 01:10 05:50 INST SCHEDULED WEATH EQUIP OBS NOT USED I/ROW/DN START FINISH D B D B D B D B ---------------------------------------------------------------- DD01/R 19:41 20:26 0 0 0 0 0.0 0.8 0 0 CU02/R 20:26 01:10 0 0 0 0 2.3 2.4 0 0 NM06/R 01:10 06:26 0 0 0 0 5.3 0.0 0 0 note: scheduled times listed include instrument change time ------------- ACTIVITY LOG -------------- Observing Specialist: R.McMillan Mostly clear and productive, with decent seeing in the beginning of the night getting worse during second half. We had a little trouble with windshake on a high-altitude target in the west when gusts were over 30 mph, but when we moved out of the wind it looked fine. Two cases of command collision between observing specialist and remote observer hung up the DIS slitviewer; this is expected. However, both times I noticed that the slitviewer warmed up noticeably after the nubs were restarted, even though it listed the temperature setpoint correctly as -20 C. Both times I reset the setpoint and it continued to warm for a while (up to -10 C) until I stopped guiding to let it cool down. In both cases the exposure time was quite long (30s and 40s), making me wonder if long exposure times interfere with temperature regulation - but then why wouldn't that happen all the time? This behavior is not familiar to me with the DIS slitviewer but I have seen it with other guiders when a restart is needed; it seems to know the setpoint but needs to have it reset anyway. The oddness with the slitviewer temperature regulation did not interfere with observations; the first time I let the slitviewer recover between spectrograph exposures, and in the second case the NA2 guider was doing the active guiding and the DIS slitviewer was just for keeping an eye on the position, anyway. ------- FAILURE LOG ------- PROG INST FAILURE MODE TIME (SEDFNVOG) TI/SHU START FINISH DESCRIPTION ---------------------------------------------------------------------- ---------------- FOCUS LOG --------------- Time Instrument Focus Az El Temp Strc Prim Sec Air filt FWHM -------------------------------------------------------------------------- 18:33 APOLLO 650( 1220) 62 54 9.3 10.9 10.8 10.8 9.6 530 1.20 19:38 dis-slit 593( 344) 126 69 8.6 8.8 9.3 8.8 7.9 - 1.40 21:32 dis-slit 493( 172) -77 77 7.5 7.4 8.0 7.6 7.3 - 1.50 00:22 dis-slit 481( 102) 136 60 6.7 6.2 6.7 6.3 5.9 - 1.90 ------------- WEATHER LOG ---------------- Wind Precip.or Time Temp F Dewp F MPH Direction Dust Sky Conditions ------------------------------------------------------------------ 16:00 54 17 12 259 (W) 1040 mstly clr none 17:00 53 14 12 281 (W) 1094 mstly clr none 18:00 53 14 10 273 (W) 865 mstly clr none 19:00 51 13 19 302 (WNW) 933 mstly clr none 20:00 48 14 18 258 (WSW) 964 mstly clr none 21:00 46 14 22 255 (WSW) 1108 mstly clr none 22:00 46 13 24 267 (W) 1374 clear none 23:00 45 14 18 262 (W) 1819 ptly cldy none 00:00 45 14 18 277 (W) 2491 clear none 01:00 44 15 10 266 (W) 1330 clear none 02:00 43 15 14 266 (W) 1352 clear none 03:00 42 15 12 267 (W) 1413 clear none 04:00 41 15 21 260 (W) 1596 clear none 05:00 40 15 14 261 (W) 1928 clear none 06:00 39 16 16 247 (WSW) 2013 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.15.0 Current TUI version: 2.0.0