[go: nahoru, domu]
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

Question: rationale duplication detection #203

Open
aistBMRG opened this issue Oct 24, 2019 · 1 comment
Open

Question: rationale duplication detection #203

aistBMRG opened this issue Oct 24, 2019 · 1 comment

Comments

@aistBMRG
Copy link

Hi,

Thanks for developing fastp - it is does everything and fast!

Small question regarding the duplication detection. From the paper on fastp, and if I am understanding correctly, it seems that the first 12bp of read1 and first 32bp of read2 are used for detection of duplicated fragments (PE mode). Would it be possible to clarify the rationale for these values, for example, why is it asymmetric or why 12 and 32 bps?

Thanks in advance.

Dieter
@sfchen
Copy link
Member
sfchen commented Oct 31, 2019 •
edited
Loading

Actually it is just due to programming convenience.

I use 12bp (24 bits) as key and 32bp (64bits) as value to make a map for computing dup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aistBMRG @sfchen