-
Notifications
You must be signed in to change notification settings - Fork 102
Falcon assembly question #590
Comments
Hi Yuri, You are looking at the stats for the associate contigs. How does 'p_ctg.fa' look? This is the primary contig assembly. Your preassembly stats look ok, no red flags from what I can see, but you are limited in data quality and quantity. Your preassembled yield (60%) is on the low side and your raw and pread length distribution isn't great. The raw coverage is also low, which may explain the low yield. We usually recommend 50x for an inbred. |
Hi |
Hello,
I am trying to assemble algal genome with falcon+faclon-unzip. The genome size is thought to be 100-150Mbp according to k-mer analysis of Illumina gDNA reads and assemblies generated by various
DBG --> OLC
andPacBio de novo
pipelines. However, the direct estimate of gDNA content per cell is unknown, so I am not completely sure in this figure. Meanwhile, according to k-mer analysis, genome contains long stretches of duplicated fragments. Some people designate this phenomenon as partial diploidy. Under settings specified below, falcon generates assembly of ~23Mbp (a_ctg_base.fa
), which is four times smaller than one obtained by feeding canu with the same input data.My gut feeling is that the raw coverage might be too low. Distribution of preads' overlaps is long-tailed suggesting considerable amount of repetitive genome content that could confuse falcon on the
2-asm
assembly stage. Though, I am quite uncomfortable with moving parameters back and forth to optimize the assembly yield.Could you please have a look at falcon output to diagnose the problem and suggest some recipe?
raw_read stats
pre_assembly stats
5' overlaps between preads
Distribution of the number of preads' 3'-overlaps is very similar.
fc_run.cfg
a_ctg_base stats
Best, Yuri.
P.S. My question might be similar with #581 and #572. I however decided to open a new issue so that not to interfere with particular discussion threads. Sorry for possible duplicate.
The text was updated successfully, but these errors were encountered: