[daip] question on FILLM from disk

[Eric Greisen]

Data Analysts writes:

   Please send queries on aips to daip at nrao.edu - you will get a
faster response if you do not require the message to be forwarded by
the analysts.

 > 
 > ----- Begin Included Message -----
 > 
 > >From lmatthew at cfa.harvard.edu Fri Jul  2 13:19 MDT 2004
 > Date: Fri, 2 Jul 2004 15:19:11 -0400 (EDT)
 > From: "Lynn D. Matthews" <lmatthew at cfa.harvard.edu>
 > To: analysts at zia.aoc.nrao.edu
 > Subject: question on FILLM from disk
 > MIME-Version: 1.0
 > X-MailScanner-Information: Please contact postmaster at aoc.nrao.edu for more information
 > X-MailScanner: Found to be clean
 > X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-5.4, required 7,
 > 	BAYES_01 -5.40, USER_AGENT_PINE 0.00)
 > X-Lines: 21
 > Status: RO
 > 
 > Hi,
 > 
 > I have just been attempting to read into AIPS some of my data for project
 > AK578, using FILLM from the disk archive files I retrieved from the web,
 > and have encountered a problem.
 > 
 > When I attempt to read in file 2004-05/vla2004-05-14.dat, FILLM always
 > splits it into two parts, 20040514.LINE.1 and 20040514.LINE.2, with the
 > split occurring where LST=0h is passed, and there is also a change in
 > frequency. My observations went SOURCE1--SOURCE2--SOURCE1, and the break
 > is occurring after SOURCE2, causing the two sets of observations of
 > SOURCE1 to be separated.  File 2004-05/vla2004-05-16.dat covers the
 > identical LST range and sources, but this problem does not occur.
 > 
 > If there an obvious reason for this difference? I've tried various things
 > to override this in FILLM without success.  As an alternative, can I
 > safely concatonate the two raw files with DBCON?

There is normally only one reason for breaking into new output files
and that is a change in mode, hence a change in number of
polarizations, number of channels, and perhaps bandwidth.  The
frequency change alone would only make a new FQID.  Can you send my
the IMHEADER outputs of the files and perhaps the LISTR('SCAN')
outputs as well?  In case of a mode change DBCON will not accept the 2
data sets for concatenation.

FILLM is very complicated so there may be a "feature" that causes this
for no good reason, but let's look for a reason first.

Eric Greisen