flame
play

FLAME 2014/11/1 Background Complex Systems or Networks Background - PowerPoint PPT Presentation

FLAME 2014/11/1 Background Complex Systems or Networks Background Design Experiment Unpredictable Circuitry Background Incompatible parts Background Our Goal Characterize and standardize circuits to organize standard parts correctly


  1. FLAME 2014/11/1

  2. Background Complex Systems or Networks

  3. Background Design Experiment Unpredictable Circuitry

  4. Background Incompatible parts

  5. Background Our Goal • Characterize and standardize circuits to organize standard parts correctly • Apply framework-based design principle to simplify the design procedures. • Design specific mathematical models for different framework to improve prediction accuracy • Direct wet-lab experiments

  6. Outline Outline

  7. Software Introduction...

  8. Software introduction Our Work Flow

  9. Software introduction Design Module

  10. Software introduction First Glance

  11. Software introduction Select Input

  12. Software introduction Select Output

  13. Software introduction Select Design Frame

  14. Software introduction VIDEO CLIP

  15. Software introduction Assistive Design with Truth Table

  16. Software introduction Design Frame Recommendation

  17. Software introduction Display Module

  18. Software introduction Device Display

  19. Software introduction More Complicated

  20. Software introduction Parts Viewer

  21. Software introduction Vecto r

  22. Software introduction DNA Sequence for Each Part

  23. Software introduction Simulation Module

  24. Software introduction Static Performance

  25. Software introduction Dynamic Performance

  26. Software introduction Changing the Input Concentration

  27. Software introduction Smart choice of RBS

  28. Software introduction EXPERIMENT MODULE

  29. Software introduction Frequently used protocol provided

  30. Software introduction VIDEO CLIP

  31. Framework-Based Method

  32. Framework-based method Framework-Based Method • Matched Component Group (Input-Receptor- Promoter Relationships) • Structure Framework

  33. Framework-based method Input-Promoter-Receptor Tend to Cooperate with Each Other

  34. Framework-based method Matched Component Group • Input-Receptor-Output Relationships: Specificity

  35. Framework-based method (The Group) (The Output) (Specificity)

  36. Framework-based method ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Structure Framework

  37. Framework-based method Baojun Wang, Richard I Kitney, Nicolas Joly & Martin Buck Engineering modular and orthogonal genetic logic gates for robust digital-like synthetic biology Framework: Abstraction from Published Synthetic Circuits

  38. Framework-based method Structure Framework 23 Fr ame works 23 Fr ame works Advantages  Simplify design procedure  Improve the accuracy of simulation  Improve the reliability of design Framework Simplified

  39. 1. Static and dynamic performance 2. Ajustment-simulation interactions 3. Automatic substitution of RBS Simulation & Model

  40. Simulation & Model 1. Static and dynamic performance 2. Ajustment-simulation interactions 3. Automatic substitution of RBS Simulation Interface

  41. Simulation & Model Challenges in Modelling 1. Complexity in Synthetic Circuit Designs. 2. Inconsistent Modelling Format in Practice. 3. Evaluation of Circuit Performance. 4. Gap between Simulation and Wet-lab.

  42. Simulation & Model 1. Complexity in Synthetic Circuit Design. • Models of Process versus Models of Structures? For Transcription d [ mRNA ]     CN TS DeRNA [ mRNA ] dt For Translation d [ Protein ]      TE TerE [ mRNA ] De Pr o [Protein] dt

  43. Simulation & Model 1. Complexity in Synthetic Circuit Design. • Models of Process versus Models of Structures? • Using studied circuits • Basic Functional Units • Standardization & Plug-and-play fashion • Sustainability

  44. Simulation & Model 2. Inconsistent Modelling Format in Practice • Unifying functions into single format and unit : Consistency • Homogeneous solutions from similar formats  d [ P ]          F ([ P ], [ R ], , , , K , n ) [ P ]  n dt 1 ([ R ] / K )  n d [ P ] ([ A ] / K )          G ([ P ], [ A ], , , , K , n ) [ P ]  n dt 1 ([ A ] / K ) • Efficiency and High-compatibility!

  45. Simulation & Model  d [ A ]          1 Different Models for F ([ A ], [ C ], , , , K , n ) [ A ] 1 1 1 1 1 1 1  n dt 1 ([ C ] / K ) 1 1 Frameworks  d [ B ]          2 F ([ B ], [ A ], , , , K , n ) [ B ] 2 2 2 2 2 2 2 dt  1 ([ A ] / K ) n 2 2  d [ C ]          F ([ C ], [ B ], , , , K , n ) 3 [ C ] 3 3 3 3 3 3 3  n dt 1 ([ B ] / K ) 3 BBa_C0040: TetR BBa_K346001: MerR BBa_K588000: TrpR

  46. Simulation & Model AND GATE as a Dual System

  47. Simulation & Model 3. Evaluation of Circuit Performance • Sensibility • Demand • Reliability • Accessibility • Specificity

  48. Simulation & Model 4. Gap between Simulation and Wet-lab HOW WE OBTAIN SIMULATION RESULT: two basic types of interactions in our models :  d [ P ]          F ([ P ], [ R ], , , , K , n ) [ P ]  n dt 1 ([ R ] / K )  n d [ P ] ([ A ] / K )          G ([ P ], [ A ], , , , K , n ) [ P ]  n dt 1 ([ A ] / K )

  49. Wet-lab validation

  50. Wet-lab validation Wetlab Validation • E. coli strain:BL21(DE3) as host cell • When IPTG is added, the repressor from the lac operator is displaced thus T7 polymerase present and the transcription of GFP started

  51. Wet-lab validation We use standard biobricks provided by iGEM Distribution to construct the plasmids

  52. Wet-lab validation Wetlab Validation Protocol generated by FLAME Wet-lab Experiment III

  53. Wet-lab validation *Time lag due to T7 RNA Polymerase synthesis. The results above indicate that our models accord well with experimental data.

  54. Conclusion Conclusion Framework-based Circuit Design • Simplification of design procedure • Potential of automatic design of larger circuits • Hierarchical Design: Device, Parts, DNA, Vector New Simulation Module • New and efficient models • Dynamic Performance, Static Performance Wet-lab validation • Successfully validated our model with a self practice wet-lab experiment

  55. Policy & Practice Policy & practice

  56. Policy & Practice Biobrick Blast Online • OpenSource online BLAST tool for Biobrick searching.

  57. Policy & Practice Practices in High School • Promoted iGEM and Synbio to high school students around April. • Helped build the first iGEM HS team, SKLBC-China, in Guangzhou, and they won the Best Software Tool award!

  58. Policy & Practice iGEM China Community • First to propose the idea of Chinese Teams setting up iGEM China Community, an online & offline platform for information sharing. • Offline activities were held and informed via this platform, for instance, – NCTU-Formosa & the Taiwan meetup, – USTC-Software & the Hefei meetup.

  59. Future work 1. Update and technological support of online version. 2. More wet-lab validation of framework-based design principle.

  60. Requirements Bronze The following 4 goals must be achieved:  1.Register the team, have a great summer, and have fun attending the Jamboree in Boston.  2.Create and share a description of the team's project via the iGEM wiki.  3.Present a Poster and Talk at the Regional Jamboree and World Championship Jamboree.  4.Develop and make available via The Registry of Software Tools. Silver In addition to the Bronze Medal requirements, the following 4 goals must be achieved:  1.Demonstrate the relevance of your development for Synthetic Biology based on standard Parts. We fulfilled all of  2.Provide a comprehensive and well-designed User Guide.  3.Provide detailed API documentation, preferably, automatically built from source code documentation. these requirements!  4.Demonstrate that you followed best practises in software development so that other developers can modify, use and reuse your code. Gold In addition to the Bronze and Silver Medal requirements, two additional goals must be achieved:  1.Provide a convincing validation, testing the performance of the development -- experimentally (can be outsourced) or by other teams and users.  And the second goal can be any one of the following:  1.Make your software interact / interface with the Registry.  2.Re-use and further develop previous iGEM software projects.  3.Develop a well-documented library or API for other developers .  4.Support and use the SBOL and / or SBOLv standard.  5.iGEM projects involve important questions beyond the bench.

  61. Team

  62. Acknowledgements Jianhua Yang Jian Ren Yongdong Zhang Xionglei He Lingling Zheng Yan Zhang Sponsor Instructors

  63. THANKS

Recommend


More recommend