more than one exon at a time.
Corrected write_supporting_evidence in Contig.pm so the contig id is
correct.

Supporting evidence is written into the DBSQL database.
transfer.pl finds and writes supporting evidence
Contig fetches predicted features
Supporting feature table expanded

Supporting evidence is written into the DBSQL database.
transfer.pl finds and writes supporting evidence
Contig fetches predicted features

Supporting evidence is written into the DBSQL database.
Contig fetches predicted features

Supporting evidence is written into the DBSQL database.

Also only reads files once and stores the features in arrays.
The repeats and the similarities are stored in separate arrays.
Find supporting evidence is in ContigI. It doe a crude overlap of all
the similarity features with an exon.
TimDB/Contig is modified so it only reads the flatfiles once.

Also only reads files once and stores the features in arrays.
The repeats and the similarities are stored in separate arrays.
Find supporting evidence is in ContigI. It doe a crude overlap of all
the similarity features with an exon.

Also only reads files once and stores the features in arrays.
The repeats and the similarities are stored in separate arrays.

Added a type function for parsing repeats and similarities separately in
FeatureParser
Similarity and repeat features are fetched separately in Contig.
ContigI extended to fetch repeats and similarities separately
Obj.pm - source_tag wasn't being added to some repeats

Added a type function for parsing repeats and similarities separately in
FeatureParser
Similarity and repeat features are fetched separately in Contig.

Added a type function for parsing repeats and similarities separately in
FeatureParser