Question: Allpaths-LG is stuck on CloseUnipathGraphs?
1
gravatar for Craig Jackson
4.4 years ago by
Bloomington, IN
Craig Jackson30 wrote:

I am working on a de novo assembly with Allpaths-LG. I have a 300bp paired-end Illumina MiSeq run with ~400-500 bp fragment size for the overlapping fragment library (~50X), and several 100bp Illumina Hiseq jumping libraries (250bp, 500bp, 2kb, 5kb, 10kb). Allpaths overlaps the Miseq fragment library well, with 99% overlap (I also verified overlaps with PEAR program).

I am running allpaths with 12 threads on a machine with 2 Intel Xeon X5660, and 192 GB of RAM available - so the machine is decent, and I'm the only user utilizing the machine. 

When Allpaths gets to the CloseUnipathGaps module, it is seeming to get hung up on the "Building those extenders" step. Allpaths ran on this building extenders step for 6 days before I decided to stop it, and try again. The second run is also stuck here for a day now. In other peoples' allpaths logs I have seen, this step only takes a couple minutes to complete.


--------------------------------------------------------------------------------
Mon Nov 24 18:20:08 2014 run on d017, pid=25701 [Jun  5 2014 15:37:46 R49856 ]
CloseUnipathGaps NUM_THREADS=12                                                \
                 DIR=/data/FG-183/pulicaria/allpaths-assembly2/run1            \
                 IN_HEAD=frag_reads_corr_cpd                                   \
                 UNIBASES=filled_reads.unibases.k96 UNIBASES_K=96              \
                 USE_LINKS=False OUT_HEAD=filled_reads.gap_closed WORKDIR=tmp  \
                 MM=True _MM_INTERVAL=10 _MM_SUMMARY=False                     \
                 _MM_OUT=/data/FG-183/pulicaria/allpaths-assembly2/run1/makein \
                 fo/filled_reads.gap_closed.CloseUnipathGaps.log.mm.CloseUnipa \
                 thGaps
--------------------------------------------------------------------------------
Mon Nov 24 18:20:23 2014: Finding seeds for unipath gaps
Mon Nov 24 18:20:23 2014: Creating KmerParcel files for FindUnipathGapSeeds
Mon Nov 24 18:20:23 2014: n_reads = 22919962
Mon Nov 24 18:21:56 2014: Creating seeds...
Mon Nov 24 18:21:56 2014: compute seeds[query_ID].size() for each query_ID.
Mon Nov 24 18:22:03 2014: reserve space for seeds[query_ID].
Mon Nov 24 18:22:04 2014: store seeds in seeds[query_ID].
Mon Nov 24 18:22:12 2014: 22919962 number of reads processed.
Mon Nov 24 18:22:12 2014: 46415402 seeds created.
Mon Nov 24 18:22:33 2014: Creating KmerParcel files for FindUnipathGapSeeds
Mon Nov 24 18:22:33 2014: n_reads = 22919962
Mon Nov 24 18:24:00 2014: Creating seeds...
Mon Nov 24 18:24:00 2014: compute seeds[query_ID].size() for each query_ID.
Mon Nov 24 18:24:06 2014: reserve space for seeds[query_ID].
Mon Nov 24 18:24:07 2014: store seeds in seeds[query_ID].
Mon Nov 24 18:24:15 2014: 22919962 number of reads processed.
Mon Nov 24 18:24:15 2014: 46685568 seeds created.
Mon Nov 24 18:24:37 2014: Loading read quality scores so we can build extenders
Mon Nov 24 18:24:45 2014: Building those extenders

Sun Nov 30 15:11:45 2014.  Interrupt received (perhaps a ctrl-c).  Stopping.

 

I had previously run Allpaths on the Illumina Hiseq jumping library data only, without the MiSeq library, and this problem was not encountered during that assembly. Only with the addition of the MiSeq library did this issue appear.

Does anyone have experience with Allpaths and have any suggestions? Do you think the 2x300 MiSeq library is too much for Allpaths to handle? (I know the fragment library code is designed for 2x100 reads with 180bp)

I'd like to be able to try out Allpaths for this assembly. But if it can't complete, I do have the merged overlapping MiSeq reads from PEAR paired-end merger - so I can try out other assemblers, using the merged MiSeq reads as single-end reads. Any recommendations on this front are also appreciated.

assembly genome • 2.0k views
ADD COMMENTlink modified 4.0 years ago • written 4.4 years ago by Craig Jackson30
2
gravatar for Craig Jackson
4.0 years ago by
Bloomington, IN
Craig Jackson30 wrote:

This was never resolved, and several others have reported similar problems with Allpaths getting stuck on this module when using MiSeq 250bp data on the Allpaths-LG google forum:
https://groups.google.com/a/broadinstitute.org/forum/?hl=en&fromgroups#!topic/allpaths-user-forum/f9JlWPfftUQ
and
https://groups.google.com/a/broadinstitute.org/forum/?hl=en&fromgroups#!topic/allpaths-user-forum/Cbcxc2suvJA
and
https://groups.google.com/a/broadinstitute.org/forum/?hl=en&fromgroups#!topic/allpaths-user-forum/WRjpBg8wuRI

At the advice from Allpaths-LG forum, I just disabled the CloseUnipathGaps module using CLOSE_UNIPATH_GAPS=False, as it was stated this doesn't affect the quality of assembly much at all.
Without this module, Allpaths-LG was able to finish the assembly process.

ADD COMMENTlink written 4.0 years ago by Craig Jackson30
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 2.3.0
Traffic: 692 users visited in the last hour