From: sjnk@apo.nmsu.edu
Subject: Re: 2.5mobslog MJD 51893 20001214
Date: Fri, 15 Dec 2000 15:03:07 -0700 (MST)
Attn. Eric, Soppies, anyone else. Can you take a look into these
problems?
>                       Thursday Dec 14 2000
>                            Observing Log
>
>When doing gotoField, sop "hung" which Mike has seen happen yesterday.
>After recovering from it, sop core dumped while trying to center the
>guide stars. We realized that this was under sop v3_22_0 (current
>version)but running sop v3_23_1 server.  We tried again with iop
>v3_23_2 (new version cut tonight with initNight fixed) with the server
>running from the same version.  This had problem grabbing the
>instrument. The message we got trying to grabInstruments is in the
>Problem section.
The servers would not affect this particular item, I do not think. The
grabInst problem is likely a red herring and a result of the "hanging"
during gotoField, not an inherent bug in this version of SOP.
So, the real issue here is the gotoField snag. Any more information you
could supply would help diagnose things.  Scott, David- can you contact
the observers tonight and see what's going on? I can also come in if
needed.
>The telescope took the loong way (almost 360 degree turn) to its position.
I don't understand this and the "recovery" described later. Soppies?
This must be related to the "hang" if connections to the TCC were screwy or
half a command got sent to it or ...?
>We don't know exactly why things were messed up, but
>we believe that has something to do with using mismatch version
>of servers and sop version.
I don't believe this could be so. The only server changes between 3_22* and
3_23*, that I know if, are imager server changes that Connie put in to copy
some files automatically.  Soppies- is this so?
>Here is what we were doing when the core dump happened.
>
>sp1> gcam 10
>sp1> /data/spectro/guider/gimg0362.fits
>WARNING: Mask does not exist
>sp1>
>sp1> offset -3 3
>/p/astroda/v14_34/bin/dscRun[422]: 737609 Memory fault(coredump)
>>
Scot