[daip] fixing channel widths

[Jacqueline Hodge]

Hi Eric,

I'm the user who was asking Meri why FILLM was sending my two IFs to 
different files.  She sent me your response regarding fixing the channel 
widths, but I have a question about fixing the tables.  I can see 
that the channel widths in the FQ tables need to be changed, but the info 
in the SU tables looks the same (at least to my untrained eye) as that for 
similar, *uncorrupted* files.  In particular, the bandwidths in Column 
10 are the same as those in other files.  What needs to be fixed in the SU 
tables then?

Thank you for your help,
Jackie Hodge


"The user should fix the channel separation 3 places: the image header
with puthead, and the SU and FQ tables with TABPUT (carefully).  Then
VBGLU might glue them back together.

The user should watch for frequency wrong errors (phase inverted,
channel separation negative) but that was an independent error and far
less common."

Cheers,

Eric Greisen


If you need any AIPS help, Eric can answer your questions.  He's at
daip at nrao.edu.

I hope this helps.

Best regards,
Meri

Jacqueline Hodge wrote:
> Hi again Meri,
> I got the data (thanks), but now I'm confused because FILLM keeps splitting 
> the two IFs into two separate files.  I thought I made the observe files 
> exactly like those of AR646, for which FILLM always put both IFs in one uv 
> dataset.  Do you know what's going on?
> 
> Thanks!
> Jackie
> 
> On Mon, 17 Sep 2007, Data Analysts wrote:
> 
>> Hi Jackie,
>> 
>> The key to unlock the data is id2riyqq.
>> 
>> Regards,
>> Meri
>> 
>> 
>> John M Benson wrote:
>>> ---------------------------- Original Message ----------------------------
>>> Subject: AR659 Dynamic time data
>>> From:    "Jacqueline Hodge" <jhodge at student.physics.ucdavis.edu>
>>> Date:    Mon, September 17, 2007 12:08 pm
>>> To:      jbenson at aoc.nrao.edu
>>> -------------------------------------------------------------------------- 
>>> 
>>> Hi there,
>>> Some of my dynamic time files were run recently, and I was wondering how I
>>> get to the data since it appears to be locked.
>>> 
>>> Thanks!
>>> Jackie
>>> 
>>> 
>