[maker-devel] Re-annotation
Carson Holt
carsonhh at gmail.com
Wed Jun 27 09:43:14 MDT 2012
If the new ESTs don't map within the threshold parameters set in the
maker_bopt.ctl file, then you would not expect new results. Don't be
surprised if the new results are just hard to identify within the context of
the ESTs already being passed back through. If you want to test the new
ESTs, then set est_pass to 0 during your next run and see if there are still
no ESTs.
Thanks,
Carson
From: Sivaranjani Namasivayam <ranjani at uga.edu>
Date: Wednesday, 27 June, 2012 9:49 AM
To: "maker-devel at yandell-lab.org" <maker-devel at yandell-lab.org>
Subject: [maker-devel] Re-annotation
Hi,
I have a quick question about re-annotation. Under the re-annotation
section, the provided maker's gff file from a previous run and set est_pass,
altest_pass, protein_pass, rm_pass to 1.
I also provided some EST evidence (to the tag est) under the EST evidence
section, but I don't see these ESTs being mapped to the genome (no blastn or
est2genome) in the output gff files.
Is this expected?
Thanks,
Ranjani
_______________________________________________ maker-devel mailing list
maker-devel at box290.bluehost.com
http://box290.bluehost.com/mailman/listinfo/maker-devel_yandell-lab.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://yandell-lab.org/pipermail/maker-devel_yandell-lab.org/attachments/20120627/4afce4ea/attachment-0003.html>
More information about the maker-devel
mailing list