Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Got "No disjointigs were assembled" error when running denovo #17

Closed
bsalehe opened this issue Aug 4, 2023 · 1 comment
Closed

Got "No disjointigs were assembled" error when running denovo #17

bsalehe opened this issue Aug 4, 2023 · 1 comment

Comments

@bsalehe
Copy link

bsalehe commented Aug 4, 2023

I have tried to run the pipeline with single ONT sample on WSL2 with singularity profile denovo i.e. running with flye assembler. The sample appears to have high coverage. It is from bacteria with 4mb genome size. Further investigation in the .nexflow.log file indicated it is a flye related error which seemed to be the case as reported here.

I manually configured the flye command in the 'main.nf' file by adding the --asm-coverage and --genome-size options which didn't throw that error anymore only threw a memory error.

Would it be convenient to add in the advanced options additional parameters in the pipeline for running flye like it is recommended here in a similar way you hva done for running prokka or medaka which are available in the pipeline usage help (nextflow run epi2me-labs/wf-bacterial-genomes --help)?

Note:
The solution given in the flye issue above require to add additional paramter --genome-size <value> as shoen in the current flye usage doc.

Thank you!

@bsalehe bsalehe changed the title Pipeline failed to assemble ONT single sample with very high coverage Got "No disjointigs were assembled" error when running denovo Aug 4, 2023
@cjalder
Copy link

cjalder commented Aug 18, 2023

Hi @bsalehe thanks for raising this. We'll try and implement these for a future update.

In regards to the memory issue, you can pass a config file to increase the memory (if your machine has more resources available) by following the instructions in this issue.

@cjalder cjalder closed this as completed Aug 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants