APACHE POINT OBSERVATORY SDSS 2.5M OBSERVING LOG Friday August 26, 2005 (MJD 53609) ---=== OBSERVING TEAM ===--- Swing: Jurek Krzesinski Night: Steph Snedden Howard Brewington Kaike Pan ---=== OBSERVING PLAN ===--- If the weather improves, we hope to complete a pointing model. And then mounted the imager for test scan and final collimation check. ---=== OBSERVING SUMMARY ===--- Completed the pointing model. Mounted the imager and did test scan. We had a problem mounting the imager; see log. ---=== OBSERVING LOG ===--- Afternoon checkout. ------------------ When the semaphore is released from MCP, then indeed who ever tries to move the telescope first (tcc or mcp) takes the semaphore. But in one case we weren't able to move the telescope with MCP (when the semaphor was released and not taken by tcc) and had to steal it. Then tcc and mpc refused to work at all, but afer a minute or so we found out that it was just a long delay caused by ????? Night: ------------------- We had clouds and rain at sunset, so we waited for better conditions. Spectro biases and the DA: ------------------------------ Kurt modified his code to prevent interrupt timeouts at the spectro crate. After this we were able to take, read out and archive normal looking spectro biases. Unfortunately, this in turn affected the photo nodes. An imager bias would start normally, but one by one different im nodes would just stop. There was no pattern as to which node or when it would time out, but it often happened early, by frame 11 or so on some random id or ad node. It is unclear why this code change would affect the photo nodes so. Spectro frame analysis: Once we had these spectro biases, I compared them to some biases taken before the DA work. In short, the biases look normal. What was r1 before is still r1 and has the same bias levels, number of pix and so forth. Below are the statistics for the ratio of old bias image / new bias image. Note that I removed cosmic rays by clipping at the 3- sigma level, so that is why the number of pixels varies somewhat from image to image. im> imstat b1 # IMAGE NPIX MIDPT MIN MAX b1 4389131 0.9995 0.9858 1.013 im> imstat b2 # IMAGE NPIX MIDPT MIN MAX b2 4387249 0.9989 0.9857 1.012 im> imstat r1 # IMAGE NPIX MIDPT MIN MAX r1 4384731 1.001 0.9863 1.015 im> imstat r2 # IMAGE NPIX MIDPT MIN MAX r2 4343913 0.9993 0.967 1.032 tcpflow tests for Fritz: ----------------- After Kurt rolled back his code so we could successfully take bias frames again, I ran tcpflow for Fritz during a bias drift started after a a track command. The bias drift while tracking is on sdsshost in /tmp/testa1 for the eth0 (tcc) side and /tmp/testb1 for the eth1 (VxWorks?) side. It turns out Fritz didn't get the info he wanted from the tcpflow so he started monitoring the packets directly during another bias drift. In this case, I made sure the focus was non-zero (set to 350). 05:03Z We pulled the building. In preparation of the pointing model and collimation check, we homed and relaxed M1 and m2. 8:00Z We completed the pointing model. Pointing model results: ----------- This month's results looked similar to those of April 27. The RMS error is a little over 0.1 asec worse than that model. There were no outliers, so we accepted the results and implemented the model. The details: * getdat PTERR_20050827.DAT;1 Skipping point too near zenith: 329.23 31.86 345.123272 89.078338 0.577274 -0.035047 0.075537 0.001506 4631841583.56 Read 71 data points * use * fit coeff change value sigma 1 IE +14.640 -136.31 1.172 2 IA -1.172 -145.30 1.248 3 AN -1.963 +3.56 0.378 4 AW -1.897 -0.09 0.377 5 HWCA2 -0.475 -0.37 0.495 6 HWSA2 +0.145 -0.47 0.500 7 HNCA1 -0.222 +0.51 0.565 8 HNSA1 -0.045 -0.91 0.563 9 CA +3.746 +40.20 0.931 10 PZZ1 +6.031 -121.80 3.846 11 ACEC -2.519 +0.16 0.686 12 ACES +0.930 +0.78 0.687 13 TX -0.670 -7.30 1.816 Sky RMS = 2.06 Popn SD = 2.28 08:42Z We mounted the imager to run some tests for Eric. When we were ready to mount the imager, however, we noticed that the rotator did not go to zero as instructed by the tcc although the mcpMenu reported that it was at zero. We used the mcpMenu to offset the rotator (~0.1-degree) to get the piece-of-tape indicator to line-up with the pointer on the east side of the scope. But, then the saddle latches would not engage after the imager was in position. After trying it several times, all latches finally engaged. And, we did a visual inspection of the latches to make sure. But, there seemed to be some type of a mechanical problem with the way the imager mounted. Imaging Tests: ---------------- 1) The focus loop works. The values in astroline are real except for timePerRow, timePerFrame and possibly rowsSkipped. All the values for these variables showed up as zero. 2) We are only able to do calcStripeParams and scanStripe on stripes that use lambda. 3) Skippy and seeingRun fail because of no TCC positional information in the headers. 4) The TCC info header problem also creates problems for idReport, as follows: im> goDrift Flavor of this run (science, bias, calibration, engineering, ignore, help) []: engineering Stripe, Strip (e.g, 22,N or SS,N) [100,O]: 86,N Please provide a one line comment [] Test of new DA imaging 2005-08-27 08:53:38Z: Beginning data taking 2005-08-27 08:53:42Z: idReport: problem in calcStripeParams, setting many params to NaN. Error was: domain error: argument not in valid range continuing with idReport anyway 0 im> After we rebooted the servers to get a working watcher, we noticed that all nodes reported a udp packet problem. We scanned 86N, and the focus loop worked okay. Although the tccMon also worked during the scan, information for tcc was still not getting into the fits headers. Therefore, skippy nor seeingRun could not work. See error message below for example. im> schedule seeingRun 5528 60 Reading data ... Analyzing ... Could not find gang file with RA in header can't read "title": no such variable can't read "title": no such variable while executing "pgLabel FRAME "MEDIAN SEEING" $title..." (procedure "seeingJudgePlot" line 126) invoked from within "seeingJudgePlot $run" (procedure "seeingRun" line 12) invoked from within "seeingRun 5528" ("eval" body line 1) invoked from within "eval $procname $args" seeingRun is scheduled, further errors sent to murmur 0 im> When we did a calcStripParams for a Segue stripe, we go the following error. im> calcStripeParams 79 N -startMu -162 Error: can't read "startNu": no such variable im> tb can't read "startNu": no such variable while executing "GCToSurvey $startMu $startNu..." invoked from within "set startSurvey [GCToSurvey $startMu $startNu..." invoked from within "if {$startMu != ""} { set limits [stripeLimits $stripe] if {[catch {keylget limits nu startNu}] != 0} { errorLog "Cannot specify a M ..." (procedure "calcStripeParams" line 94) invoked from within "calcStripeParams 79 N -startMu -162" im> Next, we move to 82 N, but tccMon still reported that we were still scanning 86 N. We did a collimation check with the imager mounted. The donuts were very slightly bottom heavy; however, we did not adjust it since the FWHM over the array was less than 1.5" Donuts were done,and we will move them to phoenix tomorrow. Run Frame Focus 5529 19 -700 5529 22 -350 5529 30 00 endNight finished and was happy ---=== IMAGING RUN SUMMARY ===--- Run Time Stripe Lambda Last Flavor Comments Start End Begin End Frame ------------------------------------------------------------------------- 5525 00:06Z 00:54Z 100 O 45.98 58.15 23 ignore 5526 03:43Z 04:03Z 100 O 100.52 105.53 47 ignore 5527 04:23Z 04:41Z 100 O 110.62 115.13 43 ignore ---=== IMAGING RUN DETAILS ===--- ---=== SKIPPY RESULTS ===--- Run Frame nFrames stars muErr muRms nuErr nuRms rot az el --------------------------------------------------------------------------- ---=== 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 ---=== 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 Stays: JL ---=== 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 00:32Z 61 48 2 103 (ESE) 278 - 01:04Z 61 49 8 75 (ENE) 323 - 01:39Z 63 47 2 188 (S) 288 - 02:10Z 62 46 4 179 (S) 255 - 05:23Z 61 44 4 204 (SSW) 215 - 05:53Z 61 46 1 207 (SSW) 266 - 06:24Z 62 48 1 201 (SSW) 273 - 07:01Z 62 47 1 222 (SW) 243 - 07:33Z 62 48 5 242 (WSW) 246 - 08:07Z 62 48 1 210 (SSW) 287 - 08:40Z 61 48 3 207 (SSW) 348 - 09:16Z 61 47 5 194 (SSW) 334 - 09:47Z 60 47 4 184 (S) 436 - 10:18Z 59 48 7 186 (S) 644 - 10:52Z 59 48 6 188 (S) 603 - 11:24Z 59 48 8 182 (S) 511 - ---=== TELESCOPE STATUS ===--- 03:00Z Cracked the doors, opened the louvers, and turned on fans. 05:03Z Pulled the enclosure 11:15Z Enclosure on, doors and louvers closed, fans off Telescope at 121,30,00 mount Imager 303lbs 18psi Spectro 251lbs 15psi Cart 01 mounted and Spectros were forced filled ---=== SOFTWARE USED ===--- IOP/SOP: iop Watcher: watcher MCP: v5_26_0 TPM: tpm_v3_0_0 AstroDa: biery TCC: TCC 2.7.2.1 August 6 2004 sdssProcedures: SoS: hoggPT: v1_6_9 plate-mapper: ---=== MIRROR NUMBERS ===--- ---=== PROBLEMS IN DETAIL ===---