Switch to PBS_NP for determining OMP threads#517
Merged
hyschive merged 1 commit intogamer-project:mainfrom Apr 6, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue
When specifying node names via
qsub(e.g.,-lnodes=spock26:ppn=32), the PBS environment variablesPBS_NUM_NODESandPBS_NUM_PPNincorrectly return0and1, respectively, rather than the expected values1and32. This behavior then leads to an incorrect automatic determination of the number of OpenMP threads inInit_ResetParameter().This is likely a bug in
TORQUE.Solution
Switching
PBS_NP, which returns the total number of requested CPU cores, resolves the issue.