anton/mlpractical
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

updated references to 2022-23 repo

Browse Source
This commit is contained in:
ThumbmasWalker 2022-09-07 10:48:53 +01:00
parent 605b61957e
commit 26eaefd1a7
3 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
notes/environment-set-up.md
View File

@ -273,7 +273,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: You should make sure you are on the first lab branch now by running:
``` ```
git checkout mlp2021-22/lab1 git checkout mlp2022-23/lab1
``` ```
## 6. Installing the `mlp` Python package ## 6. Installing the `mlp` Python package
@ -433,7 +433,7 @@ Make sure we are on the first lab branch
``` ```
cd ~/mlpractical cd ~/mlpractical
git checkout mlp2021-22/lab1 git checkout mlp2022-23/lab1
``` ```
Install the `mlp` package in the environment in develop mode Install the `mlp` package in the environment in develop mode

6
notes/getting-started-in-a-lab.md
View File

@ -34,15 +34,15 @@ We are now ready to fetch any updated code from the remote repository on Github.
git fetch origin git fetch origin
``` ```
This should display a message indicate a new branch has been found and fetched, named `origin/mlp2018-9/lab[n]` where `[n]` is the relevant lab number e.g. `origin/mlp2018-9/lab2` for the second lab. 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.
We now need to create and checkout a new local branch from the remote branch fetched above. This can be done by running 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/mlp2018-9/lab[n] git checkout -b lab[n] 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/mlp2018-9/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]`.
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. 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.

4
notes/quota-issue.md
View File

@ -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). 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/CSTR-Edinburgh/mlpractical/blob/mlp2016-7/lab1/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/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.
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 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 source activate mlp # Activate the mlp environment
cd ~/mlpractical # Change the current directory to mlpractical repository cd ~/mlpractical # Change the current directory to mlpractical repository
git checkout mlp2017-8/lab[...] # Checkout the branch for this week's lab git checkout mlp2022-23/lab[...] # Checkout the branch for this week's lab
jupyter notebook # Launch the notebook server jupyter notebook # Launch the notebook server
``` ```