[evlatests] Troubles with long slews

[Bryan Butler]

i just set up a dummy SB to test this, and can verify that there is a 
problem.  it lies in model2script.  i don't know when this could have 
appeared in the code, or all the details of how it is triggered, but it 
definitely happens when specifying an "On Source" timing.  i suspect 
it's OK if you use "Duration" timing.  i don't know if it depends on 
slew length or not.

i'll be sending more details to the programmers and we'll tackle this 
first thing in the morning.

	-bryan


Bryan Butler wrote, On 12/19/10 22:59 PM:
>
> i didn't read this carefully enough earlier (had company coming over
> myself).  looks like ken already verified that it's in the script, which
> exhonerates the executor and downstream.  so if rick says that the OPT
> is giving the right information in its display, then either it's not
> storing it right in the model database, or it's getting converted
> incorrectly in model2script.  unfortunately dave is away on vacation,
> and he's the model2script main guy.  when rick gets in tomorrow and can
> have another look at the OPT to verify what's going on at that end we
> can probe further.
>
> 	-bryan
>
>
> Ken Sowinski wrote, On 12/19/10 13:15 PM:
>> On Sun, 19 Dec 2010, Rick Perley wrote:
>>
>> It is clear that the script generated and used for this
>> observation contains the faults that rick describes.  If
>> the OPT is calculating and reporting the correct information
>> to Rick, the problem must lie in what it passes to m2s, or
>> what m2s does with that information.
>>
>> _______________________________________________
>> evlatests mailing list
>> evlatests at listmgr.cv.nrao.edu
>> http://listmgr.cv.nrao.edu/mailman/listinfo/evlatests
> _______________________________________________
> evlatests mailing list
> evlatests at listmgr.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/evlatests