Date: Wed, 11 Mar 2009 06:50:35 -0600 (MDT) Subject: 3.5m Night Log 20090310 From: "Jack Dembicky" Apache Point Observatory 3.5m Telescope Night Log Tuesday, March 10, 2009 ACTUAL ASTRONOMER OBSERVER(S) INSTRUMENT START FINISH ------------------------------------------------------------------- M.Klaene J.Dembicky Echelle 20:15 06:25 S-H, NA2gdr INST SCHED(TWILIGHT) WEATH EQUIP OBS DAY NOT USED I/ROW/DN START FINISH D B D B D B USE D B --------------------------------------------------------------------- EN01/O 20:01 06:25 0 0 0 0 0 10.4 0 0 0 note: scheduled times listed include instrument change time ------------- ACTIVITY LOG -------------- Observing Specialist: J.Dembicky Alt Vel scale measured -606.5 was -605.0 changed -606.0 Az Vel scale measured 581.0 was 581.0 changed n/c Fritz was working on the terminal server for the 3.5m until around 20:15, so this delayed me in doing my instrument checkout (since I couldn't communicate with the instruments without the terminal server working). Turned TSPEC array power on, to clear error from last night. Test images looked fine. All instruments checked out fine (I didn't check Agile). Zero'ed rotator (fritz suggested I do so as well due to the terminal server crash earlier). 0.35 deg adjustment. Mounted TSPEC. all LEDs were still lit, as they were supposed to be, after I mounted the instrument. I wiggled cables and tapped on the controller boxes to see if I could get a fault, but the LEDs stayed lit. I took a test image after I got back to the control room and the instrument appeared to be working normally. While waiting for the telescope to cool I switched to the Echelle to do a quick pointing check there (eAurigae). Star dropped almost on the slit. I didn't do any corrections, since I would be doing a pointing model later in the evening and will check after that, but things looked really good to start the night. Observed eAurigae for Bill with the echelle. Under clear sky (in the region) I used 23s exp for 32k counts. The sky was clear but for some reason the counts went up and down a bit (25s was near 40K, 20s was 25K and 18s was 15k). I choose 23s as a happy medium. 60s for HR1544 gave about 13k cts HR1544_60s.0022.fits is actually a 40s exposure, I forgot to change the exp time. Set of bias, red, blue and ThAr cals also taken The APO nightlogFocus script was broken tonight. When I clicked start to record the focus it hung and didn't record anything. I didn't catch it until after I was finished with the echelle and moved the telescope to focus the NA2 guider. I reloaded it but it still hung. Next I switched back to NA2, focused the guider and started an 80 point pointing model. The weather status page shows the 3.5m closed when we are actually open. Checked pointing at NA2 after new pointing model was implemented then switched to NA1 to check pointing there. 07:22:22 Could not focus the telescope after I switched to the Echelle. Read timed out on Port LTA10. It appeared that the tertPoint script did not finish and stopped the focus change (it took a couple minutes for the tertpoint script to time out and then I had focus control again). NA1 pointing corrections Was 1097 775 Change 95 21 Final 1192 796 This correction DID NOT move the star correctly! The tertpoint script also appeared to hang (even though it looked to be finishe with the start button active). After a minute or two a timeout on port LTA10 error would come thru and the telescope would respond again. I ran the tertpoint script again (after the initial correciton above and it gave me almost identical change values (95 and 25) even though the star was in a different position. Something was not working correctly with the tertpoint script so I manually adjusted the star into the slit. Final XTILT/YTILT positions were 1105 580 At 07:31:10 Some very strange errors coming thru the TUI log window 07:31:10 TC01.ecam 17 ecam f txtForTcc="Could not parse command doread √∏ 512.0" 07:31:10 .hub 0 cmds i CmdDone=7507 07:31:10 .tcc.0 0 tcc W Expected="doread 5.00 1 1 256.0 256.0 512.0 512.0" 07:31:10 .tcc.0 0 tcc W Received="Could not parse command doread x" 07:31:10 .tcc.0 0 tcc F Modu="prt_ReadMatch"; Text="bad reply" 07:31:10 .hub 0 cmds i CmdDone=7496 07:31:10 .hub 0 cmds i NewCmd=7508; CmdTime=1236756670.2; Cmdr=".tcc"; CmdrMID=0; CmdrCID=".tcc.0"; CmdActor="tcc"; CmdText="" 07:31:10 .tcc.0 0 tcc I GCamCmd="findstars 1 256.0 256.0 512.0 512.0 10.8 10.7" 07:31:10 .tcc.0 0 tcc W Expected="findstars 1 256.0 256.0 512.0 512.0 10.8 10.7" 07:31:10 .tcc.0 0 tcc W Received=" " 07:31:10 .tcc.0 0 tcc F Modu="prt_ReadMatch"; Text="bad reply" 07:31:10 .hub 0 cmds i CmdDone=7508 07:31:10 .hub 0 cmds i NewCmd=7509; CmdTime=1236756670.28; Cmdr=".tcc"; CmdrMID=35; CmdrCID=".tcc.3"; CmdActor="tcc"; CmdText="" 07:31:10 .tcc.3 35 tcc W Text="failed to measure pointing error" I could not connect to the F: drive on the Shack-Hartmann Machine. I saved data to c:\SHData on the Shack-Hartmann machine itself. TIP/Tilt Corrections for TR4 (star was not in FOV) 295,60 Starting tip/tilts 650,60 Final tip/tilts After a couple of attempts I finally got a goodness of fit of 0.95. The decenter M2 N1 by 0.069mm and Frt by 0.064mm. According to the online docs, less than 100mm of change is negligable so no adjustments were made. Clouds started appearing around 04:00. Grid Data for NA2Guider 0.00 0.00 304.5 307.1 0.00 0.01 306.5 217.3 0.00 0.02 308.6 128.6 0.00 0.03 311.1 29.7 0.01 0.00 217.1 300.4 0.01 0.01 219.0 212.3 0.01 0.02 220.7 123.3 0.01 0.03 223.2 28.3 0.02 0.00 129.8 285.2 0.02 0.01 132.1 196.7 0.02 0.02 135.1 108.2 0.02 0.03 136.6 20.6 0.03 0.00 41.6 279.2 0.03 0.01 44.8 191.7 0.03 0.02 46.9 103.2 0.03 0.03 49.3 15.1 Ring Data for NA2Guider 0 157.7 196.5 30 145.3 187.4 60 142.2 173.9 90 144.8 159.0 120 154.7 148.4 150 169.3 143.4 180184.5 146.3 -30 173.5 195.8 -60 187.5 192.0 -90 195.5 181.7 -120 198.8 169.3 -150 195.3 156.1 -180 184.4 145.8 No really big changes except the Rot_Inst_ang went from 0.64 to -175.94. That seemed a big jump. Also in the web docs, the instructions for taking the Grid data have you changing the Y value in a negative direction (offset bore/pabs/computed x.xx -x.xx). I found that I had to change that in the +Y direction to make the star not go off the field in the first offset (with the star in the upper Right corner). Maybe this accounts for the change??? The grid and ring data both had very nice fits. The TR3 port eyelid is INOP in auto. TR4, NA1, NA2 all worked fine as well as the mirror covers in auto. All eyelids worked fine in manual mode. ------------- ACTIVITY LOG -------------- PROG INST FAILURE MODE TIME (STEDFNVOG) TI/SHU START FINISH DESCRIPTION ---------------------------------------------------------------------- ---------------- FOCUS LOG --------------- Time Instrument Focus Az El Temp Strc Prim Sec Air filt FWHM ----------------------------------------------------------------------- 23:09 NA2gdr -1562(34000) 283 56 3.4 3.4 3.0 2.0 2.7 R 0.91 03:04 SH -575 308 65 0.4 0.7 0.8 -0.1 0.3 -- 1.3 05:08 NA2gdr -385 252 68 0.5 0.0 0.3 -0.3 0.1 clear 1.1 ------------- WEATHER LOG ---------------- Wind Precip.or Time Temp F Dewp F MPH Direction Dust Sky Conditions ------------------------------------------------------------------- 16:00 44 26 7 255 (WSW) 12 pt. cldy none 17:00 41 21 1 251 (WSW) 129 pt. cldy none 18:00 39 22 1 248 (WSW) 46 pt. cldy none 19:00 36 21 6 359 (N) 164 pt. cldy none 20:00 36 18 2 336 (NNW) 219 pt. cldy none 21:00 38 15 3 341 (NNW) 200 pt. cldy none 22:00 37 18 4 110 (ESE) 204 pt. cldy none 23:00 38 15 13 119 (ESE) 232 pt. cldy none 00:00 37 16 15 111 (ESE) 205 pt. cldy none 01:00 34 10 15 90 (E) 283 pt. cldy none 02:00 33 9 19 100 (E) 347 pt. cldy none 03:00 33 9 13 114 (ESE) 346 pt. cldy none 04:00 33 10 14 112 (ESE) 368 pt. cldy none 05:00 32 11 10 112 (ESE) 356 pt. 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 STATUS Telescope drives operational. Current TCC version: 2.10.0 Current TUI version: TUI 1.5.1