Date: Tue, 21 Aug 2001 05:07:27 -0600 (MDT) From: Pete Newman Subject: 2.5-m Obslog 20010820 (MJD 52142) APACHE POINT OBSERVATORY SDSS 2.5M OBSERVING LOG Monday August 20, 2001 (MJD 52142) ---=== OBSERVING TEAM ===--- Swing: Mike Harvanek (APO) Night: Dan Long (APO) Pete Newman (APO) Support: French Leger (FNAL) ---=== OBSERVING PLAN ===--- Science. ---=== OBSERVING SUMMARY ===--- We did not open. Overcast sky from mid-afternoon, and apart from a few short holes, it did not improve. We found the telescope front-back balance to be considerably off. ---=== OBSERVING LOG ===--- SWING SHIFT: Nothing unusual to report. NIGHT SHIFT: During preflight checks, the telescope balance was checked, and found to be good top-to-bottom, but the front (east) side is heavy. See problem #1 for more details. French made a visual inspection of the clearance between the windbaffle and weather station at the S corner of the pier, but weather kept us closed, so he will try to check clearance of the flat-field petals tomorrow. The secondary D and E actuators were homed to clear the full-step error on axis E. The cummulative error was 10 microsteps in ~2 days. The fault returned as soon as the collimate process woke up at a new altitude. We question an error message from watcher (see problem #2 below). We noted that the spectrographs consumed ~90lb of LN2 between 18:45 and 04:45, equivalent to two complete fills of the intermediate dewars. This is more than twice the normal rate. We suspect this is due to the continuing (ice-building, singing) leak at the cap of sp2/blue and the related fill faults reported by watcher. Combined with the 60lb of LN2 used by the imager into a closed building, we were careful to vent the building before swapping dewars this morning. The lower enclosure dessicant remained blue and the grade 5 N2 bottle pressure (1750psi) remained unchanged during the night, so those conditions are under control. Some further progress was made on debugging the SOP UDP-port ownership problem. ---=== IMAGING RUN SUMMARY ===--- Run Stripe Strip Flavor Lambda Last Frame # Begin End ------------------------------------------------------------------ 2501 100 O ignore 18.28 25.68 63 doghouse bias ---=== IMAGING RUN DETAILS ===--- N/A ---=== SKIPPY RESULTS ===--- N/A ---=== LTMATCH RESULTS ===--- N/A ---=== SPECTROSCOPY DATA SUMMARY ===--- UT Exp Time flavor comment (S/N)^2 totals ========================================== b1 r1 b2 r2 ----- sequence 10603, plate -9999 ------- 22:43 10603 0.0 bias {{}} 22:46 10604 0.0 bias {{}} ----- sequence 10605, plate 625 ------- 00:45 10605 0.0 bias {{}} ---=== TELESCOPE OFFSETS AND SCALE I ===--- Time Cart Plate getclock Az Alt Rot Scale N/A ---=== DATA TAPE SUMMARY ===--- Ship to FNAL: JL None Stays at APO: JL None ---=== FOCUS LOG ===--- setmir piston Temp Wind Time Inst scale M1 M2 Foc Az Alt (C) MPH Dir filt fwhm " -------------------------------------------------------------------------------- N/A ---=== WEATHER LOG ===--- Wind Time Temp F Dewp F MPH Direction Dust DIMM Sky 16:57 68 43 10 234 (SW) 624 - mcl 17:29 66 42 5 220 (SW) 813 - " 18:01 65 43 9 225 (SW) 796 - " 18:33 63 42 5 217 (SW) 854 - " 19:05 62 43 5 209 (SSW) 921 - " 19:37 61 42 8 197 (SSW) 846 - " 20:10 62 41 6 182 (S) 865 - " 20:42 62 39 5 181 (S) 895 - " 21:14 62 39 9 182 (S) 917 - " 21:46 61 40 9 204 (SSW) 919 - " 22:18 62 32 13 158 (SSE) 850 - " 22:51 59 34 14 144 (SE) 1024 - " 23:23 59 33 21 145 (SE) 1100 - " 23:55 59 32 18 159 (SSE) 1113 - " 00:27 59 32 16 164 (SSE) 1137 - " 00:59 58 32 13 162 (SSE) 1071 - " 01:32 58 32 15 144 (SE) 1109 - " 02:04 58 32 7 163 (SSE) 1159 - " 02:36 56 34 7 160 (SSE) 1212 - " 03:08 57 36 1 128 (SE) 1126 - " 03:40 58 40 0 231 (SW) 1276 - " 04:13 59 42 5 264 (W) 961 - " [pmt]cl = partly, mostly, totally cloudy ---=== LN2 SCHEDULE ===--- Spectro dewar weight at 05:00: 251 lb. Imager dewar weight at 05:00: 264 lb. ---=== TELESCOPE STATUS ===--- Stowed at 30 deg alt with cartridge 3 (plate 663) mounted. Counterweights at 230. Spectro auto-fill connected. ---=== SOFTWARE USED ===--- IOP/SOP: v3_53_6 Watcher: v2_9_0 MCP: v5_3_1 TPM: v2_4_1 AstroDa: v14_36 TCC: 2.5.5 sdssProcedures: v1_22 tccMon : v1_6 ---=== MIRROR NUMBERS ===--- Time dpTemp dewPt Press TmpOut HumOut Windd Winds 21:04 60.8 41.3 21.63 48 189.5 8.4 15 PRIMARY: -------- Scale: 0.999900 MIGS TONIGHT NOMINAL Axial A: -0.9280 0.0710 Axial B: -1.0800 -0.0980 Axial C: -0.9250 0.0610 Trans D: 4.1990 4.1800 Lateral E: 1.9330 1.9365 Lateral F: 0.4340 0.4370 GALILS Commanded: -10118. -19193. -14572. -208. 31562. 30667. Actual: -10100. -19200. -14550. -200. 31550. 30650. SETMIR VALUES primDesOrient: 987.14 -11.80 23.00 1256.90 642.10 primOrient: 986.45 -11.90 23.25 1256.15 642.48 SECONDARY: ---------- Focus: 0.0 Air temp: 16.0 C Altitude: 30.41 MIGS TONIGHT NOMINAL Axial A: -2.1120 -1.2900 Axial B: -2.1210 -1.3150 Axial C: -2.1310 -1.3060 Trans D: 0.1440 0.1890 GALILS Commanded: 2613570. 2613570. 2613570. 2456. 3656. Actual: 2613542. 2613548. 2613655. 2450. 3650. SETMIR VALUES secDesOrient: 2074.35 0.00 0.00 0.00 -175.00 secOrient: 2074.36 -0.04 0.01 0.01 -174.84 ---=== PROBLEMS IN DETAIL ===--- Problem #1: telescope front-back balance ---------------------------------------- Balance checked with a spectro cartridge mounted, the counterweights at 230+-2, and the spectro dewars about half full. Drive voltages were noted from the MCP menu while driving up and down. Between alt=40 and alt=60, voltages were up=1700, down=-1600, so top-bottom balance is good. However, between alt=80 and alt=90, we saw up=4000, down=700, which indicates the front (east) of the telescope is considerably heavy. Problem #2: watcher not handling some errors? --------------------------------------------- We occasionally (sorry for the vagueness) see the watcher process (i.e. parent of the startClient and startInterlocks processes report errors such as the following (when plotting LN2 temps): got the ln2temp data for CCD03 Open /XWINDOW got the ln2temp data for CCD04 got the ln2temp data for CCD01 got the ln2temp data for CCD03 RHL: I'm not handling error sp2Error(error): writing "file9": Bad file number watch> "Bad file number" looks like an underlying software bug, but where should the PR go?