[daip] FITLD bug?

[Amy Mioduszewski]

Hi all,

I am loading some space VLBI data into AIPS and I found
a couple oddities with FITLD.

I wanted to load the calibrators (J1550+05, J1733-13
and J2148+06) and target source (J1939-15) separately,
so I set SOURCES to the calibrator sources and set
DOCONCAT 1.  It ran along fine for the first 5 files
(there were 9), but when it hit the 6th file it all of
a sudden it creates another file where is writes file 6
and puts J1939-15 in it.  When it gets to file 7 it
concatenates that and files 8 and 9 to the first file.
Also, after this point the target source is loaded as
well and the calibrators even though it is not in the
SOURCES list.  One oddity about the data is that there
are only 6 calibrator scans and so only files 1, 5,
and 7 have the calibrators in them, although I think
this is a red herring because the same thing happens 
when I try to just load the target source (see next
paragraph).

But even odder is when I do the same thing, setting SOURCES
to the target (which is in every file), it ALSO loads file
6 into a different file and from files 1, 2, 3, 4, 5, 7, 8
and 9.  Although all the files just contain J1939-15.  The
only "error" message starting with file 6 is:
"Warning: table type OB is of zero length"
This warning does not occur for files 1-5 but does for
files 6-9.

This could very well just be wacky space VLBI data (given
the warning about OB table), but shouldn't FITLD follow what
is in the SOURCES adverb religiously?  I will try to load
files individually tomorrow and see what happens.

Cheers,

Amy