Subject: 25m Obslog 2000-04-24 (MJD 51659) Date: Tue, 25 Apr 2000 04:04:02 -0600 (MDT) From: ank@apo.nmsu.edu (Atsuko Nitta Kleinman) Monday April 24, 2000 Apache Point Observatory SDSS 2.5m Observing Log (MJD 51659) OBSERVING TEAM: =============== Atsuko Nitta Kleinman (APO) Steph Snedden (APO) Alan Uomoto (JHU) VISITORS: ========= Jim Gunn (PU) Connie Rockosi (UC) Andrew Connolly (UP) Steve Kent (FNAL) Robert Lupton esq. (PU) John Peoples (FNAL) Don Petravick (FNAL) Bill Boroski (FNAL) THE PLAN: ========= Science with the Imager if it is photometric and good seeing. SYNOPSIS FOR NIGHT: =================== TELESCOPE STATUS: ================= DIMM: ----- INTERLOCKS: =========== none bypassed SOFTWARE USED: ============== IOP/SOP: v3_13_1 Watcher: v2_8_2 MCP: v4_2_4 TPM: v1_0_8 AstroDa: 14_24 TCC: 2.2.5 WEATHER SYNOPSIS (see below for hourly data): ============================================= Clear all night. The seeing was good at the beginning of the night. GENERAL COMMENTS (see Problems below for details): ================================================== After the afternoon checkout and putting the imager on, we started on strip 37N which is the #1 priority for imaging data. Seeing started getting bad (2" or so) around 10:30pm. We stayed on the field hoping that the seeing will improve, but it did not. So we decided to take data on FASTT J. When we started data taking on the FASTT field, we found out that the seeing has improved again. oh well. We took data on from lambda=-14 to lambda=+25. After we finished the FASTT field, we checked the collimation of the mirror by defocusing. This was done under instructions from Jim and Connie. After seeing that the "donut" image was not uniform, Steph homed the secondary three times. The donut improved somewhat, and we decided to adjust the tilt and translation of the primary mirror. After this, we had nice evenly illuminated donuts. The new MIG values for the primary mirror after fixing the coma are: A=1.9284 B=0.5594 C=0.5579 D=0.3744 E=1.9065 F=0.4074 From tomorrow night, the above numbers are the nominal values for the M1 MIGs. We tried to do a focus sweep after fixing the coma, but the seeing suddenly became very bad (3" according to 3.5m). Therefore we gave up for the night. While slewing down in altitude via the MCP Menu during shutdown, we got the following message: Apr 25 02:59:27 sdssmcp SLC_DC dsc_E_trcErr Windscreen touched in altitude: UP There were no aborts due to this, however, and we kept on moving in altitude. We did not see any AZ abort as experienced last night. We should stick to this version of TCC until the cause of it is known and fixed. DATA ACQUISITION (see IOP/SOP output below): =========================================== IMAGING: -------- Run Frames Type --- ------ ---- 1400 29 bias 1401 68 setup (lskipping, focusing) 1402 221 Science 37N 1403 33 setup (lskipping) 1404 86 FASTT J (lambda: -14 -> +25) 1405 211 Engineering -- fixed the coma. Lskip info: Run 1401 Before any rotator moves were made we did 3 lskips in sequence. We got the following offsets: -0.041 +- 0.005 -0.050 +- 0.006 -0.036 +- 0.004 We then applied a rotator offset of -0.036 and did another lskip. The result: -0.002 +- 0.009 Run 1402 Rotator was in place. No offsetting the rotator. Skygang info on 37N (Run 1402): Cursor: o-observed (red), c-catalog (cyan), b-boresight, q-quit Err = True - HDR (astrotools convention for az-el) raBoreErr: -8.9", decBoreErr: 9.6", azErr: 15.6", elErr: -5.5" raBoreErr: -13.0", decBoreErr: 8.5", azErr: 14.7", elErr: -8.8" raBoreErr: -5.9", decBoreErr: 9.2", azErr: 14.7", elErr: -3.2" raBoreErr: -5.4", decBoreErr: 9.1", azErr: 14.4", elErr: -2.9" raBoreErr: -9.5", decBoreErr: 10.1", azErr: 16.4", elErr: -5.9" -------------------------------------------------------- raBoreErr: -8.5 +- 2.8", decBoreErr: 9.3 +- 0.6" azErr: 15.2 +- 0.8", elErr: -5.2 +- 2.2" muErr: 4.8 +- 1.3", nuErr: 10.3 +- 1.8" Correct idReport boresight values: xBore = -23.36 mm, yBore = -0.29 mm. Skygang info on FASTT J (Run 1404) Err = True - HDR (astrotools convention for az-el) raBoreErr: -10.9", decBoreErr: -6.6", azErr: 20.8", elErr: -5.9" raBoreErr: -10.3", decBoreErr: -6.5", azErr: 19.7", elErr: -5.8" raBoreErr: -13.1", decBoreErr: -6.0", azErr: 24.7", elErr: -5.2" raBoreErr: -10.7", decBoreErr: -9.3", azErr: 20.7", elErr: -8.6" raBoreErr: -13.6", decBoreErr: -10.7", azErr: 26.3", elErr: -9.8" -------------------------------------------------------- raBoreErr: -11.7 +- 1.4", decBoreErr: -7.8 +- 1.8" azErr: 22.5 +- 2.6", elErr: -7.1 +- 1.8" muErr: -11.7 +- 1.4", nuErr: -7.8 +- 1.8" Correct idReport boresight values: xBore = -22.27 mm, yBore = 0.71 mm. SPECTROSCOPY: ------------- Exposure Type -------- ---- MIRRORS: ======== **WARNING! SEE NEW MIG NUMBERS IN GENERAL COMMENTS SECTION** PRIMARY: -------- MIGS SHOULD BE Axial A=1.9314 1.9315 Axial B=0.5569 0.5570 Axial C=0.5564 0.5570 Transverse D=0.4084 0.4075 Lateral E=1.8990 1.8980 Lateral F=0.3984 0.3990 GALILS Commanded:4857.,-2351.,94.,-9478.,58.,-93. Actual:4850., -2350., 100., -9500., 50., -100. SETMIR VALUES primDesOrient:0.00, -3.90, 3.90, 213.50, 213.50 primOrient:-667.32, 4.99, -5.05, 50.27, -4.89 SECONDARY: ---------- Focus: Temp: Altitude: MIGS Axial A=0.3349 Axial B=0.3669 Axial C=0.3519 Transverse D=0.0320 GALILS Commanded:-828578.,-841457.,-851735.,-2881.,-7703. Actual: -828552., -841591., -851764., -2900., -7700. SETMIR VALUES secDesOrient:-665.32, 5.00, -5.00, 50.00, -6.22 secOrient:-665.30, 4.99, -4.99, 50.31, -6.00 FOCUS LOG: ========== M1 Piston M2 Piston Temp Wind Time Inst setmir TCC setmir Az El C Dir MPH filt FWHM " 21:42 Imager 0.00 -665.30 250.66,48.48 13.1 218.1 4.2 R(ccd13) 1.23 22:40 Imager 0.00 -670.55 231.35,46.44 12.4 210.1 8.0 R(ccd13) 1.28 23:20 Imager 0.00 -650.15 220.31,46.11 11.6 222.7 8.1 R(ccd13) 1.7 00:30 Imager 0.00 -649.91 364.22,57.24 12.2 245.1 8.1 R(ccd13) 1.1 LN2 SCHEDULE: ============= Spectro dewars filled at 20:00 and 02:00 Weight 140 lb Imager dewar swapped out at 20:00 Weight 220 lb. PROBLEMS: ========= We were monitoring FWHM etc. in the watcher, looking at time series using PGPLOT. At one point, the PGPLOT window disappeared, and would not come back until we restarted the watcher. What is worse, we stopped & restarted the focus loop in IOP, and the PGPLOT window disappeared and did not come back, even with a schedule plotFocus. We certainly don't want to stop a drift so we can restart IOP to get a view of the focus loop. (PR 1005) WEATHER DATA: ============= Wind Time Temp F Dewp F MPH Direction Dust Sky Precip. 20:01 55 13 3 273 (W) 1464 clear 21:01 55 14 4 259 (W) 1561 clear 22:01 55 14 8 235 (SW) 1467 clear 23:01 53 14 11 209 (SSW) 1452 clear 00:01 53 13 5 247 (WSW) 1370 clear 01:01 53 12 4 273 (W) 1559 clear 02:01 54 12 0 115 (ESE) 1752 clear 03:01 50 14 18 67 (ENE) 2257 clear [pmt]cl = partly, mostly, totally cloudy DATA LOGS FROM IOP/SOP: =======================