In <3B404922.EAC79109 at bbsrc.ac.uk> simon andrews <simon.abdrews at bbsrc.ac.uk> writes:
> I'm not actually doing any error checking within the Tcl script. The
> input to the script is verified by the calling Perl script, but is there
> anything else I should be checking that I can't catch externally? I
> noticed in the script output that some sequences were failing to be put
> into the assembly. I know there will be some duplicates, and these
> appear to give a different error message. The tests that I have run
I expect it's just sequences which match, but not perfectly. This is the
difference between the "enter all readings" parameter in the GUI. When set to
false, sequences which match, but not well enough, are rejected. The
expectation is that you'll delay entering these until all the sequences have
been tried, and then you'll try entering them again.
The alternative (enter all) is to put such sequences in a new contig instead,
just as if they hadn't matched at all.
For more details, see:
http://www.mrc-lmb.cam.ac.uk/pubseq/manual/gap4_unix_91.html
and
http://www.mrc-lmb.cam.ac.uk/pubseq/scripting_manual/scripting_69.html
James
--
James Bonfield (jkb at mrc-lmb.cam.ac.uk) Tel: 01223 402499 Fax: 01223 213556
Medical Research Council - Laboratory of Molecular Biology,
Hills Road, Cambridge, CB2 2QH, England.
Also see Staden Package WWW site at http://www.mrc-lmb.cam.ac.uk/pubseq/
