APACHE POINT OBSERVATORY SDSS 2.5M OBSERVING LOG Wednesday October 6, 2004 (MJD 53285) ---=== OBSERVING TEAM ===--- Swing: Pete Newman Night: Steph Snedden, Jurek Krzesinski Visitors: jen Adelman-McCarty (FNAL_)) ---=== OBSERVING PLAN ===--- Pointing model then science (with remaining software shake-down in parallel). ---=== OBSERVING SUMMARY ===--- Lots of alt too large to correct errors at the beginning of the night. We were half way through the pointing model when clouds arrived. While on clouds we tested left over shakedown iop commands (see the log for results). Then due to high humidity we closed the telescope and stayed closed till the clouds and lighting have gone away. Then we reopened the telescope to finish the pointing model in marginal humid conditions, but with mirrors ~2 deg warmer than the ambient temperature. Please leave the eng camera on the telescope - we'll need it for samll pointing model tommorow. We borrowed a heater from 3.5m telescope and set it up in 2.5m enclosure, after closing. The day crew can switch it off when they'll get on the site. NOTE: The hand paddle used to move the enclosure over the telescope was dropped and it didn't work when we were trying to close the telescope. We opened the paddle and directly pushed a plastic rod under the key-switch to move the enclosure. The paddle was left open. We are sorry for that, but could you fix it for us, please? ---=== OBSERVING LOG ===--- Swing shift: The engineering camera is mounted, so no spectrograph focus checks were performed. The telescope was found to be somewhat top heavy, so the counterweights were moved from 115 to 80, but it was then found the secondary spectrograph dewars were close to empty (a fill started soon after), so the balance should be checked again after opening. We note that the mechanical vacuum pump that is backup to the venturi pump controlling the imager shutters bellows is not plugged in to power. If site air pressure should fail while the imager is mounted, be sure to power-up the pump with site (not UPS) power before switching over to "Mechanical" to move the shutters. No other anomalies noted. Night: ------ Started with pointing model. The procedures say that we should be doing it in unbinned camera mode, but since April (?) we actualy were doing pointings in binned mode. The reason for using a binned mode is that, the new engcam got ~4 times more pixels then the old one and the software doesn't want to read unbinned chip, it times out. The unfocused star image on eng cam looked quite all right. There is no need at the moment to tweak collimation. So, we proceeded with the pointing model. Seeing is about < 4 pixels - not bad. Optical axis on eng camera was found off (329 and 499 instead 256, 384), but it looks like we still got stars centered inside the field of view. 02:00Z The az axis aborted twice on going to first two stars in the pointing model. Yes, we did axis stop before going for the first star and on the second we DID axis init (after dopteer failed to go for the first star). Maybe we didn't wait long enough after axis init and resumed the pointing to early? Anyway, we quit the dopteer and run it again. This time there wasn't any axis abort, but we got 2 stars in the field of view on the first slew and none on the second. We sotpped a big pointimg model at this point and started a small one (20 points) only. Unfortunately on the first slew we didn't see any star. We quit dopteer again and slew the telescope to a fk5 star. This time the star was at the edge of the ccd chip. Then the second try at different alttitude was not found in the camera field of view. We cannot tell what happened between now and then, but stars are visible now at the edge of the camera chip. Plenty of too large to correct errors in alt. We forced the fiducials in that axis a few times and after that we saw no more too-large-to-correct errors. Also to get stars closer to the frame center, we found what kind of the offset has to be applied in the declination while we were observing close to meridian (it was -60 seconds). Then we parked the telescope at alt 56:00 and using MCP p command the telescope was told that we are at 55:59. That seemed to work. Anwyay, we started our full pointing model and stars were appearing very close to the camera chip center. It looks like after dopteer finds the first star (which usualy is not at the center) the rest of the stars are centered properly as dopteer already knew what kind of the corrections have to be done to have all of the stars centered. Also we don't see any too large to correct errors anymore - we have no explanation for that, but everything is going smoothly now. 04:37Z This is a very "interactive" pointing model - we've got clouds and have to change integration time or stop observations quite often. Also our PSF is varying too. It won't be our best pointing, but it'll be a good start. 04:57Z On 41 star and 90 seconds integration time we stopped. dopteer found a star, but we didn't see it. Since we dont't see stars through clouds, we paused dopteer and worked on left over iop shakedown tests, without imager mounted (there are too many lightnings south of us). stripeAxisPositions, and scanStripe: ------------------------------------ We scanStripe 90 S 162 - first time the command timed out (well it was a long slew, but it should not have happened). Since were almost there we just issued the same command again and it worked. NOTES: We need some correction to az axis table format so it will be the same as tccmon. For instance tccmon uses az 0,180 and 0, -180 while the stripeAxisPosition table output is 0, 360. Rotator values in stripe position tables are positive while in tccmon are negative. Also they are going in oposite directions. So there is a problem with a sign. We might need more detailed table as well. At the moment values are given at 20 minutes intervals, maybe every 10 minutes would be better. Lambda and alt agrees - no problem here. On 1260 startMu 354 Table mu and alt are correct, well az is correct but it is because both table and tcc mon started at positive values. I mean tables and tccmon are in the same quadrant. Also the az table is showing az decreasing values, passes 0 and turns into negative, while before after going below zero it swapped into 360 - az. bestStartWrap: ----------- im> bestStartWrap 90 -startLambda 162 05:23 -endLambda -162 lambdaStart 162 lambdaEnd 162 162 162 lambdaStart 162 lambdaEnd 198 162 198 Ignore the above - the best wraps are as follows: {az MID} {rot MID} What is the best wrap? -hmmm we guess that if bestStartWrap agrees with scanStripe than the bestStartWrap passed the test right? So before real scan, we just need to issue bestStartWrap command to see if we can goDrift safely through the whole scan, correct? Please give us more info on how to tell if bestStartWrap has passed the test. But what about this: im> bestStartWrap 90 -startLambda 0 05:23 -endLambda 160 lambdaStart 0 lambdaEnd 0 0 0 lambdaStart 0 lambdaEnd 160 0 160 lambda hit pole Ignore the above - the best wraps are as follows: {az MID} {rot MID} lambda hit the pole (which pole? - not me ;) ), but the next line says ignore above MID,MID. 06:04Z humidity high! - closing. 10:30Z Humidity was holding between 2 and 3.1 (diff) for quite a bit, the mirrors were 2 degrees warmer than ambiet temperature (after 4 hours sitting inside the enclosure). We decided to reopen the telescope and resume our pointing model with fans off hopeing that the mirrors will not cool down before we will finish collecting the data. Whatever we'll get we'll need to confirm it with a small pointing model tomorrow. 11:30Z The telescope was closed, ponting model data collected. All aluminium surfaces were dry, paint was getting wet. endnight done. ---=== IMAGING RUN SUMMARY ===--- Run Time Stripe Lambda Last Flavor Comments Start End Begin End Frame ------------------------------------------------------------------------- 4863 20:57Z 21:16Z 100 O 39.34 44.00 45 ignore doghouse ---=== 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): nothing done QA Procedures Done (y/n): nothing done UT Exp Time flavor comment (S/N)^2 totals ========================================== b1 r1 b2 r2 ----- sequence 28743, plate -9999 ------- 20:58 28743 0.0 bias ----- sequence 28744, plate -9999 ------- 23:41 28744 0.0 bias ---=== 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 20:01Z 55 29 15 252 (WSW) -9999 - 20:34Z 58 30 16 260 (W) -9999 - 21:06Z 55 33 14 268 (W) -9999 - 21:38Z 53 34 16 271 (W) -9999 - 22:10Z 54 36 14 214 (SW) -9999 - 22:43Z 52 35 12 233 (SW) -9999 - 23:15Z 52 36 17 214 (SW) -9999 - 01:32Z 49 36 8 246 (WSW) -9999 - 02:05Z 48 36 7 243 (WSW) -9999 - 02:37Z 49 35 8 236 (SW) -9999 - 03:09Z 50 32 7 252 (WSW) -9999 - 03:41Z 50 32 7 223 (SW) -9999 - 04:13Z 50 30 9 263 (W) -9999 - 04:46Z 50 30 6 263 (W) -9999 - 05:18Z 50 31 2 210 (SSW) -9999 - 05:50Z 47 42 13 139 (SE) -9999 - 06:23Z 47 43 2 81 (E) -9999 - 07:03Z 47 37 8 214 (SW) -9999 - 07:27Z 47 36 7 197 (SSW) -9999 - 07:59Z 45 40 6 302 (WNW) -9999 - 08:32Z 45 37 9 23 (NNE) -9999 - 09:04Z 44 40 4 217 (SW) -9999 - 09:36Z 45 39 3 266 (W) -9999 - 10:08Z 45 41 1 207 (SSW) -9999 - 10:41Z 44 41 1 194 (SSW) -9999 - 11:13Z 45 41 6 242 (WSW) -9999 - ---=== TELESCOPE STATUS ===--- 00:45Z Telescope opened, spectro dewars refilled. 06:10Z Telescope closed - high humidity. 10:30Z Telescope reopened dewars refilled. ---=== SOFTWARE USED ===--- IOP/SOP: v3_142_0 (test) Watcher: v2_29_0 MCP: v5_25_0 TPM: tpm_v2_42_0 AstroDa: v14_47 TCC: TCC 2.7.2.1 August 6 2004 sdssProcedures: v1_94 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.5300 0.5310 Axial B 0.6030 0.6060 Axial C 0.9190 0.9170 Trans D -8.1800 -8.1770 Lateral E 10.0330 10.0330 Lateral F 11.5951 11.5824 GALILS Commanded: 4950. -2250. 2550. -13750. -7850. -7900. Actual: 4950. -2250. 2550. -13750. -7850. -7900. SETMIR VALUES PriDesOrient: 0.00 -5.30 1.00 57.00 -288.80 PriOrient: 0.00 -5.32 1.32 56.82 -289.65 SECONDARY: ---------- Focus: 0.00 Air Temp.: 12.6 Alt.: 29.660340 MIGS TONIGHT NOMINAL Axial A 1.5410 1.5390 Axial B 1.0480 1.0430 Axial C 1.1580 1.1560 Trans D -0.2170 -0.2170 GALILS Commanded: 1619183. 1604934. 1528569. -13800. -9950. Actual: 1619200. 1604950. 1528550. -13800. -9950. SETMIR VALUES SecDesOrient: 1257.00 27.97 -10.00 -90.00 257.89 SecOrient: 1256.99 27.96 -10.01 -89.95 257.51 ---=== PROBLEMS IN DETAIL ===--- Recurrent TPM errors reported by watcher ======================================== dewar (Imager Dewar Scale Communications Fault:: 2004-10-06 20:53:17Z) m2 mig (Communications Fault: 2004-10-06 21:17:31Z) There was some discussion with Jon Brinkmann about thses faults. It is quite likely that the dewar fault occurred when the dewar was off the scales. The m2 error may have occrured during a long move of the secondary while changing from inst=engcam to inst=spectro in TCC to get the mirror numbers. In both cases, it was thought that the respective instrument might not communicate under those circumstances.