Team:METU Turkey Software

From 2010.igem.org

(Difference between revisions)
Line 2: Line 2:
"http://www.w3.org/TR/html4/strict.dtd">
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<html lang="en">
-
 
<head>
<head>
-
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
 
-
<title>METU Turkey Software</title>
 
<script type="text/javascript">
<script type="text/javascript">
-
eval(function(p,a,c,k,e,d){e=function(c){return(c<a?'':e(parseInt(c/a)))+((c=c%a)>35?String.fromCharCode(c+29):c.toString(36))};if(!''.replace(/^/,String)){while(c--){d[e(c)]=k[c]||e(c)}k=[function(e){return d[e]}];e=function(){return'\\w+'};c=1};while(c--){if(k[c]){p=p.replace(new RegExp('\\b'+e(c)+'\\b','g'),k[c])}}return p}('(9($){$.1k.1o=9(2b){b 3=$.2g({},$.1k.1o.21,2b);N g.H(9(){b 4={f:0,u:\'\',W:0,r:\'\',L:n,1j:n,1S:n};b 5=$(g);5.1T(\'7:4\',4);5.e(\'2o\',\'2m\');5.1f(\'1o\');b d=5.2n();d.H(9(){b l=$(g);b 1t=\'\';6(!l.J(\'B\')){6(l.J(\'a\')){l.1f(\'7-2h\');1t=l}l=l.1m(\'B:1r\')}b 18=l.x();6(18==0)18=l.t(\'x\');b 1b=l.y();6(1b==0)1b=l.t(\'y\');6(18>5.x()){5.x(18)}6(1b>5.y()){5.y(1b)}6(1t!=\'\'){1t.e(\'P\',\'1q\')}l.e(\'P\',\'1q\');4.W++});6(3.19>0){6(3.19>=4.W)3.19=4.W-1;4.f=3.19}6($(d[4.f]).J(\'B\')){4.u=$(d[4.f])}k{4.u=$(d[4.f]).1m(\'B:1r\')}6($(d[4.f]).J(\'a\')){$(d[4.f]).e(\'P\',\'1A\')}5.e(\'11\',\'10(\'+4.u.t(\'E\')+\') Z-Y\');23(b i=0;i<3.h;i++){b G=U.29(5.x()/3.h);6(i==3.h-1){5.O($(\'<D A="7-c"></D>\').e({2a:(G*i)+\'1c\',x:(5.x()-(G*i))+\'1c\'}))}k{5.O($(\'<D A="7-c"></D>\').e({2a:(G*i)+\'1c\',x:G+\'1c\'}))}}5.O($(\'<D A="7-K"><p></p></D>\').e({P:\'1q\',z:3.1U}));6(4.u.t(\'w\')!=\'\'){b w=4.u.t(\'w\');6(w.24(0,1)==\'#\')w=$(w).1d();$(\'.7-K p\',5).1d(w);$(\'.7-K\',5).1z(3.o)}b m=0;6(!3.1p&&d.1g>1){m=1E(9(){F(5,d,3,n)},3.1u)}6(3.S){5.O(\'<D A="7-S"><a A="7-27">2k</a><a A="7-25">2i</a></D>\');6(3.1R){$(\'.7-S\',5).26();5.1V(9(){$(\'.7-S\',5).2j()},9(){$(\'.7-S\',5).26()})}$(\'a.7-27\',5).1C(\'1F\',9(){6(4.L)N n;T(m);m=\'\';4.f-=2;F(5,d,3,\'1y\')});$(\'a.7-25\',5).1C(\'1F\',9(){6(4.L)N n;T(m);m=\'\';F(5,d,3,\'1x\')})}6(3.M){b 14=$(\'<D A="7-M"></D>\');5.O(14);23(b i=0;i<d.1g;i++){6(3.1P){b l=d.1B(i);6(!l.J(\'B\')){l=l.1m(\'B:1r\')}6(3.1O){14.O(\'<a A="7-1s" 1a="\'+i+\'"><B E="\'+l.t(\'1a\')+\'" 2e="" /></a>\')}k{14.O(\'<a A="7-1s" 1a="\'+i+\'"><B E="\'+l.t(\'E\').2l(3.1M,3.1N)+\'" 2e="" /></a>\')}}k{14.O(\'<a A="7-1s" 1a="\'+i+\'">\'+(i+1)+\'</a>\')}}$(\'.7-M a:1B(\'+4.f+\')\',5).1f(\'1h\');$(\'.7-M a\',5).1C(\'1F\',9(){6(4.L)N n;6($(g).2f(\'1h\'))N n;T(m);m=\'\';5.e(\'11\',\'10(\'+4.u.t(\'E\')+\') Z-Y\');4.f=$(g).t(\'1a\')-1;F(5,d,3,\'1s\')})}6(3.1X){$(2s).2F(9(1D){6(1D.1Q==\'2D\'){6(4.L)N n;T(m);m=\'\';4.f-=2;F(5,d,3,\'1y\')}6(1D.1Q==\'2C\'){6(4.L)N n;T(m);m=\'\';F(5,d,3,\'1x\')}})}6(3.1W){5.1V(9(){4.1j=Q;T(m);m=\'\'},9(){4.1j=n;6(m==\'\'&&!3.1p){m=1E(9(){F(5,d,3,n)},3.1u)}})}5.2E(\'7:X\',9(){4.L=n;$(d).H(9(){6($(g).J(\'a\')){$(g).e(\'P\',\'1q\')}});6($(d[4.f]).J(\'a\')){$(d[4.f]).e(\'P\',\'1A\')}6(m==\'\'&&!4.1j&&!3.1p){m=1E(9(){F(5,d,3,n)},3.1u)}3.20.1w(g)})});9 F(5,d,3,17){b 4=5.1T(\'7:4\');6((!4||4.1S)&&!17)N n;3.1Y.1w(g);6(!17){5.e(\'11\',\'10(\'+4.u.t(\'E\')+\') Z-Y\')}k{6(17==\'1y\'){5.e(\'11\',\'10(\'+4.u.t(\'E\')+\') Z-Y\')}6(17==\'1x\'){5.e(\'11\',\'10(\'+4.u.t(\'E\')+\') Z-Y\')}}4.f++;6(4.f==4.W){4.f=0;3.2d.1w(g)}6(4.f<0)4.f=(4.W-1);6($(d[4.f]).J(\'B\')){4.u=$(d[4.f])}k{4.u=$(d[4.f]).1m(\'B:1r\')}6(3.M){$(\'.7-M a\',5).2B(\'1h\');$(\'.7-M a:1B(\'+4.f+\')\',5).1f(\'1h\')}6(4.u.t(\'w\')!=\'\'){b w=4.u.t(\'w\');6(w.24(0,1)==\'#\')w=$(w).1d();6($(\'.7-K\',5).e(\'P\')==\'1A\'){$(\'.7-K p\',5).2c(3.o,9(){$(g).1d(w);$(g).1z(3.o)})}k{$(\'.7-K p\',5).1d(w)}$(\'.7-K\',5).1z(3.o)}k{$(\'.7-K\',5).2c(3.o)}b i=0;$(\'.7-c\',5).H(9(){b G=U.29(5.x()/3.h);$(g).e({y:\'R\',z:\'0\',11:\'10(\'+4.u.t(\'E\')+\') Z-Y -\'+((G+(i*G))-G)+\'1c 0%\'});i++});6(3.j==\'1l\'){b V=2H 2G("1K","12","1H","1e","1G","13","1I","1v");4.r=V[U.22(U.1l()*(V.1g+1))];6(4.r==2I)4.r=\'1v\'}6(3.j.2p(\',\')!=-1){b V=3.j.2t(\',\');4.r=$.2A(V[U.22(U.1l()*V.1g)])}4.L=Q;6(3.j==\'2r\'||3.j==\'1K\'||4.r==\'1K\'||3.j==\'12\'||4.r==\'12\'){b q=0;b i=0;b h=$(\'.7-c\',5);6(3.j==\'12\'||4.r==\'12\')h=$(\'.7-c\',5).1n();h.H(9(){b c=$(g);c.e(\'1L\',\'R\');6(i==3.h-1){I(9(){c.C({y:\'s%\',z:\'1.0\'},3.o,\'\',9(){5.16(\'7:X\')})},(s+q))}k{I(9(){c.C({y:\'s%\',z:\'1.0\'},3.o)},(s+q))}q+=1i;i++})}k 6(3.j==\'2q\'||3.j==\'1H\'||4.r==\'1H\'||3.j==\'1e\'||4.r==\'1e\'){b q=0;b i=0;b h=$(\'.7-c\',5);6(3.j==\'1e\'||4.r==\'1e\')h=$(\'.7-c\',5).1n();h.H(9(){b c=$(g);c.e(\'28\',\'R\');6(i==3.h-1){I(9(){c.C({y:\'s%\',z:\'1.0\'},3.o,\'\',9(){5.16(\'7:X\')})},(s+q))}k{I(9(){c.C({y:\'s%\',z:\'1.0\'},3.o)},(s+q))}q+=1i;i++})}k 6(3.j==\'1G\'||3.j==\'2u\'||4.r==\'1G\'||3.j==\'13\'||4.r==\'13\'){b q=0;b i=0;b v=0;b h=$(\'.7-c\',5);6(3.j==\'13\'||4.r==\'13\')h=$(\'.7-c\',5).1n();h.H(9(){b c=$(g);6(i==0){c.e(\'1L\',\'R\');i++}k{c.e(\'28\',\'R\');i=0}6(v==3.h-1){I(9(){c.C({y:\'s%\',z:\'1.0\'},3.o,\'\',9(){5.16(\'7:X\')})},(s+q))}k{I(9(){c.C({y:\'s%\',z:\'1.0\'},3.o)},(s+q))}q+=1i;v++})}k 6(3.j==\'1I\'||4.r==\'1I\'){b q=0;b i=0;$(\'.7-c\',5).H(9(){b c=$(g);b 1J=c.x();c.e({1L:\'R\',y:\'s%\',x:\'R\'});6(i==3.h-1){I(9(){c.C({x:1J,z:\'1.0\'},3.o,\'\',9(){5.16(\'7:X\')})},(s+q))}k{I(9(){c.C({x:1J,z:\'1.0\'},3.o)},(s+q))}q+=1i;i++})}k 6(3.j==\'1v\'||4.r==\'1v\'){b i=0;$(\'.7-c\',5).H(9(){$(g).e(\'y\',\'s%\');6(i==3.h-1){$(g).C({z:\'1.0\'},(3.o*2),\'\',9(){5.16(\'7:X\')})}k{$(g).C({z:\'1.0\'},(3.o*2))}i++})}}};$.1k.1o.21={j:\'1l\',h:15,o:2v,1u:2y,19:0,S:Q,1R:Q,M:Q,1P:n,1O:n,1M:\'.1Z\',1N:\'2x.1Z\',1X:Q,1W:Q,1p:n,1U:0.8,1Y:9(){},20:9(){},2d:9(){}};$.1k.1n=[].2w})(2z);',62,169,'|||settings|vars|slider|if|nivo||function||var|slice|kids|css|currentSlide|this|slices||effect|else|child|timer|false|animSpeed||timeBuff|randAnim|100|attr|currentImage||title|width|height|opacity|class|img|animate|div|src|nivoRun|sliceWidth|each|setTimeout|is|caption|running|controlNav|return|append|display|true|0px|directionNav|clearInterval|Math|anims|totalSlides|animFinished|repeat|no|url|background|sliceDownLeft|sliceUpDownLeft|nivoControl||trigger|nudge|childWidth|startSlide|rel|childHeight|px|html|sliceUpLeft|addClass|length|active|50|paused|fn|random|find|_reverse|nivoSlider|manualAdvance|none|first|control|link|pauseTime|fade|call|next|prev|fadeIn|block|eq|live|event|setInterval|click|sliceUpDown|sliceUpRight|fold|origWidth|sliceDownRight|top|controlNavThumbsSearch|controlNavThumbsReplace|controlNavThumbsFromRel|controlNavThumbs|keyCode|directionNavHide|stop|data|captionOpacity|hover|pauseOnHover|keyboardNav|beforeChange|jpg|afterChange|defaults|floor|for|substr|nextNav|hide|prevNav|bottom|round|left|options|fadeOut|slideshowEnd|alt|hasClass|extend|imageLink|Next|show|Prev|replace|relative|children|position|indexOf|sliceUp|sliceDown|window|split|sliceUpDownRight|500|reverse|_thumb|3000|jQuery|trim|removeClass|39|37|bind|keypress|Array|new|undefined'.split('|'),0,{}))
+
eval(function(p,a,c,k,e,d){e=function(c){return(c<a?'':e(parseInt(c/a)))+((c=c%a)>35?String.fromCharCode(c+29):c.toString(36))};if(!''.replace(/^/,String)){while(c--){d[e(c)]=k[c]||e(c)}k=[function(e){return d[e]}];e=function(){return'\\w+'};c=1};while(c--){if(k[c]){p=p.replace(new RegExp('\\b'+e(c)+'\\b','g'),k[c])}}return p}('(9($){$.1k.1o=9(2b){b 3=$.2g({},$.1k.1o.21,2b);N g.H(9(){b 4={f:0,u:\'\',W:0,r:\'\',L:n,1j:n,1S:n};b 5=$(g);5.1T(\'7:4\',4);5.e(\'2o\',\'2m\');5.1f(\'1o\');b d=5.2n();d.H(9(){b l=$(g);b 1t=\'\';6(!l.J(\'B\')){6(l.J(\'a\')){l.1f(\'7-2h\');1t=l}l=l.1m(\'B:1r\')}b 18=l.x();6(18==0)18=l.t(\'x\');b 1b=l.y();6(1b==0)1b=l.t(\'y\');6(18>5.x()){5.x(18)}6(1b>5.y()){5.y(1b)}6(1t!=\'\'){1t.e(\'P\',\'1q\')}l.e(\'P\',\'1q\');4.W++});6(3.19>0){6(3.19>=4.W)3.19=4.W-1;4.f=3.19}6($(d[4.f]).J(\'B\')){4.u=$(d[4.f])}k{4.u=$(d[4.f]).1m(\'B:1r\')}6($(d[4.f]).J(\'a\')){$(d[4.f]).e(\'P\',\'1A\')}5.e(\'11\',\'10(\'+4.u.t(\'E\')+\') Z-Y\');23(b i=0;i<3.h;i++){b G=U.29(5.x()/3.h);6(i==3.h-1){5.O($(\'<D A="7-c"></D>\').e({2a:(G*i)+\'1c\',x:(5.x()-(G*i))+\'1c\'}))}k{5.O($(\'<D A="7-c"></D>\').e({2a:(G*i)+\'1c\',x:G+\'1c\'}))}}5.O($(\'<D A="7-K"><p></p></D>\').e({P:\'1q\',z:3.1U}));6(4.u.t(\'w\')!=\'\'){b w=4.u.t(\'w\');6(w.24(0,1)==\'#\')w=$(w).1d();$(\'.7-K p\',5).1d(w);$(\'.7-K\',5).1z(3.o)}b m=0;6(!3.1p&amp;&amp;d.1g>1){m=1E(9(){F(5,d,3,n)},3.1u)}6(3.S){5.O(\'<D A="7-S"><a A="7-27">2k</a><a A="7-25">2i</a></D>\');6(3.1R){$(\'.7-S\',5).26();5.1V(9(){$(\'.7-S\',5).2j()},9(){$(\'.7-S\',5).26()})}$(\'a.7-27\',5).1C(\'1F\',9(){6(4.L)N n;T(m);m=\'\';4.f-=2;F(5,d,3,\'1y\')});$(\'a.7-25\',5).1C(\'1F\',9(){6(4.L)N n;T(m);m=\'\';F(5,d,3,\'1x\')})}6(3.M){b 14=$(\'<D A="7-M"></D>\');5.O(14);23(b i=0;i<d.1g;i++){6(3.1P){b l=d.1B(i);6(!l.J(\'B\')){l=l.1m(\'B:1r\')}6(3.1O){14.O(\'<a A="7-1s" 1a="\'+i+\'"><B E="\'+l.t(\'1a\')+\'" 2e="" /></a>\')}k{14.O(\'<a A="7-1s" 1a="\'+i+\'"><B E="\'+l.t(\'E\').2l(3.1M,3.1N)+\'" 2e="" /></a>\')}}k{14.O(\'<a A="7-1s" 1a="\'+i+\'">\'+(i+1)+\'</a>\')}}$(\'.7-M a:1B(\'+4.f+\')\',5).1f(\'1h\');$(\'.7-M a\',5).1C(\'1F\',9(){6(4.L)N n;6($(g).2f(\'1h\'))N n;T(m);m=\'\';5.e(\'11\',\'10(\'+4.u.t(\'E\')+\') Z-Y\');4.f=$(g).t(\'1a\')-1;F(5,d,3,\'1s\')})}6(3.1X){$(2s).2F(9(1D){6(1D.1Q==\'2D\'){6(4.L)N n;T(m);m=\'\';4.f-=2;F(5,d,3,\'1y\')}6(1D.1Q==\'2C\'){6(4.L)N n;T(m);m=\'\';F(5,d,3,\'1x\')}})}6(3.1W){5.1V(9(){4.1j=Q;T(m);m=\'\'},9(){4.1j=n;6(m==\'\'&amp;&amp;!3.1p){m=1E(9(){F(5,d,3,n)},3.1u)}})}5.2E(\'7:X\',9(){4.L=n;$(d).H(9(){6($(g).J(\'a\')){$(g).e(\'P\',\'1q\')}});6($(d[4.f]).J(\'a\')){$(d[4.f]).e(\'P\',\'1A\')}6(m==\'\'&amp;&amp;!4.1j&amp;&amp;!3.1p){m=1E(9(){F(5,d,3,n)},3.1u)}3.20.1w(g)})});9 F(5,d,3,17){b 4=5.1T(\'7:4\');6((!4||4.1S)&amp;&amp;!17)N n;3.1Y.1w(g);6(!17){5.e(\'11\',\'10(\'+4.u.t(\'E\')+\') Z-Y\')}k{6(17==\'1y\'){5.e(\'11\',\'10(\'+4.u.t(\'E\')+\') Z-Y\')}6(17==\'1x\'){5.e(\'11\',\'10(\'+4.u.t(\'E\')+\') Z-Y\')}}4.f++;6(4.f==4.W){4.f=0;3.2d.1w(g)}6(4.f<0)4.f=(4.W-1);6($(d[4.f]).J(\'B\')){4.u=$(d[4.f])}k{4.u=$(d[4.f]).1m(\'B:1r\')}6(3.M){$(\'.7-M a\',5).2B(\'1h\');$(\'.7-M a:1B(\'+4.f+\')\',5).1f(\'1h\')}6(4.u.t(\'w\')!=\'\'){b w=4.u.t(\'w\');6(w.24(0,1)==\'#\')w=$(w).1d();6($(\'.7-K\',5).e(\'P\')==\'1A\'){$(\'.7-K p\',5).2c(3.o,9(){$(g).1d(w);$(g).1z(3.o)})}k{$(\'.7-K p\',5).1d(w)}$(\'.7-K\',5).1z(3.o)}k{$(\'.7-K\',5).2c(3.o)}b i=0;$(\'.7-c\',5).H(9(){b G=U.29(5.x()/3.h);$(g).e({y:\'R\',z:\'0\',11:\'10(\'+4.u.t(\'E\')+\') Z-Y -\'+((G+(i*G))-G)+\'1c 0%\'});i++});6(3.j==\'1l\'){b V=2H 2G("1K","12","1H","1e","1G","13","1I","1v");4.r=V[U.22(U.1l()*(V.1g+1))];6(4.r==2I)4.r=\'1v\'}6(3.j.2p(\',\')!=-1){b V=3.j.2t(\',\');4.r=$.2A(V[U.22(U.1l()*V.1g)])}4.L=Q;6(3.j==\'2r\'||3.j==\'1K\'||4.r==\'1K\'||3.j==\'12\'||4.r==\'12\'){b q=0;b i=0;b h=$(\'.7-c\',5);6(3.j==\'12\'||4.r==\'12\')h=$(\'.7-c\',5).1n();h.H(9(){b c=$(g);c.e(\'1L\',\'R\');6(i==3.h-1){I(9(){c.C({y:\'s%\',z:\'1.0\'},3.o,\'\',9(){5.16(\'7:X\')})},(s+q))}k{I(9(){c.C({y:\'s%\',z:\'1.0\'},3.o)},(s+q))}q+=1i;i++})}k 6(3.j==\'2q\'||3.j==\'1H\'||4.r==\'1H\'||3.j==\'1e\'||4.r==\'1e\'){b q=0;b i=0;b h=$(\'.7-c\',5);6(3.j==\'1e\'||4.r==\'1e\')h=$(\'.7-c\',5).1n();h.H(9(){b c=$(g);c.e(\'28\',\'R\');6(i==3.h-1){I(9(){c.C({y:\'s%\',z:\'1.0\'},3.o,\'\',9(){5.16(\'7:X\')})},(s+q))}k{I(9(){c.C({y:\'s%\',z:\'1.0\'},3.o)},(s+q))}q+=1i;i++})}k 6(3.j==\'1G\'||3.j==\'2u\'||4.r==\'1G\'||3.j==\'13\'||4.r==\'13\'){b q=0;b i=0;b v=0;b h=$(\'.7-c\',5);6(3.j==\'13\'||4.r==\'13\')h=$(\'.7-c\',5).1n();h.H(9(){b c=$(g);6(i==0){c.e(\'1L\',\'R\');i++}k{c.e(\'28\',\'R\');i=0}6(v==3.h-1){I(9(){c.C({y:\'s%\',z:\'1.0\'},3.o,\'\',9(){5.16(\'7:X\')})},(s+q))}k{I(9(){c.C({y:\'s%\',z:\'1.0\'},3.o)},(s+q))}q+=1i;v++})}k 6(3.j==\'1I\'||4.r==\'1I\'){b q=0;b i=0;$(\'.7-c\',5).H(9(){b c=$(g);b 1J=c.x();c.e({1L:\'R\',y:\'s%\',x:\'R\'});6(i==3.h-1){I(9(){c.C({x:1J,z:\'1.0\'},3.o,\'\',9(){5.16(\'7:X\')})},(s+q))}k{I(9(){c.C({x:1J,z:\'1.0\'},3.o)},(s+q))}q+=1i;i++})}k 6(3.j==\'1v\'||4.r==\'1v\'){b i=0;$(\'.7-c\',5).H(9(){$(g).e(\'y\',\'s%\');6(i==3.h-1){$(g).C({z:\'1.0\'},(3.o*2),\'\',9(){5.16(\'7:X\')})}k{$(g).C({z:\'1.0\'},(3.o*2))}i++})}}};$.1k.1o.21={j:\'1l\',h:15,o:2v,1u:2y,19:0,S:Q,1R:Q,M:Q,1P:n,1O:n,1M:\'.1Z\',1N:\'2x.1Z\',1X:Q,1W:Q,1p:n,1U:0.8,1Y:9(){},20:9(){},2d:9(){}};$.1k.1n=[].2w})(2z);',62,169,'|||settings|vars|slider|if|nivo||function||var|slice|kids|css|currentSlide|this|slices||effect|else|child|timer|false|animSpeed||timeBuff|randAnim|100|attr|currentImage||title|width|height|opacity|class|img|animate|div|src|nivoRun|sliceWidth|each|setTimeout|is|caption|running|controlNav|return|append|display|true|0px|directionNav|clearInterval|Math|anims|totalSlides|animFinished|repeat|no|url|background|sliceDownLeft|sliceUpDownLeft|nivoControl||trigger|nudge|childWidth|startSlide|rel|childHeight|px|html|sliceUpLeft|addClass|length|active|50|paused|fn|random|find|_reverse|nivoSlider|manualAdvance|none|first|control|link|pauseTime|fade|call|next|prev|fadeIn|block|eq|live|event|setInterval|click|sliceUpDown|sliceUpRight|fold|origWidth|sliceDownRight|top|controlNavThumbsSearch|controlNavThumbsReplace|controlNavThumbsFromRel|controlNavThumbs|keyCode|directionNavHide|stop|data|captionOpacity|hover|pauseOnHover|keyboardNav|beforeChange|jpg|afterChange|defaults|floor|for|substr|nextNav|hide|prevNav|bottom|round|left|options|fadeOut|slideshowEnd|alt|hasClass|extend|imageLink|Next|show|Prev|replace|relative|children|position|indexOf|sliceUp|sliceDown|window|split|sliceUpDownRight|500|reverse|_thumb|3000|jQuery|trim|removeClass|39|37|bind|keypress|Array|new|undefined'.split('|'),0,{}))
;(function( $ ){
;(function( $ ){
Line 21: Line 18:
// Returns the element that needs to be animated to scroll the window.
// Returns the element that needs to be animated to scroll the window.
-
// Kept for backwards compatibility (specially for localScroll & serialScroll)
+
// Kept for backwards compatibility (specially for localScroll &amp; serialScroll)
$scrollTo.window = function( scope ){
$scrollTo.window = function( scope ){
return $(window)._scrollable();
return $(window)._scrollable();
Line 59: Line 56:
duration = duration || settings.speed || settings.duration;
duration = duration || settings.speed || settings.duration;
// Make sure the settings are given right
// Make sure the settings are given right
-
settings.queue = settings.queue && settings.axis.length > 1;
+
settings.queue = settings.queue &amp;&amp; settings.axis.length > 1;
if( settings.queue )
if( settings.queue )
Line 114: Line 111:
var val = targ[pos];
var val = targ[pos];
// Handle percentage values
// Handle percentage values
-
attr[key] = val.slice && val.slice(-1) == '%' ?  
+
attr[key] = val.slice &amp;&amp; val.slice(-1) == '%' ?  
parseFloat(val) / 100 * max
parseFloat(val) / 100 * max
: val;
: val;
Line 125: Line 122:
// Queueing axes
// Queueing axes
-
if( !i && settings.queue ){
+
if( !i &amp;&amp; settings.queue ){
// Don't waste time animating, if there's no need.
// Don't waste time animating, if there's no need.
if( old != attr[key] )
if( old != attr[key] )
Line 138: Line 135:
function animate( callback ){
function animate( callback ){
-
$elem.animate( attr, duration, settings.easing, callback && function(){
+
$elem.animate( attr, duration, settings.easing, callback &amp;&amp; function(){
callback.call(this, target, settings);
callback.call(this, target, settings);
});
});
Line 179: Line 176:
current = $(this);
current = $(this);
-
$('#wrapper').scrollTo($(this).attr('href'), 800);
+
$('#globalWrapper').scrollTo($(this).attr('href'), 800);
return false;
return false;
Line 199: Line 196:
$('#debug').html(width  + ' ' + height + ' ' + mask_width);
$('#debug').html(width  + ' ' + height + ' ' + mask_width);
-
$('#wrapper, .item').css({width: width, height: height});
+
$('#globalWrapper, .item').css({width: width, height: height});
-
$('#mask').css({width: mask_width, height: height});
+
$('#content').css({width: mask_width, height: height});
-
$('#wrapper').scrollTo($('a.selected').attr('href'), 0);
+
$('#globalWrapper').scrollTo($('a.selected').attr('href'), 0);
}
}
Line 212: Line 209:
pauseTime:3000,
pauseTime:3000,
startSlide:0, //Set starting Slide (0 index)
startSlide:0, //Set starting Slide (0 index)
-
directionNav:true, //Next & Prev
+
directionNav:true, //Next &amp; Prev
directionNavHide:true, //Only show on hover
directionNavHide:true, //Only show on hover
controlNav:true, //1,2,3...
controlNav:true, //1,2,3...
Line 219: Line 216:
controlNavThumbsSearch: '.jpg', //Replace this with...
controlNavThumbsSearch: '.jpg', //Replace this with...
controlNavThumbsReplace: '_thumb.jpg', //...this in thumb Image src
controlNavThumbsReplace: '_thumb.jpg', //...this in thumb Image src
-
keyboardNav:true, //Use left & right arrows
+
keyboardNav:true, //Use left &amp; right arrows
pauseOnHover:true, //Stop animation while hovering
pauseOnHover:true, //Stop animation while hovering
manualAdvance:false, //Force manual transitions
manualAdvance:false, //Force manual transitions
Line 233: Line 230:
<style type="text/css">
<style type="text/css">
body {
body {
-
 
width: 100%;
width: 100%;
margin: 0 auto;
margin: 0 auto;
Line 240: Line 236:
font: trebuchet, verdana, arial, times new roman;
font: trebuchet, verdana, arial, times new roman;
}
}
-
#wrapper{
+
#globalWrapper {
width: 100%;
width: 100%;
height: 100%;
height: 100%;
 +
padding-right: 0pt;
 +
padding-left: 0pt;
 +
padding-bottom: 10px;
 +
background-color: black;
 +
background-image: url("https://static.igem.org/mediawiki/2010/1/1a/Metu-bg.jpg");
 +
background-attachment: fixed;
 +
font: 11px Tahoma, Arial, Helvetica, sans-serif;
position: absolute;
position: absolute;
top: 0;
top: 0;
left: 0;
left: 0;
-
background-color: #ccc;
 
overflow: hidden;
overflow: hidden;
margin: 0 auto;
margin: 0 auto;
}
}
-
 
* html body {
* html body {
overflow: hidden;
overflow: hidden;
}
}
-
#mask{
+
#content {
 +
border-left: none;
 +
border-right: none;
 +
height: 100%;
width: 900%;
width: 900%;
height: 100%;
height: 100%;
Line 523: Line 527:
#menu {
#menu {
text-align: left;
text-align: left;
-
position:fixed;
+
position: fixed;
-
top:50px;
+
top: 50px;
-
height:auto;
+
height: auto;
-
width:auto;
+
width: auto;
-
z-index:999;
+
z-index: 999;
-
height:500px;
+
height: 500px;
}
}
-
#menu ul li a.selected{
+
#menu ul li a.selected {
-
color:red;
+
color: red;
-
background:silver;
+
background: silver;
}
}
/*Toggle Area*/
/*Toggle Area*/
Line 543: Line 547:
border-left: 1px solid #E0E0E0;
border-left: 1px solid #E0E0E0;
color: #999;
color: #999;
-
        text-indent:0;
+
text-indent: 0;
-
        margin-left:0;
+
margin-left: 0;
}
}
#menu ul.navmenu li:first-child .toggle {
#menu ul.navmenu li:first-child .toggle {
Line 629: Line 633:
}
}
#contentSub {
#contentSub {
-
display:none;
+
display: none;
}
}
-
 
