You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Its my first time using unicycler (conda v0.4.7) for hybrid nanopore/illumina assembly of a 5.5Mb bacterial genome. The analysis always hangs at the same point: when creating simple long read bridges. When evaluating simple loops, after scoring loops 1 to 3, it produces no further output in the simple_bridging folder , except for previous output all_segments.fasta. There is no error message and seemingly no progress; after 24 hours the cluster kills the job.
I've attempted several fixes but they were all unsuccessful: using a fresh conda install of older unicycler version 0.4.4, using a single thread instead of 12, subsampling my nanopore reads to min length 5000bp, running bold mode, skipping minasm steps, and using an input canu assembly of 17 contigs instead of nanopore reads. I also didn't find a solution in issue number #118
Partial logfile is below:
Creating SPAdes contig bridges (2019-04-22 13:44:28)
SPAdes uses paired-end information to perform repeat resolution (RR) and produce
contigs from the assembly graph. SPAdes saves the graph paths corresponding to these
contigs in the contigs.paths file. When one of these paths contains two or more anchor
contigs, Unicycler can create a bridge from the path.
Creating loop unrolling bridges (2019-04-22 13:44:28)
When a SPAdes contig path connects an anchor contig with the middle contig of a
simple loop, Unicycler concludes that the sequences are contiguous (i.e. the loop is
not a separate piece of DNA). It then uses the read depth of the middle and repeat
contigs to guess the number of times to traverse the loop and makes a bridge.
Creating simple long read bridges (2019-04-22 13:45:42)
Unicycler uses long read alignments (from minimap) to resolve simple repeat
structures in the graph. This takes care of some "low-hanging fruit" of the graph
simplification.
Aligning long reads to graph using minimap
Saving /gpfs/fs0/scratch/d/dguttman/pstapton/temp/b/unicycler_output_100419/simple_bridging/all_segments.fasta
Number of minimap alignments: 187126
Two-way junctions are defined as cases where two graph contigs (A and B) join
together (C) and then split apart again (D and E). This usually represents a simple
2-copy repeat, and there are two possible options for its resolution: (A->C->D and
B->C->E) or (A->C->E and B->C->D). Each read which spans such a junction gets to "vote"
for option 1, option 2 or neither. Unicycler creates a bridge at each junction for the
most voted for option.
Simple loops are parts of the graph where two contigs (A and B) are connected via a
repeat (C) which loops back to itself (via D). It is possible to traverse the loop zero
times (A->C->B), one time (A->C->D->C->B), two times (A->C->D->C->D->C->B), etc. Long
reads which span the loop inform which is the correct number of times through. In this
step, such reads are found and each is aligned against alternative loop counts. A reads
casts its "vote" for the loop count it agrees best with, and Unicycler creates a bridge
using the most voted for count.
Its my first time using unicycler (conda v0.4.7) for hybrid nanopore/illumina assembly of a 5.5Mb bacterial genome. The analysis always hangs at the same point: when creating simple long read bridges. When evaluating simple loops, after scoring loops 1 to 3, it produces no further output in the simple_bridging folder , except for previous output all_segments.fasta. There is no error message and seemingly no progress; after 24 hours the cluster kills the job.
I've attempted several fixes but they were all unsuccessful: using a fresh conda install of older unicycler version 0.4.4, using a single thread instead of 12, subsampling my nanopore reads to min length 5000bp, running bold mode, skipping minasm steps, and using an input canu assembly of 17 contigs instead of nanopore reads. I also didn't find a solution in issue number #118
Partial logfile is below:
The text was updated successfully, but these errors were encountered: