Just wondering if you might be able to offer some insight as to what might
be going with our runs of ray. We are assembly a large eukaryotic genome
and have been using both Ray and Celera to do so. Initially, Ray gave us
some great results and increasing kmer values up to 31-kmer readily
improved our assemblies. We then ran into a memory wall and got some folks
to help us out running things off site. We were able to run a 33-kmer run
on the same set, but it looked worse than the 31-kmer run. Additionally,
longer runs of say 61-kmers have looked even worse. Genome should be around
30-40x coverage, I think, with Hi-seq and Mi-seq data (2x150 and 2x250
paired-end libraries, each heavily trimmed to get rid of anything
suspicious) and we thought we'd still have some room to increase kmer sizes
>31 to improve the assembly. Any thoughts on what might be going on here?
Did we possibly compile the program incorrectly for larger kmer sizes? Ever
see something similar?
Thanks in advance for any thoughts on the matter.
Cheers,
Nate
------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Denovoassembler-users mailing list
Denovoassembler-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/denovoassembler-users
