[daip] IMAGR multiple fields: what's the issue with beam scaling? Also: CALIB with multiply concatenated VLBA datasets.

[SUSAN BILL WIDER]

Eric, Amy.

   I'm running IMAGR with a couple of fields.  The first field looks about right with a maximum of 1.0 Jy for the beam but the second field beam has a maximum of 4.0 Jy.  How can this be?  Aren't the beams meant to have unity maximum?  Or is there some additional weighting that has to happen?  The sum of the gridding weights in both cases is the same so what's going on here?  (PRTMSG capture appended.)    

   Another issue:  I have concatenated multiple VLBA datasets together to improve my sensitivity.  The configuration of the arrays in most of the datasets is the same but not always.  Consequently, the antenna numbering scheme for each sub-array changes --- say, if one antenna was unanvailable.  If I run CALIB on this multi-epoch database, CALIB reports that some antennas get flagged because they can't be tied across sub-arrays.  This shouldn't happen, I think, because all we need is that the sub-set of antennas in each effective sub-array at each epoch should be linked.  I don't remember this sort of behavior with VLA multi-epoch data so is there something different happening when a non-VLA array is involved?   

                              Bill
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listmgr.nrao.edu/pipermail/daip/attachments/20071123/4c4dd582/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: IMAGR.TXT
URL: <http://listmgr.nrao.edu/pipermail/daip/attachments/20071123/4c4dd582/attachment.ksh>