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
- Installing Conda can be _very_ slow, so please get this done before we start.
40
+
- Installing Conda take a bit of time, so please get this done before we start.
41
41
- Note that copying `${HOME}/miniconda3` between clusters typically breaks links and pathways. You should install `miniconda3` from scratch each time and then export and recreate each environment across clusters
42
42
- You can use `virtualenv` or `poetry` if desired but I will assume that you know what you are doing / don't need help.
43
43
@@ -56,7 +56,7 @@ This is an approximate diagram of how the cluster is configured for a different
56
56
57
57
## Quick Bash Environment Setup
58
58
59
-
1. There is now only one Informatics cluster called `mlp` (note that `ilcc-cluster` still works as an alias). Throughout this guide I will assume you have either set a variable called `CLUSTER_NAME` (or you'll just replace that in the instructions) e.g `export CLUSTER_NAME=mlp`.
59
+
1. There is now only one Informatics cluster, and the head node is called `mlp` (note that `ilcc-cluster` still works as an alias). Throughout this guide I will assume you have either set a variable called `CLUSTER_NAME` (or you'll just replace that in the instructions) e.g `export CLUSTER_NAME=mlp`.
60
60
61
61
2. Run this line to ssh into the cluster: `ssh ${USER}@${CLUSTER_NAME}.inf.ed.ac.uk`
62
62
@@ -87,17 +87,16 @@ This is an approximate diagram of how the cluster is configured for a different
7. You can now play around with commands on the cluster (try running `free-gpus`, `cluster-status`)
94
+
6. You can now play around with commands on the cluster (try running `free-gpus`, `cluster-status`)
95
+
96
+
- __For more information, have a look at the `README.md`__ in the `cluster-scripts` directory.
97
+
99
98
100
-
8. You are ready to go!
99
+
7. You are ready to go!
101
100
102
101
103
102
## What's Next? Practical examples!
@@ -114,10 +113,10 @@ All the examples below expect you have performed the prior setup.
114
113
115
114
Make the conda environment. This can take a bit of time (it’s harder for the distributed filesystem to deal with lots of small files than for your local machine’s hard drive) - go get a cup of tea.
116
115
117
-
1. Check local versions of cuda available - at time of writing cuda 12.5.0 is the latest version available: `ls -d /opt/cu*`. You should use this version for the `cudatoolkit=??.?.?` argument below.
116
+
1. Check local versions of cuda available - at time of writing cuda 11.8.0 available: `ls -d /opt/cu*`. You should use this version for the `cudatoolkit=??.?.?` argument below.
118
117
119
118
2. Run the command to create a conda environment called `pt`:
120
-
`conda create -y -n pt python=3 pytorch torchvision torchaudio cudatoolkit=12.5.0 -c pytorch` (more info about PyTorch installation here if this goes wrong: https://pytorch.org/get-started/locally/)
119
+
`conda create -y -n pt python=3 pytorch torchvision torchaudio cudatoolkit=11.8.0 -c pytorch` (more info about PyTorch installation here if this goes wrong: https://pytorch.org/get-started/locally/)
121
120
3. Activate the environment `conda activate pt`
122
121
123
122
#### Get some code to run MNIST experiments.
@@ -129,25 +128,25 @@ Get some code to run MNIST in PyTorch and run it:
129
128
130
129
##### Interactive jobs (without a GPU)
131
130
132
-
1. Get an interactive session (you shouldn’t do processing on the head node)
133
-
- Find partitions which are used for Interactive sessions (they'll have interactive in the name). For example:
0 commit comments