Team:NUDT CHINA/Notebook
From 2014.igem.org
(5 intermediate revisions not shown) | |||
Line 28: | Line 28: | ||
<li><a href="https://2014.igem.org/Team:NUDT_CHINA/Modeling">Modeling</a> </li> | <li><a href="https://2014.igem.org/Team:NUDT_CHINA/Modeling">Modeling</a> </li> | ||
<li><a href="https://2014.igem.org/Team:NUDT_CHINA/Notebook">Notebook</a> </li> | <li><a href="https://2014.igem.org/Team:NUDT_CHINA/Notebook">Notebook</a> </li> | ||
- | <li><a href="https://2014.igem.org/Team:NUDT_CHINA/Safety">Safety</a> </li> | + | <li><a href="https://2014.igem.org/Team:NUDT_CHINA/Safety">Safety Policy & Practices</a> </li> |
<li><a href="https://2014.igem.org/Team:NUDT_CHINA/Attributions">Attributions</a> </li> | <li><a href="https://2014.igem.org/Team:NUDT_CHINA/Attributions">Attributions</a> </li> | ||
</ul> | </ul> | ||
Line 52: | Line 52: | ||
</p> | </p> | ||
+ | <p> | ||
+ | In this way, we can cut the RBS and target gene out which means this route does not have line L (we link the 1, 2 (or 1, 3) to keep the circle structure of plasmid). Then we can test this route by the time of arriving at the ending node which reported by the report gene (we used the GFP). | ||
+ | </p> | ||
+ | <p><h5>Second stage:</h5></p> | ||
+ | <p>But we found that it was not easy get so many different good restrict enzyme. So we change the design slightly. (Fig. 3) </p> | ||
+ | <p><center><img src="https://static.igem.org/mediawiki/2014/b/b7/NUDT_CHINA_Notes_idea_3part_fig3.png" width="302" height="113" /><br>Fig. 3 the position of two same restrict enzyme sites</center></p> | ||
+ | <p>In this way, we can still finish the function of first stage but save my restrict enzymes.</p> | ||
+ | <p><h5>Third stage:</h5></p> | ||
+ | <p>The last problem is how to compare the length of different pathway. Firstly, we decide to build all the possible route and test them. That is to say, we need to cut out 1, 2, 3,…,device(s) so that we can test the entire route, which is named exhaustion, quite time-consuming. Later, we found a better way where we can only cut one device which means we only need to build <i>n</i> graph if the graph has <i>n</i> lines.</p> | ||
+ | <p>Provided that we have 5 lines in a graph like Fig. 4.</p> | ||
+ | <p><center><img src="https://static.igem.org/mediawiki/2014/2/2e/NUDT_CHINA_Notes_idea_3part_fig4.png" width="302" height="219" /><br>Fig. 4 a graph of 5 lines, where node 1 is the beginning node 4 is the ending</center></p> | ||
+ | <p>According our method to find the shortest path, the first step is to build 6 different systems. Then we tested the “finished time” of each systems. Here is the systems and their “finish time”.</p> | ||
+ | <p><center><table width="50%" boder=1 cellpadding=0 cellspacing=0> | ||
+ | <tr><td width="20%"><strong>System</strong></td><td width="40%"><strong>Array</strong></td><td width="40%">Time (Theoretically)</td></tr><tr> | ||
+ | <td>11111</td><td rowspan=6><img src="https://static.igem.org/mediawiki/2014/7/72/NUDT_CHINA_Notes_idea_3part_array.png" width="90" height="120" /></td><td>2 units</td></tr> | ||
+ | <tr><td>01111</td><td>2 units</td></tr> | ||
+ | <tr><td>10111</td><td>2 units</td></tr> | ||
+ | <tr><td>11011</td><td>2 units</td></tr> | ||
+ | <tr><td>11101</td><td>3 units</td></tr> | ||
+ | <tr><td>11110</td><td>unreachable</td></tr> | ||
+ | </table></center></p> | ||
+ | <p>Noticed that without line L<font size="-3">5</font>, the ending is inaccessible which implicates the L5 is indispensable. Though it does not block the accessibility, the absence of L<font size="-3">4</font> slows down the arrival, which implies that L4 is on the shortest path. Thus, from the date of the chart above, we can pick out the shortest path is:</p> | ||
+ | <p><center><img src="https://static.igem.org/mediawiki/2014/d/d8/NUDT_CHINA_Notes_idea_3part_lastfigure.png" width="189" height="49" /></center></p> | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
</td> | </td> | ||
</tr> | </tr> | ||
- | <tr> <td | + | <tr> |
- | < | + | <td> |
- | < | + | <h3>Protocol</h3> |
+ | <p>Here are the recapitulative protocols of the experiments that we have used.</p> | ||
+ | <p><h5>Polymerase Chain Reaction (PCR)</h5></p> | ||
+ | <p>Most of our PCRs was performed with the Recombinant Taq DNA Polymerase <i>TaKaRa Taq</i>(TM) or PrimeSTAR(R) HS DNA Polymerase and dNTP mixture (2.5mM each) under the standard 3-step PCR protocol. Touch-down RCR procedures were also used for several times to inhibit the nonspecific amplification. (Refer to the instruction for more details).</p> | ||
- | < | + | <p><h5>Plasmid Preparation</h5></p> |
- | < | + | <p>We used the TIANprep Mini Plasmid Kit (TIANGEN) to perform all of our plasmid preparation on bacteria with target plasmid. (Refer to the TIANGEN instruction for more details).</p> |
+ | <p><h5>Gel Electrophoresis & Gel Extraction</h5></p> | ||
+ | <p>After the gel electrophoresis (normal experiment), we used the TIANgel Midi Plasmid Kit (TIANGEN) to extract all our target fragment in gel. (Refer to the TIANGEN instruction for more details).</p> | ||
- | < | + | <p><h5>Endonuclease Digestion & Ligases</h5></p> |
- | < | + | <p>The enzymes we had used were EcoR I, Spe I, Xba I, Pst I, Cla I, Sal I, Kpn I (digestion), T4 DNA ligase (ligase) all of them were bought from TaKaRaTM. The digestion and ligase systems were built following the instructions of TaKaRa(TM).</p> |
- | < | + | |
+ | <p><h5>Fluorescent Fusion Protein Gene Expression</h5></p> | ||
+ | <p>Fluorometric measurement were processed with Fluoroskan(R) Ascent FL from ThermoTM using the filters of 485nm and 538nm. The E.coli to be tested was cultured in liquid LB media containing 35μg/mL chloramphenicol to OD0.6, than split into 96 well plates (from ThermoTM) by 150μL/well. The plate was then put into the Fluoroskan(R) Ascent FL and cultured in 25℃ and background shake of 90rpms. The Fluorometric measurement was processed with the interval time of 10 minutes. <p> | ||
- | < | + | <p><h3>Blue print</h3></p> |
- | < | + | <p>According our design of the whole cascade regulatory pathway as Fig. 1 showed, we can solve the Shortest Path Problem. However, building and standardizing these devices and systems means drawing the blue print.</p> |
+ | <p><center> | ||
+ | <table width="70%" border=1 cellpadding=0 cellspacing=0> | ||
+ | <tr><td width=12%><strong>Systems</strong></td><td width=88%><strong>Functional fragments at plasmid</strong></td></tr> | ||
+ | <tr><td>System “111”</td><td width=88%><img src="https://static.igem.org/mediawiki/2014/3/3f/NUDT_CHINA_Notes_timeaction_system111.png" width="567" height="121" /></td></tr> | ||
+ | <tr><td>System “011”</td><td width=88%><img src="https://static.igem.org/mediawiki/2014/2/24/NUDT_CHINA_Notes_timeaction_system011.png" width="567" height="119" /></td></tr> | ||
+ | <tr><td>System “101”</td><td width=88%><img src="https://static.igem.org/mediawiki/2014/1/1a/NUDT_CHINA_Notes_timeaction_system101.png" width="567" height="121" /></td></tr> | ||
+ | <tr><td>System “110”</td><td width=88%><img src="https://static.igem.org/mediawiki/2014/e/e6/NUDT_CHINA_Notes_timeaction_system110.png" width="567" height="119" /></td></tr> | ||
+ | </table></center></p><p> | ||
+ | Fig. 1 regulatory pathways</p> | ||
- | < | + | <p>Thus, we drew a picture of our experiment procedure. (Fig. 2) </p> |
- | < | + | <p><center><img src="https://static.igem.org/mediawiki/2014/e/ef/NUDT_CHINA_Notes_timeaction_fig2.png" width="605" height="314" /><br>Fig. 2 experiment procedure</center></p> |
- | < | + | <p><h3>Week Events</h3></p> |
- | < | + | <p>Following our big plan, we started our daily experiment.</p> |
- | + | <p><center> | |
- | <td | + | <table width=80% cellpadding=0 cellspacing=0 border=1> |
- | < | + | <tr><td width="15%"><strong>Type</strong></td><td width="25%"><strong>Week</strong></td><td width="40%"><strong>Operation</strong></td><td width=20%><strong>Result</strong><td></tr> |
- | + | <tr><td rowspan="2">Learn</td><td rowspan="2">2013.12 - 2014.4</td><td>Learing Molecular Cloning</td><td></td></tr> | |
- | <td | + | <tr><td>Developing suitable protocols for Molecular Cloning</td></tr> |
- | < | + | <tr><td>Build</td><td rowspan="2">2014.4.19 - 5.1</td><td>Amplifying and endonuclease digest plasmids of BBa_C0012, BBa_B0015, BBa_C0080, BBa_K082003 and BBa_C0062 (from Nanjing University)</td><td>Getting plasmid of BBa_C0012, BBa_B0015, BBa_C0080 & BBa_K082003 but finding BBa_C0062 invalid</td></tr> |
- | + | <tr><td>Learn</td><td>Developing suitable protocols for the operation of PSB1C3 plasmid</td><td></td></tr> | |
- | <td | + | <tr><td>Build</td><td>2014.5.2 - 5.18</td><td>Connecting BBa_C0012 & BBa_B0015, colony PCR</td><td>Tested positive</td></tr> |
- | < | + | <tr><td>Build</td><td>2014.5.24 - 6.7</td><td>Adding [T7+RBS] to the [BBa_C0012+BBa_B0015] and sequencing it</td><td>Mutation sequenced</td></tr> |
- | + | <tr><td>Build</td><td>2014.6.20 - 6.21</td><td>Adding [T7+RBS] to the [BBa_C0012+BBa_B0015] and sequencing it</td><td>Correct [T7+RBS + BBa_C0012+BBa_B0015]</td></tr> | |
- | <td | + | <tr><td>Test</td><td rowspan="6">2014.6.28 - 8.17</td><td>Testing the function of [T7+RBS + BBa_C0012+BBa_B0015] by SDS-PAGE</td><td>Getting weak stripe from SDS-PAGE (due to low expression with LVA tag)</td></tr> |
- | < | + | <tr><td>Build</td><td>Picking out BBa_C0062 by PCR valid plasmid</td><td>Standardized BBa_C0062</td></tr> |
- | + | <tr><td>Build</td><td>Standardizing three restrict enzyme sites: Cla I, Sal I & Kpn I (basic parts)</td><td>Standardized Cla I, Sal I & Kpn I and Getting correct them with name BBa_K1532000, BBa_K1532001, BBa_K1532002</td></tr> | |
- | <td | + | <tr><td>Build</td><td>Adding K09100 to [T7+RBS+ BBa_C0012+BBa_B0015]</td><td>Fluorescent expression curve of [T7+RBS+BBa_C0012+BBa_B0015+K09100]</td></tr> |
- | < | + | <tr><td>Build</td><td>Build device [BBa_R0010 + RBS + C0080 + BBa_B0015]</td><td>Sequenced correct</td></tr> |
- | + | <tr><td>Learn</td><td>Developing protocol for technique of fluorescent fusion protein gene expression (in BL21(DE3))</td><td rowspan="2">Fluorescent expression curve of [T7+RBS+BBa_C0012+BBa_B0015+K09100]. Valid bacteria with Lux I plasmid</td></tr> | |
- | <td | + | <tr><td>Build</td><td>2014.8.29 - 9.1</td><td>Amplifying, transforming Lux I (from Wuhan University) and SDS-PAGE</td></tr> |
- | < | + | <tr><td>Other</td><td></td><td>Confecting culture medium with AHL</td><td></td></tr> |
- | + | <tr><td>Test</td><td>2014.9.1 - 9.16</td><td>Testing the interaction of IPTG and AHL</td><td>Unusual phenomenon that needs further experiment and discussion</td></tr> | |
- | + | <tr><td>Build</td><td>2014.9.17 - 9.22</td><td>Synthesizing the devices of Syn_EGFP, Syn_LuxR, Syn_LuxRI and Syn_Arac and sub-cloning them into E.coli PSB1C3</td><td>Getting correct Syn_EGFP, Syn_LuxR, Syn_LuxRI and Syn_Arac and respectively named BBa_K1532003~ BBa_K1532006</td></tr> | |
- | <td | + | <tr><td>Build</td><td>2014.9.23 - 9.26</td><td>Building [PJ23104+LacI]</td><td>Getting sequenced (but untested) [PJ23104+LacI] (named BBa_K1532007)</td></tr> |
- | </tr> | + | <tr><td>Other</td><td>2014.9.27 - 9.28</td><td>Sending BBa_K1532000~ BBa_K1532006</td><td>Arriving at 2014.9.30</td></tr> |
+ | <tr><td>Build</td><td>2014.9.23 - 10.7</td><td>Building system of “111”, ”011”, ”101” and ”110”</td><td>Finished at 2014.10.15</td></tr> | ||
+ | <tr><td>Other</td><td>2014.10.4</td><td>Sending BBa_K1532007</td><td></td></tr> | ||
+ | <tr><td>Test</td><td>2014.10.13</td><td>Testing the function of [PJ23104+LacI]</td><td>Unfinished</td></tr> | ||
</table> | </table> | ||
- | + | </center></p> | |
- | + | ||
- | </ | + | |
- | + | ||
- | + | ||
- | </ | + | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
</td> | </td> | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
</tr> | </tr> | ||
+ | </table> | ||
- | < | + | <div align="right"> |
- | < | + | <a href="https://2014.igem.org/wiki/index.php?title=Team:NUDT_CHINA/Notebook&action=edit"> Click here to edit this page!</a> |
- | < | + | <a href="https://2014.igem.org/Special:Upload">Click here to upload! </a> |
- | </ | + | </div> |
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
</html> | </html> |
Latest revision as of 03:03, 18 October 2014
To solve the first problem, we built devices that contains promoter, RBS, target gene (CDS) and terminator to simulate the nodes and lines in directed graph: the promoters are nodes and the target fragment are lines. When the promoter is activated, the target gene can coding protein which then activate the next promoter as regulatory element. This regulatory process can describe how a man the walking in a directed graph: he departed from the node P1, went through the line L and finally arrived at the spot P2. In this way, theoretically, we can describe any given directed graph in E. coli. (For further details about the coding of the graph, please refer to the project profile of our wiki) (Fig. 1) Fig. 1 One promoter and one target gene can simulate one node and one line
After building one complete graph in E. coli, different route should be labelled and tested independently so that we can get the length indirectly by the time of whole travel from beginning to ending. Then we can selected the quickest one as the shortest route. However, we are stuck in the second problem: how to build different route. First design:In each regulatory unit, three different restrict enzyme sites are put between the promoter and RBS, target gene and terminator, terminator and next promoter, respectively. (Fig. 2) Fig. 2 the position of three different restrict enzyme sites In this way, we can cut the RBS and target gene out which means this route does not have line L (we link the 1, 2 (or 1, 3) to keep the circle structure of plasmid). Then we can test this route by the time of arriving at the ending node which reported by the report gene (we used the GFP). Second stage:But we found that it was not easy get so many different good restrict enzyme. So we change the design slightly. (Fig. 3) Fig. 3 the position of two same restrict enzyme sites In this way, we can still finish the function of first stage but save my restrict enzymes. Third stage:The last problem is how to compare the length of different pathway. Firstly, we decide to build all the possible route and test them. That is to say, we need to cut out 1, 2, 3,…,device(s) so that we can test the entire route, which is named exhaustion, quite time-consuming. Later, we found a better way where we can only cut one device which means we only need to build n graph if the graph has n lines. Provided that we have 5 lines in a graph like Fig. 4. Fig. 4 a graph of 5 lines, where node 1 is the beginning node 4 is the ending According our method to find the shortest path, the first step is to build 6 different systems. Then we tested the “finished time” of each systems. Here is the systems and their “finish time”.
Noticed that without line L5, the ending is inaccessible which implicates the L5 is indispensable. Though it does not block the accessibility, the absence of L4 slows down the arrival, which implies that L4 is on the shortest path. Thus, from the date of the chart above, we can pick out the shortest path is: |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ProtocolHere are the recapitulative protocols of the experiments that we have used. Polymerase Chain Reaction (PCR)Most of our PCRs was performed with the Recombinant Taq DNA Polymerase TaKaRa Taq(TM) or PrimeSTAR(R) HS DNA Polymerase and dNTP mixture (2.5mM each) under the standard 3-step PCR protocol. Touch-down RCR procedures were also used for several times to inhibit the nonspecific amplification. (Refer to the instruction for more details). Plasmid PreparationWe used the TIANprep Mini Plasmid Kit (TIANGEN) to perform all of our plasmid preparation on bacteria with target plasmid. (Refer to the TIANGEN instruction for more details). Gel Electrophoresis & Gel ExtractionAfter the gel electrophoresis (normal experiment), we used the TIANgel Midi Plasmid Kit (TIANGEN) to extract all our target fragment in gel. (Refer to the TIANGEN instruction for more details). Endonuclease Digestion & LigasesThe enzymes we had used were EcoR I, Spe I, Xba I, Pst I, Cla I, Sal I, Kpn I (digestion), T4 DNA ligase (ligase) all of them were bought from TaKaRaTM. The digestion and ligase systems were built following the instructions of TaKaRa(TM). Fluorescent Fusion Protein Gene ExpressionFluorometric measurement were processed with Fluoroskan(R) Ascent FL from ThermoTM using the filters of 485nm and 538nm. The E.coli to be tested was cultured in liquid LB media containing 35μg/mL chloramphenicol to OD0.6, than split into 96 well plates (from ThermoTM) by 150μL/well. The plate was then put into the Fluoroskan(R) Ascent FL and cultured in 25℃ and background shake of 90rpms. The Fluorometric measurement was processed with the interval time of 10 minutes.
Blue printAccording our design of the whole cascade regulatory pathway as Fig. 1 showed, we can solve the Shortest Path Problem. However, building and standardizing these devices and systems means drawing the blue print.
Fig. 1 regulatory pathways Thus, we drew a picture of our experiment procedure. (Fig. 2) Fig. 2 experiment procedure Week EventsFollowing our big plan, we started our daily experiment.
|