velvet test

[francesco.vezzi]

I'm assembling a grapevine clone. The reference genome length is 400MB. SOAPdenovo is divided in several step. The read correction takes approximately 1 day. The denovo step takes 5 hours while the scaffolding step takes half day... I'm working on a server with 120Giga of RAM and 8 CPU. The ram peak is more or less 60Giga.
Abyss takes 7-8 hours using 8 machines with 8 CPU each and with 30 Giga of ram each.

The moral is: a lot of ram and a lot of CPU and wait

Hope this can help

Francesco

[isharon]

Hi Francesco,

Could you please provide a time estimate regarding how long it took you? Also some more details about the genome size etc would be great. I need to assemble 6 Illumina lanes and was wondering whether SOAPDenovo would be a reasonable choice for that.

[francesco.vezzi]

Hi
I think that the best way to deal with this huge amount of data is use one between SOAPdenovo and ABySS. With them I'm able to assembly 16 illumina lanes with less then 80Giga ram memory.


Francesco

[Haneko]

Thanks! I think the '&' somehow couldn't work the usual way it did. don't know why though.

[Jonathan]

1. What should the input be like? I have read 1 and read 2 for the paired-end reads. Do I combine them into one file?

If you had read the manual, you'd know:
Velvet expects paired-end data to be in an interleaved format;
aka
read1
read1pe
read2
read2pe
....

There's a tool/script for this shipped with velvet.

2. How do I run velvetg? The manual states that if insert size is not specified it will attempt to measure it for me. If that's the case do I still need to put -ins_length in my command? I do not know both the expected coverage and the insert size.

a) Expected coverage can be left for velvet with the '-exp_cov auto' switch.
b) Insert size is (usually - unless you have some other library prep) 200bp, +/- 10%; 10% is what velvet uses as default afair, just set the 200 and see if it works out.

3. While testing, I can't seem to direct the console output of velvet into any file. So for example:
velvetg velvet_data/ -exp_cov auto -min_contig_lgth 100 &> velvetg.out

This give no output whatsoever in the velvetg.out file, neither on the console.

Hm. Have you tried getting the different channels?
It works on my end:
velvetg velvet_data/ -exp_cov auto -min_contig_lgth 100 2> velvetg.err.out 1> velvetg.std.out

Best
-Jonathan

[Haneko]

Hi,

I'm also trying out velvet with Illumina paired-end reads. A few problems I'm facing right now:

1. What should the input be like? I have read 1 and read 2 for the paired-end reads. Do I combine them into one file?

2. How do I run velvetg? The manual states that if insert size is not specified it will attempt to measure it for me. If that's the case do I still need to put -ins_length in my command? I do not know both the expected coverage and the insert size.

3. While testing, I can't seem to direct the console output of velvet into any file. So for example:
velvetg velvet_data/ -exp_cov auto -min_contig_lgth 100 &> velvetg.out

This give no output whatsoever in the velvetg.out file, neither on the console.

[jvhaarst]

Curtain

You could give Curtain a try.
From the wiki:

Curtain is a Java wrapper around next-generation assemblers such as Velvet which allows the incremental introduction of read-pair information into the assembly process. This enables the assembly of larger genomes than would otherwise be possible within existing memory constraints.

[Jonathan]

Well, you could potentially denovo each lane on its own,
and then add the contigs as 'long' sequence type for subsequent runs;

Just an idea, I'd yet have to try it myself;
Only problem I see: You loose coverage information for resolving 'bubbles';
I'm not sure how exactly 'long' type sequence data is handled in the velvet algorithm...

best
-Jonathan

[strob]

genome sequencing

[wangchy]

What kind of data are you working, transcriptome or random genome sequencing.

[strob]

Dear all,

I just received 1 Flow cell of illumina plant sequencing data (75bp PE reads, ~2 X 26 million reads/lane). As we don't have in most cases a reference sequence available, I will have to do some de novo assembly.
I started doing some tests using velvet. First I did an assembly on 1 lane, next I combined 2 lanes. In att you can see the virtual memory that was used during this process (I only show the velvetg part as this was the hardest to do) (horizontal you see the time needed, vertical you have the G of RAM needed). As you can see, the more datasets you combine, the more memory that you need (additive). As I have 14 sets to combine, I will never be able to perform this assembly using velvet (2 lanes already required 91G of RAM).

My questions:
- is there an other way to use velvet (to reduce this memory issue)?
- Are there other (well performing) assembly tools that use less memory? (I tested the CLCBio assembly tool and this one requires much less memory. But, this is of course a commercial tool)
- All suggestions are welcome

Thanks

Steven