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

Merge separate amplicons for a single sample #553

Closed
donkirkby opened this issue Apr 3, 2020 · 2 comments
Closed

Merge separate amplicons for a single sample #553

donkirkby opened this issue Apr 3, 2020 · 2 comments

Comments

@donkirkby
Copy link
Member

Currently, HCV samples are sequenced and combined from two separate MiSeq samples: a whole-genome sample, and a MIDI sample. The new protocol for SARS-CoV-2 will combine about ten smaller amplicons with overlap. Try to trim the primers, as described in #552, then combine overlapping regions, and report on differences in the overlaps as a QC step. Also think through how this will work for the assembled version.

@donkirkby donkirkby added this to the 7.13 milestone Apr 3, 2020
@cbrumme
Copy link

cbrumme commented Apr 4, 2020

Correction to the above: SARS-CoV-2 genomes may be sequenced as ~100 overlapping amplicons (not 10). These amplicons may be provided in two ways

  1. A single set of paired fastq files containing reads from the overlapping amplicons
  2. Two sets of paired fastq files. The reads within each set of fastq files would NOT overlap

@donkirkby
Copy link
Member Author

In every SARS-CoV-2 run so far, we combined both PCR primer pools into a single "sample" prior to sequencing. Performance so far has been such that it probably won't be necessary to sequence the two pools separately and make micall combine the two sets of fastqs.

Closing the issue as won't fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants