Subject: 3.5m Night Log 20220415 From: cgray@apo.nmsu.edu Date: Sat, 16 Apr 2022 11:57:45 +0000 (UTC) Apache Point Observatory 3.5m Telescope Night Log Friday, April 15, 2022 PROG PI ASTRONOMER OBSERVER(S) -------------------------------------------------------------------- BY06 E.Hintz E.Hintz UW13 B.Morris B.Morris ON-SKY PROG INSTRUMENT START FINISH -------------------------------------------------------------------- BY06 TripleSpec --:-- --:-- UW13 ECHELLE 23:35 05:37 PROG SCHEDULED WEATH EQUIP OBS NOT USED I/ROW/DTN START FINISH D B D B D B D B ----------------------------------------------------------------- BY06/R 19:42 23:35 0 1.5 0 2.4 0.0 0.0 0 0 UW13/R 23:35 06:24 0 0 0 0 0.0 6.8 0 0 note: scheduled times listed include instrument change time ------------- ACTIVITY LOG -------------- Observing Specialist: C.Gray Several problems tonight. First, TUI became non-responsive during checkout. Stop/Starting and Restarting the hub but it would not start a new process. Russet suspected the truss lamp daemon, which was correct, as was a problem that occurred Oct 30 of this year (PR 1990). She quit truss lamps and was able to restart the hub. We used the steps in PR 1990 to control the lamps via telnet. The suspicion is that disk space needs to be made, which Shane will look into tomorrow. The next problem was the attempt to use the NA2 guider instead of the tcam. After many, many attempts to center up a position on gcam to fall into the slit of tcam, combined with thick clouds, we finally gave up. Since this was a combination of not having tcam as well as having clouds, we note the time it took to test gcam against tspec position and when we just couldn't test anymore due to clouds. BY06 donated the remainder of their time to UW13, who was able to punch through the clouds. Next, we had alt issues for UW13. There were strong alt oscillations at alt 66 and 55 at 00:23 and 00:25, respectively. The oscillations caused a motion error at 00:23. I stopped, reinitialized the drive, and then did a couple test slews and we were fine for the rest of the target's integration. However, it happened again at the next target before we were done slewing in az at 00:35. I did a slew, going down to 10 deg alt and then coming back up and we were fine for the rest of that target. When we were able to get through the clouds the seeing wasn't half bad. I focused tspec using agile and seeing was around 1.23. ------- FAILURE LOG ------- FAILURE MODE TIME PROG INSTR TI/SHU START FINISH DESCRIPTION ---------------------------------------------------------------------- BY06 Tspec T/S 19:42 20:25 Hub needed restart BY06 Tspec T/H 20:25 22:25 Trouble shooting guider ---------------- FOCUS LOG --------------- Time Instrument Focus Az El Temp Strc Prim Sec Air filt FWHM -------------------------------------------------------------------------- 23:38 ecamera 453( 86) 311 72 10.9 10.4 10.8 10.5 10.5 ND2 0.92 ------------- WEATHER LOG ---------------- Wind Precip.or Time Temp F Dewp F MPH Direction Dust Sky Conditions ------------------------------------------------------------------ 16:00 61 1 24 240 (WSW) 1487 mstly cldy none 17:00 59 -1 17 247 (WSW) 1560 mstly cldy none 18:00 57 -2 19 257 (WSW) 4360 cloudy none 19:00 53 -1 16 262 (W) 1971 cloudy none 20:00 51 -1 16 254 (WSW) 1621 cloudy none 21:00 52 -1 13 266 (W) 1342 cloudy none 22:00 52 -1 16 275 (W) 1273 cloudy none 23:00 51 0 17 266 (W) 1281 cloudy none 00:00 52 0 18 281 (W) 1244 cloudy none 01:00 50 -1 13 286 (WNW) 1240 mstly cldy none 02:00 50 -2 16 291 (WNW) 1308 ptly cldy none 03:00 50 1 18 271 (W) 1364 mstly cldy none 04:00 49 1 16 298 (WNW) 1329 ptly cldy none 05:00 48 5 18 304 (NW) 1524 ptly cldy 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: 2.6.0