|
|
| (54 intermediate revisions not shown) |
| Line 1: |
Line 1: |
| | + | {{:Team:Shenzhen_BGIC_0101/Templates/Header}} |
| | <html> | | <html> |
| - | <head>
| + | <script src="https://2013.igem.org/Team:Shenzhen_BGIC_0101/aaa?action=raw&ctype=text/javascript"></script> |
| - | <!-- iGem wiki hacks -->
| + | |
| - | <!-- Remove all empty <p> tags -->
| + | |
| - | <script type="text/javascript">
| + | |
| - | $(document).ready(function() {
| + | |
| - | $("p").filter( function() {
| + | |
| - | return $.trim($(this).html()) == '';
| + | |
| - | }).remove();
| + | |
| - | });
| + | |
| - | </script>
| + | |
| | | | |
| - | <!-- Remove "team" from the menubar -->
| + | <body> |
| - | <script type="text/javascript">
| + | |
| - | $(document).ready(function() {
| + | |
| - | $("menubar > ul > li:last-child").remove();
| + | |
| - | });
| + | |
| - | </script>
| + | |
| | | | |
| - | <!-- Empty heading? - Then remove it.. -->
| + | <br/><br/> |
| - | <script type="text/javascript">
| + | <section class="container"> |
| - | $(document).ready(function() {
| + | <div class="one-third column"> |
| - | if ("" == "</html>{{{1}}}<html>") {
| + | |
| - | $("#heading").remove();
| + | <a href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/Tutorial/neochr" target="_blank"> |
| - | }
| + | <img src="https://static.igem.org/mediawiki/2013/f/f9/Neochr_icon-purple.png" /> |
| - | });
| + | </a> |
| - | </script>
| + | |
| - | <script type="text/javascript">
| + | <h1>NeoChromosome</h1> |
| - | $(document).ready(function() {
| + | <a href="https://static.igem.org/mediawiki/2013/9/9e/Tutorial-Neochr.pdf" target="_self"><h4>Download</h4></a> |
| - | // document.getElementById("p-logo").style.display= "none";
| + | </div> |
| - | document.getElementsByClassName("right-menu noprint")[0].style.display= "none";
| + | |
| - | //document.getElementById("searchform").style.display= "none"; | + | |
| | | | |
| - | });
| + | <div class="one-third column"> |
| - | </script>
| + | |
| | + | <a href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/Tutorial/nucleomod" target="_blank"> |
| | + | <img src="https://static.igem.org/mediawiki/2013/e/e7/Nucleomod_icon-purple.png" /> |
| | + | </a> |
| | + | |
| | + | <h1>NucleoModifier</h1> |
| | + | |
| | + | <a href="https://static.igem.org/mediawiki/2013/9/96/Tutorial-NucleoMod.pdf" target="_self"><h4>Download</h4></a> |
| | + | </div> |
| | | | |
| - | <link rel="stylesheet" href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/css?action=raw&ctype=text/css" type="text/css" />
| |
| - | <link rel="stylesheet" href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/style?action=raw&ctype=text/css" type="text/css" />
| |
| - | <script src="http://code.jquery.com/jquery-1.7.2.min.js"></script>
| |
| | | | |
| - | <!--[if lte IE 8]><link rel="stylesheet" href="http://www.humaan.com.au/wp-content/themes/humaan/css/iestyle.css"><![endif]--> | + | <div class="one-third column"> |
| - | <!--[if IE 9]><link rel="stylesheet" href="http://www.humaan.com.au/wp-content/themes/humaan/css/ie9.css"><![endif]--> | + | |
| - | <script type="text/javascript" src="https://2013.igem.org/Team:Shenzhen_BGIC_0101/easying?action=raw&ctype=text/javascript"></script> | + | <a href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/Tutorial/segmman" target="_blank"> |
| - | <script type="text/javascript" src="//use.typekit.net/jlr8wlp.js"></script> | + | <img src="https://static.igem.org/mediawiki/2013/9/9e/Segman_icon-purple.png" /> |
| - | <script type="text/javascript">try{Typekit.load();}catch(e){}</script> | + | </a> |
| | + | |
| | + | <h1>Segmentation</h1> |
| | + | |
| | + | <a href="https://static.igem.org/mediawiki/2013/a/a8/Tutorial-Segmentation.pdf" target="_self"><h4>Download</h4></a> |
| | + | <br/><br/><br/> |
| | + | </div> |
| | | | |
| - | <style>
| + | </section> |
| - | #tabs {
| + | |
| - | overflow: hidden;
| + | |
| - | width: 70%;
| + | |
| - | margin: 0;
| + | |
| - | margin-left: 25%;
| + | |
| - | padding: 0;
| + | |
| - | list-style: none;
| + | |
| - | font-size: 1.3em;
| + | |
| | | | |
| - | font-weight: 800;
| |
| - | }
| |
| | | | |
| - | #tabs li {
| + | <section class="container"> |
| - | float: left;
| + | <div class="one-third column"> |
| - | margin: 0 -15px 0 0;
| + | |
| - | }
| + | <a href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/Tutorial/olsdesigner" target="_blank"> |
| | + | <img src="https://static.igem.org/mediawiki/2013/e/ee/Olsdesigner.png" /> |
| | + | </a> |
| | | | |
| - | #tabs a {
| + | <h1>OLS Designer</h1> |
| - | float: left;
| + | |
| - | position: relative;
| + | <a href="https://static.igem.org/mediawiki/2013/2/26/Tutorial-OLSDesigner.pdf" target="_self"><h4>Download</h4></a> |
| - | padding: 0 40px;
| + | </div> |
| - | height: 0;
| + | |
| - | line-height: 30px;
| + | |
| - |
| + | |
| - | text-decoration: none;
| + | |
| - | color: #38f;
| + | |
| - | border-right: 30px solid transparent;
| + | |
| - | border-bottom: 30px solid rgba(54, 49, 49, 0.71);
| + | |
| - | border-bottom-color: #777\9;
| + | |
| - | // opacity: .3;
| + | |
| - | filter: alpha(opacity=30);
| + | |
| - | }
| + | |
| | | | |
| - | #tabs a:hover,
| + | <div class="one-third column"> |
| - | #tabs a:focus {
| + | |
| - | border-bottom-color: #2ac7e1;
| + | <a href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/Tutorial/kgml" target="_blank"> |
| - | opacity: 1;
| + | <img src="https://static.igem.org/mediawiki/2013/0/02/Otherspuple.png" /> |
| - | filter: alpha(opacity=100);
| + | </a> |
| - | }
| + | |
| | + | <h1>Kgml2Jason</h1> |
| | + | |
| | + | <a href="https://static.igem.org/mediawiki/2013/f/fa/Turorial-Kgml2Jason.pdf" target="_self"><h4>Download</h4></a> |
| | + | </div> |
| | | | |
| - | #tabs a:focus {
| + | <div class="one-third column"> |
| - | outline: 0;
| + | |
| - | }
| + | <a href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/Tutorial/videoturorial" target="_blank"> |
| - | | + | <img src="https://static.igem.org/mediawiki/2013/c/c1/Vedior.png" /> |
| - | #tabs #current {
| + | </a> |
| - | z-index: 3;
| + | |
| - | border-bottom-color: #3d3d3d;
| + | <h1>Video Tutorial</h1> |
| - | opacity: 1;
| + | |
| - | filter: alpha(opacity=100);
| + | |
| - | }
| + | |
| - | #tab1,#tab2,#tab3,#tab4{
| + | |
| - | font-size: 16px;
| + | |
| - | line-height: 19px;
| + | |
| - | font-family: Trebuchet MS;
| + | |
| - | font-weight: 600;
| + | |
| - | color: #ccc;
| + | |
| - | }
| + | |
| - | /* ----------- */
| + | |
| - | #content2 {
| + | |
| - | background: rgba(29, 28, 28, 0.79);
| + | |
| - | border-top: 2px solid #3d3d3d;
| + | |
| - | padding: 2em;
| + | |
| - | width :55%;
| + | |
| - | margin-left: 25%;
| + | |
| - |
| + | |
| - | }
| + | |
| - | | + | |
| - | #content2 h2,
| + | |
| - | #content h3,
| + | |
| - | #content p {
| + | |
| - | margin: 0 0 15px 0;
| + | |
| - | | + | |
| - | }
| + | |
| - | | + | |
| - | </style> | + | |
| - |
| + | |
| - | <script type="text/javascript">
| + | |
| - | function FloatMenu(){
| + | |
| - | var animationSpeed=1500;
| + | |
| - | var animationEasing='easeOutQuint';
| + | |
| - | var scrollAmount=$(document).scrollTop();
| + | |
| - | var newPosition=menuPosition+scrollAmount;
| + | |
| - | if($(window).height()<$('#fl_menu').height()+$('#fl_menu .menu').height()){
| + | |
| - | $('#fl_menu').css('top',menuPosition);
| + | |
| - | } else {
| + | |
| - | $('#fl_menu').stop().animate({top: newPosition}, animationSpeed, animationEasing);
| + | |
| - | }
| + | |
| - | }
| + | |
| - | $(window).load(function(){
| + | |
| - | menuPosition=$('#fl_menu').position().top;
| + | |
| - | FloatMenu();
| + | |
| - | });
| + | |
| - | $(window).scroll(function(){
| + | |
| - | FloatMenu();
| + | |
| - | });
| + | |
| - | $(document).ready(function(){
| + | |
| - | var fadeSpeed=500;
| + | |
| - | $("#fl_menu").hover(function(){
| + | |
| - | $('#fl_menu .label').fadeTo(fadeSpeed, 1);
| + | |
| - | $("#fl_menu .menu").fadeIn(fadeSpeed);
| + | |
| - | },function(){
| + | |
| - | $('#fl_menu .label').fadeTo(fadeSpeed, 0.75);
| + | |
| - | $("#fl_menu .menu").fadeOut(fadeSpeed);
| + | |
| - | });
| + | |
| - | });
| + | |
| - | </script>
| + | |
| - | <style>
| + | |
| - | td,th{
| + | |
| - | border-style: solid; border-width: 1px;
| + | |
| - | }
| + | |
| - | .tit{
| + | |
| - | color: #6AA33D;
| + | |
| - | }
| + | |
| - | .container{
| + | |
| - | width:65%;
| + | |
| - | left: 5%;
| + | |
| - | }
| + | |
| - | /* fl_menu */
| + | |
| - | #fl_menu{position:absolute;top:150px;left:-2px;z-index:9999;
| + | |
| - | width:200px;
| + | |
| - | height:50px;
| + | |
| - | }
| + | |
| - | #fl_menu .label{line-height:50px;font-size:18px;font-weight:bold;background: #1B1B1B;color:#fff;letter-spacing:5px;text-align: center;box-shadow: 2px 1px 6px #272727;border-radius: 2px;opacity: 0.75;}
| + | |
| - | #fl_menu .label a{color:#83f;text-decoration: none;}
| + | |
| - | #fl_menu .label a:hover{color:#38f;}
| + | |
| - | | + | |
| - | </style>
| + | |
| - | <!--[if lt IE 9]><script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
| + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | <style type="text/css">.recentcomments a{display:inline !important;padding:0 !important;margin:0 !important;}</style>
| + | |
| - | | + | |
| - | </head>
| + | |
| - | <body class="blog developer-wanted">
| + | |
| - | <div id="fl_menu">
| + | |
| - | <div class="label"><a href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/Software">Overview</a></div> | + | |
| - | <div class="label"><a href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/ Modules">Modules</ a></div> | + | |
| - | <div class="label"><a href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/Next_version">Next version</a></div>
| + | |
| - | <div class="label"><a href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/Compatibility">Compatibility</a></div> | + | |
| - | <div class="label"><a href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/NewStandard">New Standard</a></div>
| + | |
| - | <div class="label"><a href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/Tutorial#">Tutorial</a></div>
| + | |
| - | <div class="label"><a href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/Web-based_trial">Web-based trial</a></div>
| + | |
| - | | + | |
| - | <div class="label"><a href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/Software_Assessment">Assessment</a></div>
| + | |
| - | <div class="label"><a href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/Downloadsl">Downloads</a></div>
| + | |
| - | | + | |
| - | | + | |
| - | </div>
| + | |
| - | <div id="wrap" style="background:url(https://static.igem.org/mediawiki/igem.org/f/fb/Backgd.jpg);">
| + | |
| - | <header class="light">
| + | |
| - | <a href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/Home" id="logo">logo</a> | + | |
| | | | |
| - | <nav class="menu-main-navigation-container"><a href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/Home" class="menu-item-20 menu-item menu-item-type-post_type menu-item-object-page">Home</a> <a href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/Team" class="menu-item-19 menu-item menu-item-type-post_type menu-item-object-page">Team</a> <a href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/Software" class="menu-item-18 menu-item menu-item-type-post_type menu-item-object-page current-menu-item">Software</a> <a href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/Requirements" class="menu-item-17 menu-item menu-item-type-post_type menu-item-object-page">Requirements</a> <a href="https://2013.igem.org/Team:Shenzhen_BGIC_0101/Criteria" class="menu-item-15 menu-item menu-item-type-post_type menu-item-object-page">Criteria</a> </nav>
| |
| - | <a href="https://2013.igem.org/Main_Page" id="logo1">logo</a>
| |
| - | </header>
| |
| - |
| |
| - |
| |
| - | <div id="page-header" style="background: url(https://static.igem.org/mediawiki/igem.org/b/b0/Za.jpg);height: 300px;box-shadow: 4px 3px 25px #000;">
| |
| - | <h1></h1>
| |
| - | </div>
| |
| - | <br/>
| |
| - | <h2 style="font-family: 'Tangerine', serif;font-size: 48px; text-shadow: 4px 4px 4px #aaa; color: #38f;
| |
| - | letter-spacing: 0.1em;
| |
| - | word-spacing: 0.3em;
| |
| - | font-weight: 700;
| |
| - | width: 30%;
| |
| - | line-height: 36px;
| |
| - | margin: 0;
| |
| - | margin-left: 20%;">Tutorial</h2><br/>
| |
| - | <ul id="tabs">
| |
| - | <li><a href="#" name="#tab1">Neochr</a></li>
| |
| - | <li><a href="#" name="#tab2">NucleoMod</a></li>
| |
| - | <li><a href="#" name="#tab3">SegmMan</a></li>
| |
| - | <li><a href="#" name="#tab4">Others</a></li>
| |
| - | </ul>
| |
| - | <div id="content2">
| |
| - | <div id="tab1">
| |
| - | <p class="tit">1. NeoChr </p>
| |
| - | <p>
| |
| - | NeoChr module would assist users to grab related genes in different pathways manually, to rewire genes’ relationship logically*, and to replace genes with ortholog that score higher*. Firstly, it would allow users to define gene order and orientation in DRAG&DROP way. Secondly, decoupled these genes if have overlap and make all genes are non-redundancy. Finally, add chromosome features to build a new chromosome and show in the JBrowse. Moreover, users can drag a window in the JBrowse and delete any gene in the window.<br/>
| |
| - | Note: <br/>
| |
| - | *These function are unavailable now, please wait for version 2.<br/>
| |
| - | **You can also add any thing here including your own water mark.<br/></p>
| |
| - | <p class="tit">2. Plugin Scripts </p>
| |
| - | <p>This module contains three plugins: Decouple.pl, Add.pl and Delete.pl.</p>
| |
| - | <p class="tit">2.1 Decouple.pl</p>
| |
| - | <p>This plugin is to decouple the genes which have overlap gene regions. These overlapping genes can be decoupled if meet the following conditions: (1)If two genes have overlap gene regions, the latter gene 5’UTR does not cover the former gene initial codon (ATG); (2)Overlapping region initial coordinate is in the coding DNA sequences(CDS) of gene which is need to be decoupled; (3)The decouple site of CDS have synonymous substitute codon to replace; After decoupling, we use these non-redundancy genes to generate a GFF file and a FASTA file.</p>
| |
| - | <p class="tit">2.1.1 Internal operation </p>
| |
| - | <p>First, this plugin extracts base sequence from the genome file according to the gene order list, and records the gene order in the list. And then plugin records the annotation information according to the specie GFF file, moreover, plugin extends gene CDS upstream 600bp as 5’-UTR and downstream 100bp as 3’-UTR if the GFF file does not contain annotated these two features.<br/>
| |
| - | Second, this plugin detects the overlapping genes in the same chromosome. In case the overlapping genes are detected, it will judge whether the overlapping initial site is located in the CDS region, and identify the site is belong to phase0/1/2.<br/>
| |
| - | Third, the plugin attempts to synonymous substitute codon to break the initial codon intra the CDS. Printing information whether or not be decoupled successfully, such as:<br/>
| |
| - | <img src="https://static.igem.org/mediawiki/2013/e/e0/T1-1.png" alt="data" style="width: 750px" /><br/>
| |
| - | And non-redundancy genes are generated.<br/>
| |
| - | Finally, the plugin links non-redundancy genes to construct a new chromosome according to the gene order.
| |
| - | </p>
| |
| - | <p class="tit">2.2.1 Example</p>
| |
| - | <p>We have two input forms to execute the plugin:<br/>
| |
| - | 1. Using string format as gene order list input form:<br/>
| |
| - | perl GeneDecouple.pl --species saccharomyces_cerevisiae_chr --list_format string --gene_order="YAL054C -,YAL038W +,YBR019C -,YBR145W +,YCL040W +,YCR012W +,YCR105W +,YDL168W +,YPL017C -,YIL177C -,YIL177W-A +,YIL172C -,YIL171W-A +,” --geneset_dir ../gene_set --upstream_extend 600 --downstream_extend 100 --neo_chr_gff neochr.gff --neo_chr_fa neochr.fa<br/>
| |
| - | 2. Using file format as gene order list input form:<br/>
| |
| - | erl GeneDecouple.pl --species saccharomyces_cerevisiae_chr --list_format file --gene_order gene_ordre.list --geneset_dir ../gene_set --upstream_extend 600 --downstream_extend 100 --neo_chr_gff neochr.gff --neo_chr_fa neochr.fa
| |
| - | </p>
| |
| - | <p class="tit">2.1.3 Parameters </p>
| |
| - | <table border="1">
| |
| - | <tr>
| |
| - | <th>Parameter</th>
| |
| - | <th>Description</th>
| |
| - | <th></th>
| |
| - | <th></th>
| |
| - | </tr>
| |
| - | <tr>
| |
| - | <th>list_format</th>
| |
| - | <th>set the input form of gene order list</th>
| |
| - | <th>string</th>
| |
| - | <th>string/file</th>
| |
| - | </tr>
| |
| - | <tr>
| |
| - | <th>gene_order</th>
| |
| - | <th>set the input gene order list file(include pathway genes and addition genes)</th>
| |
| - | <th></th>
| |
| - | <th></th>
| |
| - | </tr>
| |
| - | <tr>
| |
| - | <th>Parameter</th>
| |
| - | <th>Description</th>
| |
| - | <th>Default</th>
| |
| - | <th>Selectable range</th>
| |
| - | </tr>
| |
| - | <tr>
| |
| - | <th>geneset_dir</th>
| |
| - | <th>set the species annotation directory</th>
| |
| - | <th>600</th>
| |
| - | <th></th>
| |
| - | </tr>
| |
| - | <tr>
| |
| - | <th>upstream_extend</th>
| |
| - | <th>set the length of gene downstram(bp)</th>
| |
| - | <th>100</th>
| |
| - | <th></th>
| |
| - | </tr>
| |
| - | <tr>
| |
| - | <th>neo_chr_gff</th>
| |
| - | <th>set the name of output neochr gff file</th>
| |
| - | <th></th>
| |
| - | <th></th>
| |
| - | </tr>
| |
| - | <tr>
| |
| - | <th>neo_chr_fa</th>
| |
| - | <th>set the name of output neochr fasta file</th>
| |
| - | <th></th>
| |
| - | <th></th>
| |
| - | </tr>
| |
| - | <tr>
| |
| - | <th>help</th>
| |
| - | <th>Show help information</th>
| |
| - | <th></th>
| |
| - | <th></th>
| |
| - | </tr>
| |
| - | </table>
| |
| - | </p><br/>
| |
| - | <p class="tit">2.4.1 The format of output file</p>
| |
| - | <p>The output files are standard GFF and FASTA format files which are decoupled.<br/>
| |
| - | 1. decoupled GFF file<br/>
| |
| - | <img src="https://static.igem.org/mediawiki/2013/e/e5/T1-2.png" alt="data" style="width: 750px" /><br/>
| |
| - | 2.decoupled FASTA file<br/>
| |
| - | <img src="https://static.igem.org/mediawiki/2013/b/b2/T1-3.png" alt="data" style="width: 750px" /><br/>
| |
| - |
| |
| - | <p class="tit">2.2 Add.pl </p>
| |
| - | <p>This plugin will add the LoxPsym sequence and the customized left and right telomeres, centromere and autonomously replicating sequence (ARS) into the FASTA file and GFF file which are generated by Decouple.pl.</p>
| |
| - | <p class="tit">2.2.1 Internal operation </p>
| |
| - | <p>The plugin adds LoxPsym behind the first 3bp of 3’-UTR in each gene and adds telomere, centromere and ARS according this mode:<br/>
| |
| - | <b>left_telomere + gene1 + centromere + gene2 + ARS + gene3 + right_telomere</b><br/>
| |
| - | The distance between centromere and ARS is less than 30Kb.<br/>
| |
| - | Finally, user can see the new added features chromosome according to the JBrowse.
| |
| - | </p>
| |
| - | <p class="tit">2.2.2 Example </p>
| |
| - | <p>perl 04.Add.pl --loxp loxPsym.feat --left_telomere UTC_left.feat --right_telomere UTC_right.feat --ars chromosome_I_ARS108.feature --centromere chromosome_I_centromere.feat --chr_gff neochr.gff --chr_seq neochr.fa --neochr_seq neochr.final.fa --neochr_gff neochr.final.gff<br/><br/>
| |
| - | All the feature file format is 4 lines format, for example:<br/>
| |
| - | name = site_specific_recombination_target_region<br/>
| |
| - | type = loxPsym<br/>
| |
| - | source = BIO<br/>
| |
| - | sequence = ATAACTTCGTATAATGTACATTATACGAAGTTAT<br/>
| |
| - | Note: the first line is the detail name of feature, the second line is the type of feature, the third line is the source of feature and the last line is the sequence of feature.
| |
| - | </p>
| |
| - | <p class="tit">2.2.3 Parameters</p>
| |
| - | <pre>
| |
| - | Parameter Description Default Selectable range
| |
| - | loxp set the sequence of loxp ATAACTTCGTATAATGTATGCTATACGAAGTTAT
| |
| - | left_telomere set the sequence of left telomere
| |
| - | right_telomere set the sequence of right telomere
| |
| - | chr_gff set the input neorchr_gff file
| |
| - | chr_seq set the input neorchr_gff file
| |
| - | neochr_seq set the name of output added loxps and telomeres neochr_fa file
| |
| - | neochr_gff set the name of output added loxps and telomeres neochr_gff file
| |
| - | </pre>
| |
| - |
| |
| - | <p class="tit">2.2.4 The format of output</p>
| |
| - | <p>The output files are standard GFF and FASTA format of adding features chromosome.<br/>
| |
| - | 1. added features GFF file<br/>
| |
| - | <img src="https://static.igem.org/mediawiki/2013/e/e0/T1-4.png" alt="data" style="width: 750px" ></a>
| |
| - | </p>
| |
| - |
| |
| - | <p class="tit">2.3 Delete.pl </p>
| |
| - | <p>This plugin can modify the GFF and FASTA file which are generated by Add.pl according to the user drags a window in the JBrowse and delete any gene in the window.</p>
| |
| - | <p class="tit">2.3.1 Internal operation </p>
| |
| - | <p>Firstly, user uses mouse to drag a window in the added features FASTA file which is showed in the JBrowse and JBrowse displays all the genes in this window.Secondly, user decides which genes is need to be delected from the new chromosome and plugin deletes genes from GFF file and modify FASTA in the same time.</p>
| |
| - | <p class="tit">2.3.2 Example </p>
| |
| - | <p>perl 05.delete.pl --delete="YAL054C,YAL038W" --neochr_gff neochr.refine.final.gff --neochr_fa neochr.refine.final.fa --slim_gff neochr.refine.delete.gff --slim_fa neochr.refine.delete.fa </p>
| |
| - | <p class="tit">2.3.3 Parameters </p>
| |
| - | <p><pre>
| |
| - | Parameter Description Default Selectable range
| |
| - | delete Set the to be deleted gene list
| |
| - | neochr_gff Set the input GFF file which is generated by Add.pl
| |
| - | neochr_fa Set the input FASTA file which is generated by Add.pl
| |
| - | slim_gff Set the output GFF file
| |
| - | slim_fa Set the output FASTA file </pre></p>
| |
| - |
| |
| - | <p class="tit">2.3.4 The format of ouput</p>
| |
| - | <p>The output files are standard GFF and FASTA format of deleted genes chromosome.</p>
| |
| - |
| |
| - | </div>
| |
| - | <div id="tab2">
| |
| - | <p class="tit">1. NucleoMod </p>
| |
| - | <p>NucleoMod can modify CDS based on synoymous mutation. It has 5 applications. Firstly, NucleoMod is used to design CRISPR sites on NeoChr so that we can silence the wild type genes. Secondly, it can erase specific enzyme sites according to the users' selection. Thirdly, users can create an enzyme site in selected region of specific genes. Fourthly, it can optimize the codon efficiency to increase the expression level. Finally, it can smash the tandem repeat bases to reduce the synthesis difficulty.</p>
| |
| - | <p class="tit">2. Plugins</p>
| |
| - | <p>This module contains 5 plugins: CRISPR design, erase enzyme site, create enzyme site, codon optimization, repeat smash. All plugins are included in the main program.</p>
| |
| - | <p class="tit">2.1 CRISPR design</p>
| |
| - | <p>This plugin is used to design CRISPR site of NeoChr genes so that we can silence the wild type genes. We use blast+ to ensure the uniqueness of CRISPR sites. If you are using more than one plugin at the same time, this plugin will start firstly and deliver the data to next plugin. Otherwise it will generate a new fasta file for sequence and gff file for annotation.</p>
| |
| - | <p class="tit">2.1.1 Internal operation</p>
| |
| - | <p>First, this plugin extracts sequence and annotation from the NeoChr FASTA file and GFF3 file, respectively. Regular expression will be applied to find the 23bp basic structure of CRISPR site, with a head of ‘G’ then following 20 facultative bases and finally followed by ‘GG’. All the sequences and locus will be record in an array. <br/>
| |
| - | Second, the blast+ will be used to check whether the 12bp sequences (from 9th to 20th) are uniq in the wild type genome. Only uniq sites will be reserved. <br/>
| |
| - | Third, synonymous substitution method will be applied to change one base between the 9th to 20th bases of the CRISPR structure. The result will be record in GFF as an element of gene. If –verbose is set, the designed number will be report in STDOUT.<br/>
| |
| - | Finally, if this plugin is the last module, the sequence and annotation information will be recreated in FASTA and GFF format.</p>
| |
| - | <p class="tit">2.1.2 Example</p>
| |
| - | <p>We have two input forms to execute the plugin:<br/>
| |
| - | Run CRISPR design plugin only:<br/>
| |
| - | perl NucleoMod.pl -inputfa NeoChr.fa -inputgff NeoChr.gff -outputgff new_annotation.gff -outputfa new_chr.fa -crisprnum 2 -database saccharomyces_cerevisiae_chr.fa</p>
| |
| - | <p class="tit">2.1.3 Parameters</p>
| |
| - | <table>
| |
| - | <tr><td>Parameter</td><td>Description</td><td>Default</td><td>Selectable range</td></tr>
| |
| - | <tr><td>inputfa</td><td>The NeoChr sequence file in FASTA format</td><td></td><td>string</td></tr>
| |
| - | <tr><td>inputgff</td><td>The NeoChr annotation file in GFF3 format</td><td></td><td>string</td></tr>
| |
| - | <tr><td>outputgff</td><td>Output of new chromosome annotation in GFF3 format</td><td></td><td>string</td></tr>
| |
| - | <tr><td>outputfa</td><td>Output of new chromosome sequence in FASTA format</td><td></td><td>string</td></tr>
| |
| - | <tr><td>verbose</td><td>Output the detailed information in STDOUT</td><td>none</td><td>option</td></tr>
| |
| - | <tr><td>crisprnum</td><td>Number of CRISPR site to be design per gene</td><td></td><td>Int (>0)</td></tr>
| |
| - | <tr><td>database</td><td>The sequence of reference genome, used as blast+ database</td><td></td><td>string</td></tr>
| |
| - | <tr><td>help</td><td>Show help information</td><td></td><td></td></tr>
| |
| - | </table>
| |
| - | <p class="tit">2.1.4 The format of output file</p>
| |
| - | <p>The output files are standard GFF and FASTA format files.<br/>
| |
| - | 1. GFF file<br/>
| |
| - | <img src="" /><br/>
| |
| - | 2. FASTA file<br/>
| |
| - | <img src="" /><br/>
| |
| - | 3. Detailed information in STDOUT<br/>
| |
| - | <img src="" />
| |
| - | </p>
| |
| - | <p class="tit">2.2 Erase enzyme site</p>
| |
| - | <p>Given a list of restriction enzyme information, this plugin will erase the restriction sites in every gene. If you are using more than one plugin at the same time, this plugin will start after CRISPR design and deliver the data to next plugin. Otherwise it will generate a new fasta file for sequence and gff file for annotation.</p>
| |
| - | <p class="tit">2.2.1 Internal operation</p>
| |
| - | <p>The enzyme information will be extracted. (If the –borbrickstandard parameter is set, it will also remove EcoRI, XbaI, SpeI, PstI and NotI) The recognize site will be reformatted to regular expression and searched in the CDS regions.
| |
| - | Once a restriction site is matched, synonymous substitution method will be applied to try to erase the enzyme site. When the substitution is finished, the plugin will restart the next search from 1 base after the last matched position.
| |
| - | If this plugin is the last module, the sequence and annotation information will be recreated in FASTA and GFF format.</p>
| |
| - | <p class="tit">2.2.2 Example</p>
| |
| - | <p>perl NucleoMod.pl -inputfa NeoChr.fa -inputgff NeoChr.gff -outputgff new_annotation.gff -outputfa new_chr.fa –biobrickstandard [-delenzymelist enzyme.list ]<br/>
| |
| - | <br/>
| |
| - | Format of enzyme.list:<br/>
| |
| - | Company enzyme_name enzyme_site …<br/>
| |
| - | Eg. NEB BamHI G/GATCC</p>
| |
| - | <p class="tit">2.2.3 Parameters</p>
| |
| - | <table>
| |
| - | <tr><td>Parameter</td><td>Description</td><td>Default</td><td>Selectable range</td></tr>
| |
| - | <tr><td>inputfa</td><td>The NeoChr sequence file in FASTA format</td><td></td><td>string</td></tr>
| |
| - | <tr><td>inputgff</td><td>The NeoChr annotation file in GFF3 format</td><td></td><td>string</td></tr>
| |
| - | <tr><td>outputgff</td><td>Output of new chromosome annotation in GFF3 format</td><td></td><td>string</td></tr>
| |
| - | <tr><td>outputfa</td><td>Output of new chromosome sequence in FASTA format</td><td></td><td>string</td></tr>
| |
| - | <tr><td>verbose</td><td>Output the detailed information in STDOUT</td><td>none</td><td>option</td></tr>
| |
| - | <tr><td>biobrickstandard</td><td>Erase the biobrick standard enzyme site</td><td>none</td><td>option</td></tr>
| |
| - | <tr><td>delenzymelist</td><td>The file of enzyme going to delete</td><td></td><td>string</td></tr>
| |
| - | <tr><td>detail</td><td>Show the erased enzyme site in new gff</td><td>none</td><td>option</td></tr>
| |
| - | <tr><td>help</td><td>Show help information</td><td></td><td></td></tr>
| |
| - |
| |
| - | </table>
| |
| - | <p class="tit">2.2.4 The format of output</p>
| |
| - | <p>The output files are standard GFF and FASTA format.<br/>
| |
| - | 1. GFF file<br/>
| |
| - | <img src="" /><br/>
| |
| - | 2. FASTA file<br/>
| |
| - | <img src="" /><br/>
| |
| - | 3. Detailed information in STDOUT<br/>
| |
| - | <img src="" /><br/>
| |
| - | </p>
| |
| - | <p class="tit">2.3 Create enzyme site</p>
| |
| - | <p>Given a list of restriction enzyme information, this plugin can create a new enzyme site in specific region of selected gene. If you are using more than one plugin at the same time, this plugin will start after erase enzyme site and deliver the data to next plugin. Otherwise it will generate a new fasta file for sequence and gff file for annotation.</p>
| |
| - | <p class="tit">2.3.1 Internal operation</p>
| |
| - | <p>First, information of enzyme site will be extracted. According to 3 reading frames, a searching tree will be constructed and converted to regular expression.
| |
| - | The plugin will search the selected regions and then change the sequence to enzyme site by synonymous substitution method.
| |
| - | If this plugin is the last module, the sequence and annotation information will be recreated in FASTA and GFF format.</p>
| |
| - | <p class="tit">2.3.2 Example</p>
| |
| - | <p>perl NucleoMod.pl -inputfa NeoChr.fa -inputgff NeoChr.gff -outputgff new_annotation.gff -outputfa new_chr.fa -addenzymelist enzyme.list -addenzymeconfig gene_id,start_pos,end_pos,enzyme_name</p>
| |
| - | <p class="tit"></p>
| |
| - | <p></p>
| |
| - | <p class="tit"></p>
| |
| - | <p></p>
| |
| - | <p class="tit"></p>
| |
| - | <p></p>
| |
| - | <p class="tit"></p>
| |
| - | <p></p>
| |
| - | <p class="tit"></p>
| |
| - | <p></p>
| |
| - | <p class="tit"></p>
| |
| - | <p></p>
| |
| - | <p class="tit"></p>
| |
| - | <p></p>
| |
| - | <p class="tit"></p>
| |
| - | <p></p>
| |
| - | <p class="tit"></p>
| |
| - | <p></p>
| |
| - | </div>
| |
| - | <div id="tab3">
| |
| - | <p class="tit">3. SegmMan </p>
| |
| - | <p>This module will cut chromosome into pieces with different sizes with Gibson, Goldengate, Homologous adaptors to them so that they are able to be assembled into whole experimentally.</p>
| |
| - | <p class="tit">Plugin Scripts</p>
| |
| - | <br/>
| |
| - | <p class="tit">3-1. 01.whole2mega.pl</p>
| |
| - | <p>This utility can split the whole chromosome ( at least 90kbp long ) into about 30k segments and add homologous overlap and adaptors, so that these fragments can be integrated into whole experimentally.</p>
| |
| - | <p class="tit">Internal operation</p>
| |
| - | <p>First, this utility searches for the location of centromere and ARSs (autonomously replicating site). The minimal distance between centromere and ARS should NOT be larger than a defined megachunk which is about 30k long. <br/>
| |
| - | Second, this utility cuts out the first 30k sequence window containing the centromere and its adjacent ARS, and then adds this megachunk with two original markers and left, right telomeres.<br/>
| |
| - | Thirdly, this utility continues to cut more megachunks from the original one to both ends. But these megachunks are not independent, they all have about 1kbp overlaps. Moreover, these new splited window can be given only one marker alternately and only left or right telomere.<br/>
| |
| - | The output file will be dealed with 02.globalREmarkup.pl<br/>
| |
| - | For more information about segmentation design, please refer to the page ASSEMBLY DESIGN PRINCIPLE .</p>
| |
| - | <p class="tit">Example (command line)</p>
| |
| - | <p>perl 01.whole2mega.pl –gff sce_chrI.gff -fa sce_chr01.fa -ol 1000 -ck 30000 -m1 LEU2 -m2 URA3 -m3 HIS3 -m4 TRP1 -ot sce_chrI.mega</p>
| |
| - | <p class="tit">Parameters</p>
| |
| - | <table><tbody>
| |
| - | <tr><td></td><td></td><td>default</td><td>Option</td></tr>
| |
| - | <tr><td>gff</td><td>The gff file of the chromosome being restriction enzyme sites parsing</td><td></td><td></td></tr>
| |
| - | <tr><td>fa</td><td>The fasta file of the chromosome being restriction enzyme sites parsing
| |
| - | (The length of the chromosome is larger than 90k)</td><td></td><td></td></tr>
| |
| - | <tr><td>ol</td><td>The length of overlap between megachunks</td><td>1000bp</td><td></td></tr>
| |
| - | <tr><td>ck</td><td>The length of megachunks</td><td>30kbp</td><td></td></tr>
| |
| - | <tr><td>m1</td><td>The first marker for selection alternately</td><td>LEU2 (1797bp)</td><td>LEU2/URA3HIS3/TRP1</td></tr>
| |
| - | <tr><td>m2</td><td>The second marker for selection alternately
| |
| - | </td><td>URA3 (1112bp)</td><td>LEU2/URA3/HIS3/TRP1</td></tr>
| |
| - | <tr><td>m3</td><td>The first marker orinally residing in first 30k segmentation</td><td>HIS3 (1774bp)</td><td>LEU2/URA3/HIS3/TRP1</td></tr>
| |
| - | <tr><td>m4</td><td>The second marker orinally residing in first 30k segmentation</td><td>TRP1 (1467bp)</td><td>LEU2/URA3/HIS3/TRP1</td></tr>
| |
| - | <tr><td>ot</td><td>The output file </td><td>Prefix(fa filename)+ suffix(.mega)</td><td></td></tr>
| |
| - | </tbody></table>
| |
| - |
| |
| - | <p class="tit">The format of output:</p>
| |
| - | <p>The output file is stored in /the path where you install GENOVO/Result/ 01.whole2mega.<br/>
| |
| - | Besides, there is screen output about the process state and result.<br/>
| |
| - | 1. Screen output<br/>
| |
| - | 2. 01.state <br/>
| |
| - | Store the segmentation information<br/>
| |
| - | <table><tbody>
| |
| - | <tr><td>Megachunk_ID</td><td>Corresponding location in the designed chromosome</td></tr>
| |
| - | <tr><td>Part ID</td><td>Location in the segmentation</td></tr>
| |
| - | </tbody></table>
| |
| - | <img src="https://static.igem.org/mediawiki/2013/c/c1/T3-1.png" /><br/>
| |
| - | 3 *.mega<br/>
| |
| - | Store the fasta information of the 30k segments<br/>
| |
| - | <img src="https://static.igem.org/mediawiki/2013/f/f0/T3-2.png" />
| |
| - | </p>
| |
| - | <p class="tit">3-2. 02.globalREmarkup.pl</p>
| |
| - | <p>This utility will parse the exited restriction enzyme sites residing in the chromosome.</p>
| |
| - | <p class="tit">Internal operation</p>
| |
| - | <p>This utility searches the exited restriction enzyme sites along the chromosome both plus strand and minus strand, after users define the list of enzymes.<br/>
| |
| - | Besides, we tried to find out all the potential restriction enzyme sites, so that maybe some unusual restriction enzyme sites can be created and let segmentation go. But because it had low efficiency, we’re still working on that.<br/>
| |
| - | The output file will be dealed with 03.mega2chunk2mini.pl<br/>
| |
| - | For more information about segmentation design, please refer to the page ASSEMBLY DESIGN PRINCIPLE .
| |
| - | </p>
| |
| - | <p class="tit">Example (command line)</p>
| |
| - | <p>perl 02.globalREmarkup.pl -sg 01.whole2mega/sce_chrI.mega -re standard_and_IIB -ct Standard.ct –ot sce_chrI.mega.parse</p>
| |
| - | <p class="tit">Parameters</p>
| |
| - | <p>
| |
| - | <table><tbody>
| |
| - | <tr><td></td><td></td><td>default</td><td>Option</td></tr>
| |
| - | <tr><td>sg</td><td>The fasta file of the 30k segmentation, the output of 01.wh2mega.pl</td><td></td><td></td></tr>
| |
| - | <tr><td>ps</td><td>The markup file of the 30k segmentation, the output of 02.globalREmarkup.pl</td><td></td><td></td></tr>
| |
| - | <tr><td>re</td><td>The restriction enzyme sites list. It is devided by different standards, type (IIP, IIA, IIB), cost (standard, nonexpensive) and etc.</td><td>Standard_and_IIB</td><td>IIP/IIA/IIB/Standard/
| |
| - | Nonexpensive/
| |
| - | Standard_IIB
| |
| - | Nonexpensive_IIB</td></tr>
| |
| - | <tr><td>a2</td><td>2k to 10k assembly strategy (Gibson or Goldengate)</td><td>Gibson</td><td>Gibson/ Goldengate</td></tr>
| |
| - | <tr><td>a10</td><td>10k to 30k assembly strategy (Gibson or Goldengate)</td><td>Goldengate</td><td>Gibson/ Goldengate</td></tr>
| |
| - | <tr><td>ckmax2</td><td>The maximum length of minichunks</td><td>2200 bp</td><td></td></tr>
| |
| - | <tr><td>ckmin2</td><td>The minimum length of minichunks </td><td>1800 bp</td><td></td></tr>
| |
| - | <tr><td>cknum</td><td>The number of minichunks in a chunk</td><td>5</td><td></td></tr>
| |
| - |
| |
| - | </tbody></table>
| |
| - | Codon table list:<br/>
| |
| - | 1 The Standard Code<br/>
| |
| - | 2 The Vertebrate Mitochondrial Code<br/>
| |
| - | 3 The Yeast Mitochondrial Code<br/>
| |
| - | 4 The Mold, Protozoan, and Coelenterate Mitochondrial Code and the Mycoplasma/Spiroplasma Code<br/>
| |
| - | 5The Invertebrate Mitochondrial Code<br/>
| |
| - | 6 The Ciliate, Dasycladacean and Hexamita Nuclear Code<br/>
| |
| - | 7 The Echinoderm and Flatworm Mitochondrial Code<br/>
| |
| - | 8 The Euplotid Nuclear Code<br/>
| |
| - | 9 The Bacterial, Archaeal and Plant Plastid Code<br/>
| |
| - | 10 The Alternative Yeast Nuclear Code<br/>
| |
| - | 11 The Ascidian Mitochondrial Code<br/>
| |
| - | 12 The Alternative Flatworm Mitochondrial Code<br/>
| |
| - | 13 Blepharisma Nuclear Code<br/>
| |
| - | 14 Chlorophycean Mitochondrial Code<br/>
| |
| - | 15 Trematode Mitochondrial Code<br/>
| |
| - | 16 Scenedesmus Obliquus Mitochondrial Code<br/>
| |
| - | 17 Thraustochytrium Mitochondrial Code<br/>
| |
| - | 18 Pterobranchia Mitochondrial Code<br/>
| |
| - | 19 Candidate Division SR1 and Gracilibacteria Code<br/>
| |
| - | </p>
| |
| - | <p class="tit">The format of utput</p>
| |
| - | <p>The output file is stored in /the path where you install GENOVO/Result/. 02.globalREmarkup.<br/>
| |
| - | Besides, there is screen output about the process state and result.<br/>
| |
| - | 1. Screen output<br/>
| |
| - | 2. *.parse<br/>
| |
| - | Store the exited enzyme recognition site in the megachunks<br/>
| |
| - | Enzyme ID Start End Recognition site Real site<br/>
| |
| - | <img src="https://static.igem.org/mediawiki/2013/b/bf/T3-3.png" />
| |
| - | </p>
| |
| - | <p class="tit">3-3. 03.chunk_30k_10k_2k.pl</p>
| |
| - | <p>This utility can produce 2k minichunks with Gibson adaptors and 10k chunks with goldengate adaptors.</p>
| |
| - | <p class="tit">Internal operation</p>
| |
| - | <p>This utility will segmentate the megachunk produced by 03.mega2chunk2mini.pl into 2k minichunks with Gibson assembly adaptors, so that they can be put together into 10k chunks.<br/>
| |
| - | First, this bin will search the inexistent restriction enzyme sites locally, and then decide the size of the minichunks according to the requirements from users, and add two same Gibson adaptors to each sides of minichunks.
| |
| - | Secondly, the second part of this bin will define the start and end point of the chunks as users asked and design goldengate assembly adaptors for the chunks.<br/>
| |
| - | The output file can be sent in gene synthesis company after human attention and double check.<br/>
| |
| - | For more information about segmentation design, please refer to the page ASSEMBLY DESIGN PRINCIPLE .</p>
| |
| - | <p class="tit">Example (command line)</p>
| |
| - | <p>perl 03.mega2chunk2mini.pl -re standard_and_IIB -sg 01.whole2mega/sce_chr01_0.mega -ps 02.globalREmarkup/sce_chr01_0.parse -ot 03.mega2chunk2mini</p>
| |
| - | <p class="tit">Parameters</p>
| |
| - | <p>
| |
| - | <table><tbody>
| |
| - | <tr><td></td><td></td><td>default</td><td>Option</td></tr>
| |
| - | <tr><td>sg</td><td>The fasta file of the 30k segmentation, the output of 01.wh2mega.pl</td><td></td><td></td></tr>
| |
| - | <tr><td>ps</td><td>The markup file of the 30k segmentation, the output of 02.globalREmarkup.pl</td><td></td><td></td></tr>
| |
| - | <tr><td>re</td><td>The restriction enzyme sites list. It is devided by different standards, type (IIP, IIA, IIB), cost (standard, nonexpensive) and etc.</td><td>Standard_and_IIB</td><td>IIP/IIA/IIB/Standard/
| |
| - | Nonexpensive/
| |
| - | Standard_IIB
| |
| - | Nonexpensive_IIB</td></tr>
| |
| - | <tr><td>a2</td><td>2k to 10k assembly strategy (Gibson or Goldengate)</td><td>Gibson</td><td>Gibson/ Goldengate</td></tr>
| |
| - | <tr><td>a10</td><td>10k to 30k assembly strategy (Gibson or Goldengate)</td><td>Goldengate</td><td>Gibson/ Goldengate</td></tr>
| |
| - | <tr><td>ckmax2</td><td>The maximum length of minichunks</td><td>2200 bp</td><td></td></tr>
| |
| - | <tr><td>ckmin2</td><td>The minimum length of minichunks </td><td>1800 bp</td><td></td></tr>
| |
| - | <tr><td>cknum</td><td>The number of minichunks in a chunk</td><td>5</td><td></td></tr>
| |
| - |
| |
| - | </tbody>
| |
| - | </table>
| |
| - | If parameter a2 is Gibson, then there are additional parameters:<br/>
| |
| - | <table><tbody>
| |
| - | <tr><td>ol2</td><td>The length of overlap</td><td>40 bp</td><td></td></tr>
| |
| - | <tr><td>tmax2</td><td>The maximum melting temperature of the overlap of minichunks</td><td>60℃</td><td></td></tr>
| |
| - | <tr><td>tmin2</td><td>The minimum melting temperature of the overlap of minichunks</td><td>56℃</td><td></td></tr>
| |
| - | <tr><td>fe2</td><td>The minimum free energy of the overlap of minichunks</td><td>-3</td><td></td></tr>
| |
| - | <tr><td>ex2</td><td>The type of exonuclease used for minichunks</td><td>T5</td><td>T5/T3</td></tr>
| |
| - | <tr><td>lo2</td><td>The minimum distance between minichunks overlap and loxpsym</td><td>40 bp</td><td></td></tr>
| |
| - | <tr><td>en2</td><td>The type of enzyme flanking minichunks</td><td>IIP</td><td></td></tr>
| |
| - | <tr><td>et2</td><td></td><td></td><td></td></tr>
| |
| - | <tr><td>ep2</td><td>The maximum unit price of enzyme used in minichunks digestion</td><td>0.5 $/unit</td><td></td></tr>
| |
| - |
| |
| - | </tbody>
| |
| - | </table>
| |
| - | If parameter a10 is Goldengate, then there are additional parameters:<br/>
| |
| - | <table><tbody>
| |
| - | <tr><td>en10</td><td>The type of enzyme flanking chunks</td><td>IIB</td><td>IIA/IIB</td><tr>
| |
| - | <tr><td>et10</td><td>The temperature of enzyme used in chunks digestion</td><td>37℃</td><td></td></tr>
| |
| - |
| |
| - | </tbody>
| |
| - | </table>
| |
| - | </p>
| |
| - | <p class="tit">The format of ouput</p>
| |
| - | <p>The output file is stored in /the path where you install GENOVO/Result/. 03.mega2chunk2mini.<br/>
| |
| - | Besides, there is screen output about the process state and result.<br/>
| |
| - | 1. Screen output<br/>
| |
| - | 2. *.2kstate<br/>
| |
| - | Store the minichunks states.<br/>
| |
| - | <table><tr><td>Left IIP enzyme site</td><td>Right IIP enzyme site</td><td>Start</td><td>End</td><td>Size of minichunks</td><td>Melting temperature of overlap</td></tr>
| |
| - | </table>
| |
| - | <img src="https://static.igem.org/mediawiki/2013/b/bf/T3-3.png" /><br/>
| |
| - | 3. *.10kstate<br/>
| |
| - | Store the chunks states<br/>
| |
| - | <table>
| |
| - | <tr><td>Left IIB enzyme site</td><td>Right IIB enzyme site</td><td>Start</td><td>End</td>Size of chunks<td></td></tr>
| |
| - | </table>
| |
| - | <img src="https://static.igem.org/mediawiki/2013/a/ad/T3-4.png" /><br/>
| |
| - | 4. *.mini<br/>
| |
| - | Store the fasta of designed minichunks.<br/>
| |
| - | <img src="https://static.igem.org/mediawiki/2013/0/0f/T3-5.png" /><br/>
| |
| - | </p>
| |
| - |
| |
| - |
| |
| - | </div>
| |
| - | <div id="tab4">
| |
| - | <p class="tit">Presentation from KGML</p>
| |
| - | <p> This module will grab genes’ details in different pathways, which from KEGG with KEGG Makeup Language (KGML) file and export genes list and relationship of genes. The goal here is to visualize the pathway and rebuild it in the level of genes.</p>
| |
| - | <p class="tit">Scripts<br/>1. keggid_convert_gene.pl</p>
| |
| - | <p> This utility can convert KEGGID which in KGML file into genes’ name and rewrite KGML file.</p>
| |
| - | <p class="tit">Internal operation</p>
| |
| - | <p> First, this utility will change the pathway’s name into KEGG database names, and then open the file with the entire list of genes, push them in hash.<br/>
| |
| - | Second, this utility will read the original pathway’s xml file in and replace KEGGID with gene’s name one by one. Furthermore, it will change type element all into “gene”.<br/>
| |
| - | Thirdly, it will be the substitution of original pathway’s xml file.</p>
| |
| - | <p class="tit">Example</p>
| |
| - | <p> perl keggid_convert_gene.pl ko04010</p>
| |
| - | <p class="tit">The format of output:</p>
| |
| - | <p>It will rewrite the original pathway’s xml file, if we have following statement:<br/>
| |
| - | <entry id="30" name="ko:K08018" type="ortholog"<br/>
| |
| - | After running this scripts, it will turn into:<br/><entry id="30" name=" RAPGEF2, PDZGEF1" type="gene" </p>
| |
| - | <p class="tit">convert.py</p>
| |
| - | <p> This utility will read in KGML file which have been rewritten before, and grab genes’ information, such as genes’ name, genes’ relationship and then convert these into JSON.</p>
| |
| - | <p class="tit">Internal operation</p>
| |
| - | <p> First, this utility will use the parameter –f to determine the specified file and read it in. The output file will use the file name that put forward.<br/>
| |
| - | Second, this utility convert KGML file into JSON and grab the information of genes, such as the reactions of genes and the relationship between genes.<br/>
| |
| - | Third, this utility continue to integrate the information above into two files, ‘gene.json’ and ‘relation.json’, which can be use directly in rewrite gene’s pathway.</p>
| |
| - | <p class="tit">Example</p>
| |
| - | <p> python convert.py –f sce04111</p>
| |
| - | <p class="tit">Parameters:</p>
| |
| - | <table border='1'><tbody>
| |
| - | <tr><td></td><td>default</td></tr>
| |
| - | <tr><td>-f/--file</td><td>read KGML from FILENAME(omit '.xml'), produce two files: gene list and relation</td></tr>
| |
| - | </tbody></table>
| |
| - | <p class="tit">The format of output:</p>
| |
| - | <p>The output file is stored in the path where you running this program.<br/>
| |
| - | 1. _gene.json <br/>
| |
| - | <img src="https://static.igem.org/mediawiki/2013/1/1b/T4-1.png" />
| |
| - | type:<br/>
| |
| - | <table><tbody>
| |
| - | <tr><td>ortholog</td><td>KO (orthology group)</td></tr>
| |
| - | <tr><td>enzyme</td><td>Enzyme</td></tr>
| |
| - | <tr><td>reaction</td><td>Reaction</td></tr>
| |
| - | <tr><td>gene</td><td>gene product (mostly a protein)</td></tr>
| |
| - | <tr><td>group</td><td>a complex of gene products (mostly a protein complex)</td></tr>
| |
| - | </tbody></table>
| |
| - | geneID:the unique identification of gene<br/>
| |
| - | <table><tbody>
| |
| - | <tr><td>name</td><td>the KEGGID of this gene </td></tr>
| |
| - | <tr><td>type</td><td>the type of this gene</td></tr>
| |
| - | </tbody></table>
| |
| - | reaction:<br/>
| |
| - | <table><tbody>
| |
| - | <tr><td>name</td><td>the KEGGID of this reaction</td></tr>
| |
| - | <tr><td>reversible</td><td>true: reversible reaction; false: irreversible reaction</td></tr>
| |
| - | <tr><td>substrates</td><td>KEGGID of substrate node</td></tr>
| |
| - | <tr><td>products</td><td>the KEGGID of product node</td></tr>
| |
| - | <tr><td>related-reactions</td><td>relate to another pathway or gene</td></tr>
| |
| - | </tbody></table>
| |
| - | 2. _relation.json
| |
| - | <img src="https://static.igem.org/mediawiki/2013/c/c1/T4-2.png" />
| |
| - | relations:<br/>
| |
| - | <table><tbody>
| |
| - | <tr><td>type</td><td>The type of this relation[ ECrel, PPrel. GErel, PCrel, maplink]</td></tr>
| |
| - | <tr><td>subtype</td><td>Interaction/relation information[activation/inhibition]</td></tr>
| |
| - | <tr><td>entry1</td><td>The first (from) entry that defines this relation</td></tr>
| |
| - | <tr><td>entry2</td><td>The second (to) entry that defines this relation</td></tr>
| |
| - | </tbody></table>
| |
| - | entry1&2:<br/>
| |
| - | <table><tbody>
| |
| - | <tr><td>entry ID</td><td>The KEGGID of node which takes part in this relation</td></tr>
| |
| - | <tr><td>type</td><td>Have only two options: [gene/group]</td></tr>
| |
| - | <tr><td>name</td><td>The KEGGID of this gene</td></tr>
| |
| - | <tr><td>group</td><td>The node is a complex of gene products (mostly a protein complex)</td></tr>
| |
| - | </tbody></table>
| |
| - | </p>
| |
| - | <br/> <p class="tit">Shortcoming</p>
| |
| - | <p>We can’t automatic acquisition KGML file in the KEGG API, all the demo we have show need to be downloaded before. You can get the entire list of one database genes through KEGG API, just like http://rest.kegg.jp/list/ko , it shows the entire list of orthology genes. The download method about KGML files shows in “How to finish this plun-in” part.
| |
| - | Some genes will relate to another pathway but it doesn’t shows in the pathway so we are failed to grab the relationships between genes and pathways automatically. So we added two gene-pathway relations in ko04010 demo manually, TP53 gene connected with ko04115: P53 signaling pathway and NLK gene connected with ko04310: WNT signaling pathway.
| |
| - | We look forward to the improvement of this plun-in through these disadvantages. </p>
| |
| - | <p class="tit">How to finish this plun-in?</p>
| |
| - | <p> KEGG is a database resource for understanding high-level functions and utilities of the biological system, and KGML is an XML presentation of the KEGG pathway database, which enables automatic drawing of KEGG pathways and provides facilities for computational analysis and modeling of gene/protein networks and chemical networks. Here is the data structure of KGML.<br/>
| |
| - | <img src="https://static.igem.org/mediawiki/2013/f/fa/T4-3.png" />
| |
| - | It’s really complex and it will bother you to understand the KGML file! Do not worry, I will show you how to understand a KGML file and then how to convert it into JSON.<br/>
| |
| - | First, how to find or download KGML file?<br/>
| |
| - | Method: <br/>
| |
| - | Download KGML" link for each pathway map.<br/>
| |
| - | If you choose a pathway with prefix “map”, you can’t find the download link in the page, that’s
| |
| - | because it can be generating almost ko/rn/ec/org files. <br/>
| |
| - | Such as “map04111”, it has no link for download. But if you change the “map” into “sce” in
| |
| - | the URL, you can get the file.<br/>
| |
| - | <a href="http://www.kegg.jp/kegg/rest/keggapi.html">KEGG API:</a>
| |
| - | Take “sce04111” as an example, you can download the KGML file via the <a href="http://rest.kegg.jp/get/sce04111/KGML">this</a>.<br/>
| |
| - | Second, the KGML file is difficult to find out the relationship through the data structure show above.<br/>
| |
| - | Here is the simple but straightforward tutorial to teach you how to understand a KGML file.<br/>
| |
| - | Take “sce04111.xml” as an example. We can simplify the data structure as:<br/>
| |
| - | <img src="https://static.igem.org/mediawiki/2013/c/c5/T4-4.png" /><br/>
| |
| - | The entry element can be path/ko/ec/rn/cpd/gl/org/group, enzyme/protein/gene will have relation and gene will also have compound and reactions. We choose one relation to be example:<br/>
| |
| - | <img src="https://static.igem.org/mediawiki/2013/2/27/T4-5.png" />
| |
| - | It means that gene (YCL061C) have activation effect in gene (YPL153C).By the way, through the graphics elements, we can definitely rewrite the connection between these two genes.<br/>
| |
| - |
| |
| - | Third, thought we know how to get KGML file and can understand it but the crucial problem is, how to grab the information of genes and convert it into JSON.<br/>
| |
| - | Here we use Python programming Language, install the library “lxml” for processing XML and HTML, and we import JSON library for convert.<br/>
| |
| - |
| |
| - | Fourth, you may ask: If there have any other software to do such job, that is read KGML files, convert it and rewrite it? <br/>
| |
| - | Of course, and we indeed tried but failed for it’s not open source or the original source is difficult for modification.
| |
| - | Actually, if you want to do some visualize pathway job, Cytoscape is a good choice and it also have cytoscape.js for drawing.<br/>
| |
| - |
| |
| - | Finally, we indeed done plentiful preparatory work, maybe in the end it’s not useful in this software but it can expand our horizons.
| |
| - | <br/>
| |
| - | </p>
| |
| - |
| |
| - | </div>
| |
| - |
| |
| - | </div>
| |
| - |
| |
| - | <script>
| |
| - | function resetTabs(){
| |
| - | $("#content2 > div").hide(); //Hide all content
| |
| - | $("#tabs a").attr("id",""); //Reset id's
| |
| - | }
| |
| - |
| |
| - | var myUrl = window.location.href; //get URL
| |
| - | var myUrlTab = myUrl.substring(myUrl.indexOf("#")); // For localhost/tabs.html#tab2, myUrlTab = #tab2
| |
| - | var myUrlTabName = myUrlTab.substring(0,4); // For the above example, myUrlTabName = #tab
| |
| - |
| |
| - | (function(){
| |
| - | $("#content2 > div").hide(); // Initially hide all content
| |
| - | $("#tabs li:first a").attr("id","current"); // Activate first tab
| |
| - | $("#content2 > div:first").fadeIn(); // Show first tab content
| |
| - |
| |
| - | $("#tabs a").on("click",function(e) {
| |
| - | e.preventDefault();
| |
| - | if ($(this).attr("id") == "current"){ //detection for current tab
| |
| - | return
| |
| - | }
| |
| - | else{
| |
| - | resetTabs();
| |
| - | $(this).attr("id","current"); // Activate this
| |
| - | $($(this).attr('name')).fadeIn(); // Show content for current tab
| |
| - | }
| |
| - | });
| |
| - |
| |
| - | for (i = 1; i <= $("#tabs li").length; i++) {
| |
| - | if (myUrlTab == myUrlTabName + i) {
| |
| - | resetTabs();
| |
| - | $("a[name='"+myUrlTab+"']").attr("id","current"); // Activate url tab
| |
| - | $(myUrlTab).fadeIn(); // Show url tab content
| |
| - | }
| |
| - | }
| |
| - | })()
| |
| - | </script>
| |
| - | <br/><br/><br/><br/>
| |
| - | <div class="push"></div>
| |
| - | </div><!-- wrapper -->
| |
| - | <footer style>
| |
| - | <div class="container clearfix">
| |
| - | <div class="seven columns" id="footer-contact">
| |
| - | <h3>contact us</h3>
| |
| - | <p>BGI-Shenzhen, Beishan Industrial Zone<br />
| |
| - | Yantian District, Shenzhen, 518083, China</p>
| |
| - | <p> <span>email:</span><br />
| |
| - | <a href="mailto:gongjianhui@genomics.com">gongjianhui@genomics.com</a></p>
| |
| - | </div>
| |
| - | <div class="four columns" id="footer-project">
| |
| - | <h3>sponsor</h3>
| |
| - | <p>BGIC<br/></p>
| |
| - | </div>
| |
| - | <div class="five columns" id="footer-newsletter">
| |
| - | <a href="https://2013.igem.org/Main_Page" ><img width="150" height="120" src="https://static.igem.org/mediawiki/2013/0/02/TB_IGEM_official_logo.png" /></a>
| |
| - | </div>
| |
| | </div> | | </div> |
| - | </footer> | + | </section> |
| - | | + | <br/><br/> |
| - | | + | |
| - | <script src="https://2013.igem.org/Team:Shenzhen_BGIC_0101/aaa?action=raw&ctype=text/javascript"></script> | + | |
| - | | + | |
| - | | + | |
| | </body> | | </body> |
| | </html> | | </html> |
"
