"
Team:BostonU/PUP
From 2013.igem.org
(Difference between revisions)
| Line 170: | Line 170: | ||
| - | + | <br><br> | |
<b>June 5, 2013</b><br> | <b>June 5, 2013</b><br> | ||
Design to Direction<br> | Design to Direction<br> | ||
Revision as of 16:54, 20 June 2013
June 5, 2013
Design to Direction
compare contrast doing things via puppeteer vs. human (~100-200 parts in two weeks?)
hope to reduce error and
could use tecan to switch out backbone.
maybe create basic moclo XFP transcription units
Robot does:
Moclo rxn
Transformation
Ligation
Restriction Digest
resource tracking, when to replace
Come up with hypothesis of human vs. machine
Efficiency of Robot? Puppeteer speed up planning for robot? Error of human and reaction failure?
For human error - have a partner checking for errors
Human errors
- setting plates up wrong(have partners)
- make sure dilutions are right (excel errors? have partners do excel together)
- just always have partners.
- don’t rush
Protocols must be adapted to go with puppeteer/robot. Testing to optimize.
Aiming to test by making ten devices in duplicate
Target for Tuesday June 11
figure out steps of protocol for robot in excel sheet with exact buffer/enz/etc.
10 devices
ADD WHITEBOARD PICTURE FROM DROPBOX FOLDER
June 11, 2013
See picture for parts that need to be made * 4
dilute to 25 fmol
Janoo sent working csv files for Raven
ADD WHITEBOARD PICTURE FROM DROPBOX FOLDER
June 18, 2013
download arcs file from Raven.
Arcs = raven to puppeteer
upload arc file into puppeteer
In puppeteer, select arc file, and personnel involved.
→ then assembly graph and protocol graph generated
*went over process in the assembly graph.
next step: know details of the protocols themselves
require the specific instruction of the protocol. more detailed than excel sheets and how to allocate resources.
how much and what resources are needed to go from 1 rxn to 10 rxn etc
Want higher level details--> pick up this tube, etc
labels are 8 letter labels. generated in raven/puppeteer that needs to be written on the container. (randomly generated), doesn’t tell us about the contents of the sample
Showed current naming protocol for L1
*brain storming about labeling*
maybe send out a survey to wetlab about labeling
