Team:BostonU/Workflow
From 2014.igem.org
(Difference between revisions)
(41 intermediate revisions not shown) | |||
Line 13: | Line 13: | ||
<tr> | <tr> | ||
- | < | + | <td scope="col" colspan="2"> |
- | </ | + | <center><img src="https://static.igem.org/mediawiki/2014/1/1a/BU14_DBTcycle.png" width="40%"></center> |
+ | <br> | ||
+ | For a detailed example of our Chimera Characterization Workflow, please check out the <a href="https://2014.igem.org/Team:BostonU/ChimeraExample">Chimera Example</a> page. Below, we present a brief outline of the major steps involved in each stage (Design, Build, Test) of the Chimera workflow, along with a few high level examples. We also define what we consider Phase I, II, and III to be for our workflow. | ||
+ | <br><br> | ||
+ | |||
+ | <h2>Phase I - Build and test basic parts.</h2> | ||
+ | Key software tools: TASBE Tools, Eugene (optional), Raven (optional) | ||
+ | </td></tr> | ||
+ | |||
<tr> | <tr> | ||
- | < | + | <td scope="col" width="50%"><center><h3>General Chimera Workflow</center></h3></td> |
- | < | + | <td scope="col" class="tableborderleft" style="padding-left: 15px"><center><h3>Case Study: BU Priority Encoder</h3></center> |
</tr> | </tr> | ||
<tr> | <tr> | ||
- | < | + | <td scope="col" > |
+ | <center><img src="https://static.igem.org/mediawiki/2014/a/a2/Phase_I_Chimera.png" width="100%"></center> | ||
- | |||
- | |||
- | <p class="tab">• 3 MoClo level 1 and 3 MoClo level 2 backbones, each with a different <a href="https://2014.igem.org/Team:BostonU/Backbones">origin of replication</a>:<br> | + | </p> </td> |
+ | |||
+ | <td scope="col" class="tableborderleft" style="padding-left: 15px"> | ||
+ | • Add parts to <a href="https://2014.igem.org/Team:BostonU/MoClo">MoClo library</a>. The following parts were found to be necessary for our priority encoder:<br><br> | ||
+ | |||
+ | <p class="tab">• 3 MoClo level 1 and 3 MoClo level 2 backbones, each with a different <a href="https://2014.igem.org/Team:BostonU/Backbones">origin of replication</a>:<br></p> | ||
<p class="dtab"> | <p class="dtab"> | ||
• ColE1<br> | • ColE1<br> | ||
Line 34: | Line 46: | ||
</p> | </p> | ||
- | • | + | <p class="tab">• 4 MoClo level 0 <a href="https://2014.igem.org/Team:BostonU/FusionProteins">fusion proteins</a>:<br></p> |
<p class="dtab"> | <p class="dtab"> | ||
- | • | + | • <i>tetR</i>_GFP<br> |
- | • | + | • <i>tetR</i>_YFP<br> |
+ | • <i>araC</i>_YFP<br> | ||
+ | • <i>araC</i>_GFP<br> | ||
+ | <br><br> | ||
</p> | </p> | ||
- | • X <a href="https://2014.igem.org/Team:BostonU/ProjectTandemPromoters">tandem promoters</a>:<br> | + | <p class="tab">• X MoClo level 0 <a href="https://2014.igem.org/Team:BostonU/ProjectTandemPromoters">tandem promoters</a>:<br> |
<p class="dtab"> | <p class="dtab"> | ||
- | • | + | • pTet_pBad<br> |
- | • ...< | + | • pBad_pTet<br> |
- | </ | + | </p> |
+ | These parts were cloned into a <i>E. coli</i> Bioline strain using our MoClo and transformation protocols. They were purified and sequenced. Additionally, we built testing devices for each of the new parts. Details can be found on the <a href="https://2014.igem.org/Team:BostonU/FusionProteins">fusion proteins </a>, <a href="https://2014.igem.org/Team:BostonU/ProjectTandemPromoters">tandem promoters </a>, and <a href="https://2014.igem.org/Team:BostonU/Backbones">origin of replication</a> project pages. We tested these using our <a href="https://static.igem.org/mediawiki/2014/7/7c/Flow_Cytometer_WorkflowYABU.xls">FACS Workflow</a> and our BD LSRFortessa flow cytometer.The TASBE Tools were then employed to characterize their expression. | ||
+ | </td> | ||
+ | </tr> | ||
- | </ | + | <tr> |
+ | <br><br> | ||
+ | <td scope="col" colspan="2"><h2>Phase II - Build and characterize TU behavior.</h2> | ||
+ | Key software tools: TASBE Tools, Eugene, Raven | ||
+ | </td></tr> | ||
+ | |||
+ | <tr> | ||
+ | <td scope="col" width="50%"><center><h3>General Chimera Workflow</center></h3></td> | ||
+ | |||
+ | <td scope="col" class="tableborderleft" style="padding-left: 15px"><center><h3>Case Study: BU Priority Encoder</h3></center> | ||
</tr> | </tr> | ||
+ | <tr> | ||
+ | <td scope="col"> | ||
+ | <center><img src="https://static.igem.org/mediawiki/2014/f/fb/Phase_II_Chimera_updated.png" width="100%"></center> | ||
+ | |||
+ | </p> </td> | ||
+ | |||
+ | <td scope="col" class="tableborderleft" style="padding-left: 15px"> | ||
+ | • Run one-pot <a href="https://2014.igem.org/Team:BostonU/Multiplexing">Multiplexing MoClo reaction</a>. We initially multiplexed RBSs. | ||
+ | <p class="tab">• Eugene was employed to visualize all possible part substitutions.<br> | ||
+ | • Raven was employed to optimize the assembly of these combinations.</p><br><br> | ||
+ | • Clone multiplexed reactions into Pro strain of <i>E. coli</i> using Pro Transformation protocol.<br><br> | ||
+ | • Pick 20 colonies per plate, purify, and sequence.<br><br> | ||
+ | • Test using flow cytometry workflow and analyze data using the TASBE Tools.<br><br> | ||
+ | </tr> | ||
+ | |||
+ | <tr> | ||
+ | <br><br> | ||
+ | <td scope="col" colspan="2"><h2>Phase III - Test regulatory arcs and assemble final device.</h2> | ||
+ | Key software tools: TASBE Tools, Eugene, Raven | ||
+ | </td></tr> | ||
+ | |||
+ | <tr> | ||
+ | <td scope="col" width="50%"><center><h3>General Chimera Workflow</center></h3></td> | ||
+ | |||
+ | <td scope="col" class="tableborderleft" style="padding-left: 15px"><center><h3>Case Study: BU Priority Encoder</h3></center> | ||
+ | </tr> | ||
+ | |||
+ | <tr> | ||
+ | <td scope="col"> | ||
+ | <center><img src="https://static.igem.org/mediawiki/2014/2/29/Phase_III_Chimera_updated.png" width="100%"></center> | ||
+ | |||
+ | |||
+ | </td> | ||
+ | |||
+ | <td scope="col" class="tableborderleft" style="padding-left: 15px"> | ||
+ | • Test individual TU regulatory arcs<br> | ||
+ | • Use Eugene to plan final device topology.<br><br> | ||
+ | • Use Raven to guide MoClo assembly of encoder.<br><br> | ||
+ | • Clone multiplexed reactions into Pro strain of <i>E. coli</i> using Pro Transformation protocol.<br><br> | ||
+ | • Pick colonies, purify, and sequence.<br><br> | ||
+ | • Test using flow cytometry workflow and analyze data using the TASBE Tools.<br><br> | ||
+ | </tr> | ||
</table> | </table> | ||
Latest revision as of 02:44, 18 October 2014
For a detailed example of our Chimera Characterization Workflow, please check out the Chimera Example page. Below, we present a brief outline of the major steps involved in each stage (Design, Build, Test) of the Chimera workflow, along with a few high level examples. We also define what we consider Phase I, II, and III to be for our workflow. Phase I - Build and test basic parts.Key software tools: TASBE Tools, Eugene (optional), Raven (optional) | |
General Chimera Workflow |
Case Study: BU Priority Encoder |
|
• Add parts to MoClo library. The following parts were found to be necessary for our priority encoder: • 3 MoClo level 1 and 3 MoClo level 2 backbones, each with a different origin of replication:
• ColE1 • 4 MoClo level 0 fusion proteins:
• tetR_GFP • X MoClo level 0 tandem promoters:
• pTet_pBad |
Phase II - Build and characterize TU behavior.Key software tools: TASBE Tools, Eugene, Raven | |
General Chimera Workflow |
Case Study: BU Priority Encoder |
|
• Run one-pot Multiplexing MoClo reaction. We initially multiplexed RBSs.
• Eugene was employed to visualize all possible part substitutions. • Clone multiplexed reactions into Pro strain of E. coli using Pro Transformation protocol. • Pick 20 colonies per plate, purify, and sequence. • Test using flow cytometry workflow and analyze data using the TASBE Tools. |
Phase III - Test regulatory arcs and assemble final device.Key software tools: TASBE Tools, Eugene, Raven | |
General Chimera Workflow |
Case Study: BU Priority Encoder |
|
• Test individual TU regulatory arcs • Use Eugene to plan final device topology. • Use Raven to guide MoClo assembly of encoder. • Clone multiplexed reactions into Pro strain of E. coli using Pro Transformation protocol. • Pick colonies, purify, and sequence. • Test using flow cytometry workflow and analyze data using the TASBE Tools. |