Skip to content

marskar/biof309_fall2018

Repository files navigation

Syllabus

Introduction to Python Programming - BIOF309 - FAES

Fall 2018

Time: Thursday 5:30PM - 7:30PM

This document is subject to revision!

Changes are tracked using the git version control system.

To interact with the materials in the repo using JupyterLab (via Binder), please click the button below.

Binder

Additionally, the Jupyter Notebooks (ipynb files) in this repo can be opened in Google colab by clicking the icon below.

Instructors

  • Martin Skarzynski - marskar at gmail dot com
  • Jinping Liu - liu dot jinping at nih dot com
  • Michael Chambers - michael dot chambers2 at nih dot gov

Course Description

This course is designed for non-programmers, biologists, or those without specific knowledge of Python to learn how to program. Week by week, we will slowly build up your skills and understanding of computer programming and the Python programming language. There will be in-class demonstrations, using PyCharm and to a lesser extent JupyterLab, and activities to be completed outside of class, using DataCamp, for you to practice and learn at your own pace.

Learning Objectives

By the end of this course you should be able to:

  1. Look at a task and determine if you can or should automate it
  2. Create working Python programs
  3. Understand the difference between Python object types (e.g. lists, dicts)
  4. Perform data analysis and visualization with Python
  5. Use git for version control and collaboration
  6. Demonstrate your Python skills with a project

Communication

Before contacting us, please check to see if your question has already been answered elsewhere, e.g. StackOverflow.

