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

Combining ASV and Taxonomy tables #1076

Closed
hpremathilake opened this issue Jul 15, 2020 · 3 comments
Closed

Combining ASV and Taxonomy tables #1076

hpremathilake opened this issue Jul 15, 2020 · 3 comments

Comments

@hpremathilake
Copy link

Hi,
I have a large dataset to analyze. I'm thinking of breaking it down into segments, analyze it, and later combine the ASV and Taxonomy tables (from the different analysis attempts into a single large ASV and Taxomonoy table), since I'm trying to do the analysis on my PC until I get my HPCC account setup.

Hence, I want to know whether this method is technically correct?

Thank you.
Best,
Hasitha.

@benjjneb
Copy link
Owner

Yes you can do that.

In an ideal world you perform chimera removal and taxonomy assignment on the whole dataset together to avoid any stochastic differences between chunks though. You might be surprised on what you can run on your laptop. But yes there will be datasets that get too big for that on a laptop.

@hpremathilake
Copy link
Author

Thank you for the prompt response, Benjamin.
Attached are the error plots generated for the data. Do you think the predicted and actual error rates overlap enough?
I have seen better fitting graphs in my previous analyses. Hence, thought of getting your opinion on this.

F_errors.pdf
R_errors.pdf

@benjjneb
Copy link
Owner

benjjneb commented Jul 16, 2020

It's probably fine. These error model behavior is being seen when the underlying sequencing data is using "binned" quality scores. It's not ideal, but is unlikely to affect results much since very few quality scores occur in that dip in the error model (they are outside the binned values).

More discussion of this here, and a suggested fix to enforce monotonicity as well: #791

Edit: Also this comment has another suggested fix: #938 (comment)

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

2 participants