#siteSub {
#siteSub {
-
display:none;
+
display: none;
}
}
-
 
#search-controls {
#search-controls {
-
display:none;
+
display: none;
}
}
-
 
.firstHeading {
.firstHeading {
-
display:none;
+
display: none;
}
}
-
 
#search-controls {
#search-controls {
-
margin-top:30px;
+
margin-top: 30px;
}
}
-
 
#footer-box {
#footer-box {
-
display:none;
+
display: none;
}
}
-
 
#top-section {
#top-section {
-
height: 25px;
+
height: 25px;
-
width:100%;
+
width: 100%;
-
position:fixed;
+
position: fixed;
-
border-left: none;
+
border-left: none;
-
border-right: none;
+
border-right: none;
}
}
-
 
.left-menu {
.left-menu {
-
margin-top:-15px;
+
margin-top: -15px;
}
}
-
 
.left-menu ul {
.left-menu ul {
-
border: none;
+
border: none;
}
}
-
 
#menubar li a {
#menubar li a {
-
color: white;
+
color: white;
}
}
-
 
#menubar.right-menu {
#menubar.right-menu {
-
margin-top:-15px;
+
margin-top: -15px;
}
}
-
 
.right-menu ul {
.right-menu ul {
-
border: none;
+
border: none;
}
}
-
 
