BE/CS/CNS/Bi 191ab: Biomolecular Computation
Professor: Erik Winfree
Winter term teaching assistants: Robert Johnson, Sam Clamons, Andrés Ortiz-Muñoz, and Lily Chen
Time & Place:
BE/CS 191a: Winter 2017, Annenberg 105, Tu & Th 10:30am-11:55am
BE/CS 191b: Spring 2017, Annenberg 314, TBA
Please start your homework set early, and come to the first relevant TA session. The homework will usually be too much to do at the last minute, and planning for this is your responsibility.
TAs (191a only): Mondays 7:30-8:30pm and Tuesdays 4-5pm in Annenberg 107 (Jan 31 & Feb 28 in Annenberg 106)
For simple and quick questions, TAs can also be reached by email at cs191_ta * dna.caltech.edu, but may not be available to answer substantial questions in a timely manner. Non-trivial questions should be deferred to and answered at the office hours. Even if you know them, please do not use the TAs' personal email addresses; it is important that all TAs be kept in the loop on class-related issues.
Professor (Winter term only): Tuesdays 1-2pm in Moore 204. This is only for things that can't be handled by the TAs, such as administrative issues. Email is answered, though often not quickly, at winfree * caltech.edu.
None. Please attend class. Everything you need to know should be presented there. The references suggested below are optional further reading, but neither sufficient nor necessary.
Syllabus for 191a:
The syllabus as presented gives you a rough idea of what will be in the class, but it is subject to change in detail. The topics and references should be considered final only on the day of the lecture, and after. Prior to that, the topics and links may be revised.
Grading Policy for 191a:
There will be roughly one problem per class lecture, with homework sets due roughly every other week. There is no midterm or final.
Homeworks: Homeworks will be graded on a 0-10 scale for each problem.
Late policy: Late homework will be penalized by 10% per day, e.g. if turned in 24 hours late, the score will be multiplied by 0.9 after grading, and if turned in 48 hours late, the penalty will be 20%. The penalty increases linearly per hour, accumulating 10% per day, until a 9 day late homework's score is multiplied by 0.1, and a 10 day late homework gets no credit. The homework sets are hard, but ample time is given. Start as soon as they are handed out.
Extension policy: Extensions may be granted by the professor only, at his discretion, for interfering situations that cannot be planned for, e.g. a health problem with a doctor's note, last-minute travel for interviews, etc. Travel that can be planned well in advance (e.g. a sports competition) is less likely to merit an extension, since starting and completing homework early should be an option.
Grade composition: Your class grade will be based on homeworks only.
Collaboration policy: For all problem sets, you may discuss problems with other students prior to writing anything down, but what you turn in must be entirely written by you, by yourself, including any program code. That is to say, the "50 foot rule" applies here explicitly for both program code and mathematical derivations, and in spirit applies to other aspects of your class work. For more detail and discussion, see the nice write-up for CS11 or this more recent flier .
Accompanying Files for Homework:
For homework 1: AnnotatedExamples.nb provides some useful hints for how to use the CRN Simulator package in Mathematica. Note that some browsers will download the package as AnnotatedExamples.nb.txt, in which case you will need to rename it after download. A worked out example for how to build complex CRNs from modular components is also available: DigitalCircuits.nb. Feel free to use any of this code while answering the homework, or feel free to develop your solutions from scratch.
For homework 2: The notebooks for homework 1 have been slightly updated to correct oversights; if you are reviewing them, it wouldn't hurt to re-download them. New for homework 2, question 1, you will need to understand and explain DynamicalSystemsNoNotes.nb. For question 2, AnnotatedExamplesSSA.nb provides some useful hints for how to use the CRN Simulator package for stochastic simulations.
For homework 3: For homework 3, problem 1, please also note that the initial condition #C = 1 is also required. For question 3, you will need to understand and augment GeneticRegulatoryNetworksNoLTU.nb.
For homework 4, problem 2: stack_machine.dna, stack_species.pdf, stack_machine.pdf. It is suggested that you download and annotate stack_species.pdf, and include that in your homework solution.
For homework 4, problem 3: Here's why we recommend using ISU TAS. Our own xgrow used to be a breeze to install and run. It still is, on Linux. On Mac OS X, it is a breeze if you have installed XQuartz and XCode and are comfortable with the command-line compiler. If that's you, just download the xgrow tarball, unpack, compile, and run. (You may need to reboot your computer after installing XCode and Xquartz.)
Otherwise, it may be easiest to use a pre-compiled version of xgrow on a virtual machine. For this, you still need to do some work, for which a fast internet connection is an absolute necessity. You will need the following: compressed VirtualBox disk image (1.3 GB!!! could take an hour to download), software such as 7-zip or Keka that is capabale of unpacking the compressed image, and VirtualBox itself. After you unpack the disk image, you will get a directory "be191-xgrow" that will contain the 4.5GB file "be191-xgrow.vdi". To use that disk image, you must start VirtualBox.app, click on "new" to create a new virtual machine, use any name you want, Microsoft Windows / Windows XP (64 bit), and other defaults until you get to the choice of "hard drive", at which point you should select "be191-xgrow.vdi". Then create the machine and power it up. The password is "xgrow". There is a README on the Desktop, and xgrow is pre-compiled in a subdirectory of the same name. Click on the menu in the upper left to start a Terminal Emulator. To verify that xgrow runs, type "cd xgrow", hit return, then type "./xgrow tilesets/BinaryTree.tiles", and hit return. A simulation should run, and you can hit "quit" in that window when it's done. Other example commands can be found in the text file "example-runs". Please look at "BusyBeaver3Square.tiles" for examples of using names, rather than numbers, for bond types.
Description for 191b:
In the spring term, we will begin by reading and discussing classic and contemporary research papers on biomolecular computation.