Week 2 overview
Learning Objectives:¶
Version control with git
Tabular datasets
Python libraries
a. Pandas
b. Matplotlib
c. Cartopy
Learning and Participation Activities with Due Dates (Tuesday, Sep. 9, end of day):¶
Refreshers
a. Linux command line shell
b. Jupyterlab
Intro to version control with git: demonstrated in class
In a Terminal application, type the following commands:
git config --global user.name "Your Name" git config --global user.email "Your email address" git config --global init.defaultBranch main git config --global core.autocrlf input git config --global core.editor "nano"Clone the
week2directory in/spare11/atm533/ktyle:a. Access the class Jupyterhub server on Turing
b. In the Launcher, open up a Terminal session
c. cd to your
atm533folder: Typecd /spare11/atm533/<YourNetID>d. Type
git config --global --add safe.directory /spare11/atm533/ktyle/week2/.gite. Type
git clone /spare11/atm533/ktyle/week2f. You should then have a
week2folder visible in youratm533directory, which contains oneREADME.mdMarkdown file, and two Jupyter notebooks.Follow these directions:
a. In the terminal, change directories to your
atm533/week2folder (i.e., this repository)b. Create a new “development” branch of this repository:
git branch devc. Check out this branch:
git checkout devd. Edit the
README.mdfile as directed in that filee. Save and close the
README.mdfilef. Stage your changes:
git add README.mdg. Commit your changes:
git commit -m "Updated README"h. Open and run the
Helene.ipynbJupyter notebook.i. Open and run the
2024Atlantic_TC.ipynbJupyter notebook.j. Attempt one or more of the
Things to Trysuggestions in the latter notebook.k. Save, stage and commit your edits to this notebook as often as you’d like (more often is better!)
References¶
git and GitHub
Pandas
a. Pandas site
Matplotlib
Cartopy
a. Cartopy site