APACHE POINT OBSERVATORY SDSS 2.5M OBSERVING LOG Wednesday April 27, 2005 (MJD 53488) ---=== OBSERVING TEAM ===--- Swing Dan Long Night Mike Harvanek Steph Snedden Visitors: Scot Kleinman Support: Connie Rockosi (phone) ---=== OBSERVING PLAN ===--- Shake Night 1 ---=== OBSERVING SUMMARY ===--- Main shake items addressed: o sdssProcedures changes checked. Some (but not all) folklores that were moved to sdssProcedures were deleted. o IOP/SOP: QATopTen, fiducialCor.tcl and goStare tests completed. o Spectro header exposure time tests performed. Many cases of exposure times of zero in the fits headers. Please revert to previous specMech code. o Good pointing model implemented. We squeezed in one useful-for-science spectro exposure at the end of the night. ---=== OBSERVING LOG ===--- Afternoon: ---------- No problems with the afternoon check. Spectrograph focus checked. Settings were not changed. Depending on which you believe the focus is set for a temperature between 6 C (last night) and 8 C (today). See problem section for details. Engcam mounted. Test frames taken. Mirrors homed and relaxed. Values are well within tolerance of the existing nominal values. 00:45Z Doors Open, Fans On Night: ------ Dan noted that this afternoon goSpecFocus arcs repeatedly showed 0 exp time, but arcs from the command line or sopGUI gave the correct exposure time. We will watch for this during the shakedown specMech tests. See the spectro test section at the end of the shake items. Shakedown tests: =============== Standard Items: Engcam collimation check: Donuts before the pointing model showed some astigmatism. Donuts after the pointing model looked fairly evenly illuminated with just a little astigmatism. We will check collimation with the imager tomorrow night. sdssProcedures: -------------- All the changes in the changeLog were checked. We did not delete the engCam folklores because of a few edits that need to be made in that procedure. 1) "Mounting the engCam" proc items 1 and 2 need editing (missing sentence parts). 2) The internal links to "Setting up the guiderMac" don't work (at least in our browsers). We deleted the buildFiducials folklore entry after verifying it was part of sdssProcedures. We deleted the archiverCheck folklores after verifying all were now in sdssProcedures, however, we added a new folklore to the DA category mentioning where the folklores had been moved. Hopefully, we will remember to remove that folklore at some future date. QATopTen: -------- "QATopTen -brightest n" works as advertised for various values of n. fiducialCor: ----------- startMurmur -fidCor works as advertised. A great feature for those who just can't have too many murmur windows. Connie's goStare tests: ----------------------- We did imager goStares bracketed by goDrifts to get the following information for Connie. At first glance, it looks like the spectro frames and imager goStare frames have the same number of lines and subregion sizes. If Connie agrees the data look good, we will declare this test IOP current tomorrow. StatusDump ccd* results from bias drift: NAME ACCESS TYPE VALUE LOW HIGH DESCRIPTION ------------------ ------------- ----- -------- -------- -------- ------------------------- ccdChBotL pub w cfg int (array) 0 14 Bottom left VCI CHs for each CCD 0 2 4 6 8 14 14 14 ccdChBotR pub w cfg int (array) 0 14 Bottom right VCI CHs for each CCD 1 3 14 7 9 14 14 14 ccdChTopL pub w cfg int (array) 0 14 Top left VCI CHs for each CCD 14 14 14 14 14 14 14 14 ccdChTopR pub w cfg int (array) 0 14 Top right VCI CHs for each CCD 14 14 14 14 14 14 14 14 ccdColBias pub w cfg int 20 0 0 Num of bias pix (per CCD half) ccdColVis pub w cfg int 1024 0 0 Num of visible pix (per CCD half) ccdColOscn pub w cfg int 20 0 0 Num of overscan pix (per CCD half) ccdRowVis pub w cfg int 1361 0 0 Rows in Frame when drifting (staring ad ccdRowOscn pub w cfg int 0 0 0 Staring Only - Overscan rows per CCD re ccdRowLock pub w cfg int 0 0 0 Drifting Only - Rows in 1st group of Fr ccdPosId pub w cfg int (array) 0 0 Unique CCD position ID 16 26 36 46 56 -1 -1 0 statusDump ccd* for the staring frame: NAME ACCESS TYPE VALUE LOW HIGH DESCRIPTION ------------------ ------------- ----- -------- -------- -------- ------------------------- ccdChBotL pub w cfg int (array) 0 14 Bottom left VCI CHs for each CCD 0 2 4 6 8 14 14 14 ccdChBotR pub w cfg int (array) 0 14 Bottom right VCI CHs for each CCD 1 3 14 7 9 14 14 14 ccdChTopL pub w cfg int (array) 0 14 Top left VCI CHs for each CCD 14 14 14 14 14 14 14 14 ccdChTopR pub w cfg int (array) 0 14 Top right VCI CHs for each CCD 14 14 14 14 14 14 14 14 ccdColBias pub w cfg int 20 0 0 Num of bias pix (per CCD half) ccdColVis pub w cfg int 1024 0 0 Num of visible pix (per CCD half) ccdColOscn pub w cfg int 20 0 0 Num of overscan pix (per CCD half) ccdRowVis pub w cfg int 2048 0 0 Rows in Frame when drifting (staring ad ccdRowOscn pub w cfg int 21 0 0 Staring Only - Overscan rows per CCD re ccdRowLock pub w cfg int 0 0 0 Drifting Only - Rows in 1st group of Fr ccdPosId pub w cfg int (array) 0 0 Unique CCD position ID 16 26 36 46 56 -1 -1 0 11 Status entries found cc camstat results show the correct lines/frame and correct data_state after the stare: im> cc camstat LN2_FILL ON CAMERA_MONITOR ON E0 CAM_60=1 E1 CAM_61=1 CAM_62=1 CAM_63=1 CAM_64=1 CAM_65=1 E2 CAM_71=1 CAM_72=1 CAM_73=1 CAM_74=1 CAM_75=1 CAM_76=1 E3 CAM_11=1 CAM_12=1 CAM_13=1 CAM_14=1 CAM_15=1 CAM_16=1 E4 CAM_21=1 CAM_22=1 CAM_23=1 CAM_24=1 CAM_25=1 CAM_26=1 E5 CAM_31=1 CAM_32=1 CAM_33=1 CAM_34=1 CAM_35=1 CAM_36=1 E6 CAM_41=1 CAM_42=1 CAM_43=1 CAM_44=1 CAM_45=1 CAM_46=1 E7 CAM_51=1 CAM_52=1 CAM_53=1 CAM_54=1 CAM_55=1 CAM_56=1 E8 CAM_81=1 CAM_82=1 CAM_83=1 CAM_84=1 CAM_85=1 CAM_86=1 E9 CAM_91=1 CAM_92=1 CAM_93=1 CAM_94=1 CAM_95=1 E10 CAM_90=1 SERIAL_SPEED N/A SERIAL_BIN 1 PIXELS 1064 # PER LINE FOR EACH HALF OF THE CCD BINNED_PIXELS 1064 # PER LINE FOR EACH HALF OF THE CCD SERIAL_DIR FWD PARALLEL_BIN 1 PARALLEL_DIR FWD DATA_MODE FRAME LINES 2070 PER FRAME BINNED_LINES 2070 PER FRAME DATA_STATE IDLE LINESTART ENABLED LINESTART_PERIOD 26322_MICROSECONDS DACS_SET OK EXEC_BOOT ACKNOWLEDGED PHASE_BOOT ACKNOWLEDGED USR1 0 USR2 -1 USR3 0 After starting a bias drift, the following happened: im> goDrift -bias camera not setup for drifting, performing an initData statusEntry daqDrifting on node id1 is not 1 but 0 DA not setup for drifting, performing an initData 2005-04-28 02:13:40Z: Beginning data taking 2005-04-28 02:13:42Z: beginData has failed: {id1 {}} {id2 {}} {id3 {}} {id4 {}} {id5 {}} {id6 {}} {ad1 {Insufficient space in the Frame Pool}} {ad2 {Insufficient space in the Frame Pool}} {ad3 {Insufficient space in the Frame Pool}} {ad4 {Insufficient space in the Frame Pool}} Error: goDrift ends with error in beginData init'ing the pool fixed the above problem. After the drift, the statusDump ccd* gave: im> statusDump ccd* NAME ACCESS TYPE VALUE LOW HIGH DESCRIPTION ------------------ ------------- ----- -------- -------- -------- ------------------------- ccdChBotL pub w cfg int (array) 0 14 Bottom left VCI CHs for each CCD 0 2 4 6 8 14 14 14 ccdChBotR pub w cfg int (array) 0 14 Bottom right VCI CHs for each CCD 1 3 14 7 9 14 14 14 ccdChTopL pub w cfg int (array) 0 14 Top left VCI CHs for each CCD 14 14 14 14 14 14 14 14 ccdChTopR pub w cfg int (array) 0 14 Top right VCI CHs for each CCD 14 14 14 14 14 14 14 14 ccdColBias pub w cfg int 20 0 0 Num of bias pix (per CCD half) ccdColVis pub w cfg int 1024 0 0 Num of visible pix (per CCD half) ccdColOscn pub w cfg int 20 0 0 Num of overscan pix (per CCD half) ccdRowVis pub w cfg int 1361 0 0 Rows in Frame when drifting (staring ad ccdRowOscn pub w cfg int 0 0 0 Staring Only - Overscan rows per CCD re ccdRowLock pub w cfg int 0 0 0 Drifting Only - Rows in 1st group of Fr ccdPosId pub w cfg int (array) 0 0 Unique CCD position ID 16 26 36 46 56 -1 -1 0 and the cc camstat: im> cc camstat LN2_FILL ON CAMERA_MONITOR ON E0 CAM_60=1 E1 CAM_61=1 CAM_62=1 CAM_63=1 CAM_64=1 CAM_65=1 E2 CAM_71=1 CAM_72=1 CAM_73=1 CAM_74=1 CAM_75=1 CAM_76=1 E3 CAM_11=1 CAM_12=1 CAM_13=1 CAM_14=1 CAM_15=1 CAM_16=1 E4 CAM_21=1 CAM_22=1 CAM_23=1 CAM_24=1 CAM_25=1 CAM_26=1 E5 CAM_31=1 CAM_32=1 CAM_33=1 CAM_34=1 CAM_35=1 CAM_36=1 E6 CAM_41=1 CAM_42=1 CAM_43=1 CAM_44=1 CAM_45=1 CAM_46=1 E7 CAM_51=1 CAM_52=1 CAM_53=1 CAM_54=1 CAM_55=1 CAM_56=1 E8 CAM_81=1 CAM_82=1 CAM_83=1 CAM_84=1 CAM_85=1 CAM_86=1 E9 CAM_91=1 CAM_92=1 CAM_93=1 CAM_94=1 CAM_95=1 E10 CAM_90=1 SERIAL_SPEED N/A SERIAL_BIN 1 PIXELS 1064 # PER LINE FOR EACH HALF OF THE CCD BINNED_PIXELS 1064 # PER LINE FOR EACH HALF OF THE CCD SERIAL_DIR FWD PARALLEL_BIN 1 PARALLEL_DIR FWD DATA_MODE DRIFTSCAN DATA_STATE DRIFTSCANNING LINESTART ENABLED LINESTART_PERIOD 26322_MICROSECONDS DACS_SET OK EXEC_BOOT ACKNOWLEDGED PHASE_BOOT ? PHASEMICRO BUSY USR1 0 USR2 -1 USR3 0 And finally, the statusDump ccd* for the spectro frame: sp1> statusDump ccd* NAME ACCESS TYPE VALUE LOW HIGH DESCRIPTION ------------------ ------------- ----- -------- -------- -------- ------------------------- ccdChBotL pub w cfg int (array) 0 14 Bottom left VCI CHs for each CCD 0 2 0 2 14 14 14 14 ccdChBotR pub w cfg int (array) 0 14 Bottom right VCI CHs for each CCD 1 3 1 3 14 14 14 14 ccdChTopL pub w cfg int (array) 0 14 Top left VCI CHs for each CCD 14 14 14 14 14 14 14 14 ccdChTopR pub w cfg int (array) 0 14 Top right VCI CHs for each CCD 14 14 14 14 14 14 14 14 ccdColBias pub w cfg int 20 0 0 Num of bias pix (per CCD half) ccdColVis pub w cfg int 1024 0 0 Num of visible pix (per CCD half) ccdColOscn pub w cfg int 20 0 0 Num of overscan pix (per CCD half) ccdRowVis pub w cfg int 2048 0 0 Rows in Frame when drifting (staring ad ccdRowOscn pub w cfg int 21 0 0 Staring Only - Overscan rows per CCD re ccdRowLock pub w cfg int 0 0 0 Drifting Only - Rows in 1st group of Fr ccdPosId pub w cfg int (array) 0 0 Unique CCD position ID 1 4 3 2 -1 -1 -1 -1 Here is a comparison of the imager CCD subregions for goDrift and goStare (taken from the image headers): goDrift CCD r1: CCDSECL = '[21:1064,1:1361]' / Physical ccd section for low pixels OVERSECL= '[1:20,1:1361]' / Image section for overscan for low pix BIASSECL= '[21:40,1:1361]' / Image section for prescan for low pix DATASECL= '[41:1064,1:1361]' / Image section for data for low pixels CCDSECR = '[1065:2108,1:1361]' / Physical ccd section for high pixels DATASECR= '[1065:2088,1:1361]' / Image section for data for high pixels BIASSECL= '[2089:2108,1:1361]' / Image section for prescan for high pixels OVERSECR= '[2109:2128,1:1361]' / Image section for overscan for high pixels and for goStare CCD r2: CCDSECL = '[21:1064,1:2069]' / Physical ccd section for low pixels OVERSECL= '[1:20,1:2069]' / Image section for overscan for low pix BIASSECL= '[21:40,1:2069]' / Image section for prescan for low pix DATASECL= '[41:1064,1:2069]' / Image section for data for low pixels CCDSECR = '[1065:2108,1:2069]' / Physical ccd section for high pixels DATASECR= '[1065:2088,1:2069]' / Image section for data for high pixels BIASSECL= '[2089:2108,1:2069]' / Image section for prescan for high pixels OVERSECR= '[2109:2128,1:2069]' / Image section for overscan for high pixels and goDrift CCD z1: CCDSECL = '[21:1064,1:1361]' / Physical ccd section for low pixels OVERSECL= '[1:20,1:1361]' / Image section for overscan for low pix BIASSECL= '[21:40,1:1361]' / Image section for prescan for low pix DATASECL= '[41:1064,1:1361]' / Image section for data for low pixels CCDSECR = '[1065:2108,1:1361]' / Physical ccd section for high pixels DATASECR= '[1065:2088,1:1361]' / Image section for data for high pixels BIASSECL= '[2089:2108,1:1361]' / Image section for prescan for high pixels OVERSECR= '[2109:2128,1:1361]' / Image section for overscan for high pixels aaaaand goStare CCD z1: CCDSECL = '[21:1064,1:2069]' / Physical ccd section for low pixels OVERSECL= '[1:20,1:2069]' / Image section for overscan for low pix BIASSECL= '[21:40,1:2069]' / Image section for prescan for low pix DATASECL= '[41:1064,1:2069]' / Image section for data for low pixels CCDSECR = '[1065:2108,1:2069]' / Physical ccd section for high pixels DATASECR= '[1065:2088,1:2069]' / Image section for data for high pixels BIASSECL= '[2089:2108,1:2069]' / Image section for prescan for high pixels OVERSECR= '[2109:2128,1:2069]' / Image section for overscan for high pixels The frames themselves have been saved to juno in /home2/observer/connie as "drift_r1.fit", drift_z1.fit, "stare_r1.fit", and "stare_z1.fit". Note that the image size information for imaging drifts was the same before and after the goStares, therefore, I have only saved one set of frames. The final check we had time for was to exit iop, restart it, do a goStare -bias -init and it worked (Run 5286 frame 1). Then we did a goStare -bias. It also worked (Run 5286 frame 2). We finished with a bias drift, which also worked without problems. cc camstat also showed we were back to drifting mode with normal pix/line and linestart periods. Pointing Model: -------------- We obtained a good 72-point pointing model and implemented it. Details follow. Pointing model info: -------------------- The check of the engineering camera axis position showed it to be well-centered: 382.20, 256.79 compared to the desired position of 384, 256. New standard 72 point model compared to last month's: * fix * use ie ia pzz1 an aw ca * fit coeff change value sigma 1 IE +9.153 -149.71 0.876 2 IA -1.793 -144.02 1.428 3 AN -0.823 +6.47 0.347 4 AW +1.350 +1.88 0.348 5 HWCA2 -0.49 6 HWSA2 -0.61 7 HNCA1 -0.69 8 HNSA1 -1.18 9 CA +3.143 +36.47 0.997 10 PZZ1 +0.845 -125.02 1.078 11 ACEC +3.24 12 ACES -3.53 13 TX -8.09 Sky RMS = 2.56 Popn SD = 2.67 New standard 72 point model: * use * fit coeff change value sigma 1 IE -1.235 -150.95 1.013 2 IA -0.103 -144.12 1.113 3 AN -0.949 +5.52 0.352 4 AW -0.074 +1.81 0.344 5 HWCA2 +0.598 +0.11 0.453 6 HWSA2 -0.009 -0.62 0.466 7 HNCA1 +1.421 +0.73 0.525 8 HNSA1 +0.316 -0.87 0.524 9 CA -0.016 +36.45 0.825 10 PZZ1 -2.813 -127.83 3.322 11 ACEC -0.558 +2.68 0.632 12 ACES +3.374 -0.15 0.642 13 TX +1.453 -6.63 1.596 Sky RMS = 1.93 Popn SD = 2.14 Last 24 points of standard model compared to new model: * getdat [tcc.pterr]pterr_20050428.dat Read 24 data points * fix * use ie ia pzz1 an aw ca * fit coeff change value sigma 1 IE +1.718 -149.23 1.400 2 IA -2.241 -146.37 2.021 3 AN +1.843 +7.36 0.781 4 AW +1.103 +2.91 0.857 5 HWCA2 +0.11 6 HWSA2 -0.62 7 HNCA1 +0.73 8 HNSA1 -0.87 9 CA +0.753 +37.20 1.556 10 PZZ1 -0.225 -128.05 1.450 11 ACEC +2.68 12 ACES -0.15 13 TX -6.63 Sky RMS = 1.86 Popn SD = 2.15 Spectro Testing: ---------------- Mike did some spectro testing (pausing and aborting exposures) inside the enclosure without a cartridge. Results were inconclusive so we waited until we could go on-sky with a cartridge to test the specMech code and the header exposure time problem. The short answer is that we want to revert to the previous specMech code. Here are Mike's detailed notes: Three paused science exposures (frames 32304, 32305, 32308) and 1 unpaused science exposure (frame 32306) were taken in the enclosure. All 4 frames had an exposure time of 0 in the header. However, since the instrument was set to engcam in the tcc and the flat field screens would not open inside the exposure, we deemed these tests to be inconclusive and did further testing when we got on the sky. 08:32Z Mounted cartridge 4, plate 1841. Guide stars on gotoField. The flats & arcs from the precal showed the correct exposure times in the headers. When we got on the sky, we did 2 paused science exposures (frames 32313, 32314), 1 unpaused science exposure (frame 32315), 2 aborted exposures and a goSpecFocus. ALL headers had an exposure time of zero. "mechSend s" appeared to report the proper "requested exposure time" and the "exposure time left". However, "mechSend s" reported the "last exposure time" to be 0 (consistent with the exposure time in the headers) except in the case of the aborted exposures. In this case, "last exposure time" had the approximate value of the amount of exposure time elapsed before the exposure was aborted. The goSpecFocus was tested because Dan reported that goSpecFocus frames taken with the new specMech code have an exposure time of 0 and we confirmed this. We also did a real science exposure (frame 32320) and it, too, had an exposure time of 0 in the header. We fixed this with apofix before running endNight. The bottom line is that ALL science frames and all goSpecFocus frames taken with the new specMech code have an exposure time of 0. Therefore, we believe that we should revert back to the old specMech code. Another problem we noticed tonight that may or may not be related to the new specMech code is that twice tonight SoS was calling the plate number 0 after the cartridge (and plate) were loaded. Both times this happened just after sop had been started and the cartridge/plate had been loaded (yes, we started sop multiple times tonight). The first time we corrected this by loading the cartridge/plate again. The 2nd time we fixed this by exiting sop and starting it a 3rd time. After this, there were no more occurrences of this problem. ----- end of shakedown tests ----- 10:04Z With our remaining time, we decided to take a real 20 minute science exposure on this plate. The exposure time was zero in the header which messed up the sky counts in SoS. After an apo_fix, setting the exposure time to 1200s, and re-reducing the frame in SoS, we got useable signal with acceptable (though yellow b1 and b2) sky counts. endNight -doSpectro -doTpm ran successfully. ---=== IMAGING RUN SUMMARY ===--- Run Time Stripe Lambda Last Flavor Comments Start End Begin End Frame ------------------------------------------------------------------------- 5279 22:19Z 22:32Z 100 O -99.92 -96.66 32 ignore 5283 02:18Z 02:25Z 100 O -40.13 -38.43 25 ignore 5285 05:13Z 05:39Z 100 O 3.78 10.27 57 ignore 5287 09:39Z 09:46Z 100 O 70.40 72.15 25 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):y QA Procedures Done (y/n):y UT Exp Time flavor comment (S/N)^2 totals ========================================== b1 r1 b2 r2 ----- sequence 32298, plate 2147 ------- SpecMech tests 22:23 32298 10.0 flat 22:25 32299 2.0 arc 22:40 32300 0.0 arc 22:43 32301 0.0 arc ----- sequence 32302, plate -9999 ------- 00:51 32302 0.0 bias ----- sequence 32304, plate 0 ------- 01:57 32304 0.0 target ----- sequence 32305, plate 2147 ------- 02:20 32305 0.0 target 02:28 32306 0.0 target ----- sequence 32307, plate -9999 ------- 02:38 32307 0.0 bias ----- sequence 32308, plate 0 ------- 02:49 32308 0.0 target ----- sequence 32309, plate -9999 ------- 04:11 32309 0.0 bias ----- sequence 32310, plate -9999 ------- 08:50 32310 0.0 bias ----- sequence 32311, plate 1841 ------- specMech tests 09:00 32311 10.0 flat 09:02 32312 2.0 arc 09:13 32313 0.0 target Note the zero exposure times 09:24 32314 0.0 target 09:43 32315 0.0 target 09:56 32316 0.0 arc 09:59 32317 0.0 arc 10:08 32318 10.0 flat This is the precal for one good 10:10 32319 2.0 arc science exposure. 10:34 32320 0.0 target fixed to 1200s via apofix ---=== TELESCOPE OFFSETS AND SCALE I ===--- Time Instrument Az Alt Rot Scale pos offset pos offset pos offset ------------------------------------------------------------------------------ 10:07Z 4 1841 257.64 -0.0007 53.15 -0.0007 102.28 0.0011 1.000000 ---=== TELESCOPE OFFSETS AND SCALE II ===--- ---=== DATA TAPE SUMMARY ===--- Goes: JL8471 Stays: JL8472 ---=== FOCUS LOG ===--- setmir piston Temp Wind Time Inst scale M1 M2 Foc Az Alt (C) MPH Dir filt fwhm ------------------------------------------------------------------------------ 02:41Z engcam 1.00000 0 1247 0 121 30.3 8.2 20 253 10:07Z 4 1841 1.00000 0 1246 75 258 53.2 4.9 26 270 - 1.6 ---=== WEATHER LOG ===--- Wind Time Temp F Dewp F MPH Direction Dust DIMM Sky 22:24Z 53 16 30 228 (SW) 1256 - Mostly Clear 22:56Z 54 17 26 251 (WSW) 1496 - Mostly Clear 23:27Z 52 14 30 264 (W) 1873 - Mostly Clear 23:59Z 51 14 27 255 (WSW) 2759 - Mostly Clear 00:29Z 50 13 25 257 (WSW) 1849 - Mostly Clear 00:59Z 49 11 24 255 (WSW) 1516 - Clear 01:29Z 48 10 13 254 (WSW) 1922 - Clear 01:51Z 47 12 18 262 (W) 1389 - " 02:24Z 45 13 22 252 (WSW) 1388 - " 02:54Z 46 12 21 254 (WSW) 1473 - " 03:25Z 45 12 17 234 (SW) 1340 - " 03:58Z 45 11 20 255 (WSW) 1329 - " 04:30Z 44 12 12 266 (W) 1410 - " 05:02Z 44 12 22 247 (WSW) 1267 - " 05:34Z 44 12 16 249 (WSW) 1302 - " 06:06Z 44 11 19 257 (WSW) 1353 - " 06:38Z 42 12 16 253 (WSW) 1299 - " 07:11Z 42 12 19 239 (WSW) 1377 - " 07:43Z 42 12 15 257 (WSW) 1465 - " 08:15Z 42 11 15 256 (WSW) 1348 - " 08:48Z 42 12 19 268 (W) 1471 - " 09:19Z 41 13 20 265 (W) 1331 - " 09:53Z 41 13 23 265 (W) 1349 - " 10:23Z 40 15 23 276 (W) 1361 - " 10:53Z 40 16 14 267 (W) 1365 - " 11:26Z 39 16 18 270 (W) 1447 - " ---=== TELESCOPE STATUS ===--- 00:45Z Doors Open, Fans On 10:40Z Closed enclosure. Ventilation systems off. Telescope stowed at 30 deg alt with cart 4 mounted. Counterweights at 270. Spectro autofill connected. 11:17Z Spectro dewar weight: 208 lb 11:17Z Imager dewar weight: 170 lb ---=== SOFTWARE USED ===--- IOP/SOP: v3_147_0 Watcher: v2_30_0 MCP: v5_26_0 TPM: tpm_v2_47_0 AstroDa: v14_47 TCC: TCC 2.7.2.1 August 6 2004 sdssProcedures: v2_00 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.5830 0.5770 Axial B 0.5860 0.5880 Axial C 0.9510 0.9460 Trans D -8.2010 -8.1960 Lateral E 10.0203 10.0330 Lateral F 11.5824 11.5951 GALILS Commanded: 4300. -1900. 2850. -13300. -7600. -7650. Actual: 4300. -1900. 2850. -13300. -7600. -7650. 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.: 11.3 Alt.: 29.999997 MIGS TONIGHT NOMINAL Axial A 1.5710 1.5680 Axial B 1.0460 1.0460 Axial C 1.1580 1.1590 Trans D -0.1940 -0.2020 GALILS Commanded: 1619214. 1604947. 1528575. -13800. -9950. Actual: 1619200. 1604950. 1528550. -13800. -9950. SETMIR VALUES SecDesOrient: 1257.00 27.97 -10.00 -90.00 257.89 SecOrient: 1257.00 27.96 -10.02 -89.95 257.50 ---=== PROBLEMS IN DETAIL ===--- TCC: --- The GPS clock is not working, which prompted the following error: Modu="tut SetVAXClock" (2005-04-28 05:04:00Z) MCP: --- altitude (Windscreen touched in altitude: UP (2005-04-28 02:57:25Z sdssmcp): 2005-04-28 02:57:37Z ) rotator (correction for rotator -64003199 is too large (2005-04-28 05:16:00Z sdssmcp): 2005-04-28 05:16:17Z ) tracking (Excessive Az Tracking Error:: 2005-04-28 03:00:50Z) Spectrograph focus check ------------------------ sp1: Coll_motor_A -3155 Coll_motor_B -3554 Coll_motor_C -4350 Temp_Median 11 Temp_Hartmann_Bot 11 Temp_Hartmann_Top 11 Temp_Red_Cam_Bot 11 Temp_Red_Cam_Top 12 Temp_Blue_Cam_Bot 12 Temp_Blue_Cam_Top 11 sp2: Coll_motor_A -2459 Coll_motor_B -3663 Coll_motor_C -3650 Temp_Median 9 Temp_Hartmann_Bot 10 Temp_Hartmann_Top 10 Temp_Red_Cam_Bot 10 Temp_Red_Cam_Top 9 Temp_Blue_Cam_Bot 9 Temp_Blue_Cam_Top 9 COLLIMATE: Mean offset = 0.32 pix COLLIMATE: Camera b1 appears to be OUT-OF-FOCUS (|mean| > 0.15 pix) COLLIMATE: Predict blue camera ring movement of -11.4 degrees for spectro-1 COLLIMATE: Mean offset = 0.15 pix COLLIMATE: Camera b2 appears to be OUT-OF-FOCUS (|mean| > 0.15 pix) COLLIMATE: Predict blue camera ring movement of -5.4 degrees for spectro-2 COLLIMATE: Mean offset = -0.34 pix COLLIMATE: Camera r1 appears to be OUT-OF-FOCUS (|mean| > 0.15 pix) COLLIMATE: Predict (red) piston movement of 3137 steps for spectro-1 COLLIMATE: Mean offset = -0.19 pix COLLIMATE: Camera r2 appears to be OUT-OF-FOCUS (|mean| > 0.15 pix) COLLIMATE: Predict (red) piston movement of 1706 steps for spectro-2 Spectrograph 1 is at about 11C and is asking for 3100 so would indicate it is set for about 8 C Spectrograph 2 is at about 9 C and is asking for 1700 so would indicate it is set for about 7.5 C Last night I set them for 6 C and the collimators have not moved since then. I am leaving them unchanged, and they should be set for somewhere between 6 and 8 C.