From: harvanek@apo.nmsu.edu Subject: 2.5-m Obslog 20010529 (MJD 52059) Date: Wed, 30 May 2001 07:17:29 -0600 (MDT) APACHE POINT OBSERVATORY SDSS 2.5M OBSERVING LOG Tuesday May 29, 2001 (MJD 52059) OBSERVING TEAM: =============== Mike Harvanek (APO) Dan Long (APO) Scot Kleinman (APO) Atsuko Kleinman (APO) VISITORS: ========= Eric Neilsen (FNAL; by phone, multiple times) NHK film crew. THE PLAN: ========= Shake up. Maybe finish a plate or two. Oblique scan. Apache wheel? SYNOPSIS FOR NIGHT: =================== 19:30 Doors open, fans on 20:20 Enclosure off 05:20 Enclosure on, doors closed, fans off One plate finished (597) when the data from 52057 and 52059 are combined. Some shaking. First part of the oblique scan completed in good conditions. First half of the second part of the oblique scan completed in good conditions. Second half of the second part of the oblique scan completed in marginal seeing conditions and twilight. GENERAL COMMENTS (see Problems below for details): ================================================== NHK crew filmed the opening and a lot of action in the control room. The TPM would not allow us to get mirror numbers so we got them by hand. Had some warnings from watcher about invalid AZ barcodes: azimuth (Invalid barcode in azimuth: fididx = 12288, pos = 1099428124 (May 29 21:27:03): May 29 21:27:09 MDT ) Missed the fiducial position (in degrees) in the murmur log; sorry. AND azimuth (Invalid barcode in azimuth: fididx = 12445852, pos = 1098749 (May 30 01:14:59): May 30 01:15:09 MDT ) dsc_I_trcInfo Intermediate rot fiducial 84.07 deg AND azimuth (Invalid barcode in azimuth: fididx = 12445852, pos = -105029 (May 30 03:12:07): May 30 03:12:23 MDT ) Missed the fiducial position (in degrees) in the murmur log; sorry. Also, during a slew at 01:15:11 we had an azimuth error that was too large to correct: mcpMapProc2 axes|azimuth::Invalid barcode in azimuth: fididx = 12445852, pos = 1098749 (May 30 01:14:59):: mcpMapProc2 misc|Not disabling MS.ON; error 198997 (max allowed: 600) (May 30 01:15:11)::Not disabling MS.ON; error 198997 (max allowed: 600) mcpMapProc2 axes|azimuth::correction for azimuth 198997 is too large Changes in iop/sop somehow caused curly brackets to be added into the following 3 commands: offset object, offset rotator, track command in testInFiber Specific output is included below in the problems section. Eric N. fixed the first two commands but the track command in testInFiber still needs to be fixed as there was another problem with the position given by the track command. After the problem with the curly brackets was discovered, the track command was issued manually and no star appeared. During the preCalib for plate 597, sop complained that the flat field screens would not close. The system status cartoon showed them to be closed and visual inspection confirmed this but sop insisted they were open. The "open bit" value of every flat field petal was equal to zero, again confirming they were closed. A preCalib was issued from the old version of iop/sop and it worked fine. Eric N. was called. He could find no changes in this portion of the iop/sop code. We issued the command from the new iop/sop again and it failed again. The command "flatFieldScreen closed" was issued and it returned a value of "1" indicating that sop thought they were closed, yet sop thought they were open. At this point the flat field screens could not be opened using sop, tcc, or the mcp menu. The system status cartoon showed the screens changing back and forth between open and closed states. Finally, Dan went down to the telescope and tried opening them from the mcp menu on the laptop. It worked. Scot and Dan discovered that the problem was that the mcp.tcl file (which parses the system status message from mcp which is called by the routine that checks the flat field screen position) has been changed and contains bugs. A work around was to use the mcp.tcl file from a previous version of iop/sop. A PR (2394) was filed. Some of the output is included below in the problems section. Finished off plate 597 and started imaging by 01:00. Unfortunately, clouds came in starting around 00:45 and so the first attempt at the oblique scan was not survey quality. However, it did serve the purpose for shaking imaging items. When closing the logviewer tonight, the destroy pulldown item was used accidently, rather than the delete item (the two are next to each other) to close the logviewer window. This had the unfortunate side effect of killing the iop session from which the logviewer was issued. This could be a potentially bad situation and highlights the need for an exit button on the logviewer (and all other GUIs as well). We started another oblique scan around 03:00 when the skies cleared. Conditions were photometric and the seeing was well below 2 for all of the first (level) scan and half of the 2nd (slanted) scan. The seeing was about 2" for the remainder of the 2nd scan. The last ~10-15 minutes (after frame ~45) were done in twilight. This could not be helped as we could not start the scan any earlier due to clouds. The data from r, i and z taken in twilight may be usable but u and g were definitely affected by rising sky levels. Various items were shaken. Please see the shake summary at the end of this log for details. DATA ACQUISITION (see IOP/SOP output below): ============================================ IMAGING: -------- Run Stripe Strip Flavor Lambda Last Good Frames/ Begin End Frame Comments ------------------------------------------------------------------------- 2344 100 O ignore -17.96 -2.90 51 ignore 2345 100 O bias 62.59 66.22 38 2346 10 O ignore 48.87 77.18 203 2347 10 O engineering 59.22 69.54 82 level oblique 2348 10 O engineering 60.72 69.53 95 slanted oblique; twilight after frame 45 Runs 2347 and 2348: No rotator corrections were performed. SPECTROSCOPY: ------------- UT Exp Time flavor comment (S/N)^2 totals ------------------------------------------ b1 r1 b2 r2 ------ sequence 10135, plate -9999 ------- 01:40 10135 0.0 bias {{}} 02:54 10136 0.0 bias {{}} ------ sequence 10137, plate 597 ------- 16.9 19.7 15.3 14.6 *** 02:57 10137 0.0 bias {{}} 04:12 10138 10.0 flat pre-flat 04:14 10139 2.0 arc pre-arc 04:24 10140 0.0 bias {{}} 04:55 10141 900.0 target science 05:15 10142 901.0 target science 05:22 10143 240.0 smear {{Smear Pattern}} 05:40 10144 901.0 target science 05:46 10145 10.0 flat post-flat 05:48 10146 2.0 arc post-arc Plate 597 was observed in sequence(s) 10137 for a total of 2702 seconds *** Total S/N = combined data from 52057 and 52059. OFFSETS: -------- getclock Axis position and calibration offset Scale Time Ct Plate time Az El Rot Factor 22:13 8 597 991195984 202.16 .0021 52.70 -.0016 47.41 -0.025 0.999970 sidereal time Plate Telescope Tele - Plate " Time Ct Plate deg RA Dec RA Dec RA Dec 22:13 8 597 205 173.2454 64.4450 173.2410 64.4450 -15.8 0.0 TAPES: ------ Ship to FNAL: JL4081-4085, 4106, 4108 Stays at APO: JL4087-4092, 4109 MIRROR NUMBERS: =============== PRIMARY: -------- Scale: 1.000000 MIGS TONIGHT NOMINAL Axial A: 0.0220 0.0150 Axial B: -0.0310 -0.0510 Axial C: 0.0350 0.0300 Trans D: 3.7540 3.7560 Lateral E: 1.9085 1.9100 Lateral F: 0.4085 0.4095 GALILS Commanded: 4890. -2755. 465. -6642. 8737. 8322. Actual: 4900. -2750. 450. -6650. 8750. 8300. SETMIR VALUES primDesOrient: 0.00 -4.40 10.70 586.50 240.70 primOrient: 0.00 -4.56 10.53 586.58 240.03 SECONDARY: ---------- Focus: 0.0 Air temp: 14.7 C Altitude: 30.00 MIGS TONIGHT NOMINAL Axial A: -1.2900 -1.29 +/-.05 Axial B: -1.3160 -1.30 +/-.05 Axial C: -1.3070 -1.31 +/-.05 Trans D: 0.1810 0.20 +/-.05 GALILS Commanded: 1583838. 1583876. 1583851. 2595. 3795. Actual: 1583850. 1583850. 1583850. 2600. 3800. SETMIR VALUES secDesOrient: 1257.00 0.00 0.00 0.00 -175.00 secOrient: 1257.01 0.00 0.01 0.01 -175.13 FOCUS LOG: ========== setmir piston Temp Wind Time Inst scale M1 M2 Foc Az Alt (C) MPH Dir filt fwhm " 19:30 East door open, West door cracked, Exhaust and cone fans on 20:20 Enclosure opened 22:59 8 597 0.99997 296 1180 -250 207 48.7 14.0 10 250 - 1.3 01:41 imager 1.00000 0 -738 -509 -31 53.2 14.6 4 74 23-i' 1.14 04:02 imager 1.00000 0 -642 -483 -61 33.8 14.7 17 42 23-i' 1.63 05:20 Enclosure closed WEATHER SYNOPSIS: ================= Clouds on the western and southwestern horizons at sunset. Clear overhead. Clouds starting around 00:45. Clear again from 03:00 into twilight. WEATHER DATA: ============= Wind Time Temp F Dewp F MPH Direction Dust DIMM Sky Precip. 16:01 66 8 19 271 (W) 562 - clear none 17:01 65 8 14 264 (W) 752 - clear none 18:01 63 7 18 273 (W) 629 - clear none 19:01 63 9 18 292 (WNW) 649 - clear none 20:01 58 10 16 256 (WSW) 823 - clear none 21:01 58 8 16 232 (SW) 826 - clear none 22:01 57 8 12 235 (SW) 814 - clear none 23:01 57 8 7 257 (WSW) 759 - clear none 00:01 58 11 6 250 (WSW) 848 - clear none 01:01 57 14 1 93 (E) 836 - pcl none 02:01 57 15 4 12 (NNE) 748 - pcl none 03:01 59 15 14 0 (N) 751 - clear none 04:01 58 18 13 57 (NE) 774 - clear none 05:01 58 20 16 47 (NE) 750 - clear none [pmt]cl = partly, mostly, totally cloudy LN2 SCHEDULE: ============= Spectrographs filled at 20:25. Spectro dewar weight at 06:00: 65 lb. Imager dewar weight at 06:00: 121 lb. TELESCOPE STATUS: ================= Stowed at 30 deg alt with NOTHING mounted. Counterweights at 40. Spectro auto-fill connected. INTERLOCKS: =========== None bypassed SOFTWARE USED: ============== IOP/SOP: v3_47_1 Watcher: v2_9_0 MCP: v5_1_0 TPM: v2_3_7 AstroDa: 14_36 TCC: 2.5.2 tccMon: v1_6 sdssProcedures: v1_18 PROBLEMS IN DETAIL: =================== sop thinks closed flat field screens are open: ---------------------------------------------- sop response to preCalib and flat field screen status. The problem was traced to the parsing of the mcpPut command SYSTEM.STATUS. sp1> preCalib Closing Flat Field Screen Flat field screen failed to close; quitting sp1> flatFieldScreen closed 1 In an old sop version ( v3_45_8 ) the response to the command to check the flat field screen status shows 8 items corresponding to the 8 petals of the FFS. sp1> mcpSystemStatus -ffs mcpPut: SYSTEM.STATUS 0 0 0 0 0 0 0 0 In the latest version ( v3_47_1 ) the response to the same command only had 4 items, and sop expected 8. sp1> mcpSystemStatus -ffs mcpPut: SYSTEM.STATUS 0 0 0 0 curly brackets added to commands: --------------------------------- Excerpts from TCC showing the extra {} from some sop commands. offset object: 0 0 W Facil="CLI"; VMSMsg="MAXPARM"; EText="too many parameters - reenter command with fewer parameters" 0 0 W Facil="CLI"; VMSMsg="CMDSEG2"; EText=" \0\" 0 0 I Facil="SYSMSG"; VMSMsg="NOMSG"; EText="Message number 0069601F" 0 5 F Failed; cmdStr='offset object { 0.0019318, 0.0000000}' offset rotator: 0 0 W Facil="CLI"; VMSMsg="MAXPARM"; EText="too many parameters - reenter command with fewer parameters" 0 0 W Facil="CLI"; VMSMsg="CMDSEG2"; EText=" \0\" 0 0 I Facil="SYSMSG"; VMSMsg="NOMSG"; EText="Message number 0069601F" 0 5 F Failed; cmdStr='offset object { 0.0019318,} { 0.0000000}' track command in testInFiber: 0 5 : Cmd='show time' 0 5 I TAI= 4497919079.61 0 5 I LST= 231.3445; UT1= 4497919047.59; UTC_TAI= -32 0 5 : Cmd='show time' 0 5 W Text="value: {169.6207412402 for Coords is not a double precision number" 0 5 F Failed; cmdStr='track {169.6207412402 ,64.7825747549 } fk5=2000 /rotangle=0 /rottype=obj' SUMMARY OF SHAKE: ================= SDSS 2.5m End of Run Shakeup 29May01 Summary: Software: --------- New MCP - v5_1_0: Includes a button to iack MCP (shows up as red "Rebooted" button ONLY when a miack is needed) - works. Declared current. New *OP - IOP v3_47_0/1: A guide fiber from plate 597 did not fit onto the region specified for SAOimage whereas it did last night. Eric N. was called. He commented out this change in the code and made test iop version v3_47_1. Other problems (inserting curly brackets into commands; still no runlogs; mcp.tcl file problem; see below) prevented us from declaring it current. watcher v2_9_0: Seemed to work ok but not sure if it suppressed all axis status warnings if a stop button is in. It didn't make anything worse though and so was declared current on sdsshost. It could not be declared current on commish because: 19:14 commish /home/long % ups declare -c -f IRIX+6 watcher v2_9_0 INFORMATIONAL: Product 'watcher' (with qualifiers ''), has no product home Specification did not include a -r for product directory INFORMATIONAL: Product 'watcher' (with qualifiers ''), has no table file Specification did not include a -m for table file only default actions will be performed 6:25 commish /home/long % sdssProcedures v1_18: Dan's guider focus doc added to sdssProcedures Dan's switch criteria doc added to sdssProcedures IOP --- PR 1446: skippy running automatically during a scan - Works. Closed. PR 2375: stopFocusLoop now de-schedules plotFocus - Seemed to work but only tested once. Needs more testing. Reassigned to Pete N. as "needs test". cleanupMurmur bug is fixed - the syntax for the iop -command 'murmur "forcing murmur to exist"' was indeed corrected. However, wasn't there some discussion of eliminating this command all together (i.e., getting it to run automatically in/by cleanupMurmur)? Changes in iop/sop somehow caused curly brackets to be added into the following 3 commands: offset object, offset rotator, track command in testInFiber Eric N. fixed the first two commands but the track command in testInFiber still needs to be fixed as it had other problems (see below). makeRunLog might work automatically now - Nope. logViewer has two new categories: SOPGUI and archiver - Yep. SOP --- PR 2080- no periodic exposure time updates Still no periodic exposure time updates for spectro exposures. Reassigned. PR 1601- preCalib failure/guide stars missing A guide fiber from cartridge 8, plate 597 did not fit onto the region specified for SAOimage whereas it did last night, so the fix does not seem to have worked. Perhaps the change had the wrong sign? Eric commented out the change on the branch after it failed. Reassigned. PR 2287 - abort after instChange - should be possible to exit the GUI before instChange completes without getting errors. Works. Closed. SOP GUI's Initial Stuff sub-GUI has two new startMurmur options - both worked. GUI now uses the new setInstrument command - it worked. testInFiber - failed not only because of the addition of the curly brackets (see above) but also because of an error in the position given by the track command. After the problem with the curly brackets was discovered, the track command was issued manually and no star appeared. sop would not recognize that the flat field screens were closed during a preCalib. Scot and Dan discovered that the problem was that the mcp.tcl file (which parses the system status message from mcp which is called by the routine that checks the flat field screen position) has been changed and contains bugs. A work around was to use the mcp.tcl file from a previous version of iop/sop. A PR (2394) was filed. See the night log (52059) for further details. MCP --- PR 2346 - delay in flatField screens - works; Closed. PR 2347 - the TCC and semaphores - axis stop, track/stop, talk tcc_tel1 sem.give, all give up the semaphore so that the menu can take it nicely. Closed. Cleaned up barcode reading code: Still had some warnings from watcher about invalid AZ barcodes: azimuth (Invalid barcode in azimuth: fididx = 12288, pos = 1099428124 (May 29 21:27:03): May 29 21:27:09 MDT ) Missed the fiducial position (in degrees) in the murmur log; sorry. AND azimuth (Invalid barcode in azimuth: fididx = 12445852, pos = 1098749 (May 30 01:14:59): May 30 01:15:09 MDT ) dsc_I_trcInfo Intermediate rot fiducial 84.07 deg AND azimuth (Invalid barcode in azimuth: fididx = 12445852, pos = -105029 (May 30 03:12:07): May 30 03:12:23 MDT ) Missed the fiducial position (in degrees) in the murmur log; sorry. Also, during a slew at 01:15:11 we had an azimuth error that was too large to correct: mcpMapProc2 axes|azimuth::Invalid barcode in azimuth: fididx = 12445852, pos = 1098749 (May 30 01:14:59):: mcpMapProc2 misc|Not disabling MS.ON; error 198997 (max allowed: 600) (May 30 01:15:11)::Not disabling MS.ON; error 198997 (max allowed: 600) mcpMapProc2 axes|azimuth::correction for azimuth 198997 is too large Not sure what these problems were due to. Keeping the FFS enabled all the time (pending the arrival of the new sensors). Tested - worked.