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

Definition of good and bad overlapped read pairs #91

Open
SJJHK opened this issue Dec 11, 2023 · 0 comments
Open

Definition of good and bad overlapped read pairs #91

SJJHK opened this issue Dec 11, 2023 · 0 comments

Comments

@SJJHK
Copy link

SJJHK commented Dec 11, 2023

Thanks for the package!

We have an issue defining "good" and "bad" in the below lines in LARGE FONT and in BOLD extracted from the summary.txt. file of QoRTs' QC data.

OM_noOverlap_staggered 0 Number of read-pairs with no overlap, mis-staggered such that the fwd read occurs second.
OM_noOverlap_normal 1069491 Number of read-pairs with no overlap, arranged normally.
OM_overlap 22736461 Number of read-pairs with good overlap.
OM_BAD_OVERLAP 1929 Number of read-pairs with a bad overlap.
OM_overlap_Match 20928805 Number of read-pairs with a good overlap, and that match perfectly.
OM_overlap_mismatch 1807656 Number of read-pairs with a good overlap, but that contain one or more base mismatches.

I have looked for more detail in relation to the summary.txt file - is there somewhere I can find more detail for the summary text outputs?

Thanks in advance,
Sam

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