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.

Sign up for GitHub

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

Jump to bottom

Defining threads via variable instead of hardcoding. #360

Open
rajwanir opened this issue Nov 25, 2024 · 0 comments · May be fixed by #361
Open

Defining threads via variable instead of hardcoding. #360

rajwanir opened this issue Nov 25, 2024 · 0 comments · May be fixed by #361
Assignees
@rajwanir
Labels
CLI Command line interface submission Anything related to cluster submission

Comments

@rajwanir
Copy link

Some rules use large number of threads (~44). Not all HPC systems would have such nodes. The max_threads option was introduced in PR #346. Howver, the rules still remains hardcoded to 44. Using a variable would be bettter choice.
@rajwanir rajwanir self-assigned this Nov 25, 2024
@rajwanir rajwanir added CLI Command line interface submission Anything related to cluster submission labels Nov 25, 2024
@rajwanir rajwanir linked a pull request Nov 25, 2024 that will close this issue
Threads via variable. #361
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rajwanir rajwanir

Labels
CLI Command line interface submission Anything related to cluster submission
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Threads via variable. NCI-CGR/GwasQcPipeline
1 participant
@rajwanir