Difference between revisions of "BE 240, Spring 2020"

From Murray Wiki
Jump to navigationJump to search
Line 12: Line 12:
 
| width=50% |
 
| width=50% |
 
'''Class meeting times'''
 
'''Class meeting times'''
* Lectures (overview of the tool via Zoom): Tue, 3-4:30 pm PDT
+
* Lectures (overview of the tool via Zoom): Thu, 3-4:30 pm PDT
* Recitations (group debugging of student examples via Zoom): Thu, 3-4:30 pm PDT
+
* Recitations (group debugging of student examples via Zoom): Tue, 3-4:30 pm PDT
 
* Office hours (individual help via Slack): Fri, 1-5 pm PDT
 
* Office hours (individual help via Slack): Fri, 1-5 pm PDT
 
|}
 
|}
Line 23: Line 23:
 
=== Lecture Schedule ===
 
=== Lecture Schedule ===
  
Each week of the course will cover a different topic and/or tool.  The first class meeting of the week will be a description of the use of that tool on a representative problem, carried out using a Jupyter notebook that students can download and follow along with the instructor.  The second class meeting of the week will consist of problems brought forth by students in the class as they have tried to implement the tools on their own problems.  These problems will be discussed and solved in a group setting.  Weekly office hours will be offered after the second lecture to allow students to ask questions about individual tools and problem and receive help via Slack and/or Zoom.
+
Each week of the course will cover a different topic and/or tool.  The first class meeting of the week (Thu session) will be a description of the use of that tool on a representative problem, carried out using a Jupyter notebook that students can download and follow along with the instructor.  The second class meeting of the week (the following Tue) will consist of problems brought forth by students in the class as they have tried to implement the tools on their own problems.  These problems will be discussed and solved in a group setting.  Weekly office hours will be offered between the lectures to allow students to ask questions about individual tools and problem and receive help via Slack and/or Zoom.
  
 
{| class="mw-collapsible wikitable" width=100% border=1 cellpadding=5
 
{| class="mw-collapsible wikitable" width=100% border=1 cellpadding=5
Line 34: Line 34:
  
 
|- valign=top
 
|- valign=top
| W1 - 30 Mar
+
| W1 - 31 Mar
 
| Organizational week
 
| Organizational week
 
| Richard
 
| Richard
Line 40: Line 40:
 
| [[Media:W1_setup-31Mar2020.pdf|Computer setup instructions]]
 
| [[Media:W1_setup-31Mar2020.pdf|Computer setup instructions]]
 
|- valign=top
 
|- valign=top
| W2 - 6 Apr
+
| W2 - 7 Apr
 
| CRNs and simulating them with Bioscrape  
 
| CRNs and simulating them with Bioscrape  
 
| William
 
| William
Line 46: Line 46:
 
| [[http:www.cds.caltech.edu/~murray/courses/be240/sp2020/W2_bioscrape.ipynb|W2_bioscrape.ipynb]] (Jupyter notebook)
 
| [[http:www.cds.caltech.edu/~murray/courses/be240/sp2020/W2_bioscrape.ipynb|W2_bioscrape.ipynb]] (Jupyter notebook)
 
|- valign=top
 
|- valign=top
| W3 - 13 Apr
+
| W3 - 16 Apr
 
| Model reduction in bioscrape via non-mass-action propensities and rules
 
| Model reduction in bioscrape via non-mass-action propensities and rules
 
| Ayush
 
| Ayush
Line 52: Line 52:
 
|
 
|
 
|- valign=top
 
|- valign=top
| W4 - 20 Apr
+
| W4 - 23 Apr
 
| BioCRNpyler for generating large CRN models from parts
 
| BioCRNpyler for generating large CRN models from parts
 
| William
 
| William
Line 58: Line 58:
 
|
 
|
 
|- valign=top
 
|- valign=top
| W5 - 27 Apr
+
| W5 - 30 Apr
 
| Compartments as orthogonal CRNs connected by diffusion reactions and SubSBML  
 
| Compartments as orthogonal CRNs connected by diffusion reactions and SubSBML  
 
| Ayush
 
| Ayush
Line 64: Line 64:
 
|
 
|
 
|- valign=top
 
|- valign=top
| W6 - 4 May
+
| W6 - 7 May
 
| Spatial systems and signalling
 
| Spatial systems and signalling
 
| Cindy
 
| Cindy
Line 70: Line 70:
 
|
 
|
 
|- valign=top
 
|- valign=top
| W7 - 11 May
+
| W7 - 14 May
 
| Cells and Growth/death regulation
 
| Cells and Growth/death regulation
 
| Cindy
 
| Cindy
Line 76: Line 76:
 
|
 
|
 
|- valign=top
 
|- valign=top
| W8 - 18 May
+
| W8 - 21 May
 
| System ID: Bioscrape inference tools  
 
| System ID: Bioscrape inference tools  
 
| Ayush
 
| Ayush
Line 82: Line 82:
 
|
 
|
 
|- valign=top
 
|- valign=top
| W9 - 25 May
+
| W9 - 28 May
 
| Bioscrape Lineages as a well-mixed version of GRO
 
| Bioscrape Lineages as a well-mixed version of GRO
 
| William
 
| William
Line 88: Line 88:
 
|
 
|
 
|- valign=top
 
|- valign=top
| W10 - 1 Jun
+
| W10 - 4 Jun
 
| Advanced: Automated Model Reduction  
 
| Advanced: Automated Model Reduction  
 
| Ayush
 
| Ayush

Revision as of 21:31, 12 April 2020

Open Source Tools for Biological Circuit Design

Instructors

  • Richard Murray (CDS/BE), murray@cds.caltech.edu
  • Ayush Pandey (CDS), apandey@caltech.edu
  • Cindy Ren (CDS), xrren@caltech.edu
  • William Poole (CNS), wpoole@caltech.edu

Class meeting times

  • Lectures (overview of the tool via Zoom): Thu, 3-4:30 pm PDT
  • Recitations (group debugging of student examples via Zoom): Tue, 3-4:30 pm PDT
  • Office hours (individual help via Slack): Fri, 1-5 pm PDT

This is the course homepage for BE 240, Spring 2020.

This course covers the use of open source tools developed at Caltech for use in modeling and simulation of engineered biological circuits. Participants in the course will develop working knowledge of modeling, simulation, and design tools that are available for biological circuits and apply that knowledge to a circuit relevant to your research. Students will also gain insights into modeling and design choices, including what level of detail to include in a model based on the questions you are trying to ask. Finally, the course aims to expand the available applications of model-based design of biological circuits and/or the available tools for biological circuit design through open source implementations.

Lecture Schedule

Each week of the course will cover a different topic and/or tool. The first class meeting of the week (Thu session) will be a description of the use of that tool on a representative problem, carried out using a Jupyter notebook that students can download and follow along with the instructor. The second class meeting of the week (the following Tue) will consist of problems brought forth by students in the class as they have tried to implement the tools on their own problems. These problems will be discussed and solved in a group setting. Weekly office hours will be offered between the lectures to allow students to ask questions about individual tools and problem and receive help via Slack and/or Zoom.

Date Topic Lecturer Tools Notes
W1 - 31 Mar Organizational week Richard Anaconda, Jupyter, GitHub Computer setup instructions
W2 - 7 Apr CRNs and simulating them with Bioscrape William Bioscrape W2_bioscrape.ipynb (Jupyter notebook)
W3 - 16 Apr Model reduction in bioscrape via non-mass-action propensities and rules Ayush Bioscrape
W4 - 23 Apr BioCRNpyler for generating large CRN models from parts William BioCRNpyler
W5 - 30 Apr Compartments as orthogonal CRNs connected by diffusion reactions and SubSBML Ayush Sub-SBML
W6 - 7 May Spatial systems and signalling Cindy Gro
W7 - 14 May Cells and Growth/death regulation Cindy Gro
W8 - 21 May System ID: Bioscrape inference tools Ayush Bioscrape Inference
W9 - 28 May Bioscrape Lineages as a well-mixed version of GRO William Bioscrape Lineages
W10 - 4 Jun Advanced: Automated Model Reduction Ayush Auto-Reduce

Grading

This class is graded pass/fail. To pass the class, you must participate in at least 80% of the lectures and recitations and submit a final project report consisting of a Jupyter notebook demonstrating the use of two or more of the tools in the class on a problem of interest to your research.

Collaboration Policy

Collaboration is encouraged in figuring out how to use all of the tools of this course. The final project report should represent your individual understanding of how to apply the tools demonstrated in this course to a problem of interest to your research. Obtaining feedback and advice from the instructors, course participants, or others on the final project is allowed, but the final code included in the project should be written up individually, citing any sources of code snippets that are included in the notebook.