To preparing larger Dataset for velvet, I merged two unmapped human reads files and now I have 3 questions ?!
1) Is this the right way to increase the quality of velvet output (I mean length of contig which I produced) ?!
2) After merging the files ,New file contains near 320,000,000 seq but when I run velvet on 72Gb memory it used all the memory and then run time increased (near 4 days to complete hashing part). So Do you know how much memory Should I allocate?!
3) Can I split this new file to 320 files and then run velvet on each of them parallel and in the end merge the velvet output to use as one assembly result?!?
p.s: I use colorbased version of velvet.
•
written
by
khikho
1 answer
1) Yes, it is. More data you have - the better results are.
2) You can try smaller K to fit in memory. But assembling mammalian genomes with Velvet is somewhat nearly impossible. Assembling human genome in 72Gb RAM is also close to impossible even with any other de-novo assembler. Usually it takes 200+Gb of RAM depending on dataset.
Consider one of the following:
- Assembly be reference (Bowtie / BWA), not de-novo.
- Using ALLPATH / SOAPdenovo.
3) Definitely no.
Log in to answer this question.
-
clustalo - align milions of short seq, memory issue
written by emma.a •
-
blastn Error: mdb_env_open: Cannot allocate memory
written by Mehmet
-
[bam_sort_core] merging from 32 files and 16 in-memory blocks... samtools sort: failed to write hea…
written by eli_bayat •
-
bwa-mem: [bam_sort_core] merging from 0 files and 3 in-memory blocks
written by CaffeSospeso •
-
BWA. Allocate memory
written by windsur •
-
samtools sort error: [bam_sort_core] merging from 3 files and 1 in-memory blocks...
written by Joe •
-
MetaVelvet caught in an infinite loop?
written by slvt16 •
-
Does Running Velvet With Gzipped Files Reduce Memory Usage?
written by johnstantongeddes
-
Insert Length Estimated By Velvet
written by khikho
-
De Novo Assembly Using Colorspace
written by khikho