If you cannot find the answer, please make sure to ask your question thoughtfully (https://stackoverflow.com/help/how-to-ask) and provide everything needed to answer e.g. code, error message, dataset, etc.

In general, please use the course Slack workspace to communicate with classmates and instructors. If you have a course-relevant question or something to share, Slack is simply better than email. In case of personal/private question/concerns, please use Slack direct message (DM).

In case of an emergency, please send a DM on Slack and an email.

Logistics

This is a one-semester course starting on the 13th of September 2018 and finishing on 13th of December 2018.

Class Location: Rathskeller (Room B1A199C), Building 60, NIH Bethesda campus

Attendance in class is strongly recommended; however, we realize other commitments may occasionally prevent attendance. If you miss a class, please review the materials available at the course GitHub repository and keep up with activities and homework.

NEW THIS SEMESTER! We will be piloting REMOTE ATTENDANCE and CLASS RECORDINGS via GoToMeeting and WebEx. These two options are largely the same, you can pick whichever platform you prefer. Please do NOT use this as excuse to skip class and just watch the recorded lectures! This course is NOT a Massive Online Open Course (MOOC), it will feature a great deal of group work. Additionally, forming groups to complete the final project is highly encouraged! Remote attendance will work best if you can meet with classmates to work through exercises together. We will do our best to answers questions in the GoToMeeting and WebEx chat windows during class. We will also try to answer all questions on Slack, but please try to ask your questions during class, if at all possible.

Important FAES Fall 2018 semester dates:

  • July 9 – September 7: Online Registration.
  • September 10 – 28: Late Registration (10 dollar late fee per course applies).
  • September 10: Classes begin.
  • December 14: Classes end.

Required Materials

Each student is encouraged to bring their own laptop to each class.

Programing without a computer would be an exceptional feat.

Please install the following programs BEFORE the first class:

  1. The Anaconda Scientific Python Distribution

    The Anaconda installer will automatically install most of the software we will use during the course, including Jupyter Notebooks.

  2. The PyCharm Integrated Development Environment (IDE)

    The very nice folks at JetBrains have given us free licenses for the Professional Edition of PyCharm Integrated Development Environment (IDE), the best (in my humble opinion) Python Integrated Development Environment (IDE).

    If you have a .edu email address, please install PyCharm Integrated Development Environment (IDE) Professional using this link.

    If not, a installation link will be distributed to you by email and made available on Slack.

    Before the first class, please watch the Getting Started with PyCharm video series.

    Before the second class, please watch the PyCharm In-Depth VCS video series.

During the first few classes, we will set up accounts on:

  1. DataCamp

    Since Fall 2017, the very nice folks at DataCamp have been generously supporting our class via their DataCamp for the Classroom initiative.

    This program give us free 6 month access to DataCamp's awesome Data Visualization📊, Machine Learning🤖, and Data Science learning materials.

    We will discuss the most interesting examples from DataCamp during class and point out others to be reviewed outside of class.

  2. PluralSight

    Thanks to the DataCamp-PluralSight partnership, we can get free 6 month access to Web Development, Object-Oriented Programming, and Test-Driven Development learning materials on PluralSight.

  3. GitHub

    All of the course materials are available on GitHub. Before accessing the course materials repo, you should know that

    • it is likely to be under constant development throughout the semester and
    • you are not expected to work through everything contained therein!

Optional Materials

  1. A UNIX-like system

    If you use Windows 10, please try to set up the Windows subsystem for Linux. If you use MacOS or Linux, you are all set.

  2. GitHub student pack

    GitHub is offering some free awesome resources to students, that might be of interest to you, depending on your background:

Schedule

# Date Title Lead
1 2018-09-13 Integrated Development Environments Martin
2 2018-09-20 Python Basics Martin
3 2018-09-27 Running Python code Martin
4 2018-10-04 Git and GitHub Martin
5 2018-10-11 Functions, Modules, & Packages + Loops Martin
6 2018-10-18 Booleans and Conditionals Jinping & Michael
7 2018-10-25 NumPy and Arrays Martin
8 2018-11-01 Pandas and DataFrames Jinping & Michael
9 2018-11-19 Machine Learning Martin
10 2018-11-27 Data Visualization Jinping & Michael
11 2018-11-29 Requested Topics/Final Project Clinic All Instructors
13 2018-12-06 Student Presentations
12 2018-12-11 Student Presentations
14 2018-12-13 Student Presentations

Homework

This semester we are continuing our free-form approach to homework assignments. The due dates below are guidelines. By the end of the semester, you must complete at least one career track or at least two skills tracks on DataCamp. The DataCamp career tracks include the Python Path on PluralSight. Pick DataCamp if you want to focus on Data Analysis and Machine Learning. Choose PluralSight if are interested in Object-Oriented Programming and Test-Driven Development.

This will take 28-67 hours total to complete, depending on which you choose to do.

DataCamp Career Tracks (complete at least 1):

DataCamp Skills Tracks (complete at least 2):

Please start on your chosen track(s) on DataCamp or PluralSight as soon as possible and work towards the certificate(s) throughout the semester. This will require substantial work! Do not wait until the end of the semester!

Please use the schedule below as a guide to which DataCamp and PluralSight chapters/lessons correspond to what is covered in class.

  1. DUE September 13, 2018 (BEFORE Class)

  2. DUE September 20, 2018 (BEFORE Class)

  3. DUE September 27, 2018 (BEFORE Class)

  4. DUE October 4, 2018 (BEFORE Class)

  5. DUE October 11, 2018 (BEFORE Class)

  6. DUE October 18, 2018 (BEFORE Class)

  7. DUE October 25, 2018 (BEFORE Class)

  8. DUE November 1, 2018 (BEFORE Class)

  9. DUE November 8, 2018 (BEFORE Class)

  10. WORK ON FINAL PROJECTS Depending on your final project, you might find the following topics useful:

Recommended Books

There is no required textbook for this course.

We do, however, highly recommend Python for Data Science and its companion text A Whirlwind Tour of Python by Jake Vanderplas. Both of these books are available free on GitHub in Jupyter Notebook form. The code for Python for Data Analysis by Wes McKinney is also on GitHub but the text is only available in the printed copy of the book. For maximum enjoyment, consider working through the relevant chapters before coming to class.

We will link to relevant online resources throughout the course.

If you would like additional material on the basics, the following resources may be useful:

For more information about Python, please see the official Python Software Foundation website.

Grading

The emphasis of the course is on learning and mastering the skills covered. We hope that everyone will be able to complete one of the Python tracks on DataCamp or PluralSight and submit a final project via GitHub. If some of the material appears unclear, please ask for clarification.

Completion of the Python tracks on DataCamp or PluralSight will be graded in a binary manner (completed/incomplete).

Grading the final project will be done using the following rubric:

  • Project description / Specification

    • Goals unclear, difficulty demonstrating functionality (1-3)
    • Goals for the project and functionality are discussed but difficult to follow (4-6)
    • Goals for the project and functionality are discussed (7-9)
    • Goals for the project and functionality are logically presented and clearly communicated (10-12)
  • Documentation

    • Only comments embedded in the code (1-3)
    • Objects and methods have docstrings (4-6)
    • Objects and methods have docstrings, additional standalone documentation (7-9)
    • Objects and methods have docstrings, extensive standalone documentation with example usage (10-12)
  • Readability

    • The code is poorly organized and very difficult to read (1-3)
    • The code is readable, but challenging to understand (4-6)
    • The code is fairly easy to read (7-9)
    • The code is well organized and very easy to read (10-12)
  • Reusability

    • The code is not organized for reusability (1-3)
    • Some parts of the code could be reused (4-6)
    • Most of the code could be reused (7-9)
    • Each part of the code, and the whole, could be reused (10-12)
  • Performance

    • Program does not run (1-6)
    • Program runs, but does not produce correct output (7-12)
    • Program runs, produces correct output under most conditions (13-18)
    • Program runs, produces correct output with robust error checking (19-24)

Course Materials

Course materials are available in the course GitHub repository.