Subject: 3.5m Night Log 20230907 From: ajt@apo.nmsu.edu Date: Fri, 8 Sep 2023 14:04:21 +0000 (UTC) Apache Point Observatory 3.5m Telescope Night Log Thursday, September 07, 2023 PROG PI ASTRONOMER OBSERVER(S) -------------------------------------------------------------------- SU01 J.Hughes J.Hughes,K.Covey,K.Devine&Class UW04 J.Hughes J.Hughes,K.Covey,K.Devine&Class ON-SKY PROG INSTRUMENT START FINISH -------------------------------------------------------------------- SU01 KOSMOS 23:24 01:10 UW04 KOSMOS 01:10 05:30 UW04 EYEPIECE 05:30 06:30 PROG SCHEDULED WEATH EQUIP OBS NOT USED I/ROW/DTN START FINISH D B D B D B D B ----------------------------------------------------------------- SU01/O 19:29 01:10 4.1 0 0.1 0 0.9 0.6 0 0 UW04/O 01:10 06:34 0 0 0 0 0.0 5.4 0 0 note: scheduled times listed include instrument change time ------------- ACTIVITY LOG -------------- Observing Specialist: A.Townsend&C.Gray I think the bird flying around in the arcade is a Townsend's warbler so I'm going to name him mini-me. Dataq was frozen at the start of the night, but this time it said "Status: FILE FULL Please wait for device reconnect" at the bottom of the dataq window, and anytime I tried to close it I got a popup saying "Cannot open \\.PSF\WinDaq Data\pmss-20231556.wdq." I had to restart Windows within parallels and also power cycle dataq on hub35m, then I was able to bring it back online. Stayed closed at sunset due to nearby radar and visible virga. We opened after 23:15 with really good seeing! I focused KOSMOS both times in imaging mode, not on the slitviewer. At the first field we stopped the telescope and closed the mirror covers in order to get a calibration frame and the altitude axis was acting weird, with the error "Sub-command(s) failed: : Sub-command(s) failed: : Sub-command(s) failed: INIT: Timed out; STATUS: Timed out". I noted the current altitude, reopened the mirror covers, took out the stop button and re-initialized the axes and got the Reverse Software Limit along with the zeroed out altitude position due to axis controller reset. We reset the position in talk2boxes, did a few test slews and then got back on sky. (PR2164) We had a few troubles with MOS masks being incorrectly oriented, but were on sky for the rest of the night. For the last hour, we put the eyepiece on the telescope, and with the really good seeing we got to see some really cool things including the comet! ------- FAILURE LOG ------- FAILURE MODE TIME PROG INSTR TI/SHU START FINISH DESCRIPTION ---------------------------------------------------------------------- SU01 KOSMOS T/H 11:54 00:04 Altitude controller reset error ---------------- FOCUS LOG --------------- Time Instrument Focus Az El Temp Strc Prim Sec Air filt FWHM -------------------------------------------------------------------------- 23:49 kosmos 240( 1494) -29 75 18.5 19.3 20.4 18.9 19.0 -- 0.90 03:56 kosmos 235( 1426) -96 28 18.0 17.3 18.0 17.0 17.4 -- 1.10 ------------- WEATHER LOG ---------------- Wind Precip.or Time Temp F Dewp F MPH Direction Dust Sky Conditions ------------------------------------------------------------------ 16:00 76 36 11 278 (W) 860 ptly cldy none 17:00 76 35 11 280 (W) 745 ptly cldy none 18:00 72 33 2 245 (WSW) 759 mstly clr none 19:00 70 32 1 316 (NW) 646 mstly clr none 20:00 67 37 7 354 (N) 5975 mstly clr none 21:00 67 37 10 7 (N) 2209 mstly clr none 22:00 66 37 9 46 (NE) 1186 mstly clr none 23:00 67 36 4 21 (NNE) 982 mstly clr none 00:00 66 36 8 44 (NE) 987 mstly clr none 01:00 67 36 2 24 (NNE) 901 mstly clr none 02:00 64 36 5 355 (N) 800 mstly clr none 03:00 64 38 11 127 (SE) 1104 clear none 04:00 64 37 8 128 (SE) 1179 clear none 05:00 65 37 1 166 (SSE) 1258 clear none 06:00 63 38 3 125 (SE) 1383 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 SOFTWARE ---------- Current TCC version: 1.4.2 Current HUB version: v20171231_01 Current TUI version: 3.1.3beta0