From 6ff1debb9343bf763a8610744609f9f3c9b8eec3 Mon Sep 17 00:00:00 2001 From: jatkinson1000 <109271713+jatkinson1000@users.noreply.github.com> Date: Sun, 19 Nov 2023 18:38:14 +0000 Subject: [PATCH 1/7] Add setup.py file to allow running on binder. --- setup.py | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 setup.py diff --git a/setup.py b/setup.py new file mode 100644 index 0000000..93c246e --- /dev/null +++ b/setup.py @@ -0,0 +1,6 @@ +#!usr/bin/env python + +from setuptools import setup + +if __name__ == "__main__": + setup() From 282a14639cf76424b7f8829aa09b091bb97902b3 Mon Sep 17 00:00:00 2001 From: jatkinson1000 <109271713+jatkinson1000@users.noreply.github.com> Date: Sun, 19 Nov 2023 18:51:53 +0000 Subject: [PATCH 2/7] Add binder info to README. --- README.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 0abb846..771d911 100644 --- a/README.md +++ b/README.md @@ -6,6 +6,7 @@  [![CC BY-NC-SA 4.0][cc-by-nc-sa-shield]][cc-by-nc-sa] +[](https://mybinder.org/v2/gh/Cambridge-ICCS/ml-training-material/main) This repository contains documentation, resources, and code for the Introduction to Machine Learning with PyTorch session designed and delivered by [Jack Atkinson](https://jackatkinson.net/) ([**@jatkinson1000**](https://github.com/jatkinson1000)) @@ -136,10 +137,11 @@ us before a training session. ## Installation and setup -There are two options for participating in this workshop for which instructions are provided below: +There are three options for participating in this workshop for which instructions are provided below: * via a [local install](#local-install) * on [Google Colab](#google-colab) +* on [binder](#binder) We recommend the [local install](#local-install) approach, especially if you forked the repository, as it is the easiest way to keep a copy of your work and push back to GitHub. @@ -219,6 +221,7 @@ python -m ipykernel install --user --name=MLvenv ### Google Colab +Running on Colab is useful as it allows you to access GPU resources. To run the notebooks in Google Colab click the following links for each of the exercises: * [Exercise 01](https://colab.research.google.com/github/Cambridge-ICCS/ml-training-material/blob/colab/exercises/01_penguin_classification.ipynb) @@ -231,6 +234,15 @@ _Notes:_ * _If you leave a Colab session your work will be lost, so be careful to save any work you want to keep._ +### binder + +If you cannot operate using a local install, and do not wish to sign up for a Colab account, +the exercises can be launched +[on binder](https://mybinder.org/v2/gh/Cambridge-ICCS/ml-training-material/main). + +_Notes:_ +* _It is not possible to save work from a binder session, so we advise using one of the above options. + This is an easy way to run the worked solutions, however._ ## License From 9b379879933454d3da4cd89652ab6012489be5c7 Mon Sep 17 00:00:00 2001 From: jatkinson1000 <109271713+jatkinson1000@users.noreply.github.com> Date: Sun, 19 Nov 2023 19:31:11 +0000 Subject: [PATCH 3/7] Update README moving colab solutions and adding binder info. --- README.md | 24 ++++++++++-------------- 1 file changed, 10 insertions(+), 14 deletions(-) diff --git a/README.md b/README.md index 771d911..49ce479 100644 --- a/README.md +++ b/README.md @@ -71,13 +71,6 @@ These are for recapping after the course in case you missed anything, and contai [linted](https://docs.pylint.org/intro.html), and conforming to the [black](https://black.readthedocs.io/en/stable/) code style. -If you were working on Colab you can open the worked solutions using the following links: - -* [Exercise 01](https://colab.research.google.com/github/Cambridge-ICCS/ml-training-material/blob/colab/worked-solutions/01_penguin_classification_solutions.ipynb) -* [Exercise 02](https://colab.research.google.com/github/Cambridge-ICCS/ml-training-material/blob/colab/worked-solutions/02_penguin_regression_solutions.ipynb) -* [Exercise 03](https://colab.research.google.com/github/Cambridge-ICCS/ml-training-material/blob/colab/worked-solutions/03_mnist_classification_solutions.ipynb) -* [Exercise 04](https://colab.research.google.com/github/Cambridge-ICCS/ml-training-material/blob/colab/worked-solutions/04_ellipse_regression_solutions.ipynb) - ## Preparation and prerequisites @@ -148,7 +141,7 @@ the repository, as it is the easiest way to keep a copy of your work and push ba However, if you experience issues with the installation process or are unfamiliar with the terminal/installation process there is the option to run the notebooks in -[Google Colab](#google-colab). +[Google Colab](#google-colab) or on [binder](#binder). ### Local Install @@ -224,10 +217,10 @@ python -m ipykernel install --user --name=MLvenv Running on Colab is useful as it allows you to access GPU resources. To run the notebooks in Google Colab click the following links for each of the exercises: -* [Exercise 01](https://colab.research.google.com/github/Cambridge-ICCS/ml-training-material/blob/colab/exercises/01_penguin_classification.ipynb) -* [Exercise 02](https://colab.research.google.com/github/Cambridge-ICCS/ml-training-material/blob/colab/exercises/02_penguin_regression.ipynb) -* [Exercise 03](https://colab.research.google.com/github/Cambridge-ICCS/ml-training-material/blob/colab/exercises/03_mnist_classification.ipynb) -* [Exercise 04](https://colab.research.google.com/github/Cambridge-ICCS/ml-training-material/blob/colab/exercises/04_ellipse_regression.ipynb) +* [Exercise 01](https://colab.research.google.com/github/Cambridge-ICCS/ml-training-material/blob/colab/exercises/01_penguin_classification.ipynb) - [Worked Solution 01](https://colab.research.google.com/github/Cambridge-ICCS/ml-training-material/blob/colab/worked-solutions/01_penguin_classification_solutions.ipynb) +* [Exercise 02](https://colab.research.google.com/github/Cambridge-ICCS/ml-training-material/blob/colab/exercises/02_penguin_regression.ipynb) - [Worked Solution 02](https://colab.research.google.com/github/Cambridge-ICCS/ml-training-material/blob/colab/worked-solutions/02_penguin_regression_solutions.ipynb) +* [Exercise 03](https://colab.research.google.com/github/Cambridge-ICCS/ml-training-material/blob/colab/exercises/03_mnist_classification.ipynb) - [Worked Solution 03](https://colab.research.google.com/github/Cambridge-ICCS/ml-training-material/blob/colab/worked-solutions/03_mnist_classification_solutions.ipynb) +* [Exercise 04](https://colab.research.google.com/github/Cambridge-ICCS/ml-training-material/blob/colab/exercises/04_ellipse_regression.ipynb) - [Worked Solution 04](https://colab.research.google.com/github/Cambridge-ICCS/ml-training-material/blob/colab/worked-solutions/04_ellipse_regression_solutions.ipynb) _Notes:_ * _Running in Google Colab requires you to have a Google account._ @@ -241,8 +234,11 @@ the exercises can be launched [on binder](https://mybinder.org/v2/gh/Cambridge-ICCS/ml-training-material/main). _Notes:_ -* _It is not possible to save work from a binder session, so we advise using one of the above options. - This is an easy way to run the worked solutions, however._ +* _If you leave a binder session your work will be lost, so be careful to save any work + you want to keep_ +* _Due to the limited resources provided by binder you will struggle to run training in + exercises 3 and 4._ + ## License From 1f819ada4184cda4b82377bc01ddd998835e8238 Mon Sep 17 00:00:00 2001 From: jatkinson1000 <109271713+jatkinson1000@users.noreply.github.com> Date: Sun, 19 Nov 2023 20:20:25 +0000 Subject: [PATCH 4/7] Update githubb pages site with binder and small readme phrasing. --- README.md | 6 +++--- slides/index.html | 18 ++++++++++++++++-- 2 files changed, 19 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 49ce479..e12c340 100644 --- a/README.md +++ b/README.md @@ -215,7 +215,7 @@ python -m ipykernel install --user --name=MLvenv ### Google Colab Running on Colab is useful as it allows you to access GPU resources. -To run the notebooks in Google Colab click the following links for each of the exercises: +To launch the notebooks in Google Colab click the following links for each of the exercises: * [Exercise 01](https://colab.research.google.com/github/Cambridge-ICCS/ml-training-material/blob/colab/exercises/01_penguin_classification.ipynb) - [Worked Solution 01](https://colab.research.google.com/github/Cambridge-ICCS/ml-training-material/blob/colab/worked-solutions/01_penguin_classification_solutions.ipynb) * [Exercise 02](https://colab.research.google.com/github/Cambridge-ICCS/ml-training-material/blob/colab/exercises/02_penguin_regression.ipynb) - [Worked Solution 02](https://colab.research.google.com/github/Cambridge-ICCS/ml-training-material/blob/colab/worked-solutions/02_penguin_regression_solutions.ipynb) @@ -229,8 +229,8 @@ _Notes:_ ### binder -If you cannot operate using a local install, and do not wish to sign up for a Colab account, -the exercises can be launched +If you cannot operate using a local install, and do not wish to sign up for a Google account, +the repository can be launched [on binder](https://mybinder.org/v2/gh/Cambridge-ICCS/ml-training-material/main). _Notes:_ diff --git a/slides/index.html b/slides/index.html index f516c17..80e998f 100644 --- a/slides/index.html +++ b/slides/index.html @@ -86,6 +86,7 @@
We recommend the local install approach, especially if you forked the repository, as it is the easiest way to keep a copy of your work and push back to github.
@@ -183,7 +185,8 @@python -m ipykernel install --user --name=MLvenv
To run the notebooks in Google Colab click the following links for each of the exercises:
+Running on Colab is useful as it allows you to access GPU resources.
+ To launch the notebooks in Google Colab click the following links for each of the exercises:
To run the notebooks in binder click the following link:
+ + +Notes:
+
Worked solutions for all of the exercises can be found in the
Unless participating via Colab you will be expected to know how to:
+Unless participating via Colab or binder you will be expected to know how to:
The teaching materials are licensed under CC BY-NC-SA 4.0.
If you spot an issue with the materials please let us know by opening an issue on GitHub clearly describing the problem.
+If you are able to fix an issue that you spot, or an existing open issue please get in touch by commenting on the issue thread.
+Contributions from the community are welcome. To contribute back to the repository please first fork it, make the neccessary changes to fix the problem, and then open a pull request back to this repository clerly describing the changes you have made. We will then preform a review and merge once ready.
+If you would like support using these materials, adapting them to your needs, or delivering them please get in touch either via GitHub or via ICCS.
+