[daip] UVCOP fails on a TY table.

[R. Craig Walker]

I have a MULTi data set from the VLBA that I cannot copy with UVCOP with
both of it's TY tables attached.  The problem one (vers 2) was created by
UVCOP and edited using TABED.  When I run UVCOP, I get the following
messages:

UVCOP1 11:11:29 Copied TY file from vol/cno/vers  5    1   1 to  6    1   1
UVCOP1 11:11:29 TABIO: BAD LRNO=       14220 LIMIT       14219
UVCOP1 11:11:29 TABTY: TABIO ERROR  2
UVCOP1 11:11:29 TYSEL: ERROR   2 RETURNED FROM TABTY
UVCOP1 11:11:29 Destroyed  2 extension files of type TY
UVCOP1 11:11:29 Destroyed  1 extension files of type SU

PRTAB claims that TY number 2 had 14219 rows, and that is all it attempts
to display.  This was a table I made quite a few months ago and APCAL, the
user, did not complain.  TASAV does not complain.  TACOP does not
complain.  In fact, I have not yet found a program that has a problem with
the TY table other than UVCOP.  Unfortunately, when UVCOP has the problem,
it aborts and deletes everything already copied.  I ran a TASAV, then a
UVCOP on that.  After telling it not to delete flagged records, that UVCOP
had the same problem.  Then I deleted TY 2, and an otherwise identical
UVCOP ran ok.  So TY 2 is for sure the problem.

Using the TASAV file, I recreated a TY 2 following the same steps as
used originally.  The following steps are what was done

default tacop
  ind 6; getn 1
  outd=ind; outn=inn; outcl=incl; outs=ins
  inext='ty'; inver=1; outver=2; doflag=1
runwait ('tacop')

* Edit the table.  Unfortunately, it's one column at a time.
default tabed
  ind 6; getn 1
  outd=ind; outn=inn; outcl=incl; outs=ins
  inext 'ty'; inver 2; outver 2
  timer = 0,7,41,40, 0,7,45,55; optype 'dele'; aparm(2) = 1; aparm(3)=16
  aparm(1) = 7; runwait ('tabed')
  aparm(1) = 8; runwait ('tabed')
  aparm(1) = 9; runwait ('tabed')
  aparm(1) = 10; runwait ('tabed')

The identical error happens if I try to copy that data set with UVCOP.

I suppose I can create the output file by deleting the TY table (after
stashing it somewhere), copy the main file, then copying the TY table to
the output or recreating as above.  But it seems like such hoop jumping
should not be necessary.

Is there a way to see if the TY table really has more than 14219 rows? 
Looking at the binary file with less, there seems to be a much longer
string of blanks at the end than I see spot checking a few other TY files.
 Could that be the problem?  That applies both to the old version of TY
table and the one I just created.  I suspect TABED is adding the blanks
and for some reason only UVCOP is disturbed by them.

After first having the problem, I did a midnight job and the testing
described above used that (done today).

The data set is a large one at home so making it available is a bit of a
problem.  I could maybe make one of the TASAV files available if that
would help.

Cheers,

Craig


---------------------------------------------------------------------
    R. Craig Walker            Array Operations Center
    cwalker at nrao.edu           National Radio Astronomy Observatory
    Phone  575 835 7247        P. O. Box O
    Fax    575 835 7027        Socorro NM 87801   USA
--------------------------------------------------------------web