Date: Mon, 25 Oct 2021 14:34:42 -0600 Subject: Re: [sloan-25mlog 5707] 2.5m obslog 20211023 (SJD 59511) From: Shane Thomas This is a multi-part message in MIME format. --------------fpYeffFcDNMFDXFo8IdVZPFY Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Okay, this has been changed in /home/sdss5/software/tron/main/tron/config/apo.json from sdss5-tcc for host to sdss4-tcc for host. I guess some reset is needed. Shane On 10/25/2021 1:01 PM, Conor Sayres wrote: > Hi shane. That is tron. Which runs on sdss5-hub > > -Conor > >> On Oct 25, 2021, at 2:59 PM, Shane Thomas wrote: >> >>  >> >> So I am trying to unravel what is going on here.  Though when my name >> was mentioned it seems to edit a .json file and replace: >> >> >> "tcc": { >> >> "host": "sdss5-tcc", >> >> "port": 2500, >> >> "actorName": "tcc" >> >> }, >> >> >> >> With >> >> "tcc": { >> >> "host": "sdss4-tcc", >> >> "port": 2500, >> >> "actorName": "tcc" >> >> }, >> >> >> Then someone restarts something somewhere?  I am just not sure what >> machine this is on, on the current sdss5-tcc this file? >> >> >> On 10/25/2021 8:19 AM, Conor Sayres wrote: >>> Hi Kaike, >>> >>> You could try that, it could be a good check.  You’ll need to make >>> sure that the tcc and mirrorCtrls are killed on sdss5-tcc.  And >>> you’ll need to modify the TCC Nub in tron to point to the >>> sdss4-machine (and restart tron). >>> >>> Both José and I are traveling today so we likely won’t be much help. >>>  But I think this is the file you (or Shane?) need to modify locally >>> from host: “sdss5-tcc” to host: “sdss4-tcc”. >>> >>> https://github.com/sdss/tron/blob/main/tron/config/apo.json >>> >>> >>> >>>> On Oct 25, 2021, at 9:40 AM, Kaike wrote: >>>> >>>> Hi Russet, >>>> >>>>  Thanks for the information. We are used engineering camera. All >>>> information is in one file for us. I double checked and confirmed >>>> all information is updated properly. >>>> >>>>   Conor, I will do more research today. If nothing is found, can we >>>> test the things on sdss4-tcc? >>>> i..e run the tcc on sdss4-tcc to see if we see the same shift >>>> between track pterr and track RA, Dec? >>>> >>>> >>>>> On Oct 24, 2021, at 7:13 PM, Russet McMillan >>>>> wrote: >>>>> >>>>> By any chance, is the instrument set to something other than the >>>>> guide camera?  tcc track RA, Dec would try to center the star on >>>>> the primary instrument, the one used in set inst= and the one >>>>> displayed by "tcc show block inst."  But tcc track/pterr tries to >>>>> center the star on the designated guider.  So if the instrument is >>>>> not explicitly set to the guider, you would get different pointing >>>>> results for those two commands. >>>>> >>>>> Additionally, when you do an instrument block for the guider you >>>>> must be sure to update TWO files, both the i_blahblahblah file for >>>>> the guider as an instrument, and also the ip_blahblahblah file for >>>>> the guider as guider.  Make sure those files agree with each >>>>> other.  A discrepancy between those two files could produce the >>>>> same result, even if you have the instrument set to the guider. >>>>>  In that case the tcc track RA, Dec command would center the star >>>>> as described in the i_blahblahblah file, and the tcc track/pterr >>>>> command would center the star as described in the ip_blahblahblah >>>>> file. >>>>> >>>>> For the 3.5m, the two files are i_na2_guider.dat and ip_na2.dat , >>>>> but you must have different port and instrument names. >>>>> >>>>>> On Oct 24, 2021, at 6:07 PM, Kaike wrote: >>>>>> >>>>>> Thanks Russet. >>>>>> >>>>>> The pointing is great and can be repeated. Here is puzzling things: >>>>>> >>>>>> with "tcc track/pterr 120,60 obs/rotty=obj/rota=0 >>>>>> /magRange=(10,10.5)” command, the telescope is slewed to a star >>>>>> that is closest to AZ=120 deg, alt=60 in the magnitude range of >>>>>> 10.0 to 10.5 in the star category, and star is centered on the >>>>>> CCD. Once the telescope is in the field, Telescope Status window >>>>>> shows RA and Dec of the field, If we use “tcc track RA, Dec” slew >>>>>> the telescope to the same star, star images on the CCD move about >>>>>> 30 arc-seconds while we expect it should not move at all. The >>>>>> weird things is: >>>>>> >>>>>> Ra and Dec in two fits headers are similar (within 0.1 >>>>>> arc-second) but image displacement on CCD is 30 arc-seconds. >>>>>> >>>>>> One possible explanation I could think of: >>>>>> >>>>>> Fit header records RA/Dec in tcc track command without epoch >>>>>> information. Tcc track commands use Ra/Dec coordinates at 2000, >>>>>> but STUI display RA/Dec at the current date. We will test it tonight. >>>>>> >>>>>> -Kaike >>>>>> >>>>>>> On Oct 24, 2021, at 5:42 PM, Russet McMillan >>>>>>> wrote: >>>>>>> >>>>>>> If I found a big pointing discrepancy AFTER a pointing model, I >>>>>>> would first look at the offsets.  A large calib or guide offset >>>>>>> could cause what you describe, with the displayed RA/Dec not >>>>>>> matching where you are on sky.  Large calib offsets may be >>>>>>> needed to obtain pointing model data, but then once the pointing >>>>>>> model is implemented you have to clear the calib offset by hand. >>>>>>> >>>>>>> If the offsets are not to blame, I would look more carefully at >>>>>>> the pointing model, see if it was really trustworthy and reduced >>>>>>> correctly.  Was there a pointing check right after the model was >>>>>>> implemented?  If the after-model check was good and then the >>>>>>> pointing changed later, then you know the model is not to blame. >>>>>>>  But if there was a problem starting right after the model was >>>>>>> implemented, then it probably is the source of the problem. >>>>>>> >>>>>>> And if those things were ruled out, then I would probably start >>>>>>> worrying that a mirror is out of place.  But since you folks do >>>>>>> not have a flat mirror like our M3 (which only affects pointing >>>>>>> without affecting collimation), I guess if one of your mirrors >>>>>>> was off there should be a clear effect on image quality? >>>>>>> >>>>>>> For problems with a pointing model, the tricky spots where it's >>>>>>> easy to make a mistake are 1) When taking the grid data, make >>>>>>> sure that the rotation is zero obj.  2) When taking the grid, >>>>>>> make sure the offsets are Boresight type.  3) Make sure all >>>>>>> offsets and measured positions match up.  4) After measuring the >>>>>>> grid and before measuring the ring, make sure the Boresight >>>>>>> offset is returned to zero. >>>>>>> >>>>>>> Maybe one of those things will help? >>>>>>> >>>>>>> >>>>>>>> On Oct 24, 2021, at 4:42 PM, Conor Sayres wrote: >>>>>>>> >>>>>>>> Hi Kaike, All, >>>>>>>> >>>>>>>> It’s a little hard for me to understand the >>>>>>>> weirdness/unexpected behavior you guys saw (and I’m not a >>>>>>>> practiced instrument blocker).  I wonder if you’ve run what you >>>>>>>> saw by Russet?  She would be the first person I’d ask when >>>>>>>> understanding discrepancies like this. >>>>>>>> >>>>>>>> Russell did alert me years ago about a problem with ICRS >>>>>>>> coordinate transforms for the TCC, but I think we decided it >>>>>>>> was at the miliarcsecond level, and that’s probably bigger than >>>>>>>> you guys are seeing? >>>>>>>> >>>>>>>> The display of coordinate in STUI is *approximate* in that its >>>>>>>> only output so often (every several seconds?).  Certainly I >>>>>>>> wouldn’t trust STUI as a precision, realtime readout of where >>>>>>>> the telescope actually is... >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> On Oct 24, 2021, at 10:13 AM, Kaike wrote: >>>>>>>>> >>>>>>>>> Thanks to Dan and Karen for the detailed information. >>>>>>>>> >>>>>>>>> Jose and Conor: Is it possible that  the actual RA/Dec and >>>>>>>>> displayed Ra/Dec  in STUI status are off? e.g. one is in 2000, >>>>>>>>> one is in current date? >>>>>>>>> >>>>>>>>> Audrey and Karen: Let’s run a couple of tests tonight. Slew to >>>>>>>>> stars in star catalog with "tcc track ra, dec” command and see >>>>>>>>> the same RA, Dec are displayed in the STUI status window and >>>>>>>>> whether the star is centered on the engcam CCD.  I will log in >>>>>>>>> at about 7:00 PM or so. >>>>>>>>> >>>>>>>>> >>>>>>>>>> On Oct 24, 2021, at 5:04 AM, doravetz@apo.nmsu.edu wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>                 APACHE POINT OBSERVATORY SDSS 2.5M >>>>>>>>>> >>>>>>>>>>                           OBSERVING LOG >>>>>>>>>>                    Saturday October 23, 2021 >>>>>>>>>> >>>>>>>>>>                            (SJD 59511) >>>>>>>>>> >>>>>>>>>> ----  Observing Team ---- >>>>>>>>>> >>>>>>>>>> Dan Oravetz >>>>>>>>>> Karen Kinemuchi (R) >>>>>>>>>> Dmitry Bizyaev (phone help) >>>>>>>>>> >>>>>>>>>> ---- Observing Plan ---- >>>>>>>>>> >>>>>>>>>> Another go at a pointing model following some recent updates. >>>>>>>>>> >>>>>>>>>> ---- Observing Summary ---- >>>>>>>>>> >>>>>>>>>> We completed some of the usual pre-pointing model steps -- >>>>>>>>>> home the engCam stage, home/relax mirrors, setup engCam, >>>>>>>>>> collected grid data and partially updated instrument block >>>>>>>>>> after fitting the grid data. Had some strange behavior with >>>>>>>>>> unexplained offsets before trying to get ring data, though. >>>>>>>>>> See Log for details. For now, i_ca1_engcam.dat is only >>>>>>>>>> PARTIALLY updated - it's been updated following the fit of >>>>>>>>>> the grid data, but that's as far as we got. >>>>>>>>>> >>>>>>>>>> We saved new Nominal MIGs after the home/relax procedure. >>>>>>>>>> >>>>>>>>>> We've still been getting apogeeql.heartbeat alerts when >>>>>>>>>> exposures are running, but the alert is disabled currently. >>>>>>>>>> >>>>>>>>>> The IRSC page went down around 10pm local time or so with a >>>>>>>>>> 503 Service Unavailable error. The irsc.apo.nmsu.edu >>>>>>>>>> domain pings fine and the disk >>>>>>>>>> space doesn't appear to be a problem. Candace called Shane >>>>>>>>>> and he will try to look into it, but it's still down as of >>>>>>>>>> sending the night log out. >>>>>>>>>> >>>>>>>>>> The connection to igor.apo.nmsu.edu >>>>>>>>>> failed. Candace tried to connect >>>>>>>>>> and it failed from the 3.5m control room, too. >>>>>>>>>> >>>>>>>>>> We ran into some trouble fitting instrument-block data with >>>>>>>>>> the IDL scripts Dmitry wrote. The 'IGOR' directory was >>>>>>>>>> altogether not present in observer@sdss5-bhm and the >>>>>>>>>> fit_instrument_data3 script wasn't found at first either. >>>>>>>>>> Dmitry noted that "it turned out that [at least observers' >>>>>>>>>> directories on] sdss5-bhm and sdss5-hub are linked to be the >>>>>>>>>> same: if a file or directory is removed from sdss5-hub, same >>>>>>>>>> happens on sdss5-bhm." He was able to copy the relevant files >>>>>>>>>> from a different machine back to the observer directory on >>>>>>>>>> sdss5-bhm and then the fitting script worked again. >>>>>>>>>> >>>>>>>>>> The engCam needed to be power-cycled for some unexplained >>>>>>>>>> reason after it died abruptly. >>>>>>>>>> >>>>>>>>>> ---- Observing Log ---- >>>>>>>>>> >>>>>>>>>> ============================================================================ >>>>>>>>>>                         TELESCOPE CHECKOUT >>>>>>>>>> ============================================================================ >>>>>>>>>> >>>>>>>>>> 19:00Z - All systems alive and responsive upon arrival. >>>>>>>>>> >>>>>>>>>> No outstanding apogeeql critical alerts and the morning cals >>>>>>>>>> from this morning >>>>>>>>>> look OK. We started an early set of evening cals to see if the >>>>>>>>>> apogeeql.heartbeat alerts would start spawning again and they >>>>>>>>>> have been. So far >>>>>>>>>> the cals themselves are fine and look fine on disk (unlike >>>>>>>>>> yesterday's evening >>>>>>>>>> cals in which some images were missing). Also, the morning >>>>>>>>>> cals look fine from >>>>>>>>>> this morning, too. These alerts just seem to be spawning when >>>>>>>>>> exposures are running. >>>>>>>>>> >>>>>>>>>> JohnD pushed-through a fix that will actually keep alerts >>>>>>>>>> disabled (hopefully). >>>>>>>>>> We have disabled the apogeeql.heartbeat alert for now. >>>>>>>>>> >>>>>>>>>> 00:04Z - Started ventilation. Partly cloudy and a little windy. >>>>>>>>>> >>>>>>>>>> ============================================================================ >>>>>>>>>>                              NIGHT >>>>>>>>>> ============================================================================ >>>>>>>>>> >>>>>>>>>> 00:35Z - Homed engCam stage. Force-filled BOSS before moving >>>>>>>>>> the telescope to ALT=70 for home/relax mirrors. >>>>>>>>>> >>>>>>>>>> ****************** >>>>>>>>>> Home/Relax Mirrors >>>>>>>>>> ****************** >>>>>>>>>> >>>>>>>>>> == >>>>>>>>>> M1 >>>>>>>>>> == >>>>>>>>>> actMount=12500.02,-1600.00,5299.99,47050.00,-8800.00,-8400.00; >>>>>>>>>> cmdMount=12500.00,-1600.00,5300.00,47050.00,-8800.00,-8400.00 >>>>>>>>>> desOrient=0.00,-59.50,-9.15,-512.00,1906.30 >>>>>>>>>> >>>>>>>>>> home E,F: >>>>>>>>>> >>>>>>>>>> position error", "999999999, 999999999, 999999999, 999999999, >>>>>>>>>> 000000000, 000000000" >>>>>>>>>> >>>>>>>>>> home D: >>>>>>>>>> >>>>>>>>>> "position error", "999999999, 999999999, 999999999, >>>>>>>>>> 000000000, 999999999, 999999999" >>>>>>>>>> >>>>>>>>>> home A,B,C: >>>>>>>>>> >>>>>>>>>> "position error", "000000000, 000000000, 000000000, >>>>>>>>>> 999999999, 999999999, 999999999" >>>>>>>>>> >>>>>>>>>> == >>>>>>>>>> M2 >>>>>>>>>> == >>>>>>>>>> home D: >>>>>>>>>> >>>>>>>>>> "position error", "999999999, 999999999, 999999999, >>>>>>>>>> 000000000, 999999999" >>>>>>>>>> >>>>>>>>>> home E: >>>>>>>>>> >>>>>>>>>> "position error", "999999999, 999999999, 999999999, >>>>>>>>>> 999999999, 000000000" >>>>>>>>>> >>>>>>>>>> home A,B,C: >>>>>>>>>> >>>>>>>>>> "position error", "-000000184, -000000127, -000000033, >>>>>>>>>> 999999999, 999999999" >>>>>>>>>> >>>>>>>>>> Saved new nominals MIGs (see Mirror Numbers). >>>>>>>>>> >>>>>>>>>> 04:04Z - Cloudy. Wind picking up more. >>>>>>>>>> >>>>>>>>>> 05:14Z - Started APOGEE morning cals early so we could >>>>>>>>>> respond to any alerts. >>>>>>>>>> >>>>>>>>>> 06:15Z - Opened. Partly cloudy. Clouds are on the way, but we >>>>>>>>>> hope to get data for the instrument-block update in this hole >>>>>>>>>> before the clouds get too bad. >>>>>>>>>> >>>>>>>>>> 06:21Z - Focused engCam. >>>>>>>>>> >>>>>>>>>> --- FocusLoop --2021-10-24 06:20:14 >>>>>>>>>> current focus=0.0 >>>>>>>>>> 0  foc=-60  fwhm=3.849000  /data/ecam/59511/gimg-0005.fits >>>>>>>>>> 1  foc=-40  fwhm=3.282000  /data/ecam/59511/gimg-0006.fits >>>>>>>>>> 2  foc=-20  fwhm=3.233000  /data/ecam/59511/gimg-0007.fits >>>>>>>>>> 3  foc=0  fwhm=3.006000  /data/ecam/59511/gimg-0008.fits >>>>>>>>>> 4  foc=20  fwhm=3.865000  /data/ecam/59511/gimg-0009.fits >>>>>>>>>> 5  foc=40  fwhm=3.651000  /data/ecam/59511/gimg-0010.fits >>>>>>>>>> 6  foc=60  fwhm=4.600000  /data/ecam/59511/gimg-0011.fits >>>>>>>>>> set focus  0.0 >>>>>>>>>> done >>>>>>>>>> >>>>>>>>>> ******************************* >>>>>>>>>> Grid/Ring Instrument Block Data >>>>>>>>>> ******************************* >>>>>>>>>> >>>>>>>>>> 06:22Z - All telescope offsets are zero. Started grid data >>>>>>>>>> with gimg-0012. The seeing wasn't very good during the data >>>>>>>>>> collection. >>>>>>>>>> >>>>>>>>>> Called Dmitry for help with the IGOR-replacement IDL scripts >>>>>>>>>> since things were missing on sdss5-bhm. >>>>>>>>>> >>>>>>>>>> 07:39Z - The seeing is considerably better now. Started >>>>>>>>>> another set of grid data with gimg-0102. Seeing ~1.2" fwhm. >>>>>>>>>> >>>>>>>>>> Fit Grid Data: >>>>>>>>>> >>>>>>>>>> Type of Data:   Instrument >>>>>>>>>> Bin Factor                   1. X= 2           2. Y= 2 >>>>>>>>>> >>>>>>>>>> IIm_Ctr,unbinned pix         3. x=  512.0      4. y= 512.0 >>>>>>>>>> IIm_Sca,unbinned pix/deg     5. x= -16874.8    6. y= 16820.1 >>>>>>>>>> Aspect ratio is exact?       7. [Yes] >>>>>>>>>> Old Rot_inst_ang, deg        8.  -90.14 >>>>>>>>>> New Rot_inst_ang, deg            -90.08 >>>>>>>>>> >>>>>>>>>> == s. Now you can hit s to Fit Scale & Orientation == >>>>>>>>>> >>>>>>>>>> Old Rot_inst_xy, deg on sky  9. X =-0.004450   0. Y= 0.001323 >>>>>>>>>> New Rot_inst_xy, deg on sky     X =-0.005350      Y= 0.001900 >>>>>>>>>> >>>>>>>>>> If this instrument is also a full-frame guider >>>>>>>>>> (the whole CCD is one probe), e.g. 3.5m NA2 guider, then... >>>>>>>>>> New GP_rot_xy, deg on sky    g. 0.004724       h.  Y= 0.003895 >>>>>>>>>> >>>>>>>>>> == p. Now you can hit p to Fit Position == >>>>>>>>>>     r=Read last saved set, w=Write this set, x=eXit >>>>>>>>>>     s=Fit Scale & Orientation  p=Fit Position >>>>>>>>>> => Finished running Fit Scale & Orientation >>>>>>>>>> Mean fit error X Y, =  -0.000+/-   1.268   -0.000+/-   0.971 >>>>>>>>>> unbined pix >>>>>>>>>> Make your choice: 0 ..to.. 9 or g h s p r w x >>>>>>>>>> >>>>>>>>>> Updated IIm_Sca (x and y) and Rot_inst_ang in the >>>>>>>>>> ca_1_engcam.dat file on >>>>>>>>>> sdss5-tcc:/home/sdss5/software/tccdata/master/inst. >>>>>>>>>> >>>>>>>>>> We wanted to collect ring data, but were having problems with >>>>>>>>>> the dec offset at the beginning of the test. The instructions >>>>>>>>>> say: >>>>>>>>>> >>>>>>>>>> "Adjust the declination (Y) 10-30 arcseconds so the star >>>>>>>>>> image will locate at 1/3 to 1/2 of the way from the center >>>>>>>>>> (512,512) to the edge of the chip (512,1024), i.e. Y at about >>>>>>>>>> pixel 700. Find the current (RA, Dec) from STUI status >>>>>>>>>> window, slew the telescope with the command tcc track ra,dec >>>>>>>>>> /keep=(gcorr,arc) fk5 by adding or subtracting 10 to 30 >>>>>>>>>> arcseconds in Dec so that image will locate at Y=700 or so." >>>>>>>>>> >>>>>>>>>> After we slewed to a star, it would be centered quite well to >>>>>>>>>> begin with. Then we add 30 arcseconds to the target Dec and >>>>>>>>>> re-slew but the star would move mostly to the left in the >>>>>>>>>> image. It was bizarre. We repeated this several times and >>>>>>>>>> each time our intended Dec offset in the target Dec was not >>>>>>>>>> seen in the image, but the star was offset to the left >>>>>>>>>> instead. Even more strange, any subsequent adjustments to the >>>>>>>>>> target Dec actually did work as seen in y-pixel shifts of the >>>>>>>>>> stars in the image, but the star remained off to the left in >>>>>>>>>> the image. >>>>>>>>>> >>>>>>>>>> We tried this instead: slew to a star using a command like this: >>>>>>>>>> tcc track/pterr 120,60 obs/rotty=obj/rota=0 /magRange=(10,10.5) >>>>>>>>>> >>>>>>>>>> Then, take an image. I.e., in gimg-0223 the star is >>>>>>>>>> reasonably well centered. Next, take the RA, Dec in the STUI >>>>>>>>>> Status window and slew to that location. We specified >>>>>>>>>> everything exactly as indicated in the Status window >>>>>>>>>> including ICRS. The expectation is the star shouldn't move >>>>>>>>>> because we're slewing to the same ra/dec we're already at. >>>>>>>>>> Instead, the star moves left as seen in gimg-0224. >>>>>>>>>> >>>>>>>>>> We reverted the engCam instrument block file to the old one >>>>>>>>>> and repeated the above test and had the same problem: >>>>>>>>>> gimg-0225 the star is centered, gimg-0226 the star moved left >>>>>>>>>> after we issued a slew to the ra,dec we were already pointing at. >>>>>>>>>> >>>>>>>>>> In all cases we verified no offsets were in place (boresight, >>>>>>>>>> calib, arc, guide) for any of the images. >>>>>>>>>> >>>>>>>>>> Currently, i_ca1_engcam.dat is the PARTIALLY UPDATED file - >>>>>>>>>> the one that was updated after the grid fit tonight, but >>>>>>>>>> hasn't been updated after fitting the ring data since we >>>>>>>>>> didn't get that far. i_ca1_engcam.dat.OLD is the instrument >>>>>>>>>> block data BEFORE tonight's grid fit. >>>>>>>>>> >>>>>>>>>> 09:55Z - engCam died for no apparent reason: >>>>>>>>>> >>>>>>>>>> 09:55:19 APO.doravetz.guider 849 ecamera f text=\"command >>>>>>>>>> failed: RuntimeError('bad imaging state=3; please try gcamera >>>>>>>>>> reconnect before restarting the ICC',) at >>>>>>>>>> /home/sdss5/software/gcameraICC/main/python/gcameraICC/alta/altacam.py:242\" >>>>>>>>>> >>>>>>>>>> ecamera actor was still responsive, though, and software >>>>>>>>>> attempts to bring it back failed. >>>>>>>>>> >>>>>>>>>> 10:05Z - Power-cycled engCam and then reconnected and engCam >>>>>>>>>> was back to being responsive. >>>>>>>>>> >>>>>>>>>> 10:58Z - Closed. >>>>>>>>>> >>>>>>>>>> ---- Mirror Numbers ---- >>>>>>>>>> >>>>>>>>>> Mirror numbers from afternoon checkout: >>>>>>>>>> >>>>>>>>>> PRIMARY: >>>>>>>>>> -------- >>>>>>>>>> Scale: 1.000000 >>>>>>>>>> >>>>>>>>>> MIGSTONIGHTNOMINAL >>>>>>>>>> Axial A:0.01200.0120 >>>>>>>>>> Axial B:0.03700.0360 >>>>>>>>>> Axial C:-0.1220-0.1170 >>>>>>>>>> Trans D:-0.0364-0.0366 >>>>>>>>>> Lateral E:0.33500.3515 >>>>>>>>>> Lateral F:0.53750.5415 >>>>>>>>>> >>>>>>>>>> GALILS >>>>>>>>>> Commanded:  12500 -1600 5300 47050 -8800 -8400 >>>>>>>>>> Actual:     12500 -1600 5300 47050 -8800 -8400 >>>>>>>>>> >>>>>>>>>> SETMIR VALUES >>>>>>>>>> PrimDesOrient: 0.0 -59.5 -9.15 -512.0 1906.3 >>>>>>>>>> PrimOrient:    1.07 -59.51 -9.21 -512.13 1906.31 >>>>>>>>>> >>>>>>>>>> SECONDARY: >>>>>>>>>> ---------- >>>>>>>>>> >>>>>>>>>> Focus:      0.0000 >>>>>>>>>> Air temp:    13.11 >>>>>>>>>> Altitude:   29.999996178438877 >>>>>>>>>> >>>>>>>>>> MIGSTONIGHTNOMINAL >>>>>>>>>> Axial A:-9.4510-9.4540 >>>>>>>>>> Axial B:-9.4610-9.4680 >>>>>>>>>> Axial C:-9.4970-9.4970 >>>>>>>>>> Trans D:0.09300.0980 >>>>>>>>>> >>>>>>>>>> GALILS >>>>>>>>>> Commanded: 4628800 4623100 4647200 -50 -3450 >>>>>>>>>> Actual:    4607306 4607237 4607350 -50 -3450 >>>>>>>>>> >>>>>>>>>> SETMIR VALUES >>>>>>>>>> SecDesOrient: 3657.0 0.0 0.0 0.0 42.22 >>>>>>>>>> SecOrient:    3657.04 -0.03 -0.02 -0.01 42.71 >>>>>>>>>> Mirror numbers after home/relax: >>>>>>>>>> >>>>>>>>>> PRIMARY: >>>>>>>>>> -------- >>>>>>>>>> Scale: 1.000000 >>>>>>>>>> >>>>>>>>>> MIGSTONIGHTNOMINAL >>>>>>>>>> Axial A:0.00400.0120 >>>>>>>>>> Axial B:0.03100.0360 >>>>>>>>>> Axial C:-0.1180-0.1170 >>>>>>>>>> Trans D:-0.0362-0.0366 >>>>>>>>>> Lateral E:0.33150.3515 >>>>>>>>>> Lateral F:0.53400.5415 >>>>>>>>>> >>>>>>>>>> GALILS >>>>>>>>>> Commanded:  12500 -1600 5300 47050 -8800 -8400 >>>>>>>>>> Actual:     12500 -1600 5300 47050 -8800 -8400 >>>>>>>>>> >>>>>>>>>> SETMIR VALUES >>>>>>>>>> PrimDesOrient: 0.0 -59.5 -9.15 -512.0 1906.3 >>>>>>>>>> PrimOrient:    1.07 -59.51 -9.21 -512.13 1906.31 >>>>>>>>>> >>>>>>>>>> SECONDARY: >>>>>>>>>> ---------- >>>>>>>>>> >>>>>>>>>> Focus:      0.0000 >>>>>>>>>> Air temp:     8.61 >>>>>>>>>> Altitude:   29.999996178438877 >>>>>>>>>> >>>>>>>>>> MIGSTONIGHTNOMINAL >>>>>>>>>> Axial A:-9.4440-9.4540 >>>>>>>>>> Axial B:-9.4730-9.4680 >>>>>>>>>> Axial C:-9.5010-9.4970 >>>>>>>>>> Trans D:0.10000.0980 >>>>>>>>>> >>>>>>>>>> GALILS >>>>>>>>>> Commanded: 4632700 4629650 4648300 -50 -3450 >>>>>>>>>> Actual:    4607306 4607224 4607199 -50 -3450 >>>>>>>>>> >>>>>>>>>> SETMIR VALUES >>>>>>>>>> SecDesOrient: 3657.0 0.0 0.0 0.0 42.22 >>>>>>>>>> SecOrient:    3657.0 0.02 -0.03 -0.02 42.67 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Mirror numbers after home/relax after saving new NOMINAL values: >>>>>>>>>> >>>>>>>>>> PRIMARY: >>>>>>>>>> -------- >>>>>>>>>> Scale: 1.000000 >>>>>>>>>> >>>>>>>>>> MIGSTONIGHTNOMINAL >>>>>>>>>> Axial A:0.00400.0040 >>>>>>>>>> Axial B:0.03100.0310 >>>>>>>>>> Axial C:-0.1180-0.1180 >>>>>>>>>> Trans D:-0.0362-0.0362 >>>>>>>>>> Lateral E:0.33150.3315 >>>>>>>>>> Lateral F:0.53400.5340 >>>>>>>>>> >>>>>>>>>> GALILS >>>>>>>>>> Commanded:  12500 -1600 5300 47050 -8800 -8400 >>>>>>>>>> Actual:     12500 -1600 5300 47050 -8800 -8400 >>>>>>>>>> >>>>>>>>>> SETMIR VALUES >>>>>>>>>> PrimDesOrient: 0.0 -59.5 -9.15 -512.0 1906.3 >>>>>>>>>> PrimOrient:    1.07 -59.51 -9.21 -512.13 1906.31 >>>>>>>>>> >>>>>>>>>> SECONDARY: >>>>>>>>>> ---------- >>>>>>>>>> >>>>>>>>>> Focus:      0.0000 >>>>>>>>>> Air temp:     8.61 >>>>>>>>>> Altitude:   29.999996178438877 >>>>>>>>>> >>>>>>>>>> MIGSTONIGHTNOMINAL >>>>>>>>>> Axial A:-9.4440-9.4440 >>>>>>>>>> Axial B:-9.4730-9.4730 >>>>>>>>>> Axial C:-9.5010-9.5010 >>>>>>>>>> Trans D:0.10000.1000 >>>>>>>>>> >>>>>>>>>> GALILS >>>>>>>>>> Commanded: 4632700 4629650 4648300 -50 -3450 >>>>>>>>>> Actual:    4607306 4607237 4607193 -50 -3450 >>>>>>>>>> >>>>>>>>>> SETMIR VALUES >>>>>>>>>> SecDesOrient: 3657.0 0.0 0.0 0.0 42.22 >>>>>>>>>> SecOrient:    3657.02 0.03 -0.01 -0.01 42.66 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> ---- Telescope Status ---- >>>>>>>>>> >>>>>>>>>> Status at close: >>>>>>>>>> >>>>>>>>>> Telescope stowed at:    121.0, 30.0, 0.0 mount >>>>>>>>>> Instrument mounted:     engCam >>>>>>>>>> Counterweights at:      423 425 444 443 >>>>>>>>>> LN2 autofill systems:   Connected and turned on >>>>>>>>>> 180L LN2 dewar scales:  SP1 125 lbs, 24 psi >>>>>>>>>> >>>>>>>>>> ---- Software Used ---- >>>>>>>>>> >>>>>>>>>> --- Disk Space --- >>>>>>>>>> /dev/sdb1                2.0T   94G  2.0T   5% /home >>>>>>>>>> 10.25.1.230:/data         21T   15T  5.5T  73% /data >>>>>>>>>> >>>>>>>>>> --- Software Versions --- >>>>>>>>>> STUI          : 1.7.13 >>>>>>>>>> alerts        : 2.1.6 >>>>>>>>>> apo           : 3.0.0 >>>>>>>>>> boss          : 6.0.1-alpha.0 >>>>>>>>>> -boss.specMec : 3.0.4 >>>>>>>>>> guider        : 4.0.0 >>>>>>>>>> ecamera       : 2.3.0 >>>>>>>>>> fliswarm      : FAILED >>>>>>>>>> hartmann      : FAILED >>>>>>>>>> hub           : 5.0.0a0 >>>>>>>>>> mcp           : 2.1 >>>>>>>>>> -mcp.plc      : 34 >>>>>>>>>> -mcp.azFiduci : v1_147 >>>>>>>>>> -mcp.altFiduc : v1_147 >>>>>>>>>> -mcp.rotFiduc : v1_147 >>>>>>>>>> sop           : 0.1.0-alpha.0 >>>>>>>>>> tcc           : 1.4.0 >>>>>>>>>> apogee        : not available >>>>>>>>>> apogeecal     : not available >>>>>>>>>> apogeeql      : v1_7_0dev >>>>>>>>>> STUIAdditions : 3.1.9 >>>>>>>>>> >>>>>>>>>> ---- APOGEE Data Summary ---- >>>>>>>>>> >>>>>>>>>> 59510 morning cals: >>>>>>>>>> >>>>>>>>>> APOGEE data list,   mjd=59510,  morning >>>>>>>>>> raw_data:  /data/apogee/utr_cdr/59510/apRaw-*.fits >>>>>>>>>> archive:  /data/apogee/archive/59510/apR-[a,b,c]-*.apz >>>>>>>>>> quickred:  /data/apogee/quickred/59510/ap2D-a-*.fits.fz >>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>> >>>>>>>>>> mjd   i   UT   File/Exp  Imtype Nread A/B Dth  Ct-Plate Arch >>>>>>>>>> Offset %Flux Comm >>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>> 59510  10 10:14  39480010    Dark   60  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59510  11 10:25  39480011    Dark   60  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59510  12 10:35  39480012    Dark   60  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59510  13 10:37  39480013  QuarFlat 10  A  13.0  ------- >>>>>>>>>>  a-b-c    -   98 >>>>>>>>>> 59510  14 10:39  39480014  QuarFlat 10  A  13.0  ------- >>>>>>>>>>  a-b-c    -   99 >>>>>>>>>> 59510  15 10:41  39480015  QuarFlat 10  A  13.0  ------- >>>>>>>>>>  a-b-c    -   99 >>>>>>>>>> 59510  16 10:43  39480016  Arc----  12  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59510  17 10:45  39480017  Arc----  12  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59510  18 10:52  39480018  Arc----  40  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59510  19 10:59  39480019  Arc----  40  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59510  20 11:05  39480020    Dark   30  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59510  21 11:10  39480021  InteFlat 30  A  13.0  ------- >>>>>>>>>>  a-b-c    -  280 >>>>>>>>>> 59510  22 11:16  39480022  InteFlat 30  A  13.0  ------- >>>>>>>>>>  a-b-c    -  280 >>>>>>>>>> 59510  23 11:21  39480023  InteFlat 30  A  13.0  ------- >>>>>>>>>>  a-b-c    -  280 >>>>>>>>>> 59510  24 11:26  39480024    Dark   30  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>> >>>>>>>>>> APOGEE data list,   mjd=59511,  all >>>>>>>>>> raw_data:  /data/apogee/utr_cdr/59511/apRaw-*.fits >>>>>>>>>> archive:  /data/apogee/archive/59511/apR-[a,b,c]-*.apz >>>>>>>>>> quickred:  /data/apogee/quickred/59511/ap2D-a-*.fits.fz >>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>> >>>>>>>>>> mjd   i   UT   File/Exp  Imtype Nread A/B Dth  Ct-Plate Arch >>>>>>>>>> Offset %Flux Comm >>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>> 59511   1 18:54  39490001    Dark    3  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59511   2 19:09  39490002    Dark   60  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59511   3 19:11  39490003  QuarFlat 10  A  13.0  ------- >>>>>>>>>>  a-b-c    -   98 >>>>>>>>>> 59511   4 19:13  39490004  Arc----  12  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59511   5 19:16  39490005  Arc----  12  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59511   6 19:23  39490006  Arc----  40  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59511   7 19:30  39490007  Arc----  40  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59511   8 19:41  39490008    Dark   60  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59511   9 20:08  39490009  Arc----  30  A  13.0  ------- >>>>>>>>>>  a-b-c    -   -   FPI >>>>>>>>>> 59511  10 05:24  39490010    Dark   60  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59511  11 05:34  39490011    Dark   60  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59511  12 05:45  39490012    Dark   60  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59511  13 05:47  39490013  QuarFlat 10  A  13.0  ------- >>>>>>>>>>  a-b-c    -   98 >>>>>>>>>> 59511  14 05:49  39490014  QuarFlat 10  A  13.0  ------- >>>>>>>>>>  a-b-c    -   98 >>>>>>>>>> 59511  15 05:51  39490015  QuarFlat 10  A  13.0  ------- >>>>>>>>>>  a-b-c    -   99 >>>>>>>>>> 59511  16 05:53  39490016  Arc----  12  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59511  17 05:55  39490017  Arc----  12  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59511  18 06:02  39490018  Arc----  40  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59511  19 06:09  39490019  Arc----  40  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59511  20 06:15  39490020    Dark   30  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> 59511  21 06:20  39490021  InteFlat 30  A  13.0  ------- >>>>>>>>>>  a-b-c    -  280 >>>>>>>>>> 59511  22 06:25  39490022  InteFlat 30  A  13.0  ------- >>>>>>>>>>  a-b-c    -  280 >>>>>>>>>> 59511  23 06:31  39490023  InteFlat 30  A  13.0  ------- >>>>>>>>>>  a-b-c    -  280 >>>>>>>>>> 59511  24 06:36  39490024    Dark   30  A  13.0  ------- >>>>>>>>>>  a-b-c    -   - >>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> ---- Weather Log ---- >>>>>>>>>> >>>>>>>>>> Wind1 umDIMMIRSC >>>>>>>>>> TimeTemp CDewp CMPHDirDustfwhmmeansigma >>>>>>>>>> >>>>>>>>>> 18:0013.3-0.418.1194.6675 >>>>>>>>>> 18:1512.1-0.219.9217.3701 >>>>>>>>>> 18:3012.9-0.227.0252.1755 >>>>>>>>>> 18:4512.0-0.920.7265.0710 >>>>>>>>>> 19:0015.4-0.723.6240.5680 >>>>>>>>>> 19:1514.2-1.321.6265.6698 >>>>>>>>>> 19:3013.4-1.813.9253.1685 >>>>>>>>>> 19:4512.9-1.820.5223.4653 >>>>>>>>>> 20:0012.2-2.917.9258.3646 >>>>>>>>>> 20:1512.3-3.115.0229.2611 >>>>>>>>>> 20:3014.1-2.112.8233.1701 >>>>>>>>>> 20:4512.2-3.019.8245.5732 >>>>>>>>>> 21:0012.3-2.615.3256.1816 >>>>>>>>>> 21:1513.5-3.316.9261.7688 >>>>>>>>>> 21:3014.4-2.419.1261.4751 >>>>>>>>>> 21:4513.4-4.016.9256.5728 >>>>>>>>>> 22:0013.2-4.223.8248.4800 >>>>>>>>>> 22:1512.8-6.323.7263.2684 >>>>>>>>>> 22:3012.4-7.119.0265.2695 >>>>>>>>>> 22:4512.3-6.721.0265.0867 >>>>>>>>>> 23:0012.1-6.325.6267.1870 >>>>>>>>>> 23:1512.6-6.122.0251.8779 >>>>>>>>>> 23:3012.2-6.618.1256.3818 >>>>>>>>>> 23:4511.7-6.217.1256.1815 >>>>>>>>>> 00:0010.6-6.220.8261.4950 >>>>>>>>>> 00:1510.2-6.216.6264.5915 >>>>>>>>>> 00:309.8-6.217.6261.5961 >>>>>>>>>> 00:459.7-6.221.0248.4948 >>>>>>>>>> 01:009.9-6.221.4251.6100734159.45 >>>>>>>>>> 01:159.7-6.416.9265.099435677.42 >>>>>>>>>> 01:309.7-6.618.6254.7120834158.68 >>>>>>>>>> 01:459.4-6.818.6264.5114833329.94 >>>>>>>>>> 02:009.1-6.620.0271.598733137.51 >>>>>>>>>> 02:159.0-6.316.9265.972232924.65 >>>>>>>>>> 02:308.9-6.120.7271.181633152.75 >>>>>>>>>> 02:459.0-6.118.7272.371434257.57 >>>>>>>>>> 03:009.1-6.722.8265.571834783.32 >>>>>>>>>> 03:158.8-6.317.6265.868033344.34 >>>>>>>>>> 03:308.5-6.110.9265.579234154.16 >>>>>>>>>> 03:458.5-5.718.4286.2110334677.23 >>>>>>>>>> 04:008.3-6.115.1281.0111233959.75 >>>>>>>>>> 04:158.3-5.621.0274.4119133965.95 >>>>>>>>>> 04:308.3-5.015.2280.3112233960.50 >>>>>>>>>> 04:458.7-5.125.4271.8128528154.20 >>>>>>>>>> 05:008.1-5.316.2269.0107632632.14 >>>>>>>>>> 05:158.1-4.920.4273.694532922.80 >>>>>>>>>> 05:307.7-5.122.9287.5101332817.42 >>>>>>>>>> 05:457.9-5.115.7266.699133020.65 >>>>>>>>>> 06:007.8-5.113.3268.889432913.24 >>>>>>>>>> 06:157.7-4.612.1274.789933317.63 >>>>>>>>>> 06:307.7-4.117.9275.394634266.15 >>>>>>>>>> 06:457.7-3.822.1287.492737250.52 >>>>>>>>>> 07:007.7-3.714.3293.688834784.36 >>>>>>>>>> 07:157.6-3.322.4294.585733450.41 >>>>>>>>>> 07:307.4-3.220.0300.393433027.50 >>>>>>>>>> 07:457.2-3.017.2282.08883293.65 >>>>>>>>>> 08:007.0-3.018.1284.59493294.21 >>>>>>>>>> 08:157.3-2.730.3298.58973292.42 >>>>>>>>>> 08:307.1-2.717.6277.59183292.70 >>>>>>>>>> 08:456.9-2.718.1305.08643302.12 >>>>>>>>>> 09:007.2-2.417.7289.58903302.39 >>>>>>>>>> 09:157.1-2.614.0305.89743302.72 >>>>>>>>>> 09:306.9-2.714.0289.39383302.24 >>>>>>>>>> 09:457.0-2.717.8292.89223305.06 >>>>>>>>>> 10:007.2-2.517.5290.29073305.30 >>>>>>>>>> 10:157.0-2.616.6284.19403303.50 >>>>>>>>>> 10:307.0-2.812.9281.79013292.63 >>>>>>>>>> 10:457.4-2.913.3284.88073291.85 >>>>>>>>>> 11:007.2-2.511.6279.98823291.85 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> ____________________________________________________________ >>>>>>>>>> Logs of Nightly APO Activities >>>>>>>>>> https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/index.html >>>>>>>>> >>>>>>>> >>>>>>>> ____________________________________________________________ >>>>>>>> Logs of Nightly APO Activities >>>>>>>> https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/index.html >>>>>>> >>>>>> >>>>> >>>> >>> --------------fpYeffFcDNMFDXFo8IdVZPFY Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Okay, this has been changed in /home/sdss5/software/tron/main/tron/config/apo.json from sdss5-tcc for host to sdss4-tcc for host. I guess some reset is needed. Shane On 10/25/2021 1:01 PM, Conor Sayres wrote: Hi shane. That is tron. Which runs on sdss5-hub -Conor  On Oct 25, 2021, at 2:59 PM, Shane Thomas wrote:  So I am trying to unravel what is going on here.  Though when my name was mentioned it seems to edit a .json file and replace: "tcc": { "host": "sdss5-tcc", "port": 2500, "actorName": "tcc" }, With "tcc": { "host": "sdss4-tcc", "port": 2500, "actorName": "tcc" }, Then someone restarts something somewhere?  I am just not sure what machine this is on, on the current sdss5-tcc this file? On 10/25/2021 8:19 AM, Conor Sayres wrote: Hi Kaike, You could try that, it could be a good check.  You’ll need to make sure that the tcc and mirrorCtrls are killed on sdss5-tcc.  And you’ll need to modify the TCC Nub in tron to point to the sdss4-machine (and restart tron). Both José and I are traveling today so we likely won’t be much help.  But I think this is the file you (or Shane?) need to modify locally from host: “sdss5-tcc” to host: “sdss4-tcc”. https://github.com/sdss/tron/blob/main/tron/config/apo.json    On Oct 25, 2021, at 9:40 AM, Kaike wrote: Hi Russet,  Thanks for the information. We are used engineering camera. All information is in one file for us. I double checked and confirmed all information is updated properly.   Conor, I will do more research today. If nothing is found, can we test the things on sdss4-tcc? i..e run the tcc on sdss4-tcc to see if we see the same shift between track pterr and track RA, Dec? On Oct 24, 2021, at 7:13 PM, Russet McMillan wrote: By any chance, is the instrument set to something other than the guide camera?  tcc track RA, Dec would try to center the star on the primary instrument, the one used in set inst= and the one displayed by "tcc show block inst."  But tcc track/pterr tries to center the star on the designated guider.  So if the instrument is not explicitly set to the guider, you would get different pointing results for those two commands. Additionally, when you do an instrument block for the guider you must be sure to update TWO files, both the i_blahblahblah file for the guider as an instrument, and also the ip_blahblahblah file for the guider as guider.  Make sure those files agree with each other.  A discrepancy between those two files could produce the same result, even if you have the instrument set to the guider.  In that case the tcc track RA, Dec command would center the star as described in the i_blahblahblah file, and the tcc track/pterr command would center the star as described in the ip_blahblahblah file. For the 3.5m, the two files are i_na2_guider.dat and ip_na2.dat , but you must have different port and instrument names. On Oct 24, 2021, at 6:07 PM, Kaike wrote: Thanks Russet. The pointing is great and can be repeated. Here is puzzling things: with "tcc track/pterr 120,60 obs/rotty=obj/rota=0 /magRange=(10,10.5)” command, the telescope is slewed to a star that is closest to AZ=120 deg, alt=60 in the magnitude range of 10.0 to 10.5 in the star category, and star is centered on the CCD. Once the telescope is in the field, Telescope Status window shows RA and Dec of the field, If we use “tcc track RA, Dec” slew the telescope to the same star, star images on the CCD move about 30 arc-seconds while we expect it should not move at all. The weird things is: Ra and Dec in two fits headers are similar (within 0.1 arc-second) but image displacement on CCD is 30 arc-seconds. One possible explanation I could think of: Fit header records RA/Dec in tcc track command without epoch information. Tcc track commands use Ra/Dec coordinates at 2000, but STUI display RA/Dec at the current date. We will test it tonight. -Kaike On Oct 24, 2021, at 5:42 PM, Russet McMillan wrote: If I found a big pointing discrepancy AFTER a pointing model, I would first look at the offsets.  A large calib or guide offset could cause what you describe, with the displayed RA/Dec not matching where you are on sky.  Large calib offsets may be needed to obtain pointing model data, but then once the pointing model is implemented you have to clear the calib offset by hand. If the offsets are not to blame, I would look more carefully at the pointing model, see if it was really trustworthy and reduced correctly.  Was there a pointing check right after the model was implemented?  If the after-model check was good and then the pointing changed later, then you know the model is not to blame.  But if there was a problem starting right after the model was implemented, then it probably is the source of the problem. And if those things were ruled out, then I would probably start worrying that a mirror is out of place.  But since you folks do not have a flat mirror like our M3 (which only affects pointing without affecting collimation), I guess if one of your mirrors was off there should be a clear effect on image quality? For problems with a pointing model, the tricky spots where it's easy to make a mistake are 1) When taking the grid data, make sure that the rotation is zero obj.  2) When taking the grid, make sure the offsets are Boresight type.  3) Make sure all offsets and measured positions match up.  4) After measuring the grid and before measuring the ring, make sure the Boresight offset is returned to zero. Maybe one of those things will help? On Oct 24, 2021, at 4:42 PM, Conor Sayres wrote: Hi Kaike, All, It’s a little hard for me to understand the weirdness/unexpected behavior you guys saw (and I’m not a practiced instrument blocker).  I wonder if you’ve run what you saw by Russet?  She would be the first person I’d ask when understanding discrepancies like this.   Russell did alert me years ago about a problem with ICRS coordinate transforms for the TCC, but I think we decided it was at the miliarcsecond level, and that’s probably bigger than you guys are seeing? The display of coordinate in STUI is *approximate* in that its only output so often (every several seconds?).  Certainly I wouldn’t trust STUI as a precision, realtime readout of where the telescope actually is... On Oct 24, 2021, at 10:13 AM, Kaike wrote: Thanks to Dan and Karen for the detailed information. Jose and Conor: Is it possible that  the actual RA/Dec and displayed Ra/Dec  in STUI status are off? e.g. one is in 2000, one is in current date? Audrey and Karen: Let’s run a couple of tests tonight. Slew to stars in star catalog with "tcc track ra, dec” command and see the same RA, Dec are displayed in the STUI status window and whether the star is centered on the engcam CCD.  I will log in at about 7:00 PM or so. On Oct 24, 2021, at 5:04 AM, doravetz@apo.nmsu.edu wrote:                 APACHE POINT OBSERVATORY SDSS 2.5M                           OBSERVING LOG                    Saturday October 23, 2021                            (SJD 59511) ----  Observing Team ---- Dan Oravetz Karen Kinemuchi (R) Dmitry Bizyaev (phone help) ---- Observing Plan ---- Another go at a pointing model following some recent updates. ---- Observing Summary ---- We completed some of the usual pre-pointing model steps -- home the engCam stage, home/relax mirrors, setup engCam, collected grid data and partially updated instrument block after fitting the grid data. Had some strange behavior with unexplained offsets before trying to get ring data, though. See Log for details. For now, i_ca1_engcam.dat is only PARTIALLY updated - it's been updated following the fit of the grid data, but that's as far as we got. We saved new Nominal MIGs after the home/relax procedure. We've still been getting apogeeql.heartbeat alerts when exposures are running, but the alert is disabled currently. The IRSC page went down around 10pm local time or so with a 503 Service Unavailable error. The irsc.apo.nmsu.edu domain pings fine and the disk space doesn't appear to be a problem. Candace called Shane and he will try to look into it, but it's still down as of sending the night log out. The connection to igor.apo.nmsu.edu failed. Candace tried to connect and it failed from the 3.5m control room, too. We ran into some trouble fitting instrument-block data with the IDL scripts Dmitry wrote. The 'IGOR' directory was altogether not present in observer@sdss5-bhm and the fit_instrument_data3 script wasn't found at first either. Dmitry noted that "it turned out that [at least observers' directories on] sdss5-bhm and sdss5-hub are linked to be the same: if a file or directory is removed from sdss5-hub, same happens on sdss5-bhm." He was able to copy the relevant files from a different machine back to the observer directory on sdss5-bhm and then the fitting script worked again. The engCam needed to be power-cycled for some unexplained reason after it died abruptly. ---- Observing Log ---- ============================================================================                         TELESCOPE CHECKOUT ============================================================================ 19:00Z - All systems alive and responsive upon arrival. No outstanding apogeeql critical alerts and the morning cals from this morning look OK. We started an early set of evening cals to see if the apogeeql.heartbeat alerts would start spawning again and they have been. So far the cals themselves are fine and look fine on disk (unlike yesterday's evening cals in which some images were missing). Also, the morning cals look fine from this morning, too. These alerts just seem to be spawning when exposures are running. JohnD pushed-through a fix that will actually keep alerts disabled (hopefully). We have disabled the apogeeql.heartbeat alert for now. 00:04Z - Started ventilation. Partly cloudy and a little windy. ============================================================================                              NIGHT ============================================================================ 00:35Z - Homed engCam stage. Force-filled BOSS before moving the telescope to ALT=70 for home/relax mirrors. ****************** Home/Relax Mirrors ****************** == M1 == actMount=12500.02,-1600.00,5299.99,47050.00,-8800.00,-8400.00; cmdMount=12500.00,-1600.00,5300.00,47050.00,-8800.00,-8400.00 desOrient=0.00,-59.50,-9.15,-512.00,1906.30 home E,F: position error", "999999999, 999999999, 999999999, 999999999, 000000000, 000000000" home D: "position error", "999999999, 999999999, 999999999, 000000000, 999999999, 999999999" home A,B,C: "position error", "000000000, 000000000, 000000000, 999999999, 999999999, 999999999" == M2 == home D: "position error", "999999999, 999999999, 999999999, 000000000, 999999999" home E: "position error", "999999999, 999999999, 999999999, 999999999, 000000000" home A,B,C: "position error", "-000000184, -000000127, -000000033, 999999999, 999999999" Saved new nominals MIGs (see Mirror Numbers). 04:04Z - Cloudy. Wind picking up more. 05:14Z - Started APOGEE morning cals early so we could respond to any alerts. 06:15Z - Opened. Partly cloudy. Clouds are on the way, but we hope to get data for the instrument-block update in this hole before the clouds get too bad. 06:21Z - Focused engCam. --- FocusLoop --2021-10-24 06:20:14 current focus=0.0 0  foc=-60  fwhm=3.849000  /data/ecam/59511/gimg-0005.fits 1  foc=-40  fwhm=3.282000  /data/ecam/59511/gimg-0006.fits 2  foc=-20  fwhm=3.233000  /data/ecam/59511/gimg-0007.fits 3  foc=0  fwhm=3.006000  /data/ecam/59511/gimg-0008.fits 4  foc=20  fwhm=3.865000  /data/ecam/59511/gimg-0009.fits 5  foc=40  fwhm=3.651000  /data/ecam/59511/gimg-0010.fits 6  foc=60  fwhm=4.600000  /data/ecam/59511/gimg-0011.fits set focus  0.0 done ******************************* Grid/Ring Instrument Block Data ******************************* 06:22Z - All telescope offsets are zero. Started grid data with gimg-0012. The seeing wasn't very good during the data collection. Called Dmitry for help with the IGOR-replacement IDL scripts since things were missing on sdss5-bhm. 07:39Z - The seeing is considerably better now. Started another set of grid data with gimg-0102. Seeing ~1.2" fwhm. Fit Grid Data: Type of Data:   Instrument Bin Factor                   1. X= 2           2. Y= 2 IIm_Ctr,unbinned pix         3. x=  512.0      4. y= 512.0 IIm_Sca,unbinned pix/deg     5. x= -16874.8    6. y= 16820.1 Aspect ratio is exact?       7. [Yes] Old Rot_inst_ang, deg        8.  -90.14 New Rot_inst_ang, deg            -90.08 == s. Now you can hit s to Fit Scale & Orientation == Old Rot_inst_xy, deg on sky  9. X =-0.004450   0. Y= 0.001323 New Rot_inst_xy, deg on sky     X =-0.005350      Y= 0.001900 If this instrument is also a full-frame guider (the whole CCD is one probe), e.g. 3.5m NA2 guider, then... New GP_rot_xy, deg on sky    g. 0.004724       h.  Y= 0.003895 == p. Now you can hit p to Fit Position ==     r=Read last saved set, w=Write this set, x=eXit     s=Fit Scale & Orientation  p=Fit Position => Finished running Fit Scale & Orientation Mean fit error X Y, =  -0.000+/-   1.268   -0.000+/-   0.971 unbined pix Make your choice: 0 ..to.. 9 or g h s p r w x Updated IIm_Sca (x and y) and Rot_inst_ang in the ca_1_engcam.dat file on sdss5-tcc:/home/sdss5/software/tccdata/master/inst. We wanted to collect ring data, but were having problems with the dec offset at the beginning of the test. The instructions say: "Adjust the declination (Y) 10-30 arcseconds so the star image will locate at 1/3 to 1/2 of the way from the center (512,512) to the edge of the chip (512,1024), i.e. Y at about pixel 700. Find the current (RA, Dec) from STUI status window, slew the telescope with the command tcc track ra,dec /keep=(gcorr,arc) fk5 by adding or subtracting 10 to 30 arcseconds in Dec so that image will locate at Y=700 or so." After we slewed to a star, it would be centered quite well to begin with. Then we add 30 arcseconds to the target Dec and re-slew but the star would move mostly to the left in the image. It was bizarre. We repeated this several times and each time our intended Dec offset in the target Dec was not seen in the image, but the star was offset to the left instead. Even more strange, any subsequent adjustments to the target Dec actually did work as seen in y-pixel shifts of the stars in the image, but the star remained off to the left in the image. We tried this instead: slew to a star using a command like this: tcc track/pterr 120,60 obs/rotty=obj/rota=0 /magRange=(10,10.5) Then, take an image. I.e., in gimg-0223 the star is reasonably well centered. Next, take the RA, Dec in the STUI Status window and slew to that location. We specified everything exactly as indicated in the Status window including ICRS. The expectation is the star shouldn't move because we're slewing to the same ra/dec we're already at. Instead, the star moves left as seen in gimg-0224. We reverted the engCam instrument block file to the old one and repeated the above test and had the same problem: gimg-0225 the star is centered, gimg-0226 the star moved left after we issued a slew to the ra,dec we were already pointing at. In all cases we verified no offsets were in place (boresight, calib, arc, guide) for any of the images. Currently, i_ca1_engcam.dat is the PARTIALLY UPDATED file - the one that was updated after the grid fit tonight, but hasn't been updated after fitting the ring data since we didn't get that far. i_ca1_engcam.dat.OLD is the instrument block data BEFORE tonight's grid fit. 09:55Z - engCam died for no apparent reason: 09:55:19 APO.doravetz.guider 849 ecamera f text=\"command failed: RuntimeError('bad imaging state=3; please try gcamera reconnect before restarting the ICC',) at /home/sdss5/software/gcameraICC/main/python/gcameraICC/alta/altacam.py:242\" ecamera actor was still responsive, though, and software attempts to bring it back failed. 10:05Z - Power-cycled engCam and then reconnected and engCam was back to being responsive. 10:58Z - Closed. ---- Mirror Numbers ---- Mirror numbers from afternoon checkout: PRIMARY: -------- Scale: 1.000000 MIGS TONIGHT NOMINAL Axial A: 0.0120 0.0120 Axial B: 0.0370 0.0360 Axial C: -0.1220 -0.1170 Trans D: -0.0364 -0.0366 Lateral E: 0.3350 0.3515 Lateral F: 0.5375 0.5415 GALILS Commanded:  12500 -1600 5300 47050 -8800 -8400 Actual:     12500 -1600 5300 47050 -8800 -8400 SETMIR VALUES PrimDesOrient: 0.0 -59.5 -9.15 -512.0 1906.3 PrimOrient:    1.07 -59.51 -9.21 -512.13 1906.31 SECONDARY: ---------- Focus:      0.0000 Air temp:    13.11 Altitude:   29.999996178438877 MIGS TONIGHT NOMINAL Axial A: -9.4510 -9.4540 Axial B: -9.4610 -9.4680 Axial C: -9.4970 -9.4970 Trans D: 0.0930 0.0980 GALILS Commanded: 4628800 4623100 4647200 -50 -3450 Actual:    4607306 4607237 4607350 -50 -3450 SETMIR VALUES SecDesOrient: 3657.0 0.0 0.0 0.0 42.22 SecOrient:    3657.04 -0.03 -0.02 -0.01 42.71 Mirror numbers after home/relax: PRIMARY: -------- Scale: 1.000000 MIGS TONIGHT NOMINAL Axial A: 0.0040 0.0120 Axial B: 0.0310 0.0360 Axial C: -0.1180 -0.1170 Trans D: -0.0362 -0.0366 Lateral E: 0.3315 0.3515 Lateral F: 0.5340 0.5415 GALILS Commanded:  12500 -1600 5300 47050 -8800 -8400 Actual:     12500 -1600 5300 47050 -8800 -8400 SETMIR VALUES PrimDesOrient: 0.0 -59.5 -9.15 -512.0 1906.3 PrimOrient:    1.07 -59.51 -9.21 -512.13 1906.31 SECONDARY: ---------- Focus:      0.0000 Air temp:     8.61 Altitude:   29.999996178438877 MIGS TONIGHT NOMINAL Axial A: -9.4440 -9.4540 Axial B: -9.4730 -9.4680 Axial C: -9.5010 -9.4970 Trans D: 0.1000 0.0980 GALILS Commanded: 4632700 4629650 4648300 -50 -3450 Actual:    4607306 4607224 4607199 -50 -3450 SETMIR VALUES SecDesOrient: 3657.0 0.0 0.0 0.0 42.22 SecOrient:    3657.0 0.02 -0.03 -0.02 42.67 Mirror numbers after home/relax after saving new NOMINAL values: PRIMARY: -------- Scale: 1.000000 MIGS TONIGHT NOMINAL Axial A: 0.0040 0.0040 Axial B: 0.0310 0.0310 Axial C: -0.1180 -0.1180 Trans D: -0.0362 -0.0362 Lateral E: 0.3315 0.3315 Lateral F: 0.5340 0.5340 GALILS Commanded:  12500 -1600 5300 47050 -8800 -8400 Actual:     12500 -1600 5300 47050 -8800 -8400 SETMIR VALUES PrimDesOrient: 0.0 -59.5 -9.15 -512.0 1906.3 PrimOrient:    1.07 -59.51 -9.21 -512.13 1906.31 SECONDARY: ---------- Focus:      0.0000 Air temp:     8.61 Altitude:   29.999996178438877 MIGS TONIGHT NOMINAL Axial A: -9.4440 -9.4440 Axial B: -9.4730 -9.4730 Axial C: -9.5010 -9.5010 Trans D: 0.1000 0.1000 GALILS Commanded: 4632700 4629650 4648300 -50 -3450 Actual:    4607306 4607237 4607193 -50 -3450 SETMIR VALUES SecDesOrient: 3657.0 0.0 0.0 0.0 42.22 SecOrient:    3657.02 0.03 -0.01 -0.01 42.66 ---- Telescope Status ---- Status at close: Telescope stowed at:    121.0, 30.0, 0.0 mount Instrument mounted:     engCam Counterweights at:      423 425 444 443 LN2 autofill systems:   Connected and turned on 180L LN2 dewar scales:  SP1 125 lbs, 24 psi ---- Software Used ---- --- Disk Space --- /dev/sdb1                2.0T   94G  2.0T   5% /home 10.25.1.230:/data         21T   15T  5.5T  73% /data --- Software Versions --- STUI          : 1.7.13 alerts        : 2.1.6 apo           : 3.0.0 boss          : 6.0.1-alpha.0 -boss.specMec : 3.0.4 guider        : 4.0.0 ecamera       : 2.3.0 fliswarm      : FAILED hartmann      : FAILED hub           : 5.0.0a0 mcp           : 2.1 -mcp.plc      : 34 -mcp.azFiduci : v1_147 -mcp.altFiduc : v1_147 -mcp.rotFiduc : v1_147 sop           : 0.1.0-alpha.0 tcc           : 1.4.0 apogee        : not available apogeecal     : not available apogeeql      : v1_7_0dev STUIAdditions : 3.1.9 ---- APOGEE Data Summary ---- 59510 morning cals: APOGEE data list,   mjd=59510,  morning raw_data:  /data/apogee/utr_cdr/59510/apRaw-*.fits archive:  /data/apogee/archive/59510/apR-[a,b,c]-*.apz quickred:  /data/apogee/quickred/59510/ap2D-a-*.fits.fz ------------------------------------------------------------------------------ mjd   i   UT   File/Exp  Imtype Nread A/B Dth  Ct-Plate Arch Offset %Flux Comm ------------------------------------------------------------------------------ 59510  10 10:14  39480010    Dark   60  A  13.0  -------  a-b-c    -   -   59510  11 10:25  39480011    Dark   60  A  13.0  -------  a-b-c    -   -   59510  12 10:35  39480012    Dark   60  A  13.0  -------  a-b-c    -   -   59510  13 10:37  39480013  QuarFlat 10  A  13.0  -------  a-b-c    -   98 59510  14 10:39  39480014  QuarFlat 10  A  13.0  -------  a-b-c    -   99 59510  15 10:41  39480015  QuarFlat 10  A  13.0  -------  a-b-c    -   99 59510  16 10:43  39480016  Arc----  12  A  13.0  -------  a-b-c    -   -   59510  17 10:45  39480017  Arc----  12  A  13.0  -------  a-b-c    -   -   59510  18 10:52  39480018  Arc----  40  A  13.0  -------  a-b-c    -   -   59510  19 10:59  39480019  Arc----  40  A  13.0  -------  a-b-c    -   -   59510  20 11:05  39480020    Dark   30  A  13.0  -------  a-b-c    -   -   59510  21 11:10  39480021  InteFlat 30  A  13.0  -------  a-b-c    -  280 59510  22 11:16  39480022  InteFlat 30  A  13.0  -------  a-b-c    -  280 59510  23 11:21  39480023  InteFlat 30  A  13.0  -------  a-b-c    -  280 59510  24 11:26  39480024    Dark   30  A  13.0  -------  a-b-c    -   -   ------------------------------------------------------------------------------ APOGEE data list,   mjd=59511,  all raw_data:  /data/apogee/utr_cdr/59511/apRaw-*.fits archive:  /data/apogee/archive/59511/apR-[a,b,c]-*.apz quickred:  /data/apogee/quickred/59511/ap2D-a-*.fits.fz ------------------------------------------------------------------------------ mjd   i   UT   File/Exp  Imtype Nread A/B Dth  Ct-Plate Arch Offset %Flux Comm ------------------------------------------------------------------------------ 59511   1 18:54  39490001    Dark    3  A  13.0  -------  a-b-c    -   -   59511   2 19:09  39490002    Dark   60  A  13.0  -------  a-b-c    -   -   59511   3 19:11  39490003  QuarFlat 10  A  13.0  -------  a-b-c    -   98 59511   4 19:13  39490004  Arc----  12  A  13.0  -------  a-b-c    -   -   59511   5 19:16  39490005  Arc----  12  A  13.0  -------  a-b-c    -   -   59511   6 19:23  39490006  Arc----  40  A  13.0  -------  a-b-c    -   -   59511   7 19:30  39490007  Arc----  40  A  13.0  -------  a-b-c    -   -   59511   8 19:41  39490008    Dark   60  A  13.0  -------  a-b-c    -   -   59511   9 20:08  39490009  Arc----  30  A  13.0  -------  a-b-c    -   -   FPI 59511  10 05:24  39490010    Dark   60  A  13.0  -------  a-b-c    -   -   59511  11 05:34  39490011    Dark   60  A  13.0  -------  a-b-c    -   -   59511  12 05:45  39490012    Dark   60  A  13.0  -------  a-b-c    -   -   59511  13 05:47  39490013  QuarFlat 10  A  13.0  -------  a-b-c    -   98 59511  14 05:49  39490014  QuarFlat 10  A  13.0  -------  a-b-c    -   98 59511  15 05:51  39490015  QuarFlat 10  A  13.0  -------  a-b-c    -   99 59511  16 05:53  39490016  Arc----  12  A  13.0  -------  a-b-c    -   -   59511  17 05:55  39490017  Arc----  12  A  13.0  -------  a-b-c    -   -   59511  18 06:02  39490018  Arc----  40  A  13.0  -------  a-b-c    -   -   59511  19 06:09  39490019  Arc----  40  A  13.0  -------  a-b-c    -   -   59511  20 06:15  39490020    Dark   30  A  13.0  -------  a-b-c    -   -   59511  21 06:20  39490021  InteFlat 30  A  13.0  -------  a-b-c    -  280 59511  22 06:25  39490022  InteFlat 30  A  13.0  -------  a-b-c    -  280 59511  23 06:31  39490023  InteFlat 30  A  13.0  -------  a-b-c    -  280 59511  24 06:36  39490024    Dark   30  A  13.0  -------  a-b-c    -   -   ------------------------------------------------------------------------------ ---- Weather Log ---- Wind 1 um DIMM IRSC Time Temp C Dewp C MPH Dir Dust fwhm mean sigma 18:00 13.3 -0.4 18.1 194.6 675 18:15 12.1 -0.2 19.9 217.3 701 18:30 12.9 -0.2 27.0 252.1 755 18:45 12.0 -0.9 20.7 265.0 710 19:00 15.4 -0.7 23.6 240.5 680 19:15 14.2 -1.3 21.6 265.6 698 19:30 13.4 -1.8 13.9 253.1 685 19:45 12.9 -1.8 20.5 223.4 653 20:00 12.2 -2.9 17.9 258.3 646 20:15 12.3 -3.1 15.0 229.2 611 20:30 14.1 -2.1 12.8 233.1 701 20:45 12.2 -3.0 19.8 245.5 732 21:00 12.3 -2.6 15.3 256.1 816 21:15 13.5 -3.3 16.9 261.7 688 21:30 14.4 -2.4 19.1 261.4 751 21:45 13.4 -4.0 16.9 256.5 728 22:00 13.2 -4.2 23.8 248.4 800 22:15 12.8 -6.3 23.7 263.2 684 22:30 12.4 -7.1 19.0 265.2 695 22:45 12.3 -6.7 21.0 265.0 867 23:00 12.1 -6.3 25.6 267.1 870 23:15 12.6 -6.1 22.0 251.8 779 23:30 12.2 -6.6 18.1 256.3 818 23:45 11.7 -6.2 17.1 256.1 815 00:00 10.6 -6.2 20.8 261.4 950 00:15 10.2 -6.2 16.6 264.5 915 00:30 9.8 -6.2 17.6 261.5 961 00:45 9.7 -6.2 21.0 248.4 948 01:00 9.9 -6.2 21.4 251.6 1007 341 59.45 01:15 9.7 -6.4 16.9 265.0 994 356 77.42 01:30 9.7 -6.6 18.6 254.7 1208 341 58.68 01:45 9.4 -6.8 18.6 264.5 1148 333 29.94 02:00 9.1 -6.6 20.0 271.5 987 331 37.51 02:15 9.0 -6.3 16.9 265.9 722 329 24.65 02:30 8.9 -6.1 20.7 271.1 816 331 52.75 02:45 9.0 -6.1 18.7 272.3 714 342 57.57 03:00 9.1 -6.7 22.8 265.5 718 347 83.32 03:15 8.8 -6.3 17.6 265.8 680 333 44.34 03:30 8.5 -6.1 10.9 265.5 792 341 54.16 03:45 8.5 -5.7 18.4 286.2 1103 346 77.23 04:00 8.3 -6.1 15.1 281.0 1112 339 59.75 04:15 8.3 -5.6 21.0 274.4 1191 339 65.95 04:30 8.3 -5.0 15.2 280.3 1122 339 60.50 04:45 8.7 -5.1 25.4 271.8 1285 281 54.20 05:00 8.1 -5.3 16.2 269.0 1076 326 32.14 05:15 8.1 -4.9 20.4 273.6 945 329 22.80 05:30 7.7 -5.1 22.9 287.5 1013 328 17.42 05:45 7.9 -5.1 15.7 266.6 991 330 20.65 06:00 7.8 -5.1 13.3 268.8 894 329 13.24 06:15 7.7 -4.6 12.1 274.7 899 333 17.63 06:30 7.7 -4.1 17.9 275.3 946 342 66.15 06:45 7.7 -3.8 22.1 287.4 927 372 50.52 07:00 7.7 -3.7 14.3 293.6 888 347 84.36 07:15 7.6 -3.3 22.4 294.5 857 334 50.41 07:30 7.4 -3.2 20.0 300.3 934 330 27.50 07:45 7.2 -3.0 17.2 282.0 888 329 3.65 08:00 7.0 -3.0 18.1 284.5 949 329 4.21 08:15 7.3 -2.7 30.3 298.5 897 329 2.42 08:30 7.1 -2.7 17.6 277.5 918 329 2.70 08:45 6.9 -2.7 18.1 305.0 864 330 2.12 09:00 7.2 -2.4 17.7 289.5 890 330 2.39 09:15 7.1 -2.6 14.0 305.8 974 330 2.72 09:30 6.9 -2.7 14.0 289.3 938 330 2.24 09:45 7.0 -2.7 17.8 292.8 922 330 5.06 10:00 7.2 -2.5 17.5 290.2 907 330 5.30 10:15 7.0 -2.6 16.6 284.1 940 330 3.50 10:30 7.0 -2.8 12.9 281.7 901 329 2.63 10:45 7.4 -2.9 13.3 284.8 807 329 1.85 11:00 7.2 -2.5 11.6 279.9 882 329 1.85 ____________________________________________________________ Logs of Nightly APO Activities https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/index.html ____________________________________________________________ Logs of Nightly APO Activities https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/index.html --------------fpYeffFcDNMFDXFo8IdVZPFY--