![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
De Novo Assembly of a transcriptome | Neil | De novo discovery | 82 | 02-28-2012 10:44 AM |
De Novo assembly of a plant transcriptome | raonyguimaraes | RNA Sequencing | 7 | 07-05-2011 02:17 PM |
De Novo Transcriptome Assembly QC | Noremac | General | 0 | 05-19-2011 12:02 PM |
de novo transcriptome assembly | Niharika | Introductions | 8 | 02-07-2011 06:29 AM |
de novo transcriptome assembly | chenjy | RNA Sequencing | 4 | 12-07-2010 12:54 AM |
![]() |
|
Thread Tools |
![]() |
#1 |
Member
Location: Guelph, Ontario, Canada Join Date: Jan 2012
Posts: 31
|
![]()
Hi everyone
I'm going to be making several de novo transcriptome assemblies (using different software), and I wish to compare them. What metrics are best for this? I don't have a reference genome. Also, is there a software package for generating these metrics from output files? I've currently tried running Trinity, and I get a lot of output files, but none that seem to summarize the number of contigs, their length, etc. How can I calculate this from a fasta file of assembled contigs? |
![]() |
![]() |
![]() |
#2 |
Member
Location: usa Join Date: Jan 2009
Posts: 20
|
![]()
Hi LizBent,
I have been working on the exact same problem and have come up with some metrics to estimate the quality of a transcriptome in the absence of a ref genome. Some stats that I have used are: *n50 *percent annotated to my closest reference *percent of annotated proteins that have (what seem to be) premature stop codons *percent of reads used/percent of paired reads used *contiguity & completeness (see http://www.nature.com/nrg/journal/v1...l/nrg3068.html) *incidence of chimeric transcripts As for calculating simple metrics like n50, max contig size, etc, I use the command line program abyss-fac, which is available as part of the general ABySS package. Good luck! |
![]() |
![]() |
![]() |
#3 |
Junior Member
Location: São Paulo Join Date: Oct 2012
Posts: 8
|
![]() |
![]() |
![]() |
![]() |
#4 |
Member
Location: Garvan Institute Join Date: Mar 2015
Posts: 16
|
![]()
There're a few solutions to calculating metrics for an assembly.
1. https://github.com/ajmazurie/velvet-stats 2. Biopieces 3.http://korflab.ucdavis.edu/datasets/...athon_stats.pl 4. abyss-fac I don't recommend 1-3. The documentation is bad, I didn't have the time to go through the source code. Biopieces required a multi-stage workflow, which I think it's a very stupid idea. Use abyss-fac, don't waste your time. On a Mac, install it via "brew install abyss" |
![]() |
![]() |
![]() |
#5 |
Super Moderator
Location: Walnut Creek, CA Join Date: Jan 2014
Posts: 2,707
|
![]()
Old thread, but BBMap has a stats.sh program that will summarize basic assembly stats (N50, L50, distribution of contig sizes, GC%, etc); it's very fast even on assemblies with millions of contigs, and extremely easy to use:
stats.sh contigs.fasta For more advanced statistics, particularly if you have a reference and are evaluating different assembly methodologies, I recommend Quast because it also does alignment to the reference to calculate the number of misassemblies. Also, even if you don't have a reference, it does neat things like gene prediction. Not sure how that feature would work on a transcriptome, though. Last edited by Brian Bushnell; 05-12-2015 at 07:26 PM. |
![]() |
![]() |
![]() |
#6 | |
Junior Member
Location: São Paulo Join Date: Oct 2012
Posts: 8
|
![]() Quote:
Code:
name.extension Code:
name.middle.extension Last edited by nepossiver; 05-13-2015 at 09:06 AM. Reason: added rnaQUAST link. |
|
![]() |
![]() |
![]() |
#7 |
Member
Location: Germany/Netherlands Join Date: Feb 2014
Posts: 98
|
![]()
There are tools like CGAL and RSEM-EVAL, which calculate the likelyhood of the reads belonging to the actual assembly. That might help when you're having more than 1.
Since sometimes the size of the assembly can vary too, I also like to have an estimate of the genome size beforehand, tools to use are kmerspectrumanalyzer or kmergenie. And depending on how fragmented you can/want to get with the data: A most likely correct genome (not necessarily contigous) will be to take the consensus from all your assemblies, and break the contigs if they're not agreeing. <s>If you arrive at a chromosome, and you have a prokaryote, then you need to take a look at the GC skew of the chromosome to detect obvious misassemblies.</s> scratch that, didn't see the transcriptome part. EDIT: Eh, no strike through tags in this forum? |
![]() |
![]() |
![]() |
#8 |
Senior Member
Location: Denmark Join Date: Apr 2009
Posts: 153
|
![]()
I should say Biopieces is pretty nifty for this task:
https://code.google.com/p/biopieces/...embled_contigs You simply do: Code:
read_fasta -i contigs.fna | grab -e "SEQ_LEN>=200" | analyze_assembly -x Code:
N50: 9082 MAX: 52038 MIN: 200 MEAN: 4170 TOTAL: 3057214 COUNT: 733 --- |
![]() |
![]() |
![]() |
Thread Tools | |
|
|