APACHE POINT OBSERVATORY SDSS 2.5M OBSERVING LOG Wednesday January 22, 2003 (MJD 52662) ---=== OBSERVING TEAM ===--- Swing: Howard Brewington Night: Dan Long Pete Newman Support: Steph Snedden Eric Neilsen (by phone) Connie Rockosi (by phone) ---=== OBSERVING PLAN ===--- Shakedown! Pointing model Tracking tests Imager on sky check Bright Sky imaging Spectro on sky check SOP PR test ---=== OBSERVING SUMMARY ===--- An action packed shake night We managed to cram most of shakedown into one night. All three instruments saw sky time. We have a new 1.6 arcsecond pointing model. Tracking tests were done, and look nearly as good as the model. The imager was put on and the bright sky imaging test was done. This scan liked the new pointing model too. Skippy nu errors well under an arcsecond. The spectrographs were tested on sky too. Apart from some odd startup glitches from an aborted set inst, and a strange failure on a preCal (neither of which are attributable to the new SOP), spectroscopy worked normally. Spectrographs were refocused after the first plate. IOP v3_103_0, TPM tpm_v2_24_0, and MOP m2_22_0 were all declared current. Critical High server problem has been identified and fix should be in by the start of tomorrow night's observing ( in a new version of IOP ). ---=== OBSERVING LOG ===--- The afternoon started with continued debugging of the spectro server problem. Watcher/SP server problem A timing issue regarding startup of noop server .vs. sp server was found to be the reason why spectrograph information was not making it into the watcher. Sometime in the not too distant past a change in iop was made such that iopStartup.tcl took significantly longer for iop than sop. This means that the spectro server is ready to go well before the main noop server ( which invokes iop ). Thus the spectro server times out trying to connect, though confusingly it states that it does connect and is registered while also stating that it has no connection. The solution to this is to have the individual instrument servers not start up until the main noop server is running. The script will be modified to implement this change and a new version of IOP will be cut during the day. The critical error notification still needs to be tested. However it doesn't need sky and can be done either on a cloudy night or during the day. We should remember to do this on a night with bad weather sometime during the run. engCam work: We opened at sunset and after topping off the spectrographs, we started with the engineering camera on the telescope. Collimation looks good, on axis anyway. Instrument block check shows center within 7 pixels of desired value ( about an arcsecond ). Pointing model choked on first object with semaphore error. Second attempt was successful. Calibration offsets during pointing model often cause tpm alarm on tracking, meaning that an encoder error of more than 7 ticks occurred. Model data when fit to existing model was quite good; much better than expected given recent pointing performance of the instruments. The rms pointing error was about 4 arcseconds. When we fit the new data set, the residuals were about 1.3 arcseconds. We ran a small 24 point grid to test the new model. As expected, the fit to the previous 72 point model taken at the start of the night was excellent. The sky rms was 1.65 arcseconds. Tracking tests: The initial view of the data is that tracking is as good as advertised by the pointing model. The image appears to drift by an arcsecond or less in the 30 minutes of tracking for each test. Images were taken every 90 seconds by scheduling tccput gcam dofind 10 in a sop session. All guider images are stored on Landru in /home/long/tracktest52662. Three tests were run. The first test was centered on the meridian in the south at an altitude of about 70 degrees. It is covered by guider frames 148 - 167. The second test ran across the meridian in the south, but this time at an altitude of about 45 degrees. It is covered by guider frames 171 - 190. The third test ran along the equator and started about 3.5 hours over in the east. It is covered by guider frames 194 - 213. See the end of the log for the centroid data from these guider frames Imaging: We decided to test the imager on sky next and do the collimation check. As the moon is still quite bright, the skies are clear, we proceeded with the bright sky imaging test. There will be a coincident bright sky bias test. Is a bias any good when taken in relatively bright moon? The bias run 3599 will provide evidence. The flat field screens were closed during the bias. Run 3600 Bright Sky Imaging: In focus by about frame 18 ( lambda -28 ). Excellent seeing, sub arcsecond on several chips. Skippy reports nuErr well under an arcsecond. Maybe the new pointing model really is better, though this makes the 4 arcsecond fit of the new data to the old model somewhat puzzling. Horizontal sky variations on the chips clearly visible. Looks like uneven illumination from moonlight bouncing around the windbaffle and being shielded from the chips partly by the shutters. Moon at least 45 degrees away during this run. Cloud cruised by over the telescope starting at frame 117 ( lambda -13 ). Good data between frame 18 and 116. Spectroscopy: 01:45Z Off to inst change. Time for spectroscopy. 02:10Z Off to the field for cartridge 8. Problem at the start of the setup taking a guider flat. Apparently issuing startMon while slewing to field can cause trouble. Guider flat had few counts and there was a divide by zero error in the calculations on the flat. Reissuing the gotoField -gflat worked. guiderDataWindow now shows Yes in all the fiber in use blocks. Efficiency meter reading about a tenth of what it should. The guider for some reason is running the wrong camID ( 6 instead of 2 ) 0 12 W Text="desired camera # is 6but current camera # is 2" 0 12 I GCamID=1, 6; GCamInfo="SenSys", 768.0, 512.0, 12 0 12 I Received="2 2 0 0 384 256 10.00 2 10.00 "image: binXY begXY sizeXY expTime camID temp"" 0 12 I Received="8.00 1000 params: boxSize (FWHM units) maxFileNum" After the first science exposure read out, the instrument was again set to spectro and this time the guider gain and efficiency meter are making sense. We then noticed that SoS was complaining about the lack of a flat. For some reason the flat was never taken during original preCal at 9:36:41Z. The command issued was preCalib 1 1, so it should have taken one. What happened? Apparently the goStare attempted to take the flat 5 times and failed and went on to take the arc. The instruments were grabbed during this time, so why it couldn't take the flat in 5 tries is a mystery. Starting Flat field 0 (press cntrl-C to abort) Flushing charge for 15 sec 2003-01-23 09:38:02Z: Original command was !e10! 2003-01-23 09:38:02Z: expected reply was !e10 OK ! goStare was not successful, trying again goStare was not successful, trying again goStare was not successful, trying again goStare was not successful, trying again goStare was not successful, trying again goStare was not successful, trying again Could not do goStare in 5 attempts Finished with Flat field 0 Finished with Flat Field With a proper preCal, the science exposure was re-reduced. Some of the XSIGMA and WSIGMA values from the preCal were in the yellow, but none were in the red. Spoke too soon. There was one red WSIGMA in the postCal ( by .01, 1.05 was yellow, 1.06 was red ). The postCal arc 18265 ( which actually wasn't requested ) was declared bad. We decided to refocus the spectrographs before proceeding with the next cartridge. Moves of nearly -8000 were requested by collimate. With those in place we went ahead and started preCals. Subsequent calibrations were all in spec for XSIGMA and WSIGMA. We got one science exposure on cartridge 9 before twilight. ---=== IMAGING RUN SUMMARY ===--- Run Time Stripe Lambda Last Flavor Comments Start End Begin End Frame ------------------------------------------------------------------------- 3599 07:13Z 07:28Z 100 O -60.33 -56.46 39 bias 3600 07:32Z 08:45Z 37 N -29.39 -10.89 136 engineering ---=== IMAGING RUN DETAILS ===--- ---=== SKIPPY RESULTS ===--- Run Frame nFrames stars muErr muRms nuErr nuRms rot az el --------------------------------------------------------------------------- 3600 11 4 52 -2.800 0.375 0.300 0.187 -0.00924 360 69 3600 24 4 75 -0.700 0.139 0.300 0.130 -0.00966 0 67 3600 75 4 54 -1.700 0.280 0.000 0.661 -0.01251 3 62 3600 116 4 63 -0.400 0.187 0.400 0.124 -0.01214 7 58 3600 125 4 65 -0.600 0.578 0.300 0.162 -0.01226 7 58 ---=== LTMATCH RESULTS ===--- Run Field nFields alt az nGood rowMean rowSig colMean colSig rot ------------------------------------------------------------------------ 3600 34 1 66 179 24 0.884 0.162 2.396 0.094 -0.00805 3600 34 1 66 179 19 0.307 0.155 2.534 0.106 -0.00852 3600 34 1 66 179 21 -0.121 0.201 2.375 0.149 -0.00799 3600 34 1 66 179 16 -0.399 0.217 2.453 0.085 -0.00825 3600 34 1 66 179 22 -0.694 0.202 2.579 0.129 -0.00867 3600 52 1 64 178 21 1.968 0.113 2.136 0.085 -0.00718 3600 52 1 64 178 28 1.430 0.149 2.254 0.077 -0.00758 3600 52 1 64 178 17 0.969 0.123 2.213 0.141 -0.00744 3600 52 1 64 178 30 0.739 0.127 2.325 0.132 -0.00782 3600 52 1 64 178 13 0.417 0.144 2.480 0.163 -0.00834 3600 87 1 60 176 10 1.200 0.110 2.928 0.174 -0.00984 3600 87 1 60 176 21 0.653 0.369 3.025 0.195 -0.01017 3600 87 1 60 176 16 0.165 0.186 3.016 0.214 -0.01014 3600 87 1 60 176 20 -0.222 0.129 2.920 0.218 -0.00982 3600 87 1 60 176 20 -0.508 0.157 3.083 0.235 -0.01036 3600 105 1 59 174 17 0.223 0.204 3.142 0.193 -0.01056 3600 105 1 59 174 20 -0.272 0.124 3.291 0.125 -0.01106 3600 105 1 59 174 13 -0.621 0.152 3.426 0.165 -0.01152 3600 105 1 59 174 14 -0.765 0.206 3.385 0.180 -0.01138 3600 105 1 59 174 12 -1.298 0.230 3.475 0.186 -0.01168 3600 118 1 58 173 27 1.334 0.190 3.192 0.195 -0.01073 3600 118 1 58 173 19 0.648 0.193 3.234 0.167 -0.01087 3600 118 1 58 173 23 0.071 0.112 3.050 0.182 -0.01025 3600 118 1 58 173 14 -0.281 0.146 3.353 0.135 -0.01127 3600 118 1 58 173 13 -1.006 1.068 2.945 1.749 -0.00990 ---=== SPECTROSCOPY DATA SUMMARY ===--- UT Exp Time flavor comment (S/N)^2 totals ========================================== b1 r1 b2 r2 ----- sequence 18256, plate -9999 ------- 09:10 18256 0.0 bias ----- sequence 18257, plate 1200 ------- 12.0 18.3 12.5 17.8 09:40 18257 2.0 arc 10:04 18258 900.1 target 10:14 18259 10.0 flat 10:16 18260 2.0 arc 10:40 18261 1200.1 target 11:03 18262 1200.1 target 11:21 18263 900.1 target 11:24 18264 10.0 flat 11:27 18265 2.0 arc ----- sequence 18266, plate 1162 ------- 4.3 5.2 5.0 5.3 11:46 18266 2.1 arc 11:49 18267 2.1 arc 12:16 18268 10.0 flat 12:19 18269 2.0 arc 12:43 18270 1200.1 target ---=== TELESCOPE OFFSETS AND SCALE I ===--- Time Instrument Az Alt Rot Scale pos offset pos offset pos offset ------------------------------------------------------------------------------ 09:51Z 8 1200 241.24 -0.0003 66.79 0.0029 77.81 -0.0053 1.000150 12:30Z 9 1162 159.04 -0.0055 65.22 -0.0010 -31.78 -0.0026 1.000110 ---=== TELESCOPE OFFSETS AND SCALE II ===--- ---=== DATA TAPE SUMMARY ===--- Goes: JL5863 - JL5868, JL5901 Stays: JL5869, JL5905, JL5871 - L5874, JL5902 ^^^^^^ Why was this high numbered tape in ID2-2 and JL5870 lying on the table? Problem with that tape? ---=== FOCUS LOG ===--- setmir piston Temp Wind Time Inst scale M1 M2 Foc Az Alt (C) MPH Dir filt fwhm ------------------------------------------------------------------------------ 01:34Z engcam 1.00000 0 -2658 -310 121 60.1 3.7 12 80 ND2 1.35 04:51Z engcam 1.00000 0 -2689 -310 376 77.3 3.5 4 182 ND2 0.78 07:41Z imager 1.00000 0 -550 -421 180 67.2 2.4 5 266 23-i' 1.00 07:51Z imager 1.00000 0 -557 -431 179 65.5 2.4 6 264 23-i' 0.87 09:50Z 8 1200 1.00015 -1480 -159 -70 241 66.9 0.8 9 306 - 1.2 12:21Z 9 1162 1.00011 -1085 103 -140 157 64.5 -0.1 11 353 - 1.6 ---=== WEATHER LOG ===--- Wind Time Temp F Dewp F MPH Direction Dust DIMM Sky 23:55Z 37 22 12 51 (NE) 96 - Clear 00:27Z 37 20 14 70 (ENE) 77 - Clear 01:03Z 38 18 12 80 (E) 84 - Mostly Clear 11 01:34Z 38 17 12 79 (E) 66 - Mostly Clear 12 02:04Z 38 17 12 77 (ENE) 76 - Clear? 7.8 02:40Z 38 17 12 67 (ENE) 60 - Clear? 7.3 03:12Z 37 18 9 60 (ENE) 83 - Clear? 6.5 03:45Z 38 14 4 342 (NNW) 75 - Clear 4.8 04:17Z 38 15 1 260 (W) 81 - Clear 4.4 04:51Z 38 16 4 181 (S) 71 - Clear 5.1 05:21Z 37 17 5 181 (S) 91 - Clear 5.3 05:54Z 37 18 5 184 (S) 119 - Clear 4.8 06:26Z 36 18 1 251 (WSW) 127 - Clear 4.8 06:58Z 36 20 4 275 (W) 116 - Clear 4.4 07:30Z 36 19 4 261 (W) 117 - Clear 4.6 08:03Z 36 17 7 267 (W) 108 - Clear 4.5 08:35Z 35 17 10 316 (NW) 90 - Mostly Clear 9.8 09:07Z 33 18 9 317 (NW) 70 - Clear 4.4 09:40Z 33 18 8 303 (WNW) 82 - Cirrus 13.0 10:12Z 33 18 7 346 (NNW) 81 - Cirrus 16.1 10:45Z 33 18 6 354 (NNW) 85 - Cirrus 9.6 11:16Z 32 17 8 350 (NNW) 74 - Thin Cirrus 8.5 11:49Z 32 18 10 346 (NNW) 71 - Thin Cirrus 8.2 12:20Z 32 19 8 1 (N) 115 - Thin Cirrus 9.9 12:53Z 32 18 10 5 (N) 81 - Cirrus 48.0 13:25Z 35 16 8 315 (NW) 50 - Cirrus ---=== TELESCOPE STATUS ===--- 23:30 open doors, fans on 00:35 enclosure open 13:00 enclosure closed, fans off. Stowed at 30 deg alt, cartridge 9 installed. Spectro auto-fill connected. Spectrograph dewar 13:00Z Dewar wt 240 lb Imager dewar 13:00Z Dewar wt 76 lb No interlocks bypassed ---=== SOFTWARE USED ===--- IOP/SOP: v3_103_0 Watcher: v2_20_0 MCP: v5_17_0 TPM: tpm_v2_24_0 AstroDa: v14_47 TCC: TCC 2.6.8 November 13 2002 sdssProcedures: v1_62 SoS: v4_9_13 hoggPT: v1_5_8 plate-mapper: v4_2_0 ---=== MIRROR NUMBERS ===--- PRIMARY: -------- Scale: 1.000000 MIGS TONIGHT NOMINAL Axial A 0.0820 0.0790 Axial B 0.7990 0.7970 Axial C 0.8130 0.8240 Trans D -9.0810 -9.1130 Lateral E 1.8660 1.8870 Lateral F 0.0000 1.4300 GALILS Commanded: 5400. -3700. 900. -200. 31550. 30650. Actual: 5400. -3700. 900. -200. 31550. 30650. SETMIR VALUES PriDesOrient: 0.00 -11.80 23.00 1256.90 642.10 PriOrient: 0.00 -12.16 22.81 1257.41 642.19 SECONDARY: ---------- Focus: 0.00 Air Temp.: 3.3 Alt.: 30.017944 MIGS TONIGHT NOMINAL Axial A 1.5210 1.5170 Axial B 1.1590 1.1560 Axial C 1.0970 1.0990 Trans D -0.7040 -0.7070 GALILS Commanded: 1619756. 1555139. 1576354. -3400. -7900. Actual: 1619650. 1555250. 1576350. -3400. -7900. SETMIR VALUES SecDesOrient: 1257.00 0.00 -20.00 0.00 130.98 SecOrient: 1257.00 -0.03 -20.07 -0.53 130.90 ---=== PROBLEMS IN DETAIL ===--- Well not so much problems but extensive detail too long to put in the main body of the log. ========================================================================== Pointing Model Details: We shot pointing data using the TGRID:GRID_DEFAULT_72PT.DAT grid, implemented the resulting pointing model, then compared it to the 24-point grid GRID_6_4_27_87_T_0.DAT. Comparison of new data to old model implemented several months ago. The mean difference is 4.3 arcsec, and the plots show this to be mostly in altitude. Why is this so much less than the 12-15 arcsec errors we have occasionally seen during science observations in the last couple of months? * getdat tpterr:PTERR_20030123.DAT;2 Read 72 data points * fix * fit coeff change value sigma 1 IE -205.91 2 IA -256.32 3 AN +0.51 4 AW -7.75 5 HWCA2 -0.12 6 HWSA2 -1.10 7 HNCA1 -0.21 8 HNSA1 +0.14 9 CA +16.02 10 PZZ1 -147.03 11 ACEC +1.90 12 ACES -5.21 13 TX -2.32 Sky RMS = 4.30 Popn SD = 4.30 Fit of a new model to the new data. Looks very good: * getdat tpterr:PTERR_20030123.DAT;2 * use * fit coeff change value sigma 1 IE +5.571 -200.34 0.653 2 IA +4.208 -252.11 0.711 3 AN -1.348 -0.84 0.223 4 AW +0.804 -6.95 0.218 5 HWCA2 +0.070 -0.05 0.287 6 HWSA2 +0.622 -0.47 0.296 7 HNCA1 +0.530 +0.32 0.333 8 HNSA1 -0.331 -0.19 0.332 9 CA -0.931 +15.09 0.527 10 PZZ1 +3.946 -143.09 2.147 11 ACEC -0.740 +1.16 0.401 12 ACES +3.917 -1.29 0.407 13 TX -0.199 -2.52 1.030 Sky RMS = 1.22 Popn SD = 1.35 * outmod tdat:telmod $ dir telmod* Directory DKA300:[TCC.LOCAL.DAT] TELMOD.DAT;38 in telrun: We then compared the new model to a 6x4 grid with excellent results: * inmod tdat:telmod DKA300:[TCC.PTERR]PTERR_20030123.DAT;2 * getdat tpterr:PTERR_20030123.DAT * fix * fit coeff change value sigma 1 IE -200.34 2 IA -252.11 3 AN -0.84 4 AW -6.95 5 HWCA2 -0.05 6 HWSA2 -0.47 7 HNCA1 +0.32 8 HNSA1 -0.19 9 CA +15.09 10 PZZ1 -143.09 11 ACEC +1.16 12 ACES -1.29 13 TX -2.52 Sky RMS = 1.65 Popn SD = 1.65 ========================================================================== Tracking Test Details: Below is the data from the open-loop tracking tests. Columns are mostly the GSDataPix fields from tcc, see http://www.apo.nmsu.edu/Telescopes/TCC/MessageKeywords.html#GSDataPix Col Contents a Guider image number gimgxxxx.fits b,c x,y position on guide image (binned pixels) d,e FWHM (binned pixels) along major and minor axes of ellipse f orientation of ellipse (deg) where major axis along x=0, y=90 g amplitude (counts) h integrated brightness (counts) i sky brightness (counts) j centroid status code (0 means success, see Guide Image Controller manual for other codes) Warning: the current guide software (as of 11/25/97) is probably returning x,y FWHM instead of maj,min FWHM, and the current zero and sign convention for alpha is unknown. The documentation reflects how things will be once the guide software is finished. track 93,20 /rottype=obj /rotan=0 /pterr=(noobj) schedule {tccPut gcam dofind} 10 90 (for 20 images in ~30 mins). Starting at 22:51 MST, about 5 deg east of meridian, image every 90 seconds a b c d e f g h i j 148 383.36, 254.13, 5.72, 5.51, -16.00, 1080.20, 41754.50, 59.00, 0 149 382.27, 255.51, 7.07, 5.91, 18.60, 884.70, 40615.20, 59.00, 0 150 384.36, 255.88, 7.39, 6.79, 12.00, 753.60, 39536.90, 59.00, 0 151 384.29, 257.24, 7.86, 6.74, 36.40, 755.80, 40044.90, 59.00, 0 152 383.74, 257.79, 7.04, 6.62, 20.60, 814.20, 40303.90, 59.00, 0 153 384.87, 257.56, 6.59, 6.30, -65.80, 850.00, 40185.50, 59.00, 0 154 385.15, 257.87, 6.50, 5.86, 66.60, 936.60, 40918.50, 59.00, 0 155 385.92, 257.39, 6.26, 5.39, 14.70, 1047.90, 41388.60, 59.00, 0 156 385.77, 257.63, 6.56, 5.71, 48.40, 939.70, 40595.10, 59.00, 0 157 386.41, 258.01, 7.07, 5.83, 29.30, 898.80, 40594.50, 59.00, 0 158 386.96, 257.47, 7.41, 6.07, 19.50, 829.60, 39753.50, 59.00, 0 159 386.89, 258.04, 6.76, 5.67, 39.30, 951.50, 41270.00, 58.00, 0 160 387.29, 256.91, 5.50, 5.44, 11.40, 1111.50, 42117.80, 58.00, 0 161 387.89, 255.88, 6.84, 6.00, 11.80, 912.00, 41365.30, 58.00, 0 162 387.33, 255.09, 6.62, 5.66, 6.30, 946.70, 41286.80, 58.00, 0 163 387.47, 254.15, 6.63, 6.19, 23.90, 907.50, 41279.50, 58.00, 0 164 388.67, 255.65, 7.03, 6.25, 9.30, 852.90, 40599.00, 58.00, 0 165 389.06, 255.39, 7.19, 6.13, -1.00, 872.60, 41006.60, 58.00, 0 166 389.92, 255.31, 6.84, 6.05, -7.50, 929.30, 41529.70, 58.00, 0 167 390.11, 253.92, 6.72, 5.89, -11.40, 947.30, 41371.00, 58.00, 0 End at MST 22:20, LST 97deg track 102,-10 /rottype=obj /rotan=0 /pterr=(noobj) Start at 22:23MST, LST=97.9deg a b c d e f g h i j 171 382.98, 239.11, 8.56, 7.71, -82.60, 256.70, 16142.30, 58.00, 0 172 385.50, 240.66, 8.57, 7.74, -89.00, 253.20, 15864.20, 58.00, 0 173 383.33, 239.77, 8.53, 8.42, -22.80, 233.90, 15603.50, 58.00, 0 174 383.76, 241.85, 8.64, 8.53, -12.30, 227.10, 15666.30, 58.00, 0 175 383.64, 241.30, 8.21, 7.90, -13.60, 253.50, 15833.70, 58.00, 0 176 384.09, 241.13, 8.19, 7.87, -87.70, 256.70, 16070.50, 58.00, 0 177 383.31, 243.19, 7.96, 7.48, -83.50, 279.30, 16028.90, 58.00, 0 178 383.89, 242.72, 8.24, 8.05, -28.80, 245.10, 15774.40, 58.00, 0 179 383.72, 243.68, 7.59, 6.80, -87.90, 309.90, 16468.10, 58.00, 0 180 384.51, 243.67, 7.71, 7.01, 79.60, 291.90, 16440.20, 58.00, 0 181 385.17, 244.30, 8.43, 7.82, 58.20, 256.20, 16007.40, 58.00, 0 182 386.19, 244.40, 7.87, 7.25, -81.40, 295.50, 16259.60, 58.00, 0 183 385.79, 244.88, 7.91, 7.72, 50.60, 269.80, 16148.00, 58.00, 0 184 386.04, 244.56, 7.84, 7.35, -83.90, 287.20, 16668.00, 58.00, 0 185 387.20, 244.99, 8.03, 7.40, 85.70, 283.90, 16379.20, 58.00, 0 186 387.94, 246.48, 8.03, 7.07, 86.50, 289.10, 16132.30, 58.00, 0 187 387.58, 245.65, 7.50, 7.04, 78.40, 322.00, 16677.50, 58.00, 0 188 388.06, 246.37, 7.43, 6.84, -86.20, 332.70, 16732.30, 58.00, 0 189 388.36, 246.87, 7.97, 7.33, 69.80, 286.20, 16522.10, 58.00, 0 190 388.70, 245.91, 8.28, 6.41, -89.90, 314.30, 16316.50, 58.00, 0 track 157,0 /rottype=obj /rotan=0 /pterr=(noobj) Start at 22:57MST, LST=106 a b c d e f g h i j 194 384.45, 257.09, 10.14, 8.91, -21.20, 1863.40, 153790.80, 60.00, 0 195 385.33, 255.07, 9.07, 7.61, -42.60, 2396.10, 158089.80, 59.00, 0 196 386.90, 254.93, 8.94, 8.17, -35.60, 2260.30, 156650.00, 60.00, 0 197 386.32, 254.96, 9.39, 8.36, -50.40, 2086.80, 153826.00, 60.00, 0 198 388.17, 255.69, 9.01, 7.43, -45.70, 2430.40, 157375.30, 60.00, 0 199 388.28, 256.90, 8.64, 7.47, -39.90, 2505.70, 157991.80, 60.00, 0 200 388.02, 256.50, 8.97, 8.08, -24.10, 2251.10, 154603.40, 60.00, 0 201 389.13, 255.87, 8.96, 8.51, -73.30, 2171.10, 154641.50, 60.00, 0 202 389.81, 254.70, 8.65, 8.53, 60.00, 2217.50, 154187.00, 60.00, 0 203 389.98, 255.06, 8.77, 8.05, -78.50, 2346.60, 157673.00, 60.00, 0 204 388.38, 254.26, 10.37, 10.11, 59.90, 1566.20, 146896.80, 60.00, 0 205 390.69, 253.12, 8.84, 8.76, -43.40, 2131.50, 154165.70, 60.00, 0 206 388.99, 252.61, 9.18, 8.67, -66.10, 2088.40, 154196.20, 60.00, 0 207 389.44, 253.91, 9.79, 8.97, -61.80, 1960.30, 156633.30, 60.00, 0 208 388.78, 254.92, 8.98, 8.12, -35.80, 2225.50, 155797.40, 60.00, 0 209 390.50, 254.25, 9.45, 9.02, -77.00, 2015.80, 157650.20, 60.00, 0 210 389.32, 254.80, 9.00, 8.33, -53.70, 2248.80, 158694.40, 59.00, 0 211 390.69, 254.14, 8.81, 8.57, -19.70, 2258.70, 158600.60, 59.00, 0 212 390.25, 253.89, 8.86, 8.33, 52.60, 2336.70, 160674.40, 60.00, 0 213 391.55, 253.22, 9.43, 9.00, -37.60, 1993.30, 156064.90, 59.00, 0 ========================================================================== Spectro Focus Details: goSpecFocus said: Issue: sp1; mechPiston -7961 sp1 blue l-r = -0.658 pixels , tolerance = 0.15 pixels, not focused yet Predict a movement of 23 steps for sp1 blue If red is in focus then you need to rotate blue camera ring by 23 degrees Issue: sp2; mechPiston -8876 Predict a movement of 34 steps for sp2 blue If red is in focus then you need to rotate blue camera ring by 34 degrees collimate said: COLLIMATE: Camera b1 appears to be OUT-OF-FOCUS (|mean| > 0.15 pix) COLLIMATE: Predict blue camera ring movement of 24.7 degrees for spectro-1 COLLIMATE: (if red is already in focus) COLLIMATE: Camera r1 appears to be OUT-OF-FOCUS (|mean| > 0.15 pix) COLLIMATE: Predict (red) piston movement of -7652 steps for spectro-1 COLLIMATE: Issue SOP command: "sp1; mechPiston -7652" COLLIMATE: Camera b2 appears to be OUT-OF-FOCUS (|mean| > 0.15 pix) COLLIMATE: Predict blue camera ring movement of 28.1 degrees for spectro-2 COLLIMATE: (if red is already in focus) COLLIMATE: Camera r2 appears to be OUT-OF-FOCUS (|mean| > 0.15 pix) COLLIMATE: Predict (red) piston movement of -7522 steps for spectro-2 COLLIMATE: Issue SOP command: "sp2; mechPiston -7522" New positions: sp1: Coll_motor_A -7652 Coll_motor_B -7652 Coll_motor_C -7653 sp2: Coll_motor_A 3907 Coll_motor_B 3907 Coll_motor_C 3908