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

Does CallMolecularConsensusReads handle overlapping fragments? #926

Open
kcibul opened this issue Aug 7, 2023 · 1 comment
Open

Does CallMolecularConsensusReads handle overlapping fragments? #926

kcibul opened this issue Aug 7, 2023 · 1 comment
Labels

Comments

@kcibul
Copy link

kcibul commented Aug 7, 2023

In the docs for CallMolecularConsensusReads it says:

Also, this tool calls each end of a pair independently, and does not jointly call bases that overlap within a pair

However later on in the usage there is a flag (true by default)

--consensus-call-overlapping-bases

What does this parameter enable (and how does that align with the statement in the docs?

@nh13
Copy link
Member

nh13 commented Aug 7, 2023

This feature was added here: #805. The goal was to have a tool that would take individual raw read pairs and if the read and its mate overlap, modify (consensus call) the bases that overlap to agree (or mask) on each read pair independently. Fine-grained control is given in the OverlappingBasesConsensusCaller tool to decide strategies for when the read and mate agree/disagree in the template, while both CallMolecularConsensusReads and CallDuplexConsensusReads have a single opt-in option.

For the CallMolecularConsensusReads tool, the input raw read pairs are independently examined to see if each read and its mate overlap and then pre-process those read pairs. Those read pairs are then fed into the downstream (molecular or duplex) consensus calling step as before. So really it's a pre-processing step for convenience in the tool, rather than being part of the consensus calling step. Conceptually this is the same as piping the output of OverlappingBasesConsensusCaller into CallMolecularConsensusReads (without the --consensus-call-overlapping-bases)

@nh13 nh13 added the question label Aug 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants