APACHE POINT OBSERVATORY SDSS 2.5M OBSERVING LOG Tuesday November 30, 2004 (MJD 53340) ---=== OBSERVING TEAM ===--- Jurek Krzesinski visitor: Scot Kleinman (ups and software help), Peregine on the phone, Jon Brinkman all Mamoru's teami (working on MSP calibration). ---=== OBSERVING PLAN ===--- Science! ---=== OBSERVING SUMMARY ===--- Basicaly we've got all shake items tested, some worked, some didn't. Dithered spectroscopic flats were done, which completes monthly spectro checkout. Here are some problems we had: ------------------------------ TPM tests - done, Peregrine will work on his part and Jon(?) needs to do some work on his part (ups status display). In the night we've got a problem with connecting to sp1. mechSend s was failing and micro on mechanical board kept rebooting. It was NOT caused by low temperature (it was close to 0 C). Jon found out that it was a motor control board missbehaving. He replaced the board but 1 hour time was lost due to the problem. Astrom v3_8b was tested, but when we run skippy, the astrom printed an error: could not get requested value of keyword RA (see the log for more detail). We didn't call Pete or Scot, because of lateness of hour, we wouldn't be able to test new software cut tonight. M1 collimation was done (a slight tilt in x = -10"). The telescope was left with cart 8 mounted. The comunication between the guider camera and MAC computer is not working (MAC/guider probably needs powercycling a few times, but since it was the end of the night we decided to leave it for the day). The spectro dewars are refilling while we are sending this night log, the day crew will have plenty of time to replace spectro dewar, but it's reading now ~110 and dropping. ---=== OBSERVING LOG ===--- PT flat field lamps: -------------------- were changed during bright time. MCP: ---- New MCP was set (v5_26_0) with new fiducial tables. Watcher on commish (v2_30_0): ------------------------------ It is not beeping on startup anymore (configuration variable always_ring_bell is now set to 0). TPM: --- dewar alarms still appear while they shouldn't. status screen: we need a diffrent color scale on the display - the letters are barely visible. PVTs are working. Peregreen was called and he will work on problems tomorrow. Steve's plate database: ------------------------ Tested and works as advised. 00:30Z We couldn't connect to spectrographs. We checked if powersupplies were ok. at the spectrographs and they were. So we tried to log out the ports, but then Steph noticed that mechanicals are not responding on sp1. Quick check on sp1 board showed that something is beeping there. Jon found out that it was a motor control board missbehaving. He replaced the board but 1 hour time was lost due to the problem. After that we had to recollimate spectrographs and focus them (actualy only sp1 needed that). Monthly spectro checkout completed: ----------------------------------- dithered spectroscopic flats done (see frames 29594-29602). astrom test (left over from the shake night: nodeFromStripeNumber error): ------------------------------------------------------------------------- In testing the new astrom, Scot found the reason for the previous nodeFromStripeNumber errors as reported in shakeup was due to a dependency on the old astrotools in both the old (correct behavior) and the new (incorrect) astroms. We could go into lots of details about later dependencies over-riding earlier ones and why the command worked in an IOP dependent on the old astrom dependent on the old astrotools when you might think it wouldn't, etc., but we won't. The bottom line was we changed the table file for the v3_8b version of astrom to depend on the current v5_18 astrotools and the errors found previously went away. We could now being the real test. Both mirrors were homed/relaxed. -------------------------------- 05:40Z Engcam mounted (and after some struggle it came alive -we had to powercycle the camera and reset Mac a few times). A fk5 star found quite off the center. Good news: engcam donuts looked fairly well illuminated. The optical axis center was were it suppose to be. While getting the pointing model we've got too large to correct errors, but since they appeared on the same fiducial (~227) and they got always the same value we did not force fiducial and sure enough on the next point the correction was applied correctly. Ponting model data collection went smoothly, then we've done the fit. The new pointing model looks good, the error is 2.3, so it has been implemented. Once on slewing to instChange position we've got a spurious too large correction: 2004-12-01 09:34:43Z sdssmcp tLatch dsc_I_trcInfo rot fiducial 77 (1.00) deg 2004-12-01 09:34:43Z sdssmcp tLatch dsc_I_trcInfo Applying correction 800428 to rotator 2004-12-01 09:34:43Z sdssmcp tLatch dsc_E_trcErr correction for rotator 800428 is too large 2004-12-01 09:34:46Z sdssmcp tLatch dsc_I_trcInfo Intermediate rot fiducial 3.55 deg 2004-12-01 09:34:47Z sdssmcp tLatch dsc_I_trcInfo rot fiducial 77 (5.74) deg 08:50Z imager mounted - immediately after Mamoru's team calibration work. so we've got a "bad" opConfig-53340.par file. Good time to test astrom. astrom test v3_8b: ------------------ (left over from the shake night: nodeFromStripeNumber error). In testing the new astrom, Scot found the reason for the previous nodeFromStripeNumber errors as reported in shakeup was due to a dependency on the old astrotools in both the old (correct behavior) and the new (incorrect) astroms. We could go into lots of details about later dependencies over-riding earlier ones and why the command worked in an IOP dependent on the old astrom dependent on the old astrotools when you might think it wouldn't, etc., but we won't. The bottom line was we changed the table file for the v3_8b version of astrom to depend on the current v5_18 astrotools and the errors found previously went away. We could now being the real test. After that was done, we: im> setup -t iop im> unsetup astrom im> setup astrom -t im> startDa -tcc im> calcStripeParams 82 N gaved a proper answer (no errors). im> initNight -tapeRelabel done. im> goDrift -bias (run 5014 bias with imager on the telescope) - no errors and everything looks like it should. Then we started a drift on the sky (82 N). Everyting looked fine, we were close to focus, when we run skippy. Then problems begun: 09:46:59 700540 Executing commands in /p/dervish/v8_17/etc/dervishStartup.tcl: 09:46:59 700540 Executing commands in /p/astrotools/v5_18/etc/astrotoolsStartup.tcl 09:46:59 700540 09:47:00 700540 Executing commands in /p/astrom/v3_8b/etc/astStartup.tcl: 09:47:00 700540 astrom> fcntl stdin NONBLOCK 1 astrom> fcntl stdin NONBLOCK 1 09:47:00 700540 astrom> fcntl stdout NONBLOCK 1 astrom> fcntl stdout NONBLOCK 1 09:47:00 700540 astrom> fcntl stderr NONBLOCK 1 astrom> fcntl stderr NONBLOCK 1 09:47:00 700540 astrom> skippy 5015 15 4 -mjd 53340 astrom> skippy 5015 15 4 -mjd 53340 09:47:01 700540 Error: hdrGetAsDbl: could not get requested value of keyword RA 09:47:01 700540 astrom> flush stdout astrom> flush stdout 09:47:48 700540 astrom> skippy 5015 15 4 -mjd 53340 astrom> skippy 5015 15 4 -mjd 53340 09:47:48 700540 Error: hdrGetAsDbl: could not get requested value of keyword RA 09:47:48 700540 astrom> flush stdout astrom> flush stdout 09:48:49 700540 astrom> skippy 5015 15 4 -mjd 53340 astrom> skippy 5015 15 4 -mjd 53340 09:48:49 700540 Error: hdrGetAsDbl: could not get requested value of keyword RA 09:48:49 700540 astrom> flush stdout astrom> flush stdout 09:50:10 700540 astrom> skippy 5015 15 4 -mjd 53340 astrom> skippy 5015 15 4 -mjd 53340 09:50:10 700540 Error: hdrGetAsDbl: could not get requested value of keyword RA 09:50:10 700540 astrom> flush stdout astrom> flush stdout 09:50:59 700540 astrom> skippy 5015 15 4 -mjd 53340 astrom> skippy 5015 15 4 -mjd 53340 09:51:00 700540 Error: hdrGetAsDbl: could not get requested value of keyword RA 09:51:00 700540 astrom> flush stdout astrom> flush stdout As you see astrom was running skippy all the time on frame 15 ! even wehn it was told to use frame 18. Then Steph tried to run skippy on a SINGLE frame 21 and we've got errors: astrom> skippy 5015 20 1 -mjd 53340 astrom> skippy 5015 20 1 -mjd 53340 09:52:12 700540 ERROR: oldAstrom: oldAstrom: tunable parameter 'magDiff' missing from tunable parameters file 09:52:12 700540 NONE 09:52:12 700540 oldAstrom: tunable parameter 'magDiff' missing from tunable parameters file 09:52:12 700540 while executing 09:52:13 700540 invoked from within 09:52:13 700540 error "oldAstrom: tunable parameter '$param' missing from tunable parameters file" 09:52:13 700540 }" 09:52:13 700540 ("foreach" body line 2) 09:52:13 700540 invoked from within 09:52:14 700540 rwindowBig 09:52:14 700540 cwindowBig 09:52:14 700540 rwindowSmall 09:52:14 700540 cwindowSmall 09:52:14 700540 rwindowTiny 09:52:14 700540 cwindowTiny 09:52:14 700540 matchMeansWindow 09:52:14 700540 ..." 09:52:14 700540 09:52:14 700540 ccd dmu(") dnu(") dmag 09:52:14 700540 Error: Error processing FITS file asPMerge-005015.fit 09:52:15 700540 Error opening FITS file asPMerge-005015.fit After that she tried just a default skippy and this time it got frame: 09:53:29 700540 astrom> skippy 5015 25 4 -mjd 53340 astrom> skippy 5015 25 4 -mjd 53340 09:53:29 700540 Error: hdrGetAsDbl: could not get requested value of keyword RA 09:53:29 700540 astrom> flush stdout astrom> flush stdout So the error message was different. We ended the drift, moved the current "bad" opConfing" file into a back up file and started a new drift on the sky, which created a new "good" opConfig file. Then we run skippy from the iop with v3_8b astrom setup and saw the same errors as above, but skippy was happily running from all other windows in which we didn't setup the astrom v3_8b. We moved back the "bad" opConfig file and tried to run skippy from one of the iop window with no astrom v3_8b setup. And astrom printed the old error: 10:27:35 831081 astrom> skippy 5017 12 4 -mjd 53340 astrom> skippy 5017 12 4 -mjd 53340 10:27:40 831081 ERROR: oldAstrom: match: ccdConfig for row 7, column 1 not found 10:27:40 831081 NONE 10:27:41 831081 match: ccdConfig for row 7, column 1 not found 10:27:41 831081 while executing 10:27:41 831081 invoked from within 10:27:41 831081 error "match: ccdConfig for row $camRow, column ..." 10:27:41 831081 ("foreach" body line 16) 10:27:41 831081 invoked from within 10:27:41 831081 # Get the position of this CCD in the imaging camera, in terms 10:27:41 831081 # of camRow and camCol. 10:27:41 831081 set ccd [astCCD $d ..." 10:27:42 831081 ("foreach" body line 28) 10:27:42 831081 invoked from within 10:27:42 831081 # Write to astro or photo merge file 10:27:42 831081 set mf $mergeFile(astro) 10:27:42 831081 ..." 10:27:42 831081 (procedure "match" line 160) 10:27:42 831081 invoked from within 10:27:42 831081 invoked from within 10:27:43 831081 invoked from within 10:27:43 831081 # We have data from the astrometric chips to process. Do the 10:27:43 831081 # astrometric chips match first; it ..." 10:27:43 831081 10:27:43 831081 ccd dmu(") dnu(") dmag 10:27:43 831081 Error: Error processing FITS file asPMerge-005017.fit 10:27:43 831081 Error locating HDU 1 in FITS file asPMerge-005017.fit 10:27:43 831081 Error reading FITS header 1 10:27:43 831081 10:27:44 831081 astrom> flush stdout astrom> flush stdout 10:30Z Donuts: -------------- run 5017. in focus -120, frame 25 +300 frame 31 on that side the donuts looked slightly left heavy on the displays. -300 frame 38 they looked however quite good on this side. While in focus we looked at watcher seeing displays and we think the seeing values were similar in all collumns (from left to right), but were increasing alnog "riuzg" direction. We decided to do a collimation twick. Since the telescope was parked at equator we just got MIGs values at the telescope current position. Then Steph got donuts looking very nice in two steps and were done with finding the best x tilt (we neede only 10" tilt). Here is the output from the "colli" code: ./colli Program will calculate tilts and translation in setmir after the donuts were fixed Cut and paste: Your initial setmir mirror values before you started mucking with M1, cut them from the night log, numbers should NOT BE COMA separated!!! PriDesOrient: P0 Tx0 Ty0 Dx0 Dy0 0.00 -2.76 1.04 57.00 151.01 New setmir mirror values, after you've fixed the donuts, cut and paste the numbers from telrun SETMIR session, YES COMAs should be included!!! P0, Tx', Ty', Dx0, Dy0: 0.00, -12.16, 0.88, 57.42, 151.62 Check this before you cut and paste the result into SETMIR!!! red in INPUT values: PriDesOrient: 0.0, -2.76, 1.04, 57.42, 151.62 New setmir: 0.0, -12.16, 0.88, 57.42, 151.62 Final new setmir coordinates P0 Tx1 Ty1 Dx1 Dy1 are: 0.0, 4.57, 1.18, 64.25, -249.76 ============================================= (BTW the colli code was put into /isr/sbin direcotry, so all of us should be able to run it from our home directories). The donuts were checked after relaxing the primary and they were very good. Just on time, the seeing got very bad after we finished with the collimation. Default.dat file was edited with the new PrimDesOrient values. After seeing got improved we've checked the seeing with telescope in focus in watcher display. We think the seeing looks better than before collimation. 12:10Z cart 8 mounted on the telescope. Unfortunately we've got the parallyn error and so the guider did not work. Since that was the end of the night, we decide to leave that problem for the day. endNight run on cloudy tapes. ---=== IMAGING RUN SUMMARY ===--- Run Time Stripe Lambda Last Flavor Comments Start End Begin End Frame ------------------------------------------------------------------------- 5014 09:20Z 09:32Z 100 O -80.30 -77.15 35 bias 5015 09:38Z 09:58Z 82 N -74.51 -69.40 48 science 5016 10:04Z 10:17Z 82 N -67.92 -64.53 34 science 5017 10:20Z 11:47Z 82 N -63.90 -42.07 159 science ---=== IMAGING RUN DETAILS ===--- ---=== SKIPPY RESULTS ===--- Run Frame nFrames stars muErr muRms nuErr nuRms rot az el --------------------------------------------------------------------------- 5016 17 4 96 -3.600 0.147 2.100 0.121 0.00660 178 57 ---=== LTMATCH RESULTS ===--- Run Field nFields alt az nGood rowMean rowSig colMean colSig rot ------------------------------------------------------------------------ ---=== SPECTROSCOPY DATA SUMMARY ===--- Summary Checked (y/n): QA Procedures Done (y/n): UT Exp Time flavor comment (S/N)^2 totals ========================================== b1 r1 b2 r2 ----- sequence 29582, plate -9999 ------- 00:17 29582 0.0 bias ----- sequence 29583, plate 2058 ------- 02:40 29583 10.0 flat 02:43 29584 2.0 arc 02:54 29585 10.0 flat 02:57 29586 2.0 arc 03:05 29587 10.0 flat 03:13 29588 10.0 flat 03:21 29589 10.0 flat 03:27 29590 2.1 arc 03:30 29591 2.1 arc 03:40 29592 2.1 arc 03:43 29593 2.1 arc 03:53 29594 10.0 flat 03:57 29595 10.0 flat 04:01 29596 10.0 flat 04:05 29597 10.0 flat 04:09 29598 10.0 flat 04:13 29599 10.0 flat 04:17 29600 10.0 flat 04:21 29601 2.0 arc 04:23 29602 2.0 arc 04:28 29603 10.0 flat 04:30 29604 2.0 arc ---=== TELESCOPE OFFSETS AND SCALE I ===--- Time Instrument Az Alt Rot Scale pos offset pos offset pos offset ------------------------------------------------------------------------------ ---=== TELESCOPE OFFSETS AND SCALE II ===--- ---=== DATA TAPE SUMMARY ===--- Goes: JL none Stays: JL none ---=== FOCUS LOG ===--- setmir piston Temp Wind Time Inst scale M1 M2 Foc Az Alt (C) MPH Dir filt fwhm ------------------------------------------------------------------------------ ---=== WEATHER LOG ===--- Wind Time Temp F Dewp F MPH Direction Dust DIMM Sky 23:42Z 27 -13 14 15 (NNE) 97 - 00:14Z 26 -15 17 2 (N) 68 - 00:46Z 25 -15 24 18 (NNE) 125 - 01:19Z 25 -14 18 20 (NNE) 88 - 01:51Z 28 -18 18 21 (NNE) 74 - 02:23Z 28 -23 7 359 (NNW) 103 - 02:55Z 34 -33 8 285 (WNW) 65 - 03:28Z 33 -34 6 269 (W) 42 - 04:00Z 32 -30 6 266 (W) 52 - 04:31Z 30 -28 6 265 (W) 74 - 05:03Z 33 -33 3 269 (W) 105 - 05:35Z 34 -35 9 262 (W) 59 - 06:07Z 33 -33 11 236 (SW) 70 - 06:39Z 33 -33 8 251 (WSW) 60 - 07:09Z 32 -34 12 226 (SW) 73 - 07:40Z 31 -35 8 228 (SW) 78 - 08:11Z 31 -33 11 222 (SW) 88 - 08:43Z 31 -35 8 200 (SSW) 66 - 09:16Z 30 -33 8 222 (SW) 66 - 09:49Z 28 -30 10 216 (SW) 51 - 10:20Z 29 -29 7 184 (S) 37 - 10:52Z 29 -31 11 209 (SSW) 39 - 11:25Z 29 -22 17 234 (SW) 123 - 11:57Z 28 -9 13 236 (SW) 266 - 12:30Z 27 -8 10 212 (SSW) 369 - ---=== TELESCOPE STATUS ===--- 03:30Z Fans on doors opened, spectro dewars refilled. 05:40Z Telescope opened. Eng cam mounted. 12:30Z Telescope put to bed. Fans off, sepectro dewars refilled. ---=== SOFTWARE USED ===--- IOP/SOP: v3_143_0 Watcher: MCP: v5_26_0 TPM: tpm_v2_45_0 AstroDa: v14_47 TCC: TCC 2.7.2.1 August 6 2004 sdssProcedures: v1_96 SoS: v4_10_7 hoggPT: v1_6_9 plate-mapper: v4_3_1 ---=== MIRROR NUMBERS ===--- PRIMARY: -------- Scale: 1.000000 MIGS TONIGHT NOMINAL Axial A 0.5310 0.5250 Axial B 0.6060 0.6020 Axial C 0.9160 0.9050 Trans D -8.6000 -8.6120 Lateral E 10.0457 10.0203 Lateral F 11.6078 11.5951 GALILS Commanded: 4800. -2150. 2600. -6900. -7850. -7900. Actual: 4800. -2150. 2600. -6900. -7850. -7900. SETMIR VALUES PriDesOrient: 0.00 -2.76 1.04 57.00 151.01 PriOrient: 0.00 -3.04 0.88 57.42 149.40 SECONDARY: ---------- Focus: -131.80 Air Temp.: -1.4 Alt.: 57.277770 MIGS TONIGHT NOMINAL Axial A 3.0570 1.5390 Axial B 2.5390 1.0440 Axial C 2.6590 1.1590 Trans D -0.1320 -0.2020 GALILS Commanded: -261643. -273398. -361662. -9500. -5450. Actual: -261550. -273350. -361550. -9500. -5450. SETMIR VALUES SecDesOrient: -237.41 31.78 -10.00 -90.00 146.62 SecOrient: -237.47 31.78 -10.00 -89.48 146.60 ================== After collimation was done=========================== PRIMARY: -------- Scale: 1.000000 MIGS TONIGHT NOMINAL Axial A 0.5590 0.5250 Axial B 0.5720 0.6020 Axial C 0.9320 0.9050 Trans D -8.1960 -8.6120 Lateral E 10.0457 10.0203 Lateral F 11.6205 11.5951 GALILS Commanded: 4300. -1900. 2850. -13300. -7600. -7650. Actual: 4299. -1917. 2868. -13303. -7614. -7660. SETMIR VALUES PriDesOrient: 0.00 4.57 1.18 64.25 -249.76 PriOrient: 0.00 4.56 0.88 65.00 -249.58 SECONDARY: ---------- Focus: 0.00 Air Temp.: -1.5 Alt.: 29.999993 MIGS TONIGHT NOMINAL Axial A 1.5690 1.5390 Axial B 1.0530 1.0440 Axial C 1.1630 1.1590 Trans D -0.1950 -0.2020 GALILS Commanded: 1619101. 1604890. 1528355. -13800. -9950. Actual: 1619188. 1604973. 1528571. -13820. -9964. SETMIR VALUES SecDesOrient: 1257.00 27.97 -10.00 -90.00 257.89 SecOrient: 1256.90 28.01 -10.01 -89.94 257.47 ================ After setting up the nominal values ===================== PRIMARY: -------- Scale: 1.000000 MIGS TONIGHT NOMINAL Axial A 0.5600 0.5600 Axial B 0.5720 0.5720 Axial C 0.9330 0.9330 Trans D -8.1960 -8.1960 Lateral E 10.0457 10.0457 Lateral F 11.6205 11.6205 GALILS Commanded: 4300. -1900. 2850. -13300. -7600. -7650. Actual: 4299. -1917. 2868. -13303. -7614. -7660. SETMIR VALUES PriDesOrient: 0.00 4.57 1.18 64.25 -249.76 PriOrient: 0.00 4.56 0.88 65.00 -249.58 SECONDARY: ---------- Focus: 0.00 Air Temp.: -1.6 Alt.: 29.999993 MIGS TONIGHT NOMINAL Axial A 1.5690 1.5690 Axial B 1.0530 1.0530 Axial C 1.1620 1.1620 Trans D -0.1950 -0.1950 GALILS Commanded: 1619145. 1604871. 1528556. -13800. -9950. Actual: 1619188. 1604973. 1528571. -13820. -9964. SETMIR VALUES SecDesOrient: 1257.00 27.97 -10.00 -90.00 257.89 SecOrient: 1256.96 27.94 -10.01 -89.95 257.52 ---=== PROBLEMS IN DETAIL ===---