Date: Sat, 26 Sep 2009 22:10:44 -0000 (UTC)
Subject: Re: 2.5m obslog 20090925 (MJD 55100)
From: hjbrew@apo.nmsu.edu
Hi Steph,
  Yes, we double checked the offsets and made DOUBLE sure they were
cleared.  Since skippy only worked once last night during all three
imaging scans, I'm not sure the skippy numbers should be trusted.
H
> Just to clarify , the spectro offsets were cleared for imaging, yes?
>
> Steph
> On Sep 26, 2009, at 6:31 AM, Howard Brewington wrote:
>>
>> 06:22Z scanStripe 84 N -startLambda 141 -endLambda 166 (not
>> including ramps)
>>       See Imaging Details for more info.
>>       We tried running skippy several times during the run without
>> success.
>>       ltMatch worked some of the time, and the rot values were low.
>> See
>>       ltMatch output in Problems Section.
>>       Note: Seeing went bad at frame #169, lambda 161.1  Infact, the
>> last
>>       five science lambda were collected in seeing >2"
>>
>> 08:40Z scanStripe 72 N -startLambda -179.5 -endLambda -162.75 (no
>> ramps)
>>       See Imaging Details for more info.
>>
>>       Skippy would sometimes work on this stripe; see below;
>>
>>       astrom> skippy 8055 12 4
>>       THETAF = 0.0004 degrees, 1.60 arcsec
>>       CT     = 0.39604 arcsec/pixel
>>       SCALEF = 16.5966 arcsec/mm
>>       AMU0   = 4.9743 degrees
>>       ANU0   = -0.0008 degrees
>>       NCAT   = 116
>>       NSTARS = 65
>>       AZ     = 256.5220 degrees
>>       EL     = 67.2210 degrees
>>
>>       raBoreErr:  -10.3", decBoreErr:  -14.0"
>>       azErr:      -22.2", elErr:       -14.5"
>>       muErr:       -9.4", nuErr:       -14.0"
>>
>>
>>       We put the ltMatch output results in the Problems Section; the
>> rot
>>       values were low.
>>
>> 09:58Z scanStripe 71 S -startLambda -175.5 -endLambda -
>>       See Imaging Details for more info.  Skippy would not work on
>> this
>>       run.  The results of ltMatch are posted in the Problems Section.
>
>