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

Single-strand mode is not appropriate with unmerged R2 reads #24

Open
stschiff opened this issue Feb 4, 2022 · 1 comment
Open

Single-strand mode is not appropriate with unmerged R2 reads #24

stschiff opened this issue Feb 4, 2022 · 1 comment

Comments

@stschiff
Copy link
Owner

stschiff commented Feb 4, 2022

We realised that the current damage model used in --singleStrandMode is not appropriate if the input pileup data contains alleles from unmerged R2 reads from paired-end sequencing. Currently, this means, that users should make sure their input data does not contain unmerged reads, should they use data from paired-end sequencing.

In the longer run, I need to come up with a solution that recognises R2 reads in the pileup and treats them as reverse complements. This is not possible with the pileup-format produced by samtools mpileup, which is currently the only input format that pileupCaller accepts.

@stschiff
Copy link
Owner Author

stschiff commented Mar 8, 2024

I have for now added a line to the README, and might pick this up in the future

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

1 participant