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.

Sign up for GitHub

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

Jump to bottom

add to sample_coverage file the # of reads that map to Pf #69

Closed
jbriggs7 opened this issue Feb 23, 2023 · 1 comment
Closed

add to sample_coverage file the # of reads that map to Pf #69

jbriggs7 opened this issue Feb 23, 2023 · 1 comment
Assignees
@bgpalmer
Labels
enhancement New feature or request

Comments

@jbriggs7
Copy link

Currently I think the "Amplicons" output in the sample_coverage file is just telling you which reads have the correct primer sequences. However, that doesn't mean they actually map to Pf -- which is what is most useful to know. You can get this data out of the allele data file, but it would be nice to have it summarized in the sample_coverage file. Discussed w/Andres & he agrees
@jbriggs7 jbriggs7 added the enhancement New feature or request label Feb 23, 2023
@bgpalmer bgpalmer self-assigned this Feb 23, 2023
bgpalmer added a commit that referenced this issue Mar 7, 2023
@bgpalmer
sample coverage work (#69)
b2498d7
bgpalmer added a commit that referenced this issue Mar 7, 2023
@bgpalmer
append number of mapped amplicons to the sample coverage file (#69)
b3900a3
bgpalmer added a commit that referenced this issue Mar 9, 2023
@bgpalmer
paused
6a68ce2 
append number of mapped amplicons to the sample coverage file (#69)

sample coverage work (#69)
bgpalmer added a commit that referenced this issue Mar 10, 2023
@bgpalmer
paused
ca1a27f 
append number of mapped amplicons to the sample coverage file (#69)

sample coverage work (#69)
bgpalmer added a commit that referenced this issue Apr 4, 2023
@bgpalmer
update coverage files with Pf specific read coverage (#69)
9950606
@bgpalmer
Copy link
Contributor

merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bgpalmer bgpalmer

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bgpalmer @jbriggs7