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

call consensus threads #465

Open
PedalheadPHX opened this issue Jul 31, 2022 · 1 comment
Open

call consensus threads #465

PedalheadPHX opened this issue Jul 31, 2022 · 1 comment

Comments

@PedalheadPHX
Copy link
Member

fgbio --tmp-dir {{ temp_dir }}/fgbio_tmp CallMolecularConsensusReads \

This tool looks to be running on one CPU only even with 4 assigned, there is a --threads option and it defaults to 1 so what we see with htop makes sense but maybe the threads option reduces the runtime.

threads |   | Int | The number of threads to use while consensus calling. | Optional | 1 | 1

@PedalheadPHX
Copy link
Member Author

So this option is new to the v2.x fgbio releases, so for future update in tempe I suspect that become fully dynamic. Should review fulcrum recommendations before updates (https://github.com/fulcrumgenomics/fgbio/blob/main/docs/best-practice-consensus-pipeline.md)

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