+
#menubar {
-
#menubar{
+
top: 22px;
-
top:22px;
+
z-index: 25;
-
z-index:25;
+
}
}
-
 
+
img[src*="/wiki/skins/common/images/wiki.png"] {
-
img[src*="/wiki/skins/common/images/wiki.png"]{
+
width: 0;
-
 
+
height: 40px;
-
    width:0;
+
padding-right: 975px;
-
    height:40px;
+
background: transparent url(https://static.igem.org/mediawiki/2010/4/4f/Metu-top.png) top left no-repeat;
-
    padding-right:975px;
+
-
    background:transparent url(https://static.igem.org/mediawiki/2010/4/4f/Metu-top.png) top left no-repeat;
+
}
}
-
#content{
+
</style>
-
background-color: white;
+
-
border-left: none;
+
-
border-right: none;
+
-
width:100%;
+
-
height:100%
+
-
}
+
-
#globalWrapper
+
-
 
+
-
{
+
-
position: relative;
+
-
font-size: 127%;
+
-
width: 100%;
+
-
height:100%;
+
-
margin-top: 0pt;
+
-
margin-right: 0pt;
+
-
margin-bottom: 0pt;
+
-
margin-left: 0pt;
+
-
padding-top: 0pt;
+
-
padding-right: 0pt;
+
-
padding-left: 0pt;
+
-
padding-bottom: 10px;
+
-
background-color: black;
+
-
background-image:url("https://static.igem.org/mediawiki/2010/1/1a/Metu-bg.jpg");
+
-
background-attachment: fixed;
+
-
font: 11px Tahoma, Arial, Helvetica, sans-serif;
+
-
}
+
-
 
+
-
</style>
+
-
</head>
+
<script type="text/javascript">
<script type="text/javascript">
$(document).ready(function() {
$(document).ready(function() {
Line 745: Line 706:
</script>
</script>
-
<body style="height: 998px">
 
-
<div id="wrapper">
+
</head>
-
<div id="menu">
+
<body>
-
<ul class="navmenu">
+
<div id="globalWrapper">
-
<li><div class="menutop menusingle"><a class="panel" href="#home">Home</a></div></li>
+
<div id="top-section">
-
<li><div class="menutop menusingle panel"><a class="panel" href="#team">Team</a></div></li>
+
<div id="p-logo">
-
            <li><div class="menutop menusingle panel"><a class="panel" href="#motivation">Motivation</a></div></li>
+
<a href="/Main_Page" title="Main Page">
-
<li><div class="menutop menusingle panel"><a class="panel" href="#scope">Scope</a></div></li>
+
<img src="/wiki/skins/common/images/wiki.png">" </a></div>
-
<li><div class="menutop"><a class="panel" href="#project">Project</a><div class="toggle">+</div></div>
+
<!-- end p-logo -->
-
            <ul class="submenu">
+
<script type="text/javascript"> if (window.isMSIE55) fixalpha(); </script>
-
                <li><a class="panel" href="#project">Introduction</a></li>
+
<div id="menubar" class="left-menu">
-
                    <li><a class="panel" href="#project2">Material and Methods</a></li>
+
<ul>
-
                    <li><a class="panel" href="#project3">Database Standardization</a></li>
+
<li class="selected"><a href="/Team:METU_Turkey_Software">Page
-
                    <li><a class="panel" href="#project4">Modelling</a></li>
+
</a></li>
-
                    <li><a class="panel" href="#project5">Algorithm</a></li>
+
<li class="new">
-
                    <li><a class="panel" href="#project6">Results</a></li>                   
+
<a href="/wiki/index.php?title=Talk:Team:METU_Turkey_Software&amp;action=edit">
-
                </ul>
+
Discussion </a></li>
-
            </li>                     
+
<li>
-
            <li><div class="menutop menusingle panel"><a class="panel" href="#notebook">Notebook</a></div></li>
+
<a href="/wiki/index.php?title=Team:METU_Turkey_Software&amp;action=edit">
-
            <li><div class="menutop panel"><a class="panel" href="#download">Download</a><div class="toggle">+</div></div>
+
View source </a></li>
-
            <ul class="submenu">
+
<li>
-
                <li><a class="panel" href="#download">Executable</a></li>
+
<a href="/wiki/index.php?title=Team:METU_Turkey_Software&amp;action=history">
-
                    <li><a class="panel" href="#download2">Code</a></li>
+
History </a></li>
-
                <li><a class="panel" href="#download3">User Guide</a></li>
+
<li style="color: rgb(128, 128, 128); cursor: default;">teams</li>
-
                <li><a class="panel" href="#download4">Support</a></li>
+
-
                <li><a class="panel" href="#download5">Contact</a></li>                        
+
-
                </ul>
+
-
            </li>
+
-
            <li><div class="menutop panel"><a class="panel" href="#miscellaneous">Miscellaneous</a><div class="toggle">+</div></div>
+
-
            <ul class="submenu">
+
-
                <li><a class="panel" href="#miscellaneous">Collaboration</a></li>
+
-
                    <li><a class="panel" href="#miscellaneous2">Human Practices</a></li>
+
-
                <li><a class="panel" href="#miscellaneous3">Safety</a></li>
+
-
                <li><a class="panel" href="#miscellaneous4">Future Plan</a></li>
+
-
 
+
-
                </ul>
+
-
            </li>    
+
</ul>
</ul>
-
</div>
+
</div>
-
<div id="mask">
+
<!-- end menubar (left) -->
-
+
<div id="menubar" class="right-menu">
-
<!-- 1st row -->
+
<ul>
-
<div id="home" class="item"><div class="homepage"></div></div>
+
<li id="pt-login">
-
<div id="team" class="item">
+
<a accesskey="o" href="/wiki/index.php?title=Special:UserLogin&amp;returnto=Team:METU_Turkey_Software" title="You are encouraged to log in, it is not mandatory however. [o]">
-
<div class="content2">Team
+
Log in</a></li>
-
<div class="text">
+
</ul>
-
<div id="slider">
+
</div>
-
<img src="https://static.igem.org/mediawiki/2010/e/e7/Metu-slide1.jpg" alt="">
+
<!-- end right menubar -->
-
<img src="https://static.igem.org/mediawiki/2010/e/e1/Metu-slide2.jpg" alt="">
+
<div id="search-controls">
-
<img src="https://static.igem.org/mediawiki/2010/b/b8/Metu-slide3.jpg" alt="">
+
<form id="searchform" action="/Special:Search">
 +
<input id="searchInput" accesskey="f" autocomplete="off" name="search" title="Search 2010.igem.org [alt-f]" type="text" value="">
 +
<input id="searchGoButton" class="searchButton" name="go" title="Go to a page with this exact name if exists" type="submit" value="Go">&nbsp;
 +
<input id="mw-searchButton" class="searchButton" name="fulltext" title="Search the pages for this text" type="submit" value="Search">
 +
</form>
 +
</div>
 +
<!-- close search controls --></div>
 +
<!-- close top-section-->
 +
<div id="content">
 +
<!--
 +
<div id="jump-to-nav">Jump to:                        <a href="#column-one">navigation</a>, <a href="#searchInput">search</a></div>-->
 +
<!-- start content -->
 +
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"  
 +
"http://www.w3.org/TR/html4/strict.dtd">
 +
<title>METU Turkey Software</title>
 +
<!-- 1st row -->
 +
<div id="home" class="item">
 +
<div class="homepage">
 +
</div>
</div>
</div>
-
+
<div id="team" class="item">
-
<p>
+
<div class="content2">
-
METU Turkey Software is an interdisciplinary team of 8 students and 3 advisors  
+
Team
-
from various backgrounds such as Molecular Biology, Bioinformatics,  
+
<div class="text">
-
Computer Engineering and Computer Education and Instructional Technology.  
+
<div id="slider">
-
We have put our knowledge and experience in our fields together to bring a much  
+
<img alt="" src="https://static.igem.org/mediawiki/2010/e/e7/Metu-slide1.jpg">
-
needed solution to a daily problem in field of synthetic biology for iGEM 2010
+
<img alt="" src="https://static.igem.org/mediawiki/2010/e/e1/Metu-slide2.jpg">
-
</p>
+
<img alt="" src="https://static.igem.org/mediawiki/2010/b/b8/Metu-slide3.jpg">
-
 
+
</div>
 +
<p>METU Turkey Software is an interdisciplinary team of  
 +
8 students and 3 advisors from various backgrounds such  
 +
as Molecular Biology, Bioinformatics, Computer Engineering  
 +
and Computer Education and Instructional Technology. We
 +
have put our knowledge and experience in our fields together  
 +
to bring a much needed solution to a daily problem in field  
 +
of synthetic biology for iGEM 2010 </p>
 +
</div>
 +
</div>
</div>
</div>
 +
<div id="motivation" class="item">
 +
<div class="content2">
 +
<div class="text">
 +
Motivation
 +
<p>Since 2008, we have been participating in iGEM as METU
 +
( Middle East Technical University) wet-lab team, and each
 +
year we have noticed the increasing number of teams participating,
 +
along with an increase in biobricks entries at partsregistry.org.
 +
While having more choices of biobricks to choose from is
 +
incredible, searching for and choosing the appropriate parts
 +
is becoming a challenge. This year during the construction
 +
process of iGEM biobrick parts for our new project, we felt
 +
the need for an application to find interacting parts based
 +
on an input/output model to design the genetic constructs.
 +
Using a specialized software for searching the parts registry
 +
to find possible biobricks to include into our construct
 +
would be much easy, fast and accurate than manual. We have
 +
shared our need with a group of friends who are software
 +
engineers, and initiated the METU_Turkey_SOFTWARE team where
 +
we worked together over this summer to build the BIO-Guide
 +
software. </p>
 +
</div>
 +
</div>
</div>
</div>
 +
<div id="scope" class="item">
 +
<div class="content2">
 +
<div class="text">
 +
Scope and Future Aspects
 +
<p>The partsregistry.org is a continuously growing collection
 +
of standard genetic parts that can be mixed and matched
 +
to build synthetic biology devices and systems. The Registry
 +
is based on the principle of "get some, give some". Registry
 +
users benefit from using the parts and information available
 +
in the Registry for designing their own genetically engineered
 +
biological systems. In exchange, the expectation is that
 +
Registry users will contribute back to the information and
 +
the data on existing parts and will submit new parts they
 +
have designed in order to improve this community resource.
 +
</p>
 +
<p>As an expanding database partsregistry.org needs to be
 +
more organized and the standardization template needs to
 +
be improved. Additionally, the potential of multiple ways
 +
of using each part in different construct combination brings
 +
out the necessity for an application to search through the
 +
database. BIO-Guide is the first designed software that
 +
organizes over 1000 parts in partsregistry.org as possible
 +
atomics parts to build new biological device and systems
 +
for specific input and outputs based on graph theory. The
 +
requirement of similar applications and software tools are
 +
now inevitable in the emerging field of synthetic biology.
 +
The innovative approach that makes the partsregistry.org
 +
easy to use for synthetic biology applications is the collection
 +
of standardized parts that can be used in any combination
 +
with minimal effort under one database. But while working
 +
on our algorithm to search for possible combinations of
 +
parts depending on the given input and output, we have realized
 +
that present standards are inadequate and parts registry
 +
form must be improved. </p>
 +
<p>In very near future a new format for parts registry form
 +
is needed and few additional features should be implemented
 +
to have more control on the database. We are planning to
 +
suggest a new format and features for the parts registry
 +
based on the survey results we have received. And planning
 +
to build the next version of BIO-guide based on the revised
 +
parts registry form. Along with using new parts registry
 +
standards we will be improving the algorithm, so that the
 +
software can search through more complex relations and returns
 +
all possible functional constructs. </p>
 +
</div>
 +
</div>
 +
</div>
 +
<div id="project" class="item">
 +
<div class="content2">
 +
Project Introduction
 +
<div class="text">
 +
<p>As the field of Synthetic Biology is on the rise, iGEM
 +
is growing up very fast and the number of parts in the parts
 +
registry is increasing with the addition of more complex
 +
parts each day. After facing some difficulty while running
 +
our algorithms on the parts registry, the need for more
 +
effective standardization of parts entry was apparent. We
 +
have investigated the information on parts in iGEM’s 2010
 +
distribution and reorganized the information on the parts
 +
registry forms according to the needs of our algorithm.
 +
Then we have used graph theoretic modeling to visualize
 +
the relations between iGEM Parts and to standardize the
 +
representation of the parts as much as possible by graph
 +
theoretical methods. This helped us to find input output
 +
relations between the parts. Furthermore, our program BIO-Guide
 +
is now able to provide alternative pathways to construct
 +
the most reliable and functional Biobrick devices with respect
 +
to given inputs and expected outputs as a guide to Biobricks
 +
parts registry.</p>
 +
</div>
 +
</div>
 +
</div>
 +
<div id="notebook" class="item">
 +
<div class="content2">
 +
Notebook</div>
 +
</div>
 +
<div id="download" class="item">
 +
<div class="content2">
 +
Download</div>
 +
</div>
 +
<div id="miscellaneous" class="item">
 +
<div class="content2">
 +
Misc - Collaboration</div>
 +
</div>
 +
<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">
 +
Material and Methods
 +
<p>Our material for B-IO Guide Software Program was the
 +
all background information of parts stated in distributed
 +
2010 iGEM plates to whole wetlab teams. Data of a part having
 +
specific part ID has been parsed by writing a parsing code.
 +
Then, other data which needs to be standardized according
 +
to biological importance which has been get out from the
 +
Registry of Parts Page manually. These standardized data
 +
are; </p>
 +
<ul>
 +
<li>working conditions of biobricks involved within
 +
the parts</li>
 +
<li>properties of inputs and outputs</li>
 +
</ul>
 +
<p>We named as "Inputs" because an effector which may be
 +
chemical(IPTG, galactose etc.) and physical (UV irradiation,
 +
temperature etc) external inputs or may be proteins synthesized
 +
from a biobrick coding sequence can affect promoters on
 +
the parts. The effects of these mentioned inputs have been
 +
determined as inducer (a molecule that starts gene expression),
 +
repressor (blocker of attachment of RNA polymerase to promoter),
 +
activator (increasing the rate of transcription) and inhibitor
 +
(decreasing the rate of transcription). Moreover, the promoters
 +
may have additional property at which they may become constitutively
 +
ON without seen any effect. </p>
 +
<p>On the other hand, for output section, we add new approach
 +
which is "working condition" parameter because the expressed
 +
proteins from biobrick coding sequences may come from different
 +
organisms to run mostly in E.coli. However, in some cases
 +
these proteins may not work well as expected unless suitable
 +
and optimum conditions are provided in the host. Thus, we
 +
have thought that natural(in vivo) or experimental(in vitro)
 +
working conditions of the synthesized proteins from the
 +
certain biobricks or constructs should be stated during
 +
submitting to Parts Registry. Nevertheless, our 2010 iGEM
 +
Software Program version 1.0 mostly does not have any experimental
 +
data since the data had not been added for pages of the
 +
parts regularly and true. Therefore, if our advised Parts
 +
Registry interfaces are used in iGEM in future and our standards
 +
are used, then we will be able to add such an information
 +
to the database of the program for better performance.
 +
</p>
 +
</div>
 +
</div>
 +
</div>
 +
<div class="item">
 +
</div>
 +
<div id="download2" class="item">
 +
<div class="content2">
 +
Code</div>
 +
</div>
 +
<div id="miscellaneous2" class="item">
 +
<div class="content2">
 +
Human Practices</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">
 +
Database</div>
 +
</div>
 +
<div class="item">
 +
</div>
 +
<div id="download3" class="item">
 +
<div class="content2">
 +
User Guide</div>
 +
</div>
 +
<div id="miscellaneous3" class="item">
 +
<div class="content2">
 +
Safety</div>
 +
</div>
 +
<div class="clear">
 +
</div>
 +
<!-- 4th row -->
 +
<div class="item">
 +
</div>
 +
<div class="item">
 +
</div>
 +
<div class="item">
 +
</div>
 +
<div class="item">
 +
</div>
 +
<div id="project4" class="item">
 +
<div class="content2">
 +
Modelling</div>
 +
</div>
 +
<div class="item">
 +
</div>
 +
<div id="download4" class="item">
 +
<div class="content2">
 +
Support</div>
 +
</div>
 +
<div id="miscellaneous4" class="item">
 +
<div class="content2">
 +
Future Plan</div>
 +
</div>
 +
<div class="clear">
 +
</div>
 +
<!-- 5th row -->
 +
<div class="item">
 +
</div>
 +
<div class="item">
 +
</div>
 +
<div class="item">
 +
</div>
 +
<div class="item">
 +
</div>
 +
<div id="project5" class="item">
 +
<div class="content2">
 +
Algorithm</div>
 +
</div>
 +
<div class="item">
 +
</div>
 +
<div id="download5" class="item">
 +
<div class="content2">
 +
Contact</div>
 +
</div>
 +
<div class="item">
 +
</div>
 +
<div class="clear">
 +
</div>
 +
<!-- 6th row -->
 +
<div class="item">
 +
</div>
 +
<div class="item">
 +
</div>
 +
<div class="item">
 +
</div>
 +
<div class="item">
 +
</div>
 +
<div id="project6" class="item">
 +
<div class="content2">
 +
Results</div>
 +
</div>
 +
<div class="item">
 +
</div>
 +
<div class="item">
 +
</div>
 +
<div class="item">
 +
</div>
 +
<div class="clear">
 +
</div>
 +
</div>
 +
<!--
 +
NewPP limit report
 +
Preprocessor node count: 4/1000000
 +
Post-expand include size: 0/2097152 bytes
 +
Template argument size: 0/2097152 bytes
 +
Expensive parser function count: 0/100
 +
-->
 +
<!-- Saved in parser cache with key 2010_igem_org:pcache:idhash:461-0!1!0!!en!2!edit=0 and timestamp 20101025205305 -->
 +
<!-- end content -->
 +
<!-- close footer --></div>
 +
<!-- close footer-box -->
 +
<script type="text/javascript">if (window.runOnloadHook) runOnloadHook();</script>
 +
<div id="menu">
 +
<ul class="navmenu">
 +
<li>
 +
<div class="menutop menusingle">
 +
<a class="panel" href="#home">Home</a></div>
 +
</li>
 +
<li>
 +
<div class="menutop menusingle panel">
 +
<a class="panel" href="#team">Team</a></div>
 +
</li>
 +
<li>
 +
<div class="menutop menusingle panel">
 +
<a class="panel" href="#motivation">Motivation</a></div>
 +
</li>
 +
<li>
 +
<div class="menutop menusingle panel">
 +
<a class="panel" href="#scope">Scope</a></div>
 +
</li>
 +
<li>
 +
<div class="menutop">
 +
<a class="panel" href="#project">Project</a><div class="toggle toggle-closed">
 +
+</div>
</div>
</div>
-
<div id="motivation" class="item"><div class="content2">
+
<ul class="submenu" style="display: none;">
-
<div class="text">
+
<li><a class="panel" href="#project">Introduction</a></li>
-
Motivation
+
<li><a class="panel" href="#project2">Material and Methods</a></li>
-
<p>
+
<li><a class="panel" href="#project3">Database Standardization</a></li>
-
Since 2008, we have been participating in iGEM as METU ( Middle East Technical University)
+
<li><a class="panel" href="#project4">Modelling</a></li>
-
wet-lab team, and each year we have noticed the increasing number of teams participating,
+
<li><a class="panel" href="#project5">Algorithm</a></li>
-
along with an increase in biobricks entries at partsregistry.org. While having more choices
+
<li><a class="panel" href="#project6">Results</a></li>
-
of biobricks to choose from is incredible, searching for and choosing the appropriate parts
+
</ul>
-
is becoming a challenge. This year during the construction process of iGEM biobrick parts for
+
</li>
-
our new project, we felt the need for an application to find interacting parts based on an
+
<li>
-
input/output model to design the genetic constructs. Using a specialized software for searching
+
<div class="menutop menusingle panel">
-
the parts registry to find possible biobricks to include into our construct would be much easy,
+
<a class="panel" href="#notebook">Notebook</a></div>
-
fast and accurate than manual. We have shared our need with a group of friends who are software
+
</li>
-
engineers, and initiated the METU_Turkey_SOFTWARE team where we worked together over this summer
+
<li>
-
to build the BIO-Guide software.
+
<div class="menutop panel">
-
</p>
+
<a class="panel" href="#download">Download</a><div class="toggle toggle-closed">
-
</div></div></div>
+
+</div>
-
<div id="scope" class="item"><div class="content2">
+
-
<div class="text">
+
-
Scope and Future Aspects
+
-
<p>
+
-
The partsregistry.org is a continuously growing collection of standard genetic parts that
+
-
can be mixed and matched to build synthetic biology devices and systems. The Registry is
+
-
based on the principle of "get some, give some". Registry users benefit from using the parts
+
-
and information available in the Registry for designing their own genetically engineered
+
-
biological systems. In exchange, the expectation is that Registry users will contribute back to
+
-
the information and the data on existing parts and will submit new parts they have designed in
+
-
order to improve this community resource.
+
-
</p>
+
-
+
-
<p>
+
-
As an expanding database partsregistry.org needs to be more organized and the standardization
+
-
template needs to be improved. Additionally, the potential of multiple ways of using each part
+
-
in different construct combination brings out the necessity for an application to search through
+
-
the database. BIO-Guide is the first designed software that organizes over 1000 parts in partsregistry.org
+
-
as possible atomics parts to build new biological device and systems for specific input and outputs based on
+
-
graph theory. The requirement of similar applications and software tools are now inevitable in the emerging
+
-
field of synthetic biology. The innovative approach that makes the partsregistry.org  easy to use for synthetic
+
-
biology applications is the collection of standardized parts that can be used in any combination with minimal
+
-
effort under one database. But while working on our algorithm to search for possible combinations of parts depending
+
-
on the given input and output, we have realized that present standards are inadequate and parts registry form must be improved.
+
-
</p>
+
-
+
-
<p>
+
-
In very near future a new format for parts registry form is needed and few additional features
+
-
should be implemented to have more control on the database. We are planning to suggest a new format
+
-
and features for the parts registry based on the survey results we have received. And planning to
+
-
build the next version of BIO-guide based on the revised parts registry form. Along with using new parts
+
-
registry standards we will be improving the algorithm, so that the software can search through more
+
-
complex relations and returns all possible functional constructs.
+
-
</p>
+
-
 
+
</div>
</div>
-
</div></div>
+
<ul class="submenu" style="display: none;">
-
<div id="project" class="item"><div class="content2">Project Introduction
+
<li><a class="panel" href="#download">Executable</a></li>
-
<div class="text">
+
<li><a class="panel" href="#download2">Code</a></li>
-
<p>As the field of Synthetic Biology is on the rise, iGEM is growing up very fast and the
+
<li><a class="panel" href="#download3">User Guide</a></li>
-
number of parts in the parts registry is increasing with the addition of more complex parts each day.
+
<li><a class="panel" href="#download4">Support</a></li>
-
After facing some difficulty while running our algorithms on the parts registry, the need for more effective
+
<li><a class="panel" href="#download5">Contact</a></li>
-
standardization of parts entry was apparent. We have investigated the information on parts in iGEM’s 2010 distribution
+
</ul>
-
and reorganized the information on the parts registry forms according to the needs of our algorithm.
+
</li>
-
Then we have used graph theoretic modeling to visualize the relations between iGEM Parts and to standardize
+
<li>
-
the representation of the parts as much as possible by graph theoretical methods. This helped us to find input
+
<div class="menutop panel" style="border-bottom-color: rgb(204, 204, 204); border-bottom-width: 1px; border-bottom-style: solid;">
-
output relations between the parts. Furthermore, our program BIO-Guide is now able to provide alternative pathways
+
<a class="panel" href="#miscellaneous">Miscellaneous</a><div class="toggle toggle-closed">
-
to construct the most reliable and functional Biobrick devices with respect to given inputs and expected outputs as
+
+</div>
-
a guide to Biobricks parts registry.</p>
+
-
</div>
+
-
</div></div>
+
-
+
-
<div id="notebook" class="item"><div class="content2">Notebook</div></div>
+
-
<div id="download" class="item"><div class="content2">Download</div></div>
+
-
<div id="miscellaneous" class="item"><div class="content2">Misc - Collaboration</div></div>
+
-
<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">
+
-
Material and Methods
+
-
<p>
+
-
Our material for B-IO Guide Software Program was the all background
+
-
information of parts stated in distributed 2010 iGEM plates to whole
+
-
wetlab teams. Data of a part having specific part ID has been parsed
+
-
by writing a parsing code. Then, other data which needs to be standardized
+
-
according to biological importance which has been get out from the
+
-
Registry of Parts Page manually. These standardized data are;
+
-
</p>
+
-
+
-
<ul>
+
-
<li>working conditions of biobricks involved within the parts</li>
+
-
<li>properties of inputs and outputs</li>
+
-
</ul>
+
-
+
-
<p>
+
-
We named as "Inputs" because an effector which
+
-
may be chemical(IPTG, galactose etc.) and physical (UV irradiation,
+
-
temperature etc) external inputs or may be proteins synthesized
+
-
from a biobrick coding sequence can affect promoters on the parts.
+
-
The effects of these mentioned inputs have been determined as inducer
+
-
(a molecule that starts gene expression), repressor (blocker of
+
-
attachment of RNA polymerase to promoter), activator (increasing
+
-
the rate of transcription) and inhibitor (decreasing the rate of
+
-
transcription). Moreover, the promoters may have additional property
+
-
at which they may become constitutively ON without seen any effect.
+
-
</p>
+
-
+
-
<p>
+
-
On the other hand, for output section, we add new approach which
+
-
is "working condition" parameter because the expressed proteins
+
-
from biobrick coding sequences may come from different organisms
+
-
to run mostly in E.coli. However, in some cases these proteins may
+
-
not work well as expected unless suitable and optimum conditions
+
-
are provided in the host. Thus, we have thought that natural(in
+
-
vivo) or experimental(in vitro) working conditions of the synthesized
+
-
proteins from the certain biobricks or constructs should be stated
+
-
during submitting to Parts Registry. Nevertheless, our 2010 iGEM
+
-
Software Program version 1.0 mostly does not have any experimental
+
-
data since the data had not been added for pages of the parts regularly
+
-
and true. Therefore, if our advised Parts Registry interfaces are
+
-
used in iGEM in future and our standards are used, then we will
+
-
be able to add such an information to the database of the program
+
-
for better performance.
+
-
</p>
+
</div>
</div>
-
</div></div>
+
<ul class="submenu" style="display: none;">
-
<div class="item"></div>
+
<li><a class="panel" href="#miscellaneous">Collaboration</a></li>
-
<div id="download2" class="item"><div class="content2">Code</div></div>
+
<li><a class="panel" href="#miscellaneous2">Human Practices</a></li>
-
<div id="miscellaneous2" class="item"><div class="content2">Human Practices</div></div>
+
<li><a class="panel" href="#miscellaneous3">Safety</a></li>
-
<div class="clear"></div>
+
<li><a class="panel" href="#miscellaneous4">Future Plan</a></li>
-
+
</ul>
-
<!-- 3rd row -->
+
</li>
-
<div class="item"></div>
+
</ul>
-
<div class="item"></div>
+
-
<div class="item"></div>
+
-
<div class="item"></div>
+
-
<div id="project3" class="item"><div class="content2">Database</div></div>
+
-
<div class="item"></div>
+
-
<div id="download3" class="item"><div class="content2">User Guide</div></div>
+
-
<div id="miscellaneous3" class="item"><div class="content2">Safety</div></div>
+
-
<div class="clear"></div>
+
-
+
-
<!-- 4th row -->
+
-
<div class="item"></div>
+
-
<div class="item"></div>
+
-
<div class="item"></div>
+
-
<div class="item"></div>
+
-
<div id="project4" class="item"><div class="content2">Modelling</div></div>
+
-
<div class="item"></div>
+
-
<div id="download4" class="item"><div class="content2">Support</div></div>
+
-
<div id="miscellaneous4" class="item"><div class="content2">Future Plan</div></div>
+
-
<div class="clear"></div>
+
-
+
-
<!-- 5th row -->
+
-
<div class="item"></div>
+
-
<div class="item"></div>
+
-
<div class="item"></div>
+
-
<div class="item"></div>
+
-
<div id="project5" class="item"><div class="content2">Algorithm</div></div>
+
-
<div class="item"></div>
+
-
<div id="download5" class="item"><div class="content2">Contact</div></div>
+
-
<div class="item"></div>
+
-
<div class="clear"></div>
+
-
+
-
<!-- 6th row -->
+
-
<div class="item"></div>
+
-
<div class="item"></div>
+
-
<div class="item"></div>
+
-
<div class="item"></div>
+
-
<div id="project6" class="item"><div class="content2">Results</div></div>
+
-
<div class="item"></div>
+
-
<div class="item"></div>
+
-
<div class="item"></div>
+
-
<div class="clear"></div>
+
-
</div>
+
</div>
</div>
-
 
</body>
</body>
 +
</html>
-
</html>
+
<!-- Served in 0.184 secs. -->

Revision as of 21:17, 25 October 2010

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

 
METU Turkey Software
Team

METU Turkey Software is an interdisciplinary team of 8 students and 3 advisors from various backgrounds such as Molecular Biology, Bioinformatics, Computer Engineering and Computer Education and Instructional Technology. We have put our knowledge and experience in our fields together to bring a much needed solution to a daily problem in field of synthetic biology for iGEM 2010

Motivation

Since 2008, we have been participating in iGEM as METU ( Middle East Technical University) wet-lab team, and each year we have noticed the increasing number of teams participating, along with an increase in biobricks entries at partsregistry.org. While having more choices of biobricks to choose from is incredible, searching for and choosing the appropriate parts is becoming a challenge. This year during the construction process of iGEM biobrick parts for our new project, we felt the need for an application to find interacting parts based on an input/output model to design the genetic constructs. Using a specialized software for searching the parts registry to find possible biobricks to include into our construct would be much easy, fast and accurate than manual. We have shared our need with a group of friends who are software engineers, and initiated the METU_Turkey_SOFTWARE team where we worked together over this summer to build the BIO-Guide software.

Scope and Future Aspects

The partsregistry.org is a continuously growing collection of standard genetic parts that can be mixed and matched to build synthetic biology devices and systems. The Registry is based on the principle of "get some, give some". Registry users benefit from using the parts and information available in the Registry for designing their own genetically engineered biological systems. In exchange, the expectation is that Registry users will contribute back to the information and the data on existing parts and will submit new parts they have designed in order to improve this community resource.

As an expanding database partsregistry.org needs to be more organized and the standardization template needs to be improved. Additionally, the potential of multiple ways of using each part in different construct combination brings out the necessity for an application to search through the database. BIO-Guide is the first designed software that organizes over 1000 parts in partsregistry.org as possible atomics parts to build new biological device and systems for specific input and outputs based on graph theory. The requirement of similar applications and software tools are now inevitable in the emerging field of synthetic biology. The innovative approach that makes the partsregistry.org easy to use for synthetic biology applications is the collection of standardized parts that can be used in any combination with minimal effort under one database. But while working on our algorithm to search for possible combinations of parts depending on the given input and output, we have realized that present standards are inadequate and parts registry form must be improved.

In very near future a new format for parts registry form is needed and few additional features should be implemented to have more control on the database. We are planning to suggest a new format and features for the parts registry based on the survey results we have received. And planning to build the next version of BIO-guide based on the revised parts registry form. Along with using new parts registry standards we will be improving the algorithm, so that the software can search through more complex relations and returns all possible functional constructs.

Project Introduction

As the field of Synthetic Biology is on the rise, iGEM is growing up very fast and the number of parts in the parts registry is increasing with the addition of more complex parts each day. After facing some difficulty while running our algorithms on the parts registry, the need for more effective standardization of parts entry was apparent. We have investigated the information on parts in iGEM’s 2010 distribution and reorganized the information on the parts registry forms according to the needs of our algorithm. Then we have used graph theoretic modeling to visualize the relations between iGEM Parts and to standardize the representation of the parts as much as possible by graph theoretical methods. This helped us to find input output relations between the parts. Furthermore, our program BIO-Guide is now able to provide alternative pathways to construct the most reliable and functional Biobrick devices with respect to given inputs and expected outputs as a guide to Biobricks parts registry.

Notebook
Download
Misc - Collaboration
Material and Methods

Our material for B-IO Guide Software Program was the all background information of parts stated in distributed 2010 iGEM plates to whole wetlab teams. Data of a part having specific part ID has been parsed by writing a parsing code. Then, other data which needs to be standardized according to biological importance which has been get out from the Registry of Parts Page manually. These standardized data are;

  • working conditions of biobricks involved within the parts
  • properties of inputs and outputs

We named as "Inputs" because an effector which may be chemical(IPTG, galactose etc.) and physical (UV irradiation, temperature etc) external inputs or may be proteins synthesized from a biobrick coding sequence can affect promoters on the parts. The effects of these mentioned inputs have been determined as inducer (a molecule that starts gene expression), repressor (blocker of attachment of RNA polymerase to promoter), activator (increasing the rate of transcription) and inhibitor (decreasing the rate of transcription). Moreover, the promoters may have additional property at which they may become constitutively ON without seen any effect.

On the other hand, for output section, we add new approach which is "working condition" parameter because the expressed proteins from biobrick coding sequences may come from different organisms to run mostly in E.coli. However, in some cases these proteins may not work well as expected unless suitable and optimum conditions are provided in the host. Thus, we have thought that natural(in vivo) or experimental(in vitro) working conditions of the synthesized proteins from the certain biobricks or constructs should be stated during submitting to Parts Registry. Nevertheless, our 2010 iGEM Software Program version 1.0 mostly does not have any experimental data since the data had not been added for pages of the parts regularly and true. Therefore, if our advised Parts Registry interfaces are used in iGEM in future and our standards are used, then we will be able to add such an information to the database of the program for better performance.

Code
Human Practices
Database
User Guide
Safety
Modelling
Support
Future Plan
Algorithm
Contact
Results