|
|
(6 intermediate revisions not shown) |
Line 94: |
Line 94: |
| overflow: hidden; | | overflow: hidden; |
| margin: 0 auto; | | margin: 0 auto; |
- | color:white; | + | color: white; |
| } | | } |
| * html body { | | * html body { |
Line 112: |
Line 112: |
| height: auto; | | height: auto; |
| float: left; | | float: left; |
- | padding-bottom: 50px;
| + | padding-bottom: 50px; |
| z-index: 10; | | z-index: 10; |
- | color:white; | + | color: white; |
| } | | } |
| .content2 { | | .content2 { |
Line 122: |
Line 122: |
| margin: 0 auto; | | margin: 0 auto; |
| position: relative; | | position: relative; |
- | padding: 30px 0px 30px 0; | + | padding: 0; |
| } | | } |
| .content2 .text { | | .content2 .text { |
- | width: 800px; | + | width: 900px; |
| bottom: 0px; | | bottom: 0px; |
- | height: 420px; | + | height: 500px; |
| margin: 0 auto; | | margin: 0 auto; |
| padding: 0px 30px 0px 20px; | | padding: 0px 30px 0px 20px; |
| text-align: justify; | | text-align: justify; |
| overflow: auto; | | overflow: auto; |
- | background-color:black; | + | background-color: black; |
- | opacity:0.85; | + | opacity: 0.85; |
| } | | } |
| .content2 .text p span { | | .content2 .text p span { |
Line 142: |
Line 142: |
| .content2 .text strong { | | .content2 .text strong { |
| font-size: 12px; | | font-size: 12px; |
- | color: purple; | + | color: aqua; |
| } | | } |
| .homepage { | | .homepage { |
Line 154: |
Line 154: |
| } | | } |
| #smallwrap { | | #smallwrap { |
- | width: 750px; | + | width: 880px; |
| margin: 0 auto; | | margin: 0 auto; |
| } | | } |
| .smallbox { | | .smallbox { |
- | width: 350px; | + | width: 410px; |
| float: left; | | float: left; |
| padding: 5px; | | padding: 5px; |
Line 166: |
Line 166: |
| text-align: center; | | text-align: center; |
| } | | } |
- | h1,h2,h3,h4,h5 {color:white;} | + | h1, h2, h3, h4, h5 { |
| + | color: white; |
| + | } |
| .smallbox .img { | | .smallbox .img { |
| height: 105px; | | height: 105px; |
Line 174: |
Line 176: |
| -webkit-box-shadow: 0px 0px 10px #333; | | -webkit-box-shadow: 0px 0px 10px #333; |
| box-shadow: 0px 0px 10px #333; | | box-shadow: 0px 0px 10px #333; |
| + | background: white; |
| } | | } |
| .smalltext { | | .smalltext { |
Line 181: |
Line 184: |
| font-size: 11px; | | font-size: 11px; |
| overflow: auto; | | overflow: auto; |
| + | color: black; |
| + | } |
| + | .month { |
| + | width: 120px; |
| + | float: left; |
| + | font-size: 15px; |
| + | font-weight: bold; |
| + | padding: 10px; |
| + | background-color: #fc3c3c; |
| + | clear: both; |
| + | } |
| + | .general { |
| + | width: 800px; |
| + | float: left; |
| + | font-size: 12px; |
| + | text-transform: none; |
| + | font-weight: normal; |
| + | padding: 10px; |
| + | background-color: orange; |
| + | clear: both; |
| + | } |
| + | .week1, .week3 { |
| + | width: 180px; |
| + | float: left; |
| + | font-size: 12px; |
| + | padding-right: 5px; |
| + | font-weight: normal; |
| + | background-color: #1e6dd4; |
| + | padding: 10px; |
| + | } |
| + | .week2, .week4 { |
| + | width: 180px; |
| + | float: left; |
| + | font-size: 12px; |
| + | padding-right: 5px; |
| + | font-weight: normal; |
| + | background-color: #3fff72; |
| + | padding: 10px; |
| + | } |
| + | .lower { |
| + | width: 800px; |
| + | clear: both; |
| + | } |
| + | #notebook2 { |
| + | width: 900px; |
| + | color: black; |
| + | margin: 0 auto 20 auto; |
| + | } |
| + | #week { |
| + | font-size: 14px; |
| + | font-weight: bold; |
| } | | } |
- | .alternative { | + | .black { |
- | background-color: white; | + | color: black; |
| } | | } |
| .selected { | | .selected { |
Line 263: |
Line 317: |
| <div class="text"> | | <div class="text"> |
| <h2>Team</h2> | | <h2>Team</h2> |
- | <div id="slider" style="opacity:1;"> | + | <div id="slider"> |
- | <img alt="" src="https://static.igem.org/mediawiki/2010/e/e7/Metu-slide1.jpg"> | + | <img alt="" src="https://static.igem.org/mediawiki/2010/f/f3/Metu-team1.jpg"> |
- | <img alt="" src="https://static.igem.org/mediawiki/2010/e/e1/Metu-slide2.jpg"> | + | <img alt="" src="https://static.igem.org/mediawiki/2010/d/d4/Metu-team2.jpg"> |
- | <img alt="" src="https://static.igem.org/mediawiki/2010/b/b8/Metu-slide3.jpg"> | + | <img alt="" src="https://static.igem.org/mediawiki/2010/3/34/Metu-team3.jpg"> |
| + | <img alt="" src="https://static.igem.org/mediawiki/2010/d/d8/Metu-team4.jpg"> |
| + | <img alt="" src="https://static.igem.org/mediawiki/2010/0/03/Metu-team5.jpg"> |
| + | <img alt="" src="https://static.igem.org/mediawiki/2010/b/be/Metu-team6.jpg"> |
| </div> | | </div> |
| <p>METU Turkey Software is an interdisciplinary team of 8 students and | | <p>METU Turkey Software is an interdisciplinary team of 8 students and |
Line 277: |
Line 334: |
| </div> | | </div> |
| <div class="smallbox"> | | <div class="smallbox"> |
- | <h2>Tolga Can</h2> | + | <h2 class="black">Tolga Can</h2> |
| <img src="https://static.igem.org/mediawiki/2010/c/c3/Metu-tolgahoca.jpg"> | | <img src="https://static.igem.org/mediawiki/2010/c/c3/Metu-tolgahoca.jpg"> |
| <div class="smalltext"> | | <div class="smalltext"> |
Line 289: |
Line 346: |
| </div> | | </div> |
| </div> | | </div> |
- | <div class="smallbox alternative"> | + | <div class="smallbox"> |
- | <h2>Yeşim Aydın-Son</h2> | + | <h2 class="black">Yeşim Aydın-Son</h2> |
| <img src="https://static.igem.org/mediawiki/2010/d/d5/Metu-yesimhoca.jpg"> | | <img src="https://static.igem.org/mediawiki/2010/d/d5/Metu-yesimhoca.jpg"> |
| <div class="smalltext"> | | <div class="smalltext"> |
Line 309: |
Line 366: |
| </div> | | </div> |
| </div> | | </div> |
- | <div class="smallbox alternative"> | + | <div class="smallbox"> |
- | <h2>Ömer Nebil Yaveroğlu</h2> | + | <h2 class="black">Ömer Nebil Yaveroğlu</h2> |
- | <img src=""> | + | <img src="https://static.igem.org/mediawiki/2010/5/53/Metu-omerhoca.jpg"> |
| <div class="smalltext"> | | <div class="smalltext"> |
- | <p>Content here</p> | + | <p>Ömer Nebil Yaveroğlu is currently a PhD Student in Imperial |
| + | College, London. He has worked as a teaching assistant between |
| + | 2008 – 2010 in the Computer Engineering Department of Middle |
| + | East Turkey. Throughout his MSc studies, he tried to understand |
| + | the orthological similarities between the protein interaction |
| + | networks of different species using graph theory. He helped |
| + | the group as an advisor in the computing related discussions</p> |
| </div> | | </div> |
| </div> | | </div> |
| <div class="smallbox"> | | <div class="smallbox"> |
- | <h2>Burak Yılmaz</h2> | + | <h2 class="black">Burak Yılmaz</h2> |
| <img src="https://static.igem.org/mediawiki/2010/a/a2/Metu-burak.jpg"> | | <img src="https://static.igem.org/mediawiki/2010/a/a2/Metu-burak.jpg"> |
| <div class="smalltext"> | | <div class="smalltext"> |
Line 340: |
Line 403: |
| </div> | | </div> |
| <div class="smallbox" style="margin: 0 auto; float: none"> | | <div class="smallbox" style="margin: 0 auto; float: none"> |
- | <h2>Muhammad Akif Ağca</h2> | + | <h2 class="black">Muhammad Akif Ağca</h2> |
| <img src=""> | | <img src=""> |
| <div class="smalltext"> | | <div class="smalltext"> |
Line 348: |
Line 411: |
| <div class="clear"> | | <div class="clear"> |
| </div> | | </div> |
- | <div class="smallbox alternative"> | + | <div class="smallbox"> |
- | <h2>Cihan Taştan</h2> | + | <h2 class="black">Cihan Taştan</h2> |
| <img src="https://static.igem.org/mediawiki/2010/d/d8/Metu-cihan.jpg"> | | <img src="https://static.igem.org/mediawiki/2010/d/d8/Metu-cihan.jpg"> |
| <div class="smalltext"> | | <div class="smalltext"> |
Line 361: |
Line 424: |
| </div> | | </div> |
| <div class="smallbox"> | | <div class="smallbox"> |
- | <h2>Hassan Salehe Matar</h2> | + | <h2 class="black">Hassan Salehe Matar</h2> |
| <img src="https://static.igem.org/mediawiki/2010/3/3c/Metu-hassan.jpg"> | | <img src="https://static.igem.org/mediawiki/2010/3/3c/Metu-hassan.jpg"> |
| <div class="smalltext"> | | <div class="smalltext"> |
Line 377: |
Line 440: |
| </div> | | </div> |
| <div class="smallbox"> | | <div class="smallbox"> |
- | <h2>Ayub Rokhman Wakhid</h2> | + | <h2 class="black">Ayub Rokhman Wakhid</h2> |
| <img src="https://static.igem.org/mediawiki/2010/9/92/Metu-ayub.jpg"> | | <img src="https://static.igem.org/mediawiki/2010/9/92/Metu-ayub.jpg"> |
| <div class="smalltext"> | | <div class="smalltext"> |
Line 389: |
Line 452: |
| </div> | | </div> |
| </div> | | </div> |
- | <div class="smallbox alternative"> | + | <div class="smallbox"> |
- | <h2>Muhammad Fakhry Syauqy</h2> | + | <h2 class="black">Muhammad Fakhry Syauqy</h2> |
| <img src="https://static.igem.org/mediawiki/2010/f/fd/Metu-fakhry.jpg"> | | <img src="https://static.igem.org/mediawiki/2010/f/fd/Metu-fakhry.jpg"> |
| <div class="smalltext"> | | <div class="smalltext"> |
Line 403: |
Line 466: |
| </div> | | </div> |
| </div> | | </div> |
- | <div class="smallbox alternative"> | + | <div class="smallbox"> |
- | <h2>Saygın Karaaslan</h2> | + | <h2 class="black">Saygın Karaaslan</h2> |
| <img src="https://static.igem.org/mediawiki/2010/6/6f/Metu-saygin.jpg"> | | <img src="https://static.igem.org/mediawiki/2010/6/6f/Metu-saygin.jpg"> |
| <div class="smalltext"> | | <div class="smalltext"> |
Line 419: |
Line 482: |
| </div> | | </div> |
| <div class="smallbox"> | | <div class="smallbox"> |
- | <h2>Yener Tuncel</h2> | + | <h2 class="black">Yener Tuncel</h2> |
| <img src="https://static.igem.org/mediawiki/2010/d/dd/Metu-yener.jpg"> | | <img src="https://static.igem.org/mediawiki/2010/d/dd/Metu-yener.jpg"> |
| <div class="smalltext"> | | <div class="smalltext"> |
Line 533: |
Line 596: |
| <div class="text"> | | <div class="text"> |
| <h2>Notebook</h2> | | <h2>Notebook</h2> |
| + | <div id="notebook2"> |
| + | <div class="month"> |
| + | January</div> |
| + | <div class="general"> |
| + | <p>Brain Storming about the iGEM. </p> |
| + | <ul> |
| + | <li>What is iGEM.</li> |
| + | <li>Previous Wet-Lab Projects developed at METU.</li> |
| + | <li>What kind of projects can be developed as a software |
| + | team.</li> |
| + | </ul> |
| + | <p>NOTE: The first software team in Turkey...</p> |
| + | </div> |
| + | <div class="month"> |
| + | February</div> |
| + | <div class="general"> |
| + | <ul> |
| + | <li>Reading articles about iGEM WetLab and Software team |
| + | projects.</li> |
| + | <li>Looking for the members of the team.</li> |
| + | <li>Looking for the instructors who can consult the team. |
| + | </li> |
| + | </ul> |
| + | </div> |
| + | <div class="month"> |
| + | March</div> |
| + | <div class="general"> |
| + | <ul> |
| + | <li>Employing a member to team interested in Synthetic Biology.</li> |
| + | <li>Reading articles about Synthetic Biology, Bioinformatics |
| + | and Bio Engineering.</li> |
| + | <li>Founding the team [ An instructor, and student members |
| + | ]</li> |
| + | </ul> |
| + | </div> |
| + | <div class="month"> |
| + | April</div> |
| + | <div class="general"> |
| + | At this month we have started regular workshop about Synthetic |
| + | Biology, Bioengineering, and Bioinformatics. |
| + | <ul> |
| + | <li>This month biologists in the team telling the needed |
| + | basics to software group.</li> |
| + | </ul> |
| + | </div> |
| + | <div class="lower"> |
| + | <div class="week1" style="height: 150px;"> |
| + | <div id="week"> |
| + | Week 1</div> |
| + | <p>Workshop -1</p> |
| + | <p>[Biology basics, What is Synthetic Biology?, and the |
| + | works in this field ]</p> |
| + | </div> |
| + | <div class="week2" style="height: 150px;"> |
| + | <div id="week"> |
| + | Week 2</div> |
| + | <p>Workshop -2</p> |
| + | <p>[What is Synthetic Biology?, and the works in this field |
| + | ]</p> |
| + | </div> |
| + | <div class="week3" style="height: 150px;"> |
| + | <div id="week"> |
| + | Week 3</div> |
| + | <p>Workshop -3</p> |
| + | <p>[iGEM, Parts, Biobricks, and Devices ]</p> |
| + | </div> |
| + | <div class="week4" style="height: 150px;"> |
| + | <div id="week"> |
| + | Week 4</div> |
| + | <p>Workshop – 4</p> |
| + | <p>[iGEM, Parts, Biobricks, and Devices ]</p> |
| + | </div> |
| + | </div> |
| + | <div class="month"> |
| + | May</div> |
| + | <div class="general"> |
| + | At this month we have completed our workshops, and as the masters |
| + | in this field started meeting with instructors. / |
| + | <ul> |
| + | <li>Meanwhile, looking for sponsors [We have designed a |
| + | document telling the iGEM, previous project and our project |
| + | generally and started to send it private companies who can |
| + | found us.] </li> |
| + | <li>This month it is turn to software group; they are transferring |
| + | the basics of software concepts to biologists in the team. |
| + | </li> |
| + | <li>Furthermore, we are discussing about how we can apply |
| + | the basics of computer engineering to synthetic biology |
| + | and iGEM parts. </li> |
| + | </ul> |
| + | </div> |
| + | <div class="lower"> |
| + | <div class="week1" style="height: 180px;"> |
| + | <div id="week"> |
| + | Week 1</div> |
| + | <p>Meeting -1</p> |
| + | <p>[First, discussion on articles that have been selected |
| + | by consulters. Then, brain storming about the selected iGEM |
| + | projects from previous years and our project ]</p> |
| + | </div> |
| + | <div class="week2" style="height: 180px;"> |
| + | <div id="week"> |
| + | Week 2</div> |
| + | <p>Meeting -2[with consulters ]</p> |
| + | <p>[Tellingtheprevious projects to consulters and telling |
| + | our initial idea about project. Then, brainstorming about |
| + | our project. ]</p> |
| + | </div> |
| + | <div class="week3" style="height: 180px;"> |
| + | <div id="week"> |
| + | Week 3</div> |
| + | <p>Meeting -3</p> |
| + | <p>[Basic databaseconcepts and iGEM parts. ]</p> |
| + | </div> |
| + | <div class="week4" style="height: 180px;"> |
| + | <div id="week"> |
| + | Week 4</div> |
| + | <p>Meeting -4</p> |
| + | <p>[What is ER Diagram and How we can develop a database |
| + | model for iGEM parts with ER Model. ]</p> |
| + | </div> |
| + | </div> |
| + | <div class="month"> |
| + | June</div> |
| + | <div class="general"> |
| + | <p>At this month software group is going on to tell the basics |
| + | of software development and programming and computer engineering, |
| + | discussions about the computer engineering approaches are continuing.</p> |
| + | <ul> |
| + | <li>Furthermore, we have constructed the design group for |
| + | web page, poster, presentation, and an attractive animation |
| + | telling us.</li> |
| + | </ul> |
| + | </div> |
| + | <div class="lower"> |
| + | <div class="week1" style="height: 250px;"> |
| + | <div id="week"> |
| + | Week 1</div> |
| + | <p>Meeting – 5</p> |
| + | <p>[Graph theory, Graph theoretic modeling, and graphical |
| + | modeling of iGEM parts. Using Input Output loops on iGEM |
| + | parts. ]</p> |
| + | </div> |
| + | <div class="week2" style="height: 250px;"> |
| + | <div id="week"> |
| + | Week 2</div> |
| + | <p>Meeting – 6 [ With Consulters ]</p> |
| + | <ul> |
| + | <li>Project Description. </li> |
| + | <li>Our tasks on holiday.</li> |
| + | <li>Telling our project and basic concepts to design |
| + | team.</li> |
| + | <li>Discussion on storyboard for animation.</li> |
| + | </ul> |
| + | </div> |
| + | <div style="height: 250px; background-color: #1e6dd4; padding: 10px;"> |
| + | <div id="week"> |
| + | Week 3 and Week 4</div> |
| + | <p align="center">HAVE a NICE HOLIDAY</p> |
| + | <p align="center">SEE YOU ON JULY 1 as a POWERFUL TEAM; |
| + | <em>“METU TURKEY SOFTWARE”</em>.</p> |
| + | </div> |
| + | </div> |
| + | <div class="month"> |
| + | July</div> |
| + | <div class="general"> |
| + | <p>At this month we have started to develop application. And |
| + | divided the team to 3 groups [ Software - Gene – Design ].</p> |
| + | <ul> |
| + | <li>Gene group is providing row data to software group by |
| + | extracting it from the part registery and other resources.</li> |
| + | <li>Software group is developing application.</li> |
| + | <li>Designers are learning new design tools, and applying |
| + | those to our project [Not all Members of the group working |
| + | actively for the team].</li> |
| + | </ul> |
| + | <p><u>NOTE: Members are not strictly assigned to a group; this |
| + | is just for organization of tasks.</u></p> |
| + | </div> |
| + | <div class="lower"> |
| + | <div class="week1" style="height: 600px;"> |
| + | <div id="week"> |
| + | Week 1</div> |
| + | <p>Meeting-7</p> |
| + | <ul> |
| + | <li>Take stock for current situation.</li> |
| + | <li>Discussion on web, poster, animation design.</li> |
| + | <li>Discussion on storyboard for animation.</li> |
| + | <li>Task analyses for each group [ Software, Gene, Design |
| + | ].</li> |
| + | </ul> |
| + | </div> |
| + | <div class="week2" style="height: 600px;"> |
| + | <div id="week"> |
| + | Week 2</div> |
| + | <p>Meeting – 8</p> |
| + | <p>Checking the tasks of each group. </p> |
| + | <p>· Software Group</p> |
| + | <ul> |
| + | <li>Database Design</li> |
| + | <li>Interface for DB.</li> |
| + | <li>Designing a basic SRS and SDD to be able to state |
| + | the requirements of application exactly .</li> |
| + | </ul> |
| + | <p>· Gene Group</p> |
| + | <ul> |
| + | <li>Extracting I/O information for each part in part |
| + | registry according to specified standards by Gene group.</li> |
| + | <li>Discussion about expectation from the software. |
| + | </li> |
| + | </ul> |
| + | <p>· Design Group</p> |
| + | <ul> |
| + | <li>Team Logo</li> |
| + | <li>Web site</li> |
| + | <li>Poster</li> |
| + | <li>Animation</li> |
| + | <li>Presentation</li> |
| + | </ul> |
| + | </div> |
| + | <div style="height: 600px; background-color: #1e6dd4; padding: 10px"> |
| + | <div id="week"> |
| + | Week 3 and Week 4 |
| + | <p>DOING THE TASKS.</p> |
| + | </div> |
| + | </div> |
| + | </div> |
| + | <div class="month"> |
| + | August</div> |
| + | <div class="general"> |
| + | <p>At this month we have started to apply graph theory on iGEM |
| + | parts. We have specified nodes, edges, graph types. Furthermore, |
| + | we have started to develop a new “ Part Registery Form ” to |
| + | be able to more standardize the part entry to be able to apply |
| + | some algorithms on the parts more efficiently.</p> |
| + | </div> |
| + | <div class="lower"> |
| + | <div class="week1" style="height: 350px;"> |
| + | <div id="week"> |
| + | Week 1</div> |
| + | <p>Meeting -8</p> |
| + | <p>/ </p> |
| + | <ul> |
| + | <li>Node data extraction algorithm.</li> |
| + | <li>Node description. </li> |
| + | <li>Visualization of nodes.</li> |
| + | <li>Pathway finding according to specified I/O properties.</li> |
| + | <li>Representing the nodes with original images.</li> |
| + | </ul> |
| + | </div> |
| + | <div class="week2" style="height: 350px;"> |
| + | <div id="week"> |
| + | Week 2</div> |
| + | <p>Meeting -9</p> |
| + | <ul> |
| + | <li>Whichone is node part or subparts or both are nodes |
| + | in different graphs?</li> |
| + | <li>Part Combination rules.</li> |
| + | <li>Web site, Poster Content</li> |
| + | <li>Animation storyboard. </li> |
| + | <li>Survey for new “Part Registery Standarts”.</li> |
| + | <li>NewPart Registery Form.</li> |
| + | </ul> |
| + | </div> |
| + | <div class="week3" style="height: 350px;"> |
| + | <div id="week"> |
| + | Week 3</div> |
| + | <p>Meeting -10</p> |
| + | <p>/ </p> |
| + | <ul> |
| + | <li>Extraction of Part Combination Rules </li> |
| + | <li>Web, poster, presentation contents generally. |
| + | </li> |
| + | <li></li> |
| + | </ul> |
| + | </div> |
| + | <div class="week4" style="height: 350px;"> |
| + | <div id="week"> |
| + | Week 4</div> |
| + | <p>Meeting -11</p> |
| + | <ul> |
| + | <li>USTC and Berkeley projects.[ https://2009.igem.org/Team:USTC_Software |
| + | and https://2009.igem.org/Team:Berkeley_Software </li> |
| + | <li>Graphical representation of node relations. </li> |
| + | <li>Part Combination Rules </li> |
| + | <li>Subpart Combinations Rules </li> |
| + | <li>Expectations from the software (SRS: Functional; |
| + | Requirements) </li> |
| + | </ul> |
| + | </div> |
| + | </div> |
| + | <div class="month"> |
| + | September</div> |
| + | <div class="general"> |
| + | At this time all bases for application were nearly to finish, |
| + | the software group was waiting row data from the gene group. |
| + | Meanwhile, they were working on code bases.</div> |
| + | <div class="lower"> |
| + | <div class="week1" style="height: 350px;"> |
| + | <div id="week"> |
| + | Week 1 </div> |
| + | <p>DOING THE TASKS. </p> |
| + | </div> |
| + | <div class="week2" style="height: 350px;"> |
| + | <div id="week"> |
| + | Week 2</div> |
| + | <p>Meeting -12</p> |
| + | <ul> |
| + | <li>Final Database </li> |
| + | <li>Final Graphs </li> |
| + | <li>GUI </li> |
| + | <li>Expectations from the software (SRS: Functional |
| + | Requirements) (Suggestions)</li> |
| + | <li>Survey details</li> |
| + | </ul> |
| + | </div> |
| + | <div class="week3" style="height: 350px;"> |
| + | <div id="week"> |
| + | Week 3</div> |
| + | <p>Meeting -13</p> |
| + | <ul> |
| + | <li>Animation (Storyboard, timeline) </li> |
| + | <li>Web site (Suggestions to web site) </li> |
| + | <li>Poster (How we can use 3D stereoscopic image, How |
| + | we can tell the development progress and our concepts |
| + | by 3D effect etc...) </li> |
| + | <li>Presentation ( Suggestions about presentation )</li> |
| + | </ul> |
| + | </div> |
| + | <div class="week4" style="height: 350px;"> |
| + | <div id="week"> |
| + | Week 4</div> |
| + | <p>Meeting -14</p> |
| + | <ul> |
| + | <li>Final Graphs </li> |
| + | <li>GUI ( about 70 % is over ) </li> |
| + | <li>How to send the software to other teams for collaboration |
| + | ( just general ideas, details will be talked later ). |
| + | </li> |
| + | <li>With survey or not , can it shade the software? |
| + | </li> |
| + | <li>What to ask to teams while sending?</li> |
| + | </ul> |
| + | </div> |
| + | </div> |
| + | <div class="month"> |
| + | October</div> |
| + | <div class="general"> |
| + | <p>Now everything is nearly over, it is time to put everything |
| + | together.</p> |
| + | <ul> |
| + | <li>Gene group explaining the methods that we have used |
| + | during project.</li> |
| + | <li>Software group finalizing, software, testing it importing |
| + | new function according to collaboration results with METU |
| + | TURKEY wet lab team., trying to solve infinite bugs…</li> |
| + | <li>Design group putting all together…</li> |
| + | <li>Meanwhile, all team is writing the content for web, |
| + | poster, and presentation.</li> |
| + | </ul> |
| + | </div> |
| + | <div class="lower"> |
| + | <div class="week1" style="height: 170px;"> |
| + | <div id="week"> |
| + | Week 1</div> |
| + | <p>Meeting -15</p> |
| + | <ul> |
| + | <li>BioGuide Application, missing points.</li> |
| + | <li>Content writing</li> |
| + | <li>Web, poster, animation</li> |
| + | </ul> |
| + | </div> |
| + | <div style="float: left; width: 540px; height: 170px; font-weight: normal; background-color: #3fff72; padding: 10px;"> |
| + | <div id="week"> |
| + | Week 2, Week 3, & Week 4 |
| + | <p>GOOD NEWS Infinite meetings started :) </p> |
| + | <ul> |
| + | <li>Writing content [shared it, tasks assigned to |
| + | members according to their fields.]</li> |
| + | <li>Software; debugging, testing, adding functions…</li> |
| + | <li>Designers web, poster, presentation, animation, |
| + | importing content…</li> |
| + | </ul> |
| + | </div> |
| + | </div> |
| + | </div> |
| + | <div class="month"> |
| + | November</div> |
| + | <div class="general"> |
| + | <p align="center">November 1 – 12 is our ticket dates,</p> |
| + | <p align="center">See you in BOSTON …</p> |
| + | <p align="center">METU TURKEY SOFTWARE</p> |
| + | </div> |
| + | </div> |
| </div> | | </div> |
| </div> | | </div> |
Line 562: |
Line 1,019: |
| <li>Lethbridge</li> | | <li>Lethbridge</li> |
| <li>WashU</li> | | <li>WashU</li> |
- | <li>...</li>
| |
- | <li>...</li>
| |
- | <li>...</li>
| |
| </ul> | | </ul> |
| <li>Out of 244 participants between 10 to 22.10.2010, 57% of the | | <li>Out of 244 participants between 10 to 22.10.2010, 57% of the |
Line 814: |
Line 1,268: |
| all parts registry users as a build-in option in the next version of | | all parts registry users as a build-in option in the next version of |
| BioGuide in iGEM 2011. </i></p> | | BioGuide in iGEM 2011. </i></p> |
- | <h4>NEW PARTS REGISTRY FORM SUGGESTED FOR THE NEW STANDARDS</h4> | + | <br> |
- | <p><a href="">Link out to the form</a></p>
| + | <h2>New Parts Registry Form Suggested for The New Standards</h2> |
- | </div>
| + | <img src="https://static.igem.org/mediawiki/2010/1/17/Metu-form1.png"> |
- | </div>
| + | <h3>Description</h3> |
- | </div>
| + | <p>Warning Boxes: </p> |
- | <div class="clear">
| + | |
- | </div>
| + | |
- | <!-- 2nd row -->
| + | |
- | <div class="item">
| + | |
- | </div>
| + | |
- | <div class="item">
| + | |
- | </div>
| + | |
- | <div class="item">
| + | |
- | </div>
| + | |
- | <div class="item">
| + | |
- | </div>
| + | |
- | <div id="project2" class="item">
| + | |
- | <div class="content2">
| + | |
- | <div class="text">
| + | |
- | <h2>Design</h2> | + | |
- | </div>
| + | |
- | </div>
| + | |
- | </div>
| + | |
- | <div class="item"> | + | |
- | </div>
| + | |
- | <div id="download2" class="item">
| + | |
- | <div class="content2">
| + | |
- | <div class="text">
| + | |
- | <h2>Code</h2>
| + | |
- | </div>
| + | |
- | </div>
| + | |
- | </div>
| + | |
- | <div id="miscellaneous2" class="item">
| + | |
- | <div class="content2">
| + | |
- | <div class="text">
| + | |
- | <h2>Human Practices</h2>
| + | |
- | </div>
| + | |
- | </div>
| + | |
- | </div>
| + | |
- | <div class="clear">
| + | |
- | </div>
| + | |
- | <!-- 3rd row -->
| + | |
- | <div class="item">
| + | |
- | </div>
| + | |
- | <div class="item">
| + | |
- | </div>
| + | |
- | <div class="item">
| + | |
- | </div>
| + | |
- | <div class="item">
| + | |
- | </div>
| + | |
- | <div id="project3" class="item">
| + | |
- | <div class="content2">
| + | |
- | <div class="text">
| + | |
- | <h2>Material</h2> | + | |
- | </div>
| + | |
- | </div>
| + | |
- | </div>
| + | |
- | <div class="item">
| + | |
- | </div>
| + | |
- | <div id="download3" class="item">
| + | |
- | <div class="content2">
| + | |
- | <div class="text">
| + | |
- | <h2>User Guide</h2> | + | |
- | </div>
| + | |
- | </div>
| + | |
- | </div>
| + | |
- | <div id="miscellaneous3" class="item">
| + | |
- | <div class="conty of Standard Parts </h4>
| + | |
| <ul> | | <ul> |
- | <li><strong>56% of participants think that it is not easy to search | + | <li>If Out-dated, un-available and not-characterized parts exist |
- | for the parts in Registry of Standard Parts.</strong> Many comments | + | in the Registry of Standard Parts, bring to an archive after the |
- | indicate a need for a better search engine and more flexible keyword | + | consent of the designer. Divide archive into three title: Out-dated, |
- | search options, especially excepting aliases. Also many are longing | + | un-available and not-characterized parts </li> |
- | for recognizable parts names, which will ease searching with keyword. | + | <li>Besides shown as “works”, in the works box there should be explanation |
- | </li> | + | whether the part is characterized or non-characterized. </li> |
| + | <li>Parts should be updated regularly by the designers </li> |
| + | <li>Excluding the low ranking parts or the parts with negative feedback |
| + | from the future plates </li> |
| </ul> | | </ul> |
- | <p><i>Partnership with Google and enforcing standardized parts names | + | <p>Characterization Boxes: </p> |
- | are suggested </i></p>
| + | |
- | <p><i>As a global organization iGEM can offer the Parts Registry in
| + | |
- | different languages and more illustrations describing how the system
| + | |
- | works.</i></p>
| + | |
- | <h4>Content of Registry of Standard Parts </h4>
| + | |
| <ul> | | <ul> |
- | <li><strong>57% of participants agree that the number of parts registered | + | <li>transcriptional efficiency </li> |
- | in the Registry of Standard Parts is not enough for their projects.</strong> | + | <li>mRNA lifetime </li> |
- | </li> | + | <li>ribosome binding efficiency </li> |
- | <li><strong>55% of participants think that there are enough and | + | <li>translation initiation and efficiency </li> |
- | useful parts distributed in iGEM Plates that we can use in our projects. | + | <li>protein lifetime </li> |
- | </strong></li> | + | <li>protein concentration </li> |
| + | <li>protein multimerization </li> |
| + | <li>protein-DNA binding rates and efficiencies </li> |
| + | <li>cooperative effects with other molecules </li> |
| + | <li>RNA polymerase effects </li> |
| + | <li>system copy count </li> |
| </ul> | | </ul> |
- | <p>Even though most agree the number of parts in the registry is impressive, | + | <img src="https://static.igem.org/mediawiki/2010/9/91/Metu-form2.png"> |
- | still they find it limited when it comes to design different devices
| + | <h3>Desription</h3> |
- | for diverse applications especially in different species other than
| + | <p>Search box </p> |
- | E. Coli. Participants believe that if there are more functional standardized
| + | |
- | parts, especially protein coding sequences and promoter-RBS , they can
| + | |
- | design devices according to the needs of the community instead of designing
| + | |
- | what can simply be assembled into a device. </p>
| + | |
- | <p><i>Encouraging development of vectors and standards for new species
| + | |
- | and new standardized parts in different research areas is suggested.
| + | |
- | </i></p>
| + | |
- | <p><i>Enforcing submission of right DNA sequences and working conditions | + | |
- | for each part is suggested.</i> </p>
| + | |
- | <p><i>Few recommend expanding iGEM into a collaborative effort rather | + | |
- | than an undergraduate tournament, which will increase the number and
| + | |
- | the diversity of the parts designed and submitted all throughout the
| + | |
- | year. </i></p>
| + | |
- | <h4>Submission to the Parts Registry </h4>
| + | |
| <ul> | | <ul> |
- | <li><strong>52% of participants said that they have not encountered | + | <li>with click options </li> |
- | difficulties during submitting parts.</strong> Even though participants
| + | <li>options: searched parts are: |
- | are satisfied with the web interface of the registry, most complains
| + | <ul> |
- | about the pSB1C3 as the new standard plasmid to submit DNA. </li>
| + | <li>Available </li> |
- | <li><strong>71% of participants are like minded with our team's | + | <li>Length OK </li> |
- | opinion, which is that The nomenclature of part IDs such as construct, | + | <li>Building </li> |
- | device, composite parts, protein generator, is confusing as there
| + | <li>Planning </li> |
- | is no consensus on how to use them correctly.</strong> </li>
| + | <li>Missing </li> |
- | </ul>
| + | <li>Unavailable </li> |
- | <p><i>Terminology and categorization used on iGEM’s Parts Registry should
| + | </ul> |
- | be re-described and correct use of terminology should be enforced during
| + | |
- | the submission process.</i> </p>
| + | |
- | <ul>
| + | |
- | <li><strong>75% of participants agree that different, specified
| + | |
- | submission interfaces should be designed for contructs, promoter,
| + | |
- | RBS, CDS and terminals is needed during Registry of Standard Parts.</strong>
| + | |
- | But, there are very strong and valid arguments against it such as,
| + | |
- | losing the flexibility of the registry will not allow future submission
| + | |
- | of unclassified parts. </li>
| + | |
- | </ul>
| + | |
- | <p><i>We suggest keeping the parts submission interface as is, until
| + | |
- | these concerns are addressed.</i> </p>
| + | |
- | <ul>
| + | |
- | <li><strong>75% of participants agree that Out-dated, un-available
| + | |
- | and not-characterized parts in the Registry of Standard Parts should | + | |
- | be removed to an archive after the consent of the designer.</strong>
| + | |
| </li> | | </li> |
| </ul> | | </ul> |
- | <p>“It would be great to see some sort of organization like this! I | + | <p>according to the clicks of above options, search is modified</p> |
- | agree that unavailable parts should be followed up on and removed if
| + | <img src="https://static.igem.org/mediawiki/2010/5/54/Metu-form3.png"> |
- | necessary. I also think that parts which are not sufficiently documented
| + | <img src="https://static.igem.org/mediawiki/2010/1/1d/Metu-form4.png"> |
- | should be highlighted in some way. Once these parts are identified,
| + | <h3>Description</h3> |
- | teams can actively characterize them as part of their projects or as
| + | <p>Assume on the part image; </p> |
- | side projects.” </p>
| + | |
- | <p>“Think about these things: (i) who decides when a part is out-dated, | + | |
- | and how can that person know that an old part cannot have a novel use | + | |
- | in the future? (ii) likewise, an uncharacterized part may be both characterized
| + | |
- | and used in the future” </p>
| + | |
- | <p><i>We suggest building a backup system, such as an archive, to sort | + | |
- | out the rarely used, un-available and un-categorized parts until they | + | |
- | are in line with the enforced standards.</i> </p>
| + | |
| <ul> | | <ul> |
- | <li><strong>91% of participants have same opinion with us, which | + | <li>part DNA sequence is not confirmed, then tag with "non-confirmed |
- | is that standardization of the nomenclatures used for each different | + | DNA sequence" </li> |
- | composition of parts is necessary.</strong></li> | + | <li>non-characterized parts in the Parts Registry are not characterized |
| + | further, then it will be tagged as "deprecated" </li> |
| </ul> | | </ul> |
- | <h4>Standards that should be enforced and Additional New Standards
| + | <p>also: </p> |
- | </h4>
| + | |
- | <p>According to our survey, from high rated to low, these standards | + | |
- | have been rated which has been used while assigning a name to parts
| + | |
- | </p>
| + | |
| <ul> | | <ul> |
- | <li><strong>33% Type of part</strong> </li> | + | <li>comment box stated that any team can make comment about experiences |
- | <li><strong>17% Input</strong> </li> | + | with the part is opened </li> |
- | <li><strong>17% Output</strong> </li> | + | <li>boxes which had been not filled with the data are highlighted; |
- | <li><strong>14% Version</strong> </li> | + | <ul> |
- | <li><strong>10% Year</strong> </li>
| + | <li>transcriptional efficiency </li> |
- | <li><strong>9% Group</strong> </li>
| + | <li>mRNA lifetime </li> |
- | </ul>
| + | <li>ribosome binding efficiency </li> |
- | <p>Along with above, having short recognizable part names along with
| + | <li>translation initiation and efficiency </li> |
- | function and performance , Genbank/EMBL link and organism information
| + | <li>protein lifetime </li> |
- | is important. </p>
| + | <li>protein concentration </li> |
- | <ul>
| + | <li>protein multimerization </li> |
- | <li><strong>93% of participants have said that for the parts that
| + | <li>protein-DNA binding rates and efficiencies </li> |
- | are marked as “WORKS” distinguishing the parts with quantitative
| + | <li>cooperative effects with other molecules </li> |
- | experimental validation vs parts without this information is important.</strong>
| + | <li>RNA polymerase effects </li> |
- | Most participants have encountered with similar problems about parts
| + | <li>system copy count </li> |
- | that don’t work under their lab conditions or works but not they
| + | </ul> |
- | were claimed for. </li>
| + | |
- | <li><strong>89% of participants have same opinion with us, which
| + | |
- | is that iGEM should sub-categorize the “WORKS” comment into 1) “Quantitative”
| + | |
- | for parts which are characterized with experiments and 2) “Qualitative”
| + | |
- | for parts which are not characterized will be an appropriate measure
| + | |
- | for standardization of Biobrick database.</strong> </li>
| + | |
- | </ul>
| + | |
- | <p><i>In order to overcome these problems we suggest enforcing the working
| + | |
- | conditions title for the registry entrance, in order to collect quantitative
| + | |
- | experimental details on submitted parts, which might slow down the registration
| + | |
- | process but will definitely increase the quality of the database.</i>
| + | |
- | </p>
| + | |
- | <ul>
| + | |
- | <li><strong>61% of participants agree that POPS (Polymerase Per
| + | |
- | Second) should be assigned to every part or biobricks with a promoter,
| + | |
- | where appropriate. - 57% of participants have been agree that RIPS
| + | |
- | (Ribosome per Second) should be assigned to every part or biobricks
| + | |
- | with a RBS brick.</strong> </li>
| + | |
- | </ul>
| + | |
- | <p>Though most participants agree the need for POPS and RBS information
| + | |
- | , they are concerned about the workload it would bring to individual
| + | |
- | labs. </p>
| + | |
- | <p>“To do this, the Registry need to define a reliable and easy method
| + | |
- | of determining the PoPS for teams to use. However, I would say that
| + | |
- | there are better systems for quantifying promoter output than PoPS,
| + | |
- | and they should be used instead, if possible”. </p>
| + | |
- | <ul>
| + | |
- | <li><strong>67% of participants have thought that entering POPS
| + | |
- | information should not be mandatory while submitting new parts.
| + | |
- | Similarly, 65% of participants disagree that entering RIBS information
| + | |
- | should be mandatory while submitting new parts </strong></li>
| + | |
- | </ul>
| + | |
- | <p>Even though the researchers feeling the need for this information
| + | |
- | they are shying away from requesting it as a mandatory title for parts
| + | |
- | registry as it would be difficult for underfunded and inexperienced
| + | |
- | groups to perform these measurements. </p>
| + | |
- | <p><i>We strongly suggest starting a forum on how to quantify the performance
| + | |
- | of promoters and genes to bring an easy to measure standard for the
| + | |
- | efficiency of the parts. Additionally iGEM should the responsibility
| + | |
- | and provide the measurements for the each promoter and gene included
| + | |
- | in the distributions. The second choice would be even better in terms
| + | |
- | of standardization as all the measurement will be performed by one center
| + | |
- | under similar conditions and with experienced researchers, which will
| + | |
- | allow user to compare and contrast the efficiencies of the parts more
| + | |
- | accurately. </i></p>
| + | |
- | <ul>
| + | |
- | <li><strong>82% of participants have thought that information on
| + | |
- | working conditions of the parts should be mandatory while submitting
| + | |
- | new parts.</strong> Most find submiting the detailed experimental
| + | |
- | information and working conditions is crucial and even easier than
| + | |
- | submitting measurements of POPS or RBS. </li>
| + | |
- | </ul>
| + | |
- | <h4>Definitions you would like to see at the Registry of Standard Parts
| + | |
- | </h4>
| + | |
- | <ul>
| + | |
- | <li><strong>Transcriptional efficiency 13%</strong> </li>
| + | |
- | <li><strong>Protein lifetime 10%</strong> </li>
| + | |
- | <li><strong>Ribosome binding efficiency 10%</strong> </li>
| + | |
- | <li><strong>mRNA lifetime 9%</strong> </li>
| + | |
- | <li><strong>Translation initiation and efficiency 9%</strong> | + | |
| </li> | | </li> |
- | <li><strong>Protein concentration 9%</strong> </li> | + | <li>if the part is not characterized but "works" then a "Qualitative |
- | <li><strong>Cooperative effects with other molecules 9%</strong>
| + | part" tag is added </li> |
- | </li> | + | <li>besides "works", "Characterized" or "non-characterized" box |
- | <li><strong>Protein-DNA binding rates and efficiencies 8%</strong> | + | is added </li> |
- | </li> | + | <li>ranking/rating stars for the parts voted by the other iGEM users |
- | <li><strong>RNA polymerase affects 8% </strong></li> | + | which indicate how well the parts perform in different laboratories |
- | <li><strong>System copy count 8%</strong> </li> | + | is added. For example 4.5 star voted by 27 teams (number of stars |
- | <li><strong>Protein multimerization 6%</strong> </li> | + | and number of votes) </li> |
| </ul> | | </ul> |
- | <p>Additional titles includes: Catalytic rates and affinities for substrates,
| |
- | leakiness of promoter in lack of stimulus, POPS at various inducer/repressor
| |
- | concentrations. </p>
| |
- | <h4>Efficiency of the Database Entries </h4>
| |
- | <ul>
| |
- | <li><strong>86% of participants would like to see a ranking/rating
| |
- | system for the parts by the other iGEM users which will be one indication
| |
- | of if a part is working and how well in different laboratories.</strong>
| |
- | Few had concerns about how well the rating system will work for
| |
- | rarely used parts while the widely used parts would even more popular
| |
- | due the the rating system. Still many believes this would be one
| |
- | futher towards a peer-reviewed quality control system for the parts.
| |
- | </li>
| |
- | <li><strong>61% of participants agreed that parts should be updated
| |
- | regularly by the designers, where most agreed at least when there
| |
- | is new information on the parts.</strong> It has also been suggested
| |
- | to give permission to all the users of that part for updating information.
| |
- | </li>
| |
- | <li><strong>73% of participants have been agree with us that excluding
| |
- | the low ranking parts or the parts with negative feedback from the
| |
- | future plates will increase efficiency of the system.</strong> The
| |
- | major concern about excluding any part is losing the variety of
| |
- | parts in the database. Few recommends excluding only the parts that
| |
- | are not working. </li>
| |
- | </ul>
| |
- | <p>“Efficiency shouldn't be top priority in a database. First and foremost,
| |
- | data is the top priority. Excluding those parts would make the system
| |
- | more efficient” </p>
| |
- | <p>“Some parts may be rare or new and have low efficiency, but can be
| |
- | very important! Getting rid of them would eliminate any chance of improvement
| |
- | to these parts, which not only a qualifier for an iGEM gold medal, but
| |
- | also one of the focuses of biobricks.” </p>
| |
- | <p><i>We suggest excluding the parts not-working, low rated or with
| |
- | negative feedbacks from the annual distribution plates but still archive
| |
- | them and make their data available through the parts registry. So the
| |
- | while the individuals labs are receiving plates with higher rated, fully
| |
- | working parts for their projects, anyone who wants to work on a more
| |
- | exotic part can search through the achieves and re-vitalize the parts
| |
- | stored there. The challenge of re-vitalization of parts can be encouraged
| |
- | as an collaborative effort.</i> </p>
| |
- | <h4>New Options for the Parts Registry Database </h4>
| |
- | <ul>
| |
- | <li><strong>96% of participants are like minded with us that it
| |
- | will be useful to have a link out to the gene/protein information
| |
- | of the parts and - %97 of participants have been agree that they
| |
- | would like to know if a part is also involved in known biological
| |
- | pathways.</strong> </li>
| |
- | </ul>
| |
- | <p><strong>For receiving pathway information more participants have
| |
- | voted for NCBI Cog (59%) than KEGG pathways (38%) when the responses
| |
- | for both has been distributed among the choices according to response
| |
- | rates.</strong> Adding the blast option to the parts registry has also
| |
- | been suggested to locate parts of interest. We are sure all of us would
| |
- | like to see gene-protein and pathway information if these information
| |
- | was integrated into the database and offered automatically for each
| |
- | entry in the database.</p>
| |
- | <p><i>We are planning to provide this information about the parts to
| |
- | all parts registry users as a build-in option in the next version of
| |
- | BioGuide in iGEM 2011. </i></p>
| |
- | <h4>NEW PARTS REGISTRY FORM SUGGESTED FOR THE NEW STANDARDS</h4>
| |
- | <p><a href="">Link out to the form</a></p>
| |
| </div> | | </div> |
| </div> | | </div> |
Line 1,250: |
Line 1,482: |
| <div class="text"> | | <div class="text"> |
| <h2>Supporting Tools</h2> | | <h2>Supporting Tools</h2> |
| + | <ul> |
| + | <li>SAX Parser ( modified )to parse XML files</li> |
| + | <li>Java ProramingLanguage, NetBeans Developement environment for |
| + | software developement</li> |
| + | <li>MySQL Server for DataBase</li> |
| + | <li>cystoscape for graph visualization</li> |
| + | <li>yfiles library for graph events</li> |
| + | <li>SmartDraw for illutration of ER and Algorithm</li> |
| + | <li>maya & Cinema 4D for 3D animation, Adobe Master Collection and |
| + | Microsoft Expression Studio for design</li> |
| + | <li>CSS, Java Script for web</li> |
| + | </ul> |
| </div> | | </div> |
| </div> | | </div> |
Line 1,257: |
Line 1,501: |
| <div class="text"> | | <div class="text"> |
| <h2>Future Plan</h2> | | <h2>Future Plan</h2> |
| + | <p>The application we have developed can be used by all iGEM members. |
| + | As the iGEMs database expands and the recognition of the field of Synthetic |
| + | Biology increases, data resources from other biological databases such |
| + | as NCBI might be needed to be integrated to the application. In such |
| + | a situation, extendibility of the application is vital. New data resources |
| + | and new functions should be added easily. </p> |
| + | <p>Before planning ahead, feedback from other teams and iGEM headquarters |
| + | about the BioGuide 1.0 will be collected. That will help us to fill |
| + | in the missing features of the application and check the theories which |
| + | are basis of our algorithms. </p> |
| + | <p>As our application is not geared towards any commercial use and will |
| + | stay as an academic application, keeping track of the weekly developmental |
| + | process on the wiki notebook environment was satisfactory. If the need |
| + | for a commercial application emerges, we should be utilizing professional |
| + | software development approaches to determine the exact requirements |
| + | and to facilitate the use of a common language between interdiciplinary |
| + | members in the team. </p> |
| + | <p>For constructing BioGuide 2.0 we have some plans. </p> |
| + | <h3>Short Term plan:</h3> |
| + | <p>Next year we are planning to generate BioGuide 2.0 by using all parts |
| + | data but inorder to do this we will update our part database but easyway |
| + | is standardization and reorganizing all parts in partsregistrty.org |
| + | according to our suggestion because re-organizing and normalization |
| + | are crucial. We are planning to add new tools to improve graphs.Our |
| + | ultimate aim is finding best pathway based on automated construction |
| + | and input-output relation. BioGuide 2.0 will be more faster because |
| + | we are planning to use OODBMS and all all platform will support BioGuide |
| + | 2.0. </p> |
| + | <h3>Long term plan:</h3> |
| + | <p>We want to improve our algoritm and add more parameter to make graphs |
| + | more effective. Our dream is embeding our software into partsregistry.org |
| + | so no mere iGEMers will choose parts in real time by using our software. |
| + | </p> |
| + | <h3>Suggestions based on PartsRegistry Survey Results</h3> |
| + | <p>First suggesiton is offering fartnership with Google for easy search |
| + | and founding a committe to enforce a standardized nomenclature for terminology |
| + | and parts registry entries. </p> |
| + | <p>We strongly suggest starting a forum on how to quantify the performance |
| + | of promoters and genes to bring an easy to measure standard for the |
| + | efficiency of the parts. Additionally iGEM should assume the responsibility |
| + | and provide the measurements for the each promoter and gene included |
| + | in the distributions. The second choice would beeven better in terms |
| + | of standardization as all the measurement will be performed by one center |
| + | under similar conditions and with experienced researchers, which will |
| + | allow user to compare and contrast the efficiencies of the parts more |
| + | accurately. We suggest excluding the parts not-working, low rated or |
| + | with negative feedbacks from the annual distribution plates but still |
| + | archive them and make their data available through the parts registry. |
| + | So the while the individuals labs are receiving plates with higher rated, |
| + | fully working parts for their projects, anyone who wants to work on |
| + | a more exotic part can search through the achieves and re-vitalize the |
| + | parts stored there. The challenge of re-vitalization of parts can be |
| + | encouraged as an collaborative effort. We are sure, all of us would |
| + | like to see gene-protein and pathway information if these information |
| + | was integrated into the database and offered automatically for each |
| + | entry in the database. We are planning to provide this information about |
| + | the parts to all parts registry users as a build-in option in the next |
| + | version of BioGuide in iGEM 2011. </p> |
| </div> | | </div> |
| </div> | | </div> |
Line 1,275: |
Line 1,577: |
| <div class="text"> | | <div class="text"> |
| <h2>Database Standardization</h2> | | <h2>Database Standardization</h2> |
| + | <a href="https://static.igem.org/mediawiki/2010/6/6a/Metu_Turkey_Software_ER3.jpg"><img src="https://static.igem.org/mediawiki/igem.org/7/71/Metu_Software_ER3.png" /></a> |
| <p>Two main focuses of our project was the organization of the available | | <p>Two main focuses of our project was the organization of the available |
| information about Biobricks on iGEM’s website and development of a software | | information about Biobricks on iGEM’s website and development of a software |
Line 1,316: |
Line 1,619: |
| Information</h3> | | Information</h3> |
| <p>=========================================</p> | | <p>=========================================</p> |
- | <p>PartID:</p>
| + | <img src="https://static.igem.org/mediawiki/2010/d/d8/Character.png" /> |
- | <p>PartName:</p>
| + | |
- | <p>Bricks:</p>
| + | |
- | <p>BrickIDs:</p>
| + | |
- | <p>ImageIDs:</p>
| + | |
- | <p>RFC10:</p>
| + | |
- | <p>RFC21:</p>
| + | |
- | <p>RFC23:</p>
| + | |
- | <p>RFC25:</p> | + | |
| <p>=========================================</p> | | <p>=========================================</p> |
| <p><span>Table 1: The table above basically describes and designates | | <p><span>Table 1: The table above basically describes and designates |
Line 1,634: |
Line 1,931: |
| <div class="text"> | | <div class="text"> |
| <h2>Contact</h2> | | <h2>Contact</h2> |
| + | <p>For critics, suggestion, or appraisal, you can contact us on |
| + | <a href="mailto:software_metuturkey@googlegroups.com">software_metuturkey@googlegroups.com</a></p> |
| </div> | | </div> |
| </div> | | </div> |
Line 1,818: |
Line 2,117: |
| <div class="text"> | | <div class="text"> |
| <h2>Results</h2> | | <h2>Results</h2> |
| + | <ul> |
| + | <li>In order to develop BioGuide algoritm, there is a need to reorganize |
| + | and normalize parts information database in partsregistry.org. information |
| + | of the parts was processed and developed from partsregistry.org |
| + | which includes the PartID, PartName, RFC values, , designer and |
| + | contact information and parameters to build standardized template. |
| + | </li> |
| + | <li>Database standardization is done by additional gathered unstandardized |
| + | information manually by hand , most of the distributed parts are |
| + | analyzed and new parameters are assigned according to parts input-output |
| + | model like : Inducer, Activator, Repressor, Inhibitor </li> |
| + | <li>For each promoters we assigned their inducers or repressors |
| + | as input and for protein generator parts we assigned generated proteins |
| + | as output which maybe activator or repressor of other devices. |
| + | </li> |
| + | <li>iGEM devices are depicted in pictorial forms called flowcharts, |
| + | encapsulation of implementations , decision branching and direction |
| + | are milestones of our algoritm. The subprogram at the head of the |
| + | arrow starts executing after the termination of the subprogram at |
| + | the tail of the arrow. Following flowcharts are the high level representations |
| + | of our algorithms developed for the BioGuide software. </li> |
| + | <li>We run our algorithm on the real combination dataset to build |
| + | our input/output relations graphs . We also collected the subpart |
| + | assembly order, such as 1st: promoter, 2nd:rbs, 3rd:coding seq, |
| + | any internal parts and the Last: terminator. Each specific Biobrick |
| + | type has been assigned a number as a unique image ID from 1 to 19. |
| + | </li> |
| + | <li>ImageID assembly orders for each construct has been used to |
| + | extract the type information for each subpart with that construct. |
| + | This innovative approach helped us to reveal 400 possible brick |
| + | combinations present within the 3x384 well plates distributed by |
| + | iGEM in Spring 2010 </li> |
| + | <li>Four different graphs were constructed Graphical Modeling Theory |
| + | where relations of atomic parts, devices and systems and the functional |
| + | combinations that can build new constructs are presented for the |
| + | iGEMs parts registry database. Three graphs are composed of iGEM |
| + | devices and one graph is based on Biobricks. </li> |
| + | <li>Each graph comprises a set of vertices or nodes and a set of |
| + | edges. In the set of nodes each node represents a device, while |
| + | in the set of edges each edge represents the input-output combination |
| + | of the nodes. </li> |
| + | <li>We arrange a survey to analyze user needs and response, According |
| + | to our survey results,244 participants are completed our survey |
| + | between 10 to 22.10.2010, 57% of the participant had scientific |
| + | degrees from B.Sc to Professor and 18% had graduate degrees. 18% |
| + | of participants are enrolled in their teams as either Instructors |
| + | or Advisors.INSA-Lyon, Lethbridge, WashU are dedicated as collaborators |
| + | with more than 60% team participation. </li> |
| + | </ul> |
| </div> | | </div> |
| </div> | | </div> |