You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: kempner_computing_handbook/s1_high_performance_computing/development_and_runtime_envs/software_module_and_environment_management.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,4 +44,4 @@ Each module is defined by a script that runs when the module is loaded. This scr
44
44
45
45
These changes to the terminal environment will persist until `module unload <module_name>` or `module purge` is called. They act independently of other modifications to environment variables, namely virtual environments.
46
46
47
-
You can read more about modules at the [Lmod documentation](https://lmod.readthedocs.io/).
47
+
You can read more about modules at the [Lmod documentation](https://lmod.readthedocs.io/en/latest/).
Copy file name to clipboardExpand all lines: kempner_computing_handbook/s1_high_performance_computing/efficient_use_of_resources/fair_use_and_prioritization_policies.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@
5
5
6
6
The Kempner cluster uses a system called fairshare to determine prioritization and which jobs run when. The fairshare algorithm prioritizes a balanced allocation of resources, aimed at facilitating the timely completion of tasks from various user groups. This means that jobs, particularly those that are resource intensive or are being run in labs with high recent usage, may not run immediately or on demand.
7
7
8
-
As an approved user of the Kempner cluster, you will be part of one or more [fairshare groups (called slurm accounts)](resource_management:understanding_slurm:slurm_accounts), through which you receive a share of the cluster resources. For more information, please see the [Cluster Governance guidelines](https://sites.harvard.edu/kempner/computing/).
8
+
As an approved user of the Kempner cluster, you will be part of one or more [fairshare groups (called slurm accounts)](resource_management:understanding_slurm:slurm_accounts), through which you receive a share of the cluster resources. For more information, please see the [Cluster Governance guidelines](https://kempnerinstitute.harvard.edu/kempner-community/).
9
9
10
10
```{tip}
11
11
One common misconception around fairshare is that a given user or lab should have access at any given moment to exactly "their share" of the cluster. Instead, fairshare guarantees access to resources averaged over a period of several months. At any given moment, a user or lab may be using a greater or lesser amount of their available share.
Copy file name to clipboardExpand all lines: kempner_computing_handbook/s1_high_performance_computing/kempner_cluster/kempner_policies_for_responsible_use.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ If your job exceeds this predefined limit, please adhere to the following guidel
33
33
- Use a run-time limit to prevent large jobs from running for a long period of time unexpectedly.
34
34
- Consider running the job with a smaller number of GPUs over a longer time-period.
35
35
36
-
If none of the above strategies will work, users should submit a reservation request (see [Cluster Governance Guideline](https://sites.harvard.edu/kempner/computing/)) so that large projects can be planned and communicated to the community, limiting disruptions for other users.
36
+
If none of the above strategies will work, users should submit a reservation request (see [Cluster Governance Guideline](https://kempnerinstitute.harvard.edu/kempner-community/)) so that large projects can be planned and communicated to the community, limiting disruptions for other users.
Copy file name to clipboardExpand all lines: kempner_computing_handbook/s1_high_performance_computing/kempner_cluster/overview_of_kempner_cluster.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,17 +46,17 @@ This is a diagram of the GPU racks and network core.
46
46
47
47
## Can I buy into the Kempner Institute AI Cluster?
48
48
49
-
If you have a Kempner Institute affiliation, you may request to contribute funds towards a Kempner cluster purchase. If you contribute funds we will increase your priority on the cluster to reflect the proportion of the cluster you have contributed. Please see the Cluster Governance guidelines for more information: https://sites.harvard.edu/kempner/computing/
49
+
If you have a Kempner Institute affiliation, you may request to contribute funds towards a Kempner cluster purchase. If you contribute funds we will increase your priority on the cluster to reflect the proportion of the cluster you have contributed. Please see the Cluster Governance guidelines for more information: https://kempnerinstitute.harvard.edu/kempner-community/
50
50
51
51
## How is priority set on the Kempner Institute AI Cluster?
52
52
53
-
Priority is set through Fairshare scheduling. For more information, please see the Cluster Governance guidelines: https://sites.harvard.edu/kempner/computing/
53
+
Priority is set through Fairshare scheduling. For more information, please see the Cluster Governance guidelines: https://kempnerinstitute.harvard.edu/kempner-community/
54
54
55
55
56
56
## Can I reserve GPUs on the Kempner Institute AI Cluster?
57
57
58
-
Generally we hope to have enough GPUs available on the cluster for most use cases. However, for situations in which you need a large number of GPUs that are dedicated for a period of time, or need a smaller subset for a longer period of time, you can make a reservation request. Please see the full governance guidelines for further details: https://sites.harvard.edu/kempner/computing/
58
+
Generally we hope to have enough GPUs available on the cluster for most use cases. However, for situations in which you need a large number of GPUs that are dedicated for a period of time, or need a smaller subset for a longer period of time, you can make a reservation request. Please see the full governance guidelines for further details: https://kempnerinstitute.harvard.edu/kempner-community/
59
59
60
60
## Where is the Kempner Institute AI Cluster located physically?
61
61
62
-
The cluster is located at the [Massachusetts Green High-Performance Computing Center](https://www.mghpcc.org) (MGHPCC) in Holyoke, MA. This is a state-of-the-art datacenter that is shared among the Boston-area universities. It runs off of hydropower, making it one of the “greenest” computing centers in the world. FASRC also provides co-located [storage resources](https://docs.rc.fas.harvard.edu/kb/storage-service-center/) at MGHPCC.
62
+
The cluster is located at the [Massachusetts Green High-Performance Computing Center](https://mghpcc.org) (MGHPCC) in Holyoke, MA. This is a state-of-the-art datacenter that is shared among the Boston-area universities. It runs off of hydropower, making it one of the “greenest” computing centers in the world. FASRC also provides co-located [storage resources](https://docs.rc.fas.harvard.edu/kb/data-storage-workflow-rdm/) at MGHPCC.
Copy file name to clipboardExpand all lines: kempner_computing_handbook/s1_high_performance_computing/storage_and_data_transfer/shared_data_repository.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,13 +30,13 @@ We will develop a web interface later for data and model discovery.
30
30
---
31
31
32
32
-**OpenAI**
33
-
- Path: `$MODEL_PATH/gpt2` (see on [HuggingFace](https://huggingface.co/gpt2))
33
+
- Path: `$MODEL_PATH/gpt2` (see on [HuggingFace](https://huggingface.co/openai-community/gpt2))
34
34
- Size: 4.5 M
35
35
36
36
---
37
37
38
38
-**Google**
39
-
- Path: `$MODEL_PATH/t5-base` (see on [HuggingFace](https://huggingface.co/t5-base))
39
+
- Path: `$MODEL_PATH/t5-base` (see on [HuggingFace](https://huggingface.co/google-t5/t5-base))
Copy file name to clipboardExpand all lines: kempner_computing_handbook/s1_high_performance_computing/storage_and_data_transfer/understanding_storage_options.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,7 +93,7 @@ The following table summarizes the details of the default scratch storage (`nets
93
93
|**Use Cases**| Optimized for Varieties of Workflows including High I/O AI Workflows |
94
94
95
95
96
-
The following table summarizes the storage options available on the cluster, visit [data storage](https://www.rc.fas.harvard.edu/services/data-storage/) for more information.
96
+
The following table summarizes the storage options available on the cluster, visit [data storage](https://www.rc.fas.harvard.edu/data-storage/) for more information.
Copy file name to clipboardExpand all lines: kempner_computing_handbook/s5_ai_scaling_and_engineering/experiment_management/logging_and_monitoring.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,4 +40,4 @@ for epoch in range(epochs):
40
40
wandb.log({"accuracy": acc, "loss": loss})
41
41
```
42
42
43
-
Access your project and view your runs on [wandb.ai](https://wandb.ai/home) website. Additionally, invite any collaborators you have to your project at this page. Refer to the [W&B Quickstart](https://docs.wandb.ai/quickstart/) for more details.
43
+
Access your project and view your runs on [wandb.ai](https://wandb.ai/home) website. Additionally, invite any collaborators you have to your project at this page. Refer to the [W&B Quickstart](https://docs.wandb.ai/models/quickstart) for more details.
0 commit comments