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

Add FAQ entry re identification of possible duplicates reads/pairs #631

Merged
merged 3 commits into from
Mar 20, 2024

Conversation

TomSmithCGAT
Copy link
Member

I've added two entries to the FAQ to explain how possible duplicate reads are identified and why the output of dedup can appear to contain reads with the same coordinates. I don't find this easy to explain clearly, so very happy to take suggested edits!

See #555 for an example motivation, though I feel like this has come up a few times in issues.

@IanSudbery
Copy link
Member

@TomSmithCGAT Had a bit of a tweak (might have gotten carried away)

@TomSmithCGAT
Copy link
Member Author

Not got carried away at all - I think this is perfect! I had something very similar in mind, but was too lazy to do it!

I'm happy if we merge this now.

@TomSmithCGAT TomSmithCGAT merged commit ed9965f into master Mar 20, 2024
6 checks passed
@TomSmithCGAT TomSmithCGAT deleted the ts_update_faq_define_duplicates branch March 20, 2024 09:52
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

Successfully merging this pull request may close these issues.

2 participants