Closed lborcard closed 1 month ago
Just to complete my question, these are amplicons with 50K+ reads .
There was an issue in v2.2 correcting reads less than 500bp, see https://github.com/marbl/canu/issues/2182. You can either use the latest tip of canu or wait for a release of v2.3 which should be done in the next couple of weeks.
Thank you very much, I will update it then. Thanks for the work.
Question answered
I have tried to find a way to use the dev branch but the github docs say that it is not possible to compile from the github version and I really need to use the current updates how could I implement the newest changes? @skoren
The docs say that it is not possible to compile from downloaded .zip source code, but it should work if the repository is cloned; have you tried that?
Yes, @gringer is correct. You can checkout and compile the latest unreleased code following the instructions here: https://github.com/marbl/canu?tab=readme-ov-file#install. Starting with git clone
.
Ok I managed to compile from the repo into a singularity container (ubuntu), but now I am getting this error
ABORT:
ABORT: canu snapshot v2.3-development +162 changes (r10433 c61ebbb7a5f90abb9c034650e2fd95642138de31)
ABORT: Don't panic, but a mostly harmless error occurred and Canu stopped.
ABORT: Try restarting. If that doesn't work, ask for help.
ABORT:
ABORT: failed to find the number of jobs in 'unitigging/0-mercounts/meryl-count.sh'.
ABORT:
Any idea if it's something on my end?
thanks a lot for the support,
Can you open a new issue and post the command you're using and the full canu output, including the report file it generates?
Alright, I opened a new issue, thanks for the support!
Dear Canu team,
We had contacted you last year regarding the assembly of amplicon and you had kindly answered. Our test with amplicon of size>1000 showed promising results. We now tested we new data of amplicon ~400bp and the output is more erratic but mostly empty. We are getting this error message for certain samples while do produce a contig file:
canu v2.2
System: Centos, ran within nextflow.
thanks for the help