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

Improve documentation for NUM_CPU #8405

Merged
merged 1 commit into from
Aug 7, 2024

Conversation

berland
Copy link
Contributor

@berland berland commented Aug 6, 2024

Don't mention any longer requirements for Torque, which are now deprecated.

Issue
Resolves #8403

Approach
✍🏻

  • PR title captures the intent of the changes, and is fitting for release notes.
  • Added appropriate release note label
  • Commit history is consistent and clean, in line with the contribution guidelines.
  • Make sure tests pass locally (after every commit!)

When applicable

  • When there are user facing changes: Updated documentation
  • New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
  • Large PR: Prepare changes in small commits for more convenient review
  • Bug fix: Add regression test for the bug
  • Bug fix: Create Backport PR to latest release

@berland berland self-assigned this Aug 6, 2024
@berland berland added release-notes:misc Automatically categorise as miscellaneous change in release notes documentation labels Aug 6, 2024
@codecov-commenter
Copy link

codecov-commenter commented Aug 6, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.88%. Comparing base (c2c02b2) to head (e1e0c43).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #8405      +/-   ##
==========================================
- Coverage   90.88%   90.88%   -0.01%     
==========================================
  Files         347      347              
  Lines       21078    21078              
==========================================
- Hits        19157    19156       -1     
- Misses       1921     1922       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Comment on lines 272 to 273
exclusiveness on the compute node. If set incorrectly, there is no guarantee
that the realization will fail.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
exclusiveness on the compute node. If set incorrectly, there is no guarantee
that the realization will fail.
exclusiveness on the compute node. If set incorrectly, there is no guarantee
that the realization will run.

Is this correct?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Nope. You are lucky if you are able to fail your realization by specifying wrong cpu count. We had only a few failures when num_cpu was missing altogheter in the lsf_driver and hundreds of multi-cpu Eclipse runs were running and all of them said to the LSF system what "I only need 1 cpu".

Copy link
Contributor

@jonathan-eq jonathan-eq left a comment

Choose a reason for hiding this comment

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

Very nice!
See minor question 📝

Copy link
Contributor

@jonathan-eq jonathan-eq left a comment

Choose a reason for hiding this comment

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

LGTM!

@berland
Copy link
Contributor Author

berland commented Aug 7, 2024

@sondreso any comment?

Copy link
Collaborator

@sondreso sondreso left a comment

Choose a reason for hiding this comment

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

Except for the small comment from @jonathan-eq, this LGTM!

Don't mention any longer requirements for Torque, which
are now deprecated.
@berland berland merged commit 104e1ee into equinor:main Aug 7, 2024
37 checks passed
@berland berland deleted the improve_num_cpu_docs branch August 23, 2024 07:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation release-notes:misc Automatically categorise as miscellaneous change in release notes
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Rewrite documentation on NUM_CPU
4 participants