Closed jonhultqvist closed 7 years ago
This has been under quite active development over the past week or two. Give the latest a shot - it just ran a human from nanopore. No need to start from scratch, just restart canu or directly run unitigger.sh.
That was a fix for the issue: The assembly is now through the unitigger stage and into consensus building.
Thanks a bunch!
Hi, Thank you for developing this fine tool. Unfortunaley, we have been experiencing some problems with one of our assemblies. The dataset is about 5.0 Gbp of Oxford Nanopore 1D reads (from R9.5 pore, 1D^2 library but used as 1D reads only), basecalled using Albacore 1.0.2, trimmed 75 bp at either end and filtered to only have reads longer than 3 kb. The assembly appears to progress nicely until the unitigging stage where it fails. I have tried to re-launch it from where is failed without success. I also tried some changes to the settings, like increasing the memory allowed for the 'bat' stage without any effect. The Canu version is: Canu snapshot v1.5 +98 changes (r8298 ffb36aae9419bd600247237e8cfdb378b8fbedf2).
I have seen some similar issues in issue threads but not exactly at the unitigging stage. Could it be problematic reads that is causing this? In any case, I would very much appreciate your help in trying to figure of what could be going wrong here.
This is the shell script for launching Canu (UNIX system).
The error message in assembly log-file occurs in the unitigging stage.
From unitigging.err