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

Automatically get cores_per_node on single node #357

Merged
merged 3 commits into from
Apr 14, 2022

Conversation

xylar
Copy link
Collaborator

@xylar xylar commented Apr 14, 2022

For non-HPC machines, it's typically fine to just detect the number of available cores.

This should reduce the amount of information needed in a user config file.

For non-HPC machines, it's typically fine to just detect the
number of available cores.
@xylar
Copy link
Collaborator Author

xylar commented Apr 14, 2022

@matthewhoffman, I don't think you need to do any testing of this. It is only useful on a Mac or Linux machine. I just wanted to flag you because I pulled this out of #353 for clarity.

Copy link
Member

@matthewhoffman matthewhoffman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@xylar , thanks for flagging me. I glanced it over and it make sense. The one thing I looked for is that the docs explain how a user could specify this now that it's gone from the default cfg file (and, hence, a user might not realize this option exists). But you have that covered, so this looks good!

@xylar
Copy link
Collaborator Author

xylar commented Apr 14, 2022

Thanks @matthewhoffman!

@xylar xylar merged commit 25730ed into MPAS-Dev:master Apr 14, 2022
@xylar xylar deleted the auto_cores_per_node branch April 14, 2022 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants