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

CallOverlappingConsensusBases vs "consensus-call-overlapping-bases" in CallDuplexConsensusReads #886

Closed
gevro opened this issue Nov 24, 2022 · 2 comments

Comments

@gevro
Copy link

gevro commented Nov 24, 2022

Hi,
What is the difference between:
CallOverlappingConsensusBases tool
vs
"consensus-call-overlapping-bases" in CallDuplexConsensusReads tool
?

The former tool has two options: agreement-strategy and disagreement-strategy

But these options are not available in the CallDuplexConsensusReads tool.

What strategy is used by CallDuplexConsensusReads "consensus-call-overlapping-bases" option? And is there a way to change options there?

Also, I'm assuming that running both of these in the pipeline is not recommended?

Thanks

@tobyaicher
Copy link

Hi,

I wanted to follow-up on this issue as I am also interested in the answer.

Thanks

@nh13
Copy link
Member

nh13 commented Feb 21, 2025

The CallDuplexConsensusReads tools use the Consensus agreement and disagreement strategies. We do not expose both as command line options to the tool, like we do for CallOverlappingConsensusBases .

Running both of these is not recommended. Pick one, and only CallOverlappingConsensusBases if you want to explore different agreement and disagreement strategies.

If you want a different strategy for CallDuplexConsensusReads, feel reach out and we may be able to help if you'd be willing to provide some motivating examples.

Also, feel free to re-open if this doesn't answer the question.

@nh13 nh13 closed this as completed Feb 21, 2025
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

3 participants