Hi Bryan,<div>The script that ran is at:</div><div>/home/mchost/evla/scripts/opt/2010/12/TDEM0011_sb2831326_1.evla</div><div>It ran between roughly 1235 LST and 2135 LST on the 16th.</div><div>Joe<br><br><div class="gmail_quote">
On Sun, Dec 19, 2010 at 4:16 PM, <span dir="ltr"><<a href="mailto:bbutler@nrao.edu">bbutler@nrao.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
the OPT doesn't really "pass" anything (in the normal sense) to<br>
model2script. the results of work in the OPT are put into the database<br>
(that's the "model" part), which is then accessed by model2script at the<br>
time the script needs to be run (the "script" part).<br>
<br>
i'm confused by your example though, rick - i don't quite understand what<br>
happened on those scans. a 2m20s scan seems very odd when it should have<br>
been ~4m10s, and not getting the following scan is odder still. it sounds<br>
like something funny with the executor, but that seems odd as well.<br>
<br>
what was the name of the script that was run, and the database ID for the<br>
stored model? and what times (precisely, please!) were those odd scans?<br>
i can have a look at the generated script (or re-generate it myself) and<br>
see if i see anything funky there with the timing. i'll also have a look<br>
at the executor log to see if something looks funny there.<br>
<br>
-bryan<br>
<div><div></div><div class="h5"><br>
<br>
> On Sun, 19 Dec 2010, Rick Perley wrote:<br>
><br>
>> The problem does not appear to lie with the OPT. I examined the<br>
>> OPTs calculations of time moving and 'sitting' -- and these are always<br>
>> in excellent agreement with what I expect given the distance to be<br>
>> traversed.<br>
>> An example should help clarify the problem:<br>
>> At one particular moment, we needed to move from Herc A to<br>
>> 3C286. The azimuths and elevations were at that time:<br>
>> Herc A: Az = 118 El = 42<br>
>> 3C286: Az = 252 El = 79<br>
>><br>
>> With azimuth slew speeds of 40 deg/min, and elevation speeds of 20<br>
>> deg/min, it's obvious that more than 3 minutes will be needed to cover<br>
>> that distance. The OPT states the time required would be 3m 26s.<br>
>> Adding in my requested 45 seconds 'on source' time, the scan observation<br>
>> time for 3C286 in this instance should be a little over 4 minutes. And<br>
>> indeed, this is what the OPT says will be provided.<br>
>> But it's not what happened. In fact, the length of that scan was 2m<br>
>> 20s -- nearly 2 minutes short. So not only was that calibration scan<br>
>> missed, but so was the subsequent one (same source, different band).<br>
>><br>
>> Further evidence of the problem lies with the total length of the<br>
>> observation. The OPT claims the total length of the observation is 8h<br>
>> 0m. (Indeed, I constructed the file to fit this time window). But the<br>
>> *real* observation length was 7h 47m -- the 23 minutes differential is<br>
>> the sum of the all travel time miscalculations.<br>
>><br>
>> This is a significant problem, especially to those programs which<br>
>> have many long slews -- like the 'flux densities/calibration scale'<br>
>> run. Fortunately, this program was not run this weekend, due to poor<br>
>> weather.<br>
><br>
> It is clear that the script generated and used for this<br>
> observation contains the faults that rick describes. If<br>
> the OPT is calculating and reporting the correct information<br>
> to Rick, the problem must lie in what it passes to m2s, or<br>
> what m2s does with that information.<br>
><br>
> _______________________________________________<br>
> evlatests mailing list<br>
> <a href="mailto:evlatests@listmgr.cv.nrao.edu">evlatests@listmgr.cv.nrao.edu</a><br>
> <a href="http://listmgr.cv.nrao.edu/mailman/listinfo/evlatests" target="_blank">http://listmgr.cv.nrao.edu/mailman/listinfo/evlatests</a><br>
><br>
<br>
<br>
_______________________________________________<br>
evlatests mailing list<br>
<a href="mailto:evlatests@listmgr.cv.nrao.edu">evlatests@listmgr.cv.nrao.edu</a><br>
<a href="http://listmgr.cv.nrao.edu/mailman/listinfo/evlatests" target="_blank">http://listmgr.cv.nrao.edu/mailman/listinfo/evlatests</a><br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Dr. Joseph P. McMullin <br>EVLA <br>Ph: +1 575 835 7315<br>E-mail: <a href="mailto:jmcmulli@nrao.edu" target="_blank">jmcmulli@nrao.edu</a><br>
<a href="http://science.nrao.edu/evla/" target="_blank">http://science.nrao.edu/evla/</a><br><br>
</div>