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

How to use spades and set minimum coverage #215

Closed
Stupid747 opened this issue Mar 14, 2018 · 4 comments
Closed

How to use spades and set minimum coverage #215

Stupid747 opened this issue Mar 14, 2018 · 4 comments

Comments

@Stupid747
Copy link

Thanks for a great program. I’m new at linux and ariba so this might be stupid question. I wonder what is the command for setting spades as the assembler when performing a run.

I thought it was “ariba run [--assembler spades] ref reads_1.fq reads_2.fq output_dir

but I get error argument.

I also wonder if its possible to set a minimum coverage? We experience carryover between some sample when doing multiplexing in Illumina and we get a hit on genes we know are wrong, with few reads (around 5-10) and ctg_cov around 1-2.

Thanks for the help

@martinghunt
Copy link
Collaborator

Re spades: that command looks correct. What error do you get? But in any case, unless you have a compelling reason for using spades, I recommend using the default assembler instead.

Re min coverage: you can filter the output file on the ctg_cov column, which is the mean read depth across the contig.

@Stupid747
Copy link
Author

when running the command I get

"ariba: error: unrecognized arguments: reads_2.fq output_dir

@martinghunt
Copy link
Collaborator

What was the exact command that you ran?

@kpepper
Copy link
Member

kpepper commented Apr 3, 2019

This issue would have been caused by a mismatch/error in the program arguments provided. Closing due to age.

@kpepper kpepper closed this as completed Apr 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants