From 849c83f418877248accd92b4eb47efa1d6e96b6a Mon Sep 17 00:00:00 2001 From: ana deligny Date: Mon, 25 Sep 2023 00:42:26 +0100 Subject: [PATCH] update notes --- notes/environment-set-up.md | 16 ++++++++++++++-- notes/getting-started-in-a-lab.md | 6 +++--- notes/quota-issue.md | 4 ++-- notes/remote-working-guide.md | 2 +- 4 files changed, 20 insertions(+), 8 deletions(-) diff --git a/notes/environment-set-up.md b/notes/environment-set-up.md index eff30e2..32d9f43 100644 --- a/notes/environment-set-up.md +++ b/notes/environment-set-up.md @@ -125,6 +125,12 @@ conda install numpy scipy matplotlib jupyter Again you will be given a list of the packages to be installed and asked to confirm whether to proceed. Enter `y` then wait for the packages to install (this should take around five minutes). In addition to Jupyter, NumPy and SciPy which we have already mentioned, we are also installing [matplotlib](http://matplotlib.org/) a plotting and visualisation library. +Install PyTorch. The command below installs the CPU-only version of PyTorch. If you have access to a CUDA-enabled GPU and wish to install the GPU version of PyTorch instead, replace `cpuonly -c pytorch` with your CUDA version reference, e.g. for CUDA 11.7 use `pytorch-cuda=11.7 -c pytorch -c nvidia` in the command below. For more information see [here](https://pytorch.org/get-started/locally/). + +``` +conda install pytorch torchvision torchaudio cpuonly -c pytorch +``` + Once the installation is finished, to recover some disk space we can clear the package tarballs Conda just downloaded: ``` @@ -273,7 +279,7 @@ This will change the code in the working directory to the current state of the c You should make sure you are on the first lab branch now by running: ``` -git checkout mlp2022-23/lab1 +git checkout mlp2023-24/lab1 ``` ## 6. Installing the `mlp` Python package @@ -417,6 +423,12 @@ Install the dependencies for the course into the new environment: conda install numpy scipy matplotlib jupyter ``` +Install PyTorch. The command below installs the CPU-only version of PyTorch. If you have access to a CUDA-enabled GPU and wish to install the GPU version of PyTorch instead, replace `cpuonly -c pytorch` with your CUDA version reference, e.g. for CUDA 11.7 use `pytorch-cuda=11.7 -c pytorch -c nvidia` in the command below. For more information see [here](https://pytorch.org/get-started/locally/). + +``` +conda install pytorch torchvision torchaudio cpuonly -c pytorch +``` + Clear the package tarballs Conda just downloaded: ``` @@ -433,7 +445,7 @@ Make sure we are on the first lab branch ``` cd ~/mlpractical -git checkout mlp2022-23/lab1 +git checkout mlp2023-24/lab1 ``` Install the `mlp` package in the environment in develop mode diff --git a/notes/getting-started-in-a-lab.md b/notes/getting-started-in-a-lab.md index 4c1a6ac..ae52e97 100644 --- a/notes/getting-started-in-a-lab.md +++ b/notes/getting-started-in-a-lab.md @@ -34,15 +34,15 @@ We are now ready to fetch any updated code from the remote repository on Github. git fetch origin ``` -This should display a message indicate a new branch has been found and fetched, named `origin/mlp2022-23/lab[n]` where `[n]` is the relevant lab number e.g. `origin/mlp2022-23/lab2` for the second lab. +This should display a message indicate a new branch has been found and fetched, named `origin/mlp2023-24/lab[n]` where `[n]` is the relevant lab number e.g. `origin/mlp2023-24/lab2` for the second lab. We now need to create and checkout a new local branch from the remote branch fetched above. This can be done by running ``` -git checkout -b lab[n] origin/mlp2022-23/lab[n] +git checkout -b lab[n] origin/mlp2023-24/lab[n] ``` -where again `lab[n]` corresponds to the relevant lab number fetched above e.g. `lab2`. This command creates a new local branch named `lab[n]` from the fetched branch on the remote repository `origin/mlp2022-23/lab[n]`. +where again `lab[n]` corresponds to the relevant lab number fetched above e.g. `lab2`. This command creates a new local branch named `lab[n]` from the fetched branch on the remote repository `origin/mlp2023-24/lab[n]`. Inside the `notebooks` directory there should new be a new notebook for today's lab. The notebook for the previous lab will now also have proposed solutions filled in. diff --git a/notes/quota-issue.md b/notes/quota-issue.md index cd1cb7c..c8db162 100644 --- a/notes/quota-issue.md +++ b/notes/quota-issue.md @@ -17,13 +17,13 @@ this should clean out the old partially installed packages and reinstall them fr Your homespace can be accessed from any Informatics computer running DICE (e.g. any of the computers in the [Forrest Hill labs](http://web.inf.ed.ac.uk/infweb/student-services/ito/students/year2/student-support/facilities/computer-labs) which are open-access outside of booked lab sessions or for those who know how to use SSH you can [log in remotely](http://computing.help.inf.ed.ac.uk/external-login)). You can therefore finish your environment set up prior to the next lab if you want though it is also fine to wait till the beginning of the next lab (it will take around 5 minutes to complete the installation). -At this point assuming you ran through the rest of the instructions to clone the Git repository to your homespace and install the `mlp` package (i.e. the instructions from [here](https://github.com/VICO-UoE/mlpractical/tree/mlp2016-7/lab1/notes/environment-set-up.md#getting-the-course-code-and-a-short-introduction-to-git) on-wards), you should have a fully working environment. +At this point assuming you ran through the rest of the instructions to clone the Git repository to your homespace and install the `mlp` package (i.e. the instructions from [here](https://github.com/VICO-UoE/mlpractical/tree/mlp2023-24/lab1/notes/environment-set-up.md#getting-the-course-code-and-a-short-introduction-to-git) on-wards), you should have a fully working environment. Once your environment is set up in all future labs you will only need to activate it to get started. So at the beginning of each subsequent lab we will ask you to do something like the following ``` source activate mlp # Activate the mlp environment cd ~/mlpractical # Change the current directory to mlpractical repository -git checkout mlp2022-23/lab[...] # Checkout the branch for this week's lab +git checkout mlp2023-24/lab[...] # Checkout the branch for this week's lab jupyter notebook # Launch the notebook server ``` diff --git a/notes/remote-working-guide.md b/notes/remote-working-guide.md index 022b54d..1e48d8b 100644 --- a/notes/remote-working-guide.md +++ b/notes/remote-working-guide.md @@ -32,7 +32,7 @@ bash scripts/secure-notebook-server.sh ``` As this script creates a self-signed certificate to set up the secure HTTP encrypted communication between the browser and server, you will be shown a security warning when you load up the URL the notebooks are being served on. -If you want to manually secure the notebook server yourself or to create a certificate which will stop the security warnings appearing you can refer to the [relevant official Jupyter documentation page](http://jupyter-notebook.readthedocs.io/en/latest/public_server.html). +If you want to manually secure the notebook server yourself or to create a certificate which will stop the security warnings appearing you can refer to the [relevant official Jupyter documentation page](https://jupyter-notebook.readthedocs.io/en/latest/notebook.html). ## Connecting to a remote `student.compute` server over SSH