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

DADA2 analysis for two different platforms MISEQ and Novaseq -Merging of sequence table #2018

Open
Jayakanthankk opened this issue Sep 13, 2024 · 2 comments

Comments

@Jayakanthankk
Copy link

I have sequenced V3V4 region 50 samples in each by two platforms MISEQ and Novaseq and two different formats 2x250 and 2x300 bp. Is possible to merge sequences from both runs and construct sequence tables, followed by assigning taxonomy. Basically all samples of same cohort. How to analyses and what codes required for this.

@benjjneb
Copy link
Owner

Yes, as long as the primer sets you are using are the same you can simply merge ASVs across those sequencing types.

@Jayakanthankk
Copy link
Author

Jayakanthankk commented Sep 26, 2024

We have sequenced V3-V4 region in two platforms: Miseq 2x250 bp (batch1) and Novaseq 2x300 bp (batch2), not samples and but same cohort. I have trimmed fastq files of Novaseq to 250 bp. I have pooled both data and analyzed it at the same time. I have trim 17 and 21 base pairs to remove primers that are present in samples. The problem here is that each ASV count was present in either of the data sequences. For example, ASV1 is present only in Miseq reads but not in Novaseq, and for ASV2, it is vice versa. Even though primers were the same, ASV generate behaves differently and is platform-specific. What would be the reason for this and how to overcome this issue?

Screenshot 2024-09-27 162922

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