[evla-sw-discuss] Reference pointing

[Bryan Butler]

i also don't quite get why the dummy scans are needed?

	-bryan


On 4/11/05 16:24, Barry Clark wrote:
> Ah, I understand.  That case was what the 'copy' variants was for.
> 
> z = subarray.refPointingInit()
> subarray.setRefPointing(z)
> <X band pointing scan>
> refpointingAgent.register(z)
> <short dummy scan to wait for results>
> <pointing scan at K band>
> w = subarray.refPointingInit(z)    # copies X band offsets
> refPointingAgent.register(z)
> <K band target obsn>
> subarry.setRefPointing(w)
> <pointing scan at Q band>
> refpointingAgent.register(w)
> <Q band target obsn>
> etc.
> 
>> From evla-sw-discuss-bounces at donar.cv.nrao.edu  Mon Apr 11 15:53:25 2005
>> Return-Path: <evla-sw-discuss-bounces at donar.cv.nrao.edu>
>> Date: Mon, 11 Apr 2005 15:52:58 -0600
>> From: Bryan Butler <bbutler at nrao.edu>
>> 
>> 
>> the use case your example doesn't handle, that mine does (i think, 
>> anyway), is observing at K & Q-bands, and double reference pointing at 
>> both (with, say, X-band as the lower band).  i believe that the way your 
>> example would work, you would need to do the X-band reference pointing 
>> scan twice.  in mine, you just do one each at X-, K-, and Q-bands, and 
>> then apply either X+K or X+Q, depending on the target frequency.  this 
>> is, for instance, how rick and i do the double reference pointing during 
>> the flux density runs (well, kind of, but the concept is the same).
>> 
>> it just seems simpler to me to not add up the offsets into a single 
>> object - keep them separate and apply whichever ones you wish at the 
>> time you observe your targets.
>> 
>> i wasn't thinking of the on-the-fly collimation determination, though 
>> it's an interesting idea.
>> 
>> 	-bryan
>> 
> _______________________________________________
> evla-sw-discuss mailing list
> evla-sw-discuss at listmgr.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/evla-sw-discuss