• LectureVideo
• IntroProgramming16

Practical Introduction to Programming for Scientists

Spring 2016

Mondays & Fridays, 9am - 10:30 N315

Since some of you don't have Blackboard access, this Wiki page will host all class material, including:

• Lecture notes
• Screen-capture video of each lecture
• Homework assignments

Note that this class now uses Python 3.5 via a free distribution called Anaconda available for Linux, Max and Windows. By using a common environment, it is easier to deal with the differences between Python on different platforms. The default Python available on Linux and Mac is still Python 2.7. Please make sure you set up Anaconda 3.5 and use that instead.

Important Instructions for Class Projects

If you believe you will need an exception to something below, please ask by Feb 26 (the final lecture !)

For your class presentation, your first slide should have:

• Your name
• Your department/program
• Descriptive title of your project
• You may wish to say something very briefly about your previous programming experience
• We will be on a tight schedule, so I will have to enforce the 10 minute timeline pretty rigorously
• Test your laptop with the projector in this room BEFORE Feb 29! You may use the network-based connection if you like, but note that it is laggy.

Please follow these instructions exactly:

• Your class project MUST be submitted by 11:59 PM on Sat, Feb 27. No revisions will be accepted after this time. You can use Sunday to prepare your oral presentation
• Your submission should consist of:
  • one or more .py files (should have sufficient comments to figure out how they work)
  • any necessary additional files to demonstrate that the program works
  • A PDF file with a brief description of your program, what inputs the program takes, what outputs the program produces, and what it is supposed to do.
  • The final item in the PDF should be a command-line to use in running the program, and any necessary instructions to demonstrate that it works.
• Combine all files into a .zip file named: Familyname_Givenname_project_2016.zip

• Email sludtke@bcm.edu with the subject "Class project submission", and attach the .zip file

Note: If your project requires data files too large to email (even for a basic demonstration), you can share the extra files with me via BigFile, DropBox or Google Drive. If you need to do this, prepare the files in advance, and include the download instructions in the PDF in the .zip file.

Class Project Overview

The class project will count for 1/2 of your grade in the class, and will be scored on both your presentation and the program itself. You will likely have only ~5 minutes to present your projects when the time comes, but that shouldn't limit their complexity or your ambitions. It is a good idea to select a project which is somewhat ambitious but has some fallback positions in case you don't succeed in everything you had planned to do. Your initial project plan will not be a factor in your final grade. If the program meets the criteria below, even if it's very different than your original aim, you will still receive full credit.

Each person will, over the course of the term, write a program, and briefly present it at the end of the term. The sole requirements for the program are:

1. It must do something useful not easily completed with existing freely available tools
2. Not be completely trivial. The complexity of your project is expected to correspond somewhat to your level of past programming experience.

Examples of past class projects

• Analysis of DNA capture targets that failed during sequencing
• Calculating the probabilities of different discrete distributions
• A Candidate Gene Searcher
• Calculating dN/dS automatically from pairs of orthologs by pipelining clustal and paml
• Pubmed search tool
• Identify evolutionarily conserved water molecules in structure
• 96-well reader and calculator
• PCR Annealing Temperature Calculator
• One click identifier for PDF files
• Scraping and processing microarray data from the lab webpage

This class attracts people with widely varying backgrounds and skill levels. Since the course is supposed to be accessible to people with little to no programming experience, the bar for achieving an acceptable grade (B) in the class is set fairly low. If you make a reasonable attempt at all of the homework assignments, even if not completely successful, and complete a class project of some sort, you can expect to get at least a B in the class. This does not mean you can slip through without making an effort at all. Particularly if you have no programming experience at all, the class WILL take a significant effort on your part. Those who don't make a reasonable attempt at virtually every assignment may not achieve a B. Turning in something incomplete is better than turning in nothing.

Homework will be assigned each class, due before the next class, at least for the first 2/3 of the term, and is handed in via email to the class TA, James (Michael) Bell <James.Bell@bcm.edu>, with a cc to sludtke@bcm.edu. We will go over solutions to homework assignments in-class. Since the class is offered for credit, homework will be graded, but on a lenient scale:

1. Homework turned in, something attempted, but not functional
2. A good effort, but with major flaws
3. Largely correct solution, but with some flaws
4. Program does what it should, with minimal flaws

Auditors are welcome, but if possible (all students, and some others) please formally audit the class, rather than just showing up. 1) this means you have at least a small commitment to actually attend and 2) if you don't formally audit, the GS has no record of your interest and they may give me a very small room to teach in next time.