You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
In the docs for
CallMolecularConsensusReads
it says:However later on in the usage there is a flag (true by default)
What does this parameter enable (and how does that align with the statement in the docs?
The text was updated successfully, but these errors were encountered: