diff --git a/book/_toc.yml b/book/_toc.yml index 47a939c7..f427aa5c 100644 --- a/book/_toc.yml +++ b/book/_toc.yml @@ -5,7 +5,6 @@ format: jb-book parts: - caption: Details chapters: - - file: application - file: logistics - title: Schedule url: https://uwhackweek.github.io/jupyterbook-template/index.html?jump_to=schedule @@ -14,15 +13,9 @@ parts: - file: CoC - caption: Preparation chapters: - - file: preliminary/checklist_index - sections: - - file: preliminary/checklist/github - - file: preliminary/checklist/jupyterhub - - file: preliminary/checklist/git - - file: preliminary/checklist/earthdata - - file: preliminary/skills_refresher_index - sections: - - file: preliminary/skills-refresher/swc + - file: preliminary/index + - file: preliminary/checklist + - file: preliminary/git - caption: Tutorials chapters: - file: tutorials/index diff --git a/book/application.md b/book/application.md deleted file mode 100644 index 474f7fa6..00000000 --- a/book/application.md +++ /dev/null @@ -1,27 +0,0 @@ -# Application - -We are glad you are interested in applying to participate in {{hackweek}}! - -```{warning} Applications not yet open -Come back soon to apply! -``` - -## Considerations - -Hackweeks are participant-driven events that encourage collaboration and teamwork. We welcome people from a diverse range of career stages, experience levels, backgrounds and identities. - -Participant selection will be made with the goal of enhancing the diversity of our communities and building lasting connections that foster open science and data sharing. - -Our events are often over-subscribed so we ask that you ensure you can attend the majority of our sessions during {{dates}} before applying. - - -## Selection Criteria - -The hackweek organizing committee follows a two phase process in selecting applicants, adopted from {cite:p}`huppenkothen_entrofy_2020`: - -```{image} img/participant-selection.png -:alt: participant-selection -:class: bg-primary mb-1 -:width: 1000px -:align: center -``` \ No newline at end of file diff --git a/book/img/CoC.png b/book/img/CoC.png deleted file mode 100644 index 0814c232..00000000 Binary files a/book/img/CoC.png and /dev/null differ diff --git a/book/img/belonging.png b/book/img/belonging.png deleted file mode 100644 index f1407797..00000000 Binary files a/book/img/belonging.png and /dev/null differ diff --git a/book/img/clone-result.png b/book/img/clone-result.png deleted file mode 100644 index ed7d3e13..00000000 Binary files a/book/img/clone-result.png and /dev/null differ diff --git a/book/img/clone.png b/book/img/clone.png deleted file mode 100644 index a493f516..00000000 Binary files a/book/img/clone.png and /dev/null differ diff --git a/book/img/co-creation.png b/book/img/co-creation.png deleted file mode 100644 index 43a9c71a..00000000 Binary files a/book/img/co-creation.png and /dev/null differ diff --git a/book/img/earthdata-login.png b/book/img/earthdata-login.png deleted file mode 100644 index 45041bb1..00000000 Binary files a/book/img/earthdata-login.png and /dev/null differ diff --git a/book/img/education.png b/book/img/education.png deleted file mode 100644 index 9941d7be..00000000 Binary files a/book/img/education.png and /dev/null differ diff --git a/book/img/git-fork-clone-update.png b/book/img/git-fork-clone-update.png deleted file mode 100644 index 7b936e62..00000000 Binary files a/book/img/git-fork-clone-update.png and /dev/null differ diff --git a/book/img/git-linear-flow-2.png b/book/img/git-linear-flow-2.png deleted file mode 100644 index 60e3f2da..00000000 Binary files a/book/img/git-linear-flow-2.png and /dev/null differ diff --git a/book/img/git-repo-structure.png b/book/img/git-repo-structure.png deleted file mode 100644 index 3154cc99..00000000 Binary files a/book/img/git-repo-structure.png and /dev/null differ diff --git a/book/img/github-clone-url.png b/book/img/github-clone-url.png deleted file mode 100644 index bb9fc18a..00000000 Binary files a/book/img/github-clone-url.png and /dev/null differ diff --git a/book/img/github-fork.png b/book/img/github-fork.png deleted file mode 100644 index ee9b8d24..00000000 Binary files a/book/img/github-fork.png and /dev/null differ diff --git a/book/img/github-signup.png b/book/img/github-signup.png deleted file mode 100644 index a2a40ee9..00000000 Binary files a/book/img/github-signup.png and /dev/null differ diff --git a/book/img/github-token.png b/book/img/github-token.png index d9e8c5ed..baac58c2 100644 Binary files a/book/img/github-token.png and b/book/img/github-token.png differ diff --git a/book/img/github_whw_repos_image.png b/book/img/github_whw_repos_image.png deleted file mode 100644 index e2540fc3..00000000 Binary files a/book/img/github_whw_repos_image.png and /dev/null differ diff --git a/book/img/hackweek-mission.png b/book/img/hackweek-mission.png deleted file mode 100644 index d58cf432..00000000 Binary files a/book/img/hackweek-mission.png and /dev/null differ diff --git a/book/img/hub-logout-button.png b/book/img/hub-logout-button.png deleted file mode 100644 index 92a4a2ab..00000000 Binary files a/book/img/hub-logout-button.png and /dev/null differ diff --git a/book/img/interactivity.png b/book/img/interactivity.png deleted file mode 100644 index c4fa0fb6..00000000 Binary files a/book/img/interactivity.png and /dev/null differ diff --git a/book/img/jupyter-terminal.png b/book/img/jupyter-terminal.png index 47ca871f..d625163d 100644 Binary files a/book/img/jupyter-terminal.png and b/book/img/jupyter-terminal.png differ diff --git a/book/img/jupyterhub-authentication.png b/book/img/jupyterhub-authentication.png deleted file mode 100644 index 48c8faee..00000000 Binary files a/book/img/jupyterhub-authentication.png and /dev/null differ diff --git a/book/img/jupyterhub-connectivity.png b/book/img/jupyterhub-connectivity.png deleted file mode 100644 index defaf4ee..00000000 Binary files a/book/img/jupyterhub-connectivity.png and /dev/null differ diff --git a/book/img/jupyterhub-overview.png b/book/img/jupyterhub-overview.png deleted file mode 100644 index b15383ec..00000000 Binary files a/book/img/jupyterhub-overview.png and /dev/null differ diff --git a/book/img/jupyterhub-upload.png b/book/img/jupyterhub-upload.png deleted file mode 100644 index 78d7be40..00000000 Binary files a/book/img/jupyterhub-upload.png and /dev/null differ diff --git a/book/img/jupyterhub-website-folder.png b/book/img/jupyterhub-website-folder.png deleted file mode 100644 index ccaa07ae..00000000 Binary files a/book/img/jupyterhub-website-folder.png and /dev/null differ diff --git a/book/img/jupyterlab-git.jpg b/book/img/jupyterlab-git.jpg deleted file mode 100644 index f992aacd..00000000 Binary files a/book/img/jupyterlab-git.jpg and /dev/null differ diff --git a/book/img/jupyterlab.png b/book/img/jupyterlab.png deleted file mode 100644 index 92fe775b..00000000 Binary files a/book/img/jupyterlab.png and /dev/null differ diff --git a/book/img/networking.png b/book/img/networking.png deleted file mode 100644 index 2f6bbc1f..00000000 Binary files a/book/img/networking.png and /dev/null differ diff --git a/book/img/pangeo-image-select.png b/book/img/pangeo-image-select.png deleted file mode 100644 index 10e3823a..00000000 Binary files a/book/img/pangeo-image-select.png and /dev/null differ diff --git a/book/img/pangeo-opening.png b/book/img/pangeo-opening.png deleted file mode 100644 index 7412563b..00000000 Binary files a/book/img/pangeo-opening.png and /dev/null differ diff --git a/book/img/pangeo-server-starting.png b/book/img/pangeo-server-starting.png deleted file mode 100644 index 3d322a81..00000000 Binary files a/book/img/pangeo-server-starting.png and /dev/null differ diff --git a/book/img/participant-selection.png b/book/img/participant-selection.png deleted file mode 100644 index 1e7c3850..00000000 Binary files a/book/img/participant-selection.png and /dev/null differ diff --git a/book/img/people-github.png b/book/img/people-github.png deleted file mode 100644 index 3859ca20..00000000 Binary files a/book/img/people-github.png and /dev/null differ diff --git a/book/img/private-github.png b/book/img/private-github.png deleted file mode 100644 index 63dc1a70..00000000 Binary files a/book/img/private-github.png and /dev/null differ diff --git a/book/img/projects.png b/book/img/projects.png deleted file mode 100644 index c9b831dd..00000000 Binary files a/book/img/projects.png and /dev/null differ diff --git a/book/img/public-github.png b/book/img/public-github.png deleted file mode 100644 index 31be155a..00000000 Binary files a/book/img/public-github.png and /dev/null differ diff --git a/book/img/repos.png b/book/img/repos.png deleted file mode 100644 index 2c078f2a..00000000 Binary files a/book/img/repos.png and /dev/null differ diff --git a/book/img/terminal-button.png b/book/img/terminal-button.png deleted file mode 100644 index a976932c..00000000 Binary files a/book/img/terminal-button.png and /dev/null differ diff --git a/book/img/terminal-clone.png b/book/img/terminal-clone.png deleted file mode 100644 index e9ef5b2e..00000000 Binary files a/book/img/terminal-clone.png and /dev/null differ diff --git a/book/img/terminal.png b/book/img/terminal.png deleted file mode 100644 index c734b900..00000000 Binary files a/book/img/terminal.png and /dev/null differ diff --git a/book/preliminary/checklist_index.md b/book/preliminary/checklist.md similarity index 53% rename from book/preliminary/checklist_index.md rename to book/preliminary/checklist.md index 36dfa173..37f0ebeb 100644 --- a/book/preliminary/checklist_index.md +++ b/book/preliminary/checklist.md @@ -42,22 +42,32 @@ the week. ### EarthData Login We'll have you download some data from NSIDC for your tutorials and projects. -Visit our [Earthdata](checklist/earthdata.md) page to learn how to access and Earthdata -login account if you don't already have one! +Visit the [Earthdata](https://www.earthdata.nasa.gov/eosdis/science-system-description/eosdis-components/earthdata-login) +help page and learn how to register, access, and login if you don't already have +an account! ### GitHub Account Everyone attending {{ hackweek }} will require obtaining a GitHub account. -Visit our [GitHub instruction page](checklist/github.md) to learn how! +Visit [the GitHub help pages](https://docs.github.com/en/get-started/start-your-journey/creating-an-account-on-github) +if you are in need for an account! +(accessing-jupyterhub)= ### JupyterHub -We will offer all tutorials within the Jupyter Hub computing environment. -Visit our [Introduction to Jupyter Hub](checklist/jupyterhub.md) page to learn more! +We will offer all tutorials based on a JupyterHub environment. Please visit the +[Project Pythia Foundation Skills](https://foundations.projectpythia.org/foundations/getting-started-jupyter.html) +to learn more about the components of project Jupyter. -### Git +Specifically for the event, we will be using [CryoCloud](https://book.cryointhecloud.com/intro.html). +To get started, please see the [onboarding instructions](https://book.cryointhecloud.com/content/Getting_Started.html) +to gain access. -All content of the hackweek will be shared via GitHub and interacting with the -website will be done via the `git` command. -Visit [Setting up the `git` command](checklist/git.md) to learn how to configure that! +Optional setup after you are logged in CryoCloud: +* Earthdata authentication to automate data downloads: + [Configure a netrc file](https://wiki.earthdata.nasa.gov/display/EL/How+To+Access+Data+With+cURL+And+Wget) +* Git authentication: + All content of the hackweek will be shared via GitHub and interacting with the + website will be done via the `git` command. See our {ref}`setting-up-git` + to configure your access. diff --git a/book/preliminary/checklist/earthdata.md b/book/preliminary/checklist/earthdata.md deleted file mode 100644 index 973e3ade..00000000 --- a/book/preliminary/checklist/earthdata.md +++ /dev/null @@ -1,35 +0,0 @@ -# Earthdata Login - -## Overview - -NASA data are stored at one of several Distributed Active Archive Centers (DAACs). If you're interested in available data for a given area and time of interest, the [Earthdata Search](https://earthdata.nasa.gov/) portal provides a convenient web interface. - -## Why do I need an Earthdata login? - -Each participant will need a login. We will be teaching you ways to programmatically access NASA data from within your Python scripts. You will need to enter your Earthdata username and password in order for this to work. - -## Getting an Earthdata login - -If you do not already have an Earthdata login, then navigate to the [Earthdata Login](https://urs.earthdata.nasa.gov/) page, a username and password, and then record this somewhere for use during the tutorials: - -![earthdata-login](../../img/earthdata-login.png) - -## Configure programmatic access to NASA servers - -If you use web interfaces to retrieve nasa data such as -[Earthdata Search](https://earthdata.nasa.gov/) you are prompted to login. -We will be using software to retrieve data from NASA Servers during the hackweek, -so you must store your credentials on the JupyterHub as explained in -[this documentation](https://wiki.earthdata.nasa.gov/display/EL/How+To+Access+Data+With+cURL+And+Wget). - -Run the following commands on the JupyterHub: - -```{important} -In the below command, replace `EARTHDATA_LOGIN` with your personal username and -`EARTHDATA_PASSWORD` with your password -``` - -```shell -echo 'machine urs.earthdata.nasa.gov login "EARTHDATA_LOGIN" password "EARTHDATA_PASSWORD"' > ~/.netrc -chmod 0600 ~/.netrc -``` diff --git a/book/preliminary/checklist/github.md b/book/preliminary/checklist/github.md deleted file mode 100644 index 7225a80e..00000000 --- a/book/preliminary/checklist/github.md +++ /dev/null @@ -1,70 +0,0 @@ -# GitHub - -## What is GitHub? -[GitHub](https://github.com) is a hosting service for {term}`Git` repositories, -enabling us to share code across teams in a web environment. - -## Why do I need a GitHub account? - -There are three reasons you are required to have a GitHub account for the hackweek: - -1. Your GitHub accounts will give you access to the hackweek cloud computing resources -2. All hackweek tutorials will be shared on GitHub -3. All project teams will use GitHub to collaborate and work together on their code - -## Creating a GitHub account - -Go to [GitHub](https://github.com/). - -![github-signup](../../img/github-signup.png) - -Next, enter your email address and click on the green 'Sing up for GitHub' button. -You will need to answer a few required questions in the following dialogs. -Be sure to save your password somewhere safe because you will need it later! - -## Why are you joining the a Hackweek GitHub Organization? - -GitHub organizations are a way for teams to manage many repositories -specific to a project or workshop in one place. For the hackweek, having -an organization creates a central location to access all hackweek content. -GitHub organizations also have 'teams' that offer simple ways to provide repository -access to groups of people, rather than individuals. - -We have created a {{ hackweek }} GitHub organization ({{ github_org_url}}). -For security purposes you can only join the organization by invitation. -Here are the steps: - -1. If you confirmed participation in the hackweek you will receive an email notification to the email you provided when you signed up for GitHub. -1. Follow the link in the email to accept the invitation. - -(configure-github)= - -## How should I configure my GitHub account? - -As you'll learn in the next lesson, we will use the {{ hackweek }} GitHub -organization as a way to manage access to our cloud computing resources. - -```{attention} -You must have *Public*, rather than *Private* organization membership (GitHub's default), -in order for our JupyterHub authentication to work. For events like hackweeks, -public membership also helps so that others can recognize your participation in the event! -``` - -First, navigate to the "People" tab on the {{ hackweek }} GitHub organization -({{ github_org_url }}) and find yourself: - -![people-tab](../../img/people-github.png) - -Now, if you see "Private" to the right of your account, you will need to switch this to "Public": - -![private-setting](../../img/public-github.png) - -The steps for doing this are also well documented on [this](https://help.github.com/en/articles/publicizing-or-hiding-organization-membership) GitHub help page. - -## How will GitHub repositories be structured? - -When you click on the "Repositories" tab in the {{ '[GitHub organization]({url})'.format(url=github_org_url) }} you will see a list of names, each of which links to a separate GitHub repository: - -![repos-tab](../../img/repos.png) - -Each repository is a container for a specific subset of material for this event. For example, there is a repository for the public-facing website you used to register for this event {{website_url}}. We'll also create new repositories for each project. diff --git a/book/preliminary/checklist/jupyterhub.md b/book/preliminary/checklist/jupyterhub.md deleted file mode 100644 index c6c5fc00..00000000 --- a/book/preliminary/checklist/jupyterhub.md +++ /dev/null @@ -1,67 +0,0 @@ -# JupyterHub - -(event-jupyterhub)= -## Why are we using a shared cloud environment? - -We use {term}`JupyterHub` in an educational setting because it enables us to quickly begin working with code. Each participant connects to a computational environment hosted in the cloud. All that is required is a web browser, and a GitHub username for authentication: - -![jupyterhub-connectivity](../../img/jupyterhub-connectivity.png) - -We encourage you to use these shared cloud environments for all the tutorials, and you can optionally use this for your projects as well. - -(accessing-jupyterhub)= -## How do I access the shared cloud environment? - -Access to our shared cloud environment (JupyterHub) is under this URL: {{ jupyterhub_url }}! - -### First time login - -```{attention} -Before going to {{ jupyterhub_url }} you need to setup your {{ hackweek }} -organization membership correctly. See: {ref}`configure-github` -``` - -The first time you sign in, you will be asked to authorize the OAuth app as access -to the JupyterHub is restricted to {{ hackweek }} GitHub Organization members. - -```{note} -The screenshots below will not exactly match what you see and you should see your -user information for instance. -``` - -![jupyterhub-authentication](../../img/jupyterhub-authentication.png) - -### After each login - -```{attention} -It can take several minutes for new servers to launch on the cloud - be patient! -Once things are spun up you will see your very own instance of a {term}`JupyterLab` environment -``` - -![jupyterhub-overview](../../img/jupyterhub-overview.png) - -When you log into JupyterHub you have access to your own virtual drive space -under the `/home/jovyan` directory. No other users will be able to see or access -your data files. You can add/remove/edit files in your virtual drive space. - - -### How do I end my JupyterHub session? - -Stopping the server happens automatically when you navigate to "File -> Log Out" -and click "Log Out"! to end a session. You can also select "File -> Hub Control -Panel -> Stop my Server". - -![hub-control-panel-button](../../img/hub-logout-button.png) - -```{attention} -When you are finished working for the day it is important to explicitly log -out of your JupyterHub session. -``` - -The reason for this is it will save us a bit of money! When you keep a session -active it uses up AWS resources and keeps a series of virtual machines deployed. - -### Will I lose all of my work? - -Logging out will **NOT** cause any files under `/home/jovyan` to be deleted. It -is equivalent to turning off your desktop computer at the end of the day. diff --git a/book/preliminary/checklist/git.md b/book/preliminary/git.md similarity index 91% rename from book/preliminary/checklist/git.md rename to book/preliminary/git.md index 0c1d5f97..1904454f 100644 --- a/book/preliminary/checklist/git.md +++ b/book/preliminary/git.md @@ -1,4 +1,4 @@ -# Git +# Setting up `git` ## What is Git? @@ -14,7 +14,7 @@ You are not required to know Git in advance of this event, but come prepared to Below are instructions to get you setup with `git` on the {{hackweek}} hackweek JupyterHub. These are only basic instructions to get started. See the -[Software Carpentry Git](http://swcarpentry.github.io/git-novice/02-setup/index.html) +[Software Carpentry Git](https://swcarpentry.github.io/git-novice/index.html) instructions for a more thorough explanation and background information. ### 1. Login to JupyterHub @@ -23,7 +23,7 @@ Go to {{ jupyterhub_url }}. See also our JupyterHub documentation: {ref}`accessi ### 2. Open a Terminal Choose the 'Terminal' from the 'Other' options in the 'Launcher' tab. -![jupyterlab](../../img/jupyter-terminal.png) +![jupyterlab](../img/jupyter-terminal.png) ### 3. Configure basic `git` information Set your username and email address. The email address should be the same @@ -45,7 +45,7 @@ git config --global credential.helper store The third line is a configuration option that needs to be done with a first time setup. It specifies the strategy on how git will apply changes you pull from -a remote git repository. +a remote git repository. More on strategies is [described here.](http://git-scm.com/book/en/v2/Git-Branching-Rebasing) The last line of the config will store your GitHub credentials and will save @@ -73,10 +73,12 @@ However, a better, more secure practice is to use a GitHub Personal Access Token more customizable permissions and can be revoked without affecting your main GitHub user account password. -Take a moment to work through the instructions on the [GitHub personal access tokens](https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token) page. For this hackweek, you need to check the **repo**, **admin:org**, and **workflow** scope. +Take a moment to work through the instructions on the +[GitHub personal access tokens](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-personal-access-token-classic) +page. For this hackweek, you need to check the **repo**, **admin:org**, and **workflow** scope. Screenshot from github.com setting up the token: -![github-token](../../img/github-token.png) +![github-token](../img/github-token.png) Once you have created your token, be sure to save it on your computer in case you need to re-authenticate again. The token will give you access to your @@ -89,7 +91,7 @@ terminal on the JupyterHub. where you will be prompted for your GitHub username and the token. ```shell -git clone {{github_org_url}}.github_setup_check.git + git clone {{ github_org_url }}/github_setup_check.git ``` Since this is the first time you are interacting from the JupyterHub with GitHub, diff --git a/book/preliminary/skills_refresher_index.md b/book/preliminary/index.md similarity index 52% rename from book/preliminary/skills_refresher_index.md rename to book/preliminary/index.md index c68b8478..b858512b 100644 --- a/book/preliminary/skills_refresher_index.md +++ b/book/preliminary/index.md @@ -1,6 +1,13 @@ -# Skills Refresher +# What to Expect -Our hackweeks focus on applied, hands-on learning, with participants engaging in extended periods of small-group work. Our tutorials are designed to offer a broad snapshot of data science tools to support your applied investigations. Due to the relatively short duration of our events, we are not able to provide comprehensive, in-depth training in fundamental tools. Rather, our goal is to inform you about the types of tools we think are best suited to working with your datasets, leaving details of implementation to be supported through peer-learning and office hours. +Our hackweeks focus on applied, hands-on learning, with participants engaging in +extended periods of small-group work. Our tutorials are designed to offer a broad +snapshot of data science tools to support your applied investigations. Due to the +relatively short duration of our events, we are not able to provide comprehensive, +in-depth training in fundamental tools. Rather, our goal is to inform you about +the types of tools we think are best suited to working with your datasets, +leaving details of implementation to be supported through peer-learning and +office hours. ## Typical Workflows and Tools @@ -26,13 +33,10 @@ bit less time for applied group work. If you are already proficient in a lot of tools you may find you can dedicate more energy to applied project work, which we support through facilitated group activities. -## Software Carpentry Session +## Prerequisites -We strongly suggest that participants who are just beginning to learn Python and -collaborative data science tools to complete our -recorded ([Software Carpentry Training](./skills-refresher/swc)) in advance of the hackweek. You -may choose whichever topics you'd like to brush up on or learn. - -## Project Pythia - -Another excellent resource for training and skills development is the [Project Pythia](https://projectpythia.org/) organization. Their lessons and galleries are developed specifically for the geoscience community. For a good skills refesher, we encourage you to work through their [Pythia Foundations](https://foundations.projectpythia.org/landing-page.html) notebooks. \ No newline at end of file +All tutorials and project work will assume participants are familiar with Python-based +computing in the geosciences as described on the +[Pythia Foundations](https://foundations.projectpythia.org/landing-page.html) website. + We can provide resources to participants wishing to brush up on their skills before +an event, however we will not be teaching these core concepts during the hackweek. \ No newline at end of file diff --git a/book/preliminary/skills-refresher/swc.md b/book/preliminary/skills-refresher/swc.md deleted file mode 100644 index feaca3bb..00000000 --- a/book/preliminary/skills-refresher/swc.md +++ /dev/null @@ -1,46 +0,0 @@ -# Software Carpentry Training - -[Software Carpentry](https://software-carpentry.org) is a fantastic -organization that teaches basic lab skills for research computing. - -For past hackweeks we have offered unofficial, abbreviated 2-day software -carpentry trainings to help everyone gain skills in fundamental data science -tools (Git, Linux Terminal, Python). By offering this work in advance of the -hackweek we can maximize the amount of time we get to focus on more advanced -topics. - -Below you will find links to our training materials from the 2021 SnowEx -Hackweek. If you are new to Git, Linux, Python, please set aside a day or two -to go over these materials in advance. - -## Getting ready - -Please take a minute before the workshop to go over -the [GitHub instructions](../checklist/github.md), create an account. - -## Jupyter, Git, and Unix Shell - -### [Link to video of Day 1 tutorial](https://www.youtube.com/watch?v=F8VhkKwCx0k) - -This lessons covers: - -* http://swcarpentry.github.io/shell-novice/ -* http://swcarpentry.github.io/git-novice/ - -* Introductions and getting connected -* Getting connected to JupyterHub environment via GitHub -* Orientation to the JupyterHub environment -* Unix Shell ([Topics 1 to 3](http://swcarpentry.github.io/shell-novice/)) -* Git/GitHub ([Topics 1 to 5](http://swcarpentry.github.io/git-novice/)) - -## Python Programming Language - -### [Link to video of Day 2 tutorial](https://www.youtube.com/watch?v=OhzHoGe9ZeI) - -This lessons covers: - -* http://swcarpentry.github.io/python-novice-gapminder/ - -* Jupyter Notebooks, running Python code, [Topics 1 to 3](http://swcarpentry.github.io/python-novice-gapminder) -* Variables, datatypes, libraries, [Topics 3,4,6](http://swcarpentry.github.io/python-novice-gapminder) -* Lists, for loops, conditionals, functions [Topics 11,12,13,16](http://swcarpentry.github.io/python-novice-gapminder)