Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Allow partial hugemem node usage #10

Merged
merged 2 commits into from
Jan 26, 2023
Merged

Allow partial hugemem node usage #10

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9fa37ee
Remove hugemem "uses entire nodes" help text
lukew3 Jan 24, 2023
7b3610c
Add min/max cores for different node_types
lukew3 Jan 24, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 17 additions & 5 deletions form.yml.erb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,17 +44,29 @@ attributes:
help: |
- **any** - (*1-28 cores*) Use any available Owens node. This reduces the
wait time as there are no node requirements.
- **hugemem** - (*48 cores*) Use an Owens node that has 1.5TB of
- **hugemem** - (*4-48 cores*) Use an Owens node that has 1.5TB of
available RAM as well as 48 cores. There are 16 of these nodes on
Owens. Requesting hugemem nodes allocates entire nodes.
Owens.
- **vis** - (*1-28 cores*) Use an Owens node that has an [NVIDIA Tesla P100
GPU](http://www.nvidia.com/object/tesla-p100.html) with an X server
running in the background. This utilizes the GPU for hardware
accelerated 3D visualization. There are 160 of these nodes on Owens.
options:
- "any"
- "hugemem"
- "vis"
- [
"any", "any",
data-min-num-cores: 1,
data-max-num-cores: 28,
]
- [
"hugemem", "hugemem",
data-min-num-cores: 4,
data-max-num-cores: 48,
]
- [
"vis", "vis",
data-min-num-cores: 1,
data-max-num-cores: 28,
]
version:
widget: select
label: "Schrodinger version"
Expand Down