Date: Thu, 22 Apr 2004 07:10:54 -0600 (MDT) From: Jack Dembicky Subject: 3.5m Night Log 20040421 Apache Point Observatory 3.5m Telescope Night Log Wednesday, April 21, 2004 ACTUAL ASTRONOMER OBSERVER(S) INSTRUMENT START FINISH -------------------------------------------------------------------- R.Kron L.Grodnicki DIS 20:34 07:10 INST SCHEDULED WEATH EQUIP OBS DAY NOT USED I/RO/DN START FINISH D B D B D B USE D B --------------------------------------------------------------------- UC01/R 20:34 05:29 0 0 0 0 7.5 1.4 0 0 0 note: scheduled times listed include instrument change time ------------- ACTIVITY LOG -------------- Observing Specialist: J.Dembicky We opened around 19:30 to start things cooling. Around Midnight the observers linux box started doing strange things (becoming unresponsive and/or sluggish). I noticed that the slitview images were starting and stopping as well, while the remote observer reported not stopping/re-starting them. The NA2 guider also had problems loosing the guidestar around Midnight, but it may have just been a focus/seeing issue in this case and that seemed to solve itself as I adjusted focus, which is how I discovered the slitview problem. Finally she was not able to type back at me in TUI (she was receiving messages from me fine though). After her image (3 of 4) read out and it started the next exposure, I had her log out of TUI (It wouldn't close down, but did show her logged out on my end) and she rebooted her Linux box. This didn't seem to fix the problem on her end (her computer was still running slow) so she decided to revert back to Remark to finish observing (her 4th exposure continued on it's merry way even after she logged out, which does now begs the question of how do the obs specs kill a in-progress TUI exposure, not that I wanted to do that in this case. There is probably a low level TCC command that will do this maybe???). No observing time was lost, as TUI (on our end) handled the exposures fine, even after the observer logged out. Moving to Remark didn't seem to remidy the situation (Our guess was it was an internet connection problem on the Chicago end of things) so Idid the slews and exposures for the observer. She was able to FTP the images, so it's not positive if it is an internet problem or not. Since she was able to effectively work with the telescope, I did her observations for her for most of the 2nd half (luckily she was just taking spectra of one galaxy all night long). In the morning she logged back in and the connection seemed to be back to normal, she was able to complete a final std. star and do her cals. ------- FAILURE LOG ------- PROG INST FAILURE MODE TIME (SEGDFVO) TI/SHU START FINISH DESCRIPTION ----------------------------------------------------------------------- ---------------- FOCUS LOG --------------- Air/Truss Wind Time Instrument Focus Az El Temp-C Dir MPH filt FWHM --------------------------------------------------------------------- 20:38 DISslit 275(1416) 67 69 7.5/8.4 256 20 none 1.5 20:39 NA2gdr -4621(42358) 66 69 7.4/8.4 267 23 clear 1.3 01:05 NA2gdr -3160(43839) -137 54 5.9/6.0 296 17 clear 1.1 ------------- WEATHER LOG ---------------- Wind Precip.or Time Temp F Dewp F MPH Direction Dust Sky Conditions ------------------------------------------------------------------ 16:01 54 14 16 236 (SW) 1269 Clear none 17:01 52 12 25 255 (WSW) 1069 Clear none 18:01 52 14 17 264 (W) 1438 Clear none 19:01 49 14 19 256 (WSW) 1383 Clear none 20:01 46 13 20 256 (WSW) 1419 Clear none 21:01 45 11 17 244 (WSW) 1514 Clear none 22:01 44 11 9 264 (W) 1806 Clear none 23:01 44 10 12 267 (W) 1976 Clear none 00:01 44 11 10 271 (W) 2629 Clear none 01:01 43 11 15 281 (W) 2550 Clear none 02:01 42 12 17 291 (WNW) 2181 Clear none 03:01 42 9 13 319 (NW) 2389 Clear none 04:01 41 11 14 303 (WNW) 2233 Clear none 05:01 43 5 14 307 (NW) 2979 Clear none 06:01 43 0 9 310 (NW) 3391 Clear none 07:01 40 7 11 266 (W) 3161 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 Remark version: 2.85b Current guide software version: guider v4.1b4 Current TCC version: 2.7.2 Current TUI version: TUI-0.842