Difference between revisions of "Team:Vilnius-Lithuania/Engineering"

Line 1: Line 1:
<!DOCTYPE html>
+
<html>  
<html> <head> <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/main&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/> <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/fonts&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/> <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/background&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/> <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/contentpage-desktop&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/> <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/contentpage-mobile&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/> <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/sideindex-desktop&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/> <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/sideindex-mobile&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/> <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/navbar&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/> <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/navmenu-desktop&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/> <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/navmenu-mobile&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/> <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/accesibility-menu-desktop&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/> <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/accesibility-menu-mobile&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/> <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/button-pill&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/> <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/footer&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/> <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/table&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/> <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/bypass-block&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/> <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/engineering-success&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/> </head> <body> <div class="navbar-container"> <nav class="navbar"> <a class="bypass-block-link visually-hidden visible-when-focused" href="#main-content">Skip to main content</a> <a class="navbar-logo" href="/Team:Vilnius-Lithuania"> <img alt="AmebyeLogo" src="https://static.igem.org/mediawiki/2021/b/b0/T--Vilnius-Lithuania--amebyeLogo.svg"/>      AmeBye    </a> <ul class="nav-menu"></ul> </nav> <div class="progress-container"> <div class="progress-bar"></div> </div></div> <div class="background"> <canvas id="background-canvas"></canvas> <canvas id="canvas-transition"></canvas> <div class="app-header"> <h1 id="title">ENGINEERING SUCCESS</h1> <div class="app-header-image-wrapper" id="img"> <img alt="Header" src="https://static.igem.org/mediawiki/2021/3/34/T--Vilnius-Lithuania--Engineering.jpg"/> </div> </div> <div class="app-content"> <div class="app-content-text"> <div class="content-page-container"> <h3 class="index-headline">Overview</h3> <p>              Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus              ac enim id metus rutrum blandit sed non dolor. Pellentesque              feugiat odio eu imperdiet rutrum. Duis consectetur porttitor enim,              id elementum nibh tempus in. Nulla ut massa rutrum, ullamcorper              dui et, posuere velit. Cras viverra, tortor at porta pulvinar,              libero eros pulvinar orci, sed pulvinar neque felis eget dui.              Fusce laoreet libero vitae nunc hendrerit consequat. Nunc eget              bibendum turpis. Vestibulum pulvinar interdum mauris nec congue.              Etiam id nunc ac risus dictum semper sed in nisl.            </p> <svg id="overview-animation" viewbox="0 0 710 350"></svg> <h3 class="index-headline">Fusion protein modeling</h3> <div> <h3>Cycle 1: Design</h3> <p>                Since one of the parts of our project is to create a fusion protein system for the bottleneck                reaction of naringenin synthesis, we decided to model it in silico. The model’s primary purpose is                to check whether the shorter distance between active sites leads to the higher production of naringenin.                In the process, we found out that even the modeling part required to cover the main steps of engineering:                design, build, test, and learn. Therefore, we began with the already existing modeling workflow described                for a fusion construct with a malaria pre-erythrocytic vaccine candidate [1].                The described modeling approach was initially designed as follows:              </p> <ol> <li>Choosing the protein candidates</li> <li>Selecting linkers</li> <li>Primary structural analysis of the fusion system</li> <li>Protein modeling</li> <li>Scoring modeled complexes to choose the model for visualization</li> <li>Plotting Ramachandran graphs before structure refinement</li> <li>Structure refinement</li> <li>Plotting Ramachandran graphs after structure refinement</li> </ol> </div> <div> <h3>Cycle 1: Build</h3> <p>                The building stage of the modeling flow consisted of performing the initial design flow.                In this cycle we have raised a hypothesis that homology-based protein modeling approaches                should not be the most suitable method for our case, since there are few fusion models existing.              </p> <ol> <li>The protein candidates were chosen to be 4-coumarate-CoA ligase 2 from Glycine max and chalcone synthase from Arabidopsis thaliana</li> <li>Seven linkers were chosen for our fusion system. Four of them were flexible glycine and serine linkers (GSG, (GGGGS)n, where n is equal to 1, 2, and 3) and the other three were rigid ((EAAAK)n, where n is equal to 1, 2, and 3)</li> <li>For a primary structural analysis we studied PDB: 3TSY structure - an experimentally determined structure of the fusion system that has 4CL protein in it. We took this structure as a starting point of what we can expect from our models</li> <li>Protein modeling was initially attempted to perform using homology-based modeling program SWISS-MODEL[2]</li> <li>The modeled structures in the first cycle were evaluated using VoroMQA[3], QMEAN[4], and QMEANDisCo[5] scores</li> <li>The plot was not drawn in this cycle</li> <li>The structure refinement was not performed in this cycle</li> <li>The plot was not drawn in this cycle</li> </ol> </div> <div> <h3>Cycle 1: Test</h3> <p>                The output of SWISS-MODEL showed that sequence identity between the templates found and the sequence                that is modeled is 66.42 - 69.36%. According to the specialists in protein modeling,                homology-based methods are suitable, when the sequence identity between the template                and the modeled sequence is more than 25%, belonging to the “daylight” zone[7], thus, in theory,                the method could be applied.              </p> <p>                The modeling flow was tested with PyMOL[6] visualization program using commands                `cealign`, `set seq_view`. We were looking for an accurate representation of the                linked proteins in the fusion system by comparing them to their distinct versions.                The main focus on the system was the linker region, which in the homology-based modeling                case was composed of the uncoiled domain of 4CL that made up a highly disordered massive linker region.                We stopped the flow after the visualization because we decided that structure refinement using molecular                dynamics will not introduce any significant changes to the structure.              </p> </div> <div> <h3>Cycle 1: Learn</h3> <p>                Nonetheless in theory the homology-based modeling method could be applied,                these modeling results proved that this approach could not be applied to our fusion protein system.                Therefore, we decided to try running <i>ab initio</i> protein modeling programs.              </p> </div> <div> <h3>Cycle 2: Design</h3> <p>                The design (main steps) of the modeling flow stayed the same as it was in the first cycle,                yet also we included one more step - energy minimization with Yasara[10] -                that was inserted after the protein modeling step. The main changes in the second                cycle were the choice of protein modeling programs. In this engineering cycle we took <i>ab initio</i>                modeling programs trRosetta[8] and RoseTTAFold[9] to model our proteins.              </p> </div> <div> <h3>Cycle 2: Build</h3> <ol> <li>Protein candidates stayed the same as in the first cycle</li> <li>Linkers stayed the same as in the first cycle</li> <li>Primary structure analysis was not required to be redone in the second cycle</li> <li>Protein modeling was performed using trRosetta and RoseTTAFold simultaneously</li> <li>The modeled structures were evaluated using VoroMQA score</li> <li>Energy minimization with Yasara.</li> <li>The Ramachandran plots were drawn before molecular dynamics (MD) simulations</li> <li>We performed short MD simulations for the trivial linker (GSG) case</li> <li>The Ramachandran plots were drawn before molecular dynamics (MD) simulations</li> </ol> </div> <div> <h3>Cycle 2: Test</h3> <p>                The modeled structures visually were not satisfactory - the disordered domain of 4CL                protein was still present in the structure. The energy minimization step with Yasara                and MD simulations did not introduce any significant changes to the structure.              </p> </div> <div> <h3>Cycle 2: Learn</h3> <p>                After this step we decided to consult the bioinformatician who works with protein modeling.                He suggested we include multiple sequence alignment files into our modeling flow. Additionally,                we got advice to use more scoring functions in the evaluation step.                Yet also we consulted the protein molecular dynamics specialist to get a professional                insight into how we should run the MD for our system to get a more significant output.                After the consultation we adjusted the box size of the system and the duration of the simulations.              </p> </div> <div> <h3>Cycle 3: Design</h3> <p>                In the third engineering cycle we included our own generated multiple sequence alignment (MSA)                files as input to the protein modeling programs of our choice.                In addition, we took into account the advice from the specialists and included                QMEAN and QMEANDisCo scores into the evaluation of the structures. The structure                refinement was not performed in this cycle due to the lack of computational resources at the time.              </p> </div> <div> <h3>Cycle 3: Build</h3> <ol> <li>Protein candidates stayed the same as in the previous cycle</li> <li>Linkers stayed the same as in the previous cycle</li> <li>Primary structure analysis was not required to be redone</li> <li>Protein modeling was performed using RoseTTAFold</li> <li>The modeled structures were evaluated using QMEAN, QMEANDisCo, and VoroMQA scores</li> <li>The plot was not drawn in this cycle</li> <li>The structure refinement was not performed in this cycle</li> <li>The plot was not drawn in this cycle</li> <li>The distances between active sites in fusion protein systems with rigid linkers were calculated</li> </ol> </div> <div> <h3>Cycle 3: Test</h3> <p>                The modeled structures were visually satisfactory -                the disordered domain of 4CL protein was less disordered in the modeled structure.              </p> </div> <div> <h3>Cycle 3: Learn</h3> <p>                The multiple sequence alignment (MSA) files have a significant impact on the modeling output.              </p> </div> <div> <h3>Cycle 4: Design</h3> <p>                According to the output of the third cycle, the fourth engineering cycle was not required.                However, after the latter cycle was finished, AlphaFold2[11] became available for public use.                Therefore, we decided to apply this highly evaluated tool in our modeling workflow.                The structure refinement was not performed in this cycle due to the insignificant impact of                MD for structures recorded in the studies[12].              </p> </div> <div> <h3>Cycle 4: Build</h3> <ol> <li>Protein candidates stayed the same as in the previous cycle</li> <li>Linkers stayed the same as in the previous cycle</li> <li>Primary structure analysis was not required to be redone</li> <li>Protein modeling was performed using AlphaFold2</li> <li>The modeled structures were evaluated using QMEAN, QMEANDisCo, ProQ2D, ProQRosCenD, ProQRosFAD, ProQ3D scores</li> <li>The plots were drawn in this cycle</li> <li>The structure refinement was not performed in this cycle</li> <li>The distances between active sites in fusion protein systems with rigid linkers were calculated</li> </ol> </div> <div> <h3>Cycle 4: Test</h3> <p>                The output of the fourth cycle had the less disordered domain just as the output of the third cycle.              </p> </div> <div> <h3>Cycle 4: Learn</h3> <p>                We were visually satisfied with the modeled complex.                Nonetheless, AlphaFold2 models do not require the usage of molecular                dynamics for structure refinement, we considered applying them to get a                better insight of the system with flexible linkers.              </p> </div> </div> <div class="references-wrapper"> <div class="breaker"></div> <h2>References</h2> <div class="references-container"> <div class="number">1.</div><div>Trundle, K. Teaching Science During the Early Childhood Years. National Geographic Learning (2010).</div> <div class="number">11.</div><div>Trundle, K. Teaching Science During the Early Childhood Years. National Geographic Learning (2010).</div> </div> </div> </div> <div class="index-container"> <div class="index-header"></div> <div class="index-content"></div> </div> </div> <footer> <div class="logo-igem"> <object data="https://static.igem.org/mediawiki/2021/f/ff/T--Vilnius-Lithuania--iGEM-2021.svg"> </object> </div> <div class="social-container"> <div>FOLLOW US</div> <div> <a class="placeholder-social-icon" href="https://www.facebook.com/VilniusiGEM"> <img src="https://static.igem.org/mediawiki/2021/3/36/T--Vilnius-Lithuania--facebook.svg"/> </a> <a class="placeholder-social-icon" href="https://www.instagram.com/igem_vilnius/"> <img src="https://static.igem.org/mediawiki/2021/6/64/T--Vilnius-Lithuania--instagram.svg"/> </a> <a class="placeholder-social-icon" href="https://www.linkedin.com/company/vilnius-igem/"> <img src="https://static.igem.org/mediawiki/2021/e/e7/T--Vilnius-Lithuania--linkedin.svg"/> </a> </div> </div> <div class="mail-container"> <div>CONTACT US</div> <a href="mailto:info@vilniusigem.lt">info@vilniusigem.lt</a> </div> <div class="grid-sponsors"> <div> <div> <object data="https://static.igem.org/mediawiki/2021/d/dc/T--Vilnius-Lithuania--VU.svg"> </object> </div> <div> <object data="https://static.igem.org/mediawiki/2021/b/bf/T--Vilnius-Lithuania--Termofisher.svg"> </object> </div> <div> <object data="https://static.igem.org/mediawiki/2021/1/10/T--Vilnius-Lithuania--CityOfVilnius.svg"> </object> </div> </div> <div> <div> <object data="https://static.igem.org/mediawiki/2021/b/bb/T--Vilnius-Lithuania--GMC.svg"> </object> </div> <div> <object data="https://static.igem.org/mediawiki/2021/9/98/T--Vilnius-Lithuania--Nanodiagnostika.svg"> </object> </div> <div> <object data="https://static.igem.org/mediawiki/2021/1/16/T--Vilnius-Lithuania--Telesoftas.svg"> </object> </div> <div> <object data="https://static.igem.org/mediawiki/2021/7/70/T--Vilnius-Lithuania--Kopicentras.svg"> </object> </div> </div> <div> <div> <object data="https://static.igem.org/mediawiki/2021/d/df/T--Vilnius-Lithuania--SnapGene.svg"> </object> </div> <div> <object data="https://static.igem.org/mediawiki/2021/3/3e/T--Vilnius-Lithuania--Laborama.svg"> </object> </div> <div> <object data="https://static.igem.org/mediawiki/2021/c/c1/T--Vilnius-Lithuania--Biotecha.svg"> </object> </div> <div> <object data="https://static.igem.org/mediawiki/2021/4/4f/T--Vilnius-Lithuania--Grida.svg"> </object> </div> </div> </div></footer> </div> <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/navigationTabs&amp;action=raw&amp;ctype=text/javascript" type="text/javascript"></script> <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/background&amp;action=raw&amp;ctype=text/javascript" type="text/javascript"></script> <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/contentpage&amp;action=raw&amp;ctype=text/javascript" type="text/javascript"></script> <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/navbar&amp;action=raw&amp;ctype=text/javascript" type="text/javascript"></script> <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/drawSineAnimation&amp;action=raw&amp;ctype=text/javascript" type="text/javascript"></script> <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/engineeringSuccess&amp;action=raw&amp;ctype=text/javascript" type="text/javascript"></script> <script>      contentPage(        "Sections",        true,        300,      )    </script> <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/GlslCanvas&amp;action=raw&amp;ctype=text/javascript" type="text/javascript"></script> <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/backgroundTransition&amp;action=raw&amp;ctype=text/javascript" type="text/javascript"></script> </body></html>
+
  <head>
 +
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/main&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
 +
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/fonts&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
 +
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/background&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
 +
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/contentpage-desktop&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
 +
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/contentpage-mobile&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
 +
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/sideindex-desktop&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
 +
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/sideindex-mobile&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
 +
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/navbar&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
 +
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/navmenu-desktop&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
 +
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/navmenu-mobile&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
 +
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/accesibility-menu-desktop&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
 +
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/accesibility-menu-mobile&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
 +
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/button-pill&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
 +
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/footer&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
 +
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/table&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
 +
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/bypass-block&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
 +
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/engineering-success&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
 +
  </head>
 +
  <body>
 +
    <div class="navbar-container">
 +
      <nav class="navbar">
 +
        <a class="bypass-block-link visually-hidden visible-when-focused" href="#main-content">Skip to main content
 +
        </a>
 +
        <a class="navbar-logo" href="/Team:Vilnius-Lithuania">
 +
          <img alt="AmebyeLogo" src="https://static.igem.org/mediawiki/2021/b/b0/T--Vilnius-Lithuania--amebyeLogo.svg"/>      AmeBye   
 +
        </a>
 +
        <ul class="nav-menu">
 +
        </ul>
 +
      </nav>
 +
      <div class="progress-container">
 +
        <div class="progress-bar">
 +
        </div>
 +
      </div>
 +
      <div class="animation-container">
 +
        <script>      document.querySelector('body').classList.add("content-hidden");
 +
          window.addEventListener("load", function() {
 +
            setTimeout(function() {
 +
              document.querySelector('body').classList.remove("content-hidden");
 +
              document.querySelector('.animation-container').classList.add("loaded");
 +
              document.querySelector('.animation-container').innerHTML="";
 +
            }
 +
                      , 200);
 +
          }
 +
                                );
 +
        </script>
 +
        <div id="loading-animation">
 +
        </div>
 +
        <div>Loading...
 +
        </div>
 +
        <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/lottie&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
 +
        </script>
 +
        <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/loading_animation&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
 +
        </script>
 +
        <script>      var animation = bodymovin.loadAnimation({
 +
            container: document.getElementById('loading-animation'),      animationData: loading_animation,      renderer: 'svg',      loop: true,      autoplay: true,    }
 +
                                                            );
 +
        </script>
 +
      </div>
 +
    </div>
 +
    <div class="background">
 +
      <canvas id="background-canvas">
 +
      </canvas>
 +
      <canvas id="canvas-transition">
 +
      </canvas>
 +
      <div class="app-header">
 +
        <h1 id="title">ENGINEERING SUCCESS
 +
        </h1>
 +
        <div class="app-header-image-wrapper" id="img">
 +
          <img alt="Header" src="https://static.igem.org/mediawiki/2021/3/34/T--Vilnius-Lithuania--Engineering.jpg"/>
 +
        </div>
 +
      </div>
 +
      <div class="app-content">
 +
        <div class="app-content-text">
 +
          <div class="content-page-container">
 +
            <h3 class="index-headline">Overview
 +
            </h3>
 +
            <p>              Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus              ac enim id metus rutrum blandit sed non dolor. Pellentesque              feugiat odio eu imperdiet rutrum. Duis consectetur porttitor enim,              id elementum nibh tempus in. Nulla ut massa rutrum, ullamcorper              dui et, posuere velit. Cras viverra, tortor at porta pulvinar,              libero eros pulvinar orci, sed pulvinar neque felis eget dui.              Fusce laoreet libero vitae nunc hendrerit consequat. Nunc eget              bibendum turpis. Vestibulum pulvinar interdum mauris nec congue.              Etiam id nunc ac risus dictum semper sed in nisl.           
 +
            </p>
 +
            <svg id="overview-animation" viewbox="0 0 710 350">
 +
            </svg>
 +
            <h3 class="index-headline">Fusion protein modeling
 +
            </h3>
 +
            <div>
 +
              <h3>Cycle 1: Design
 +
              </h3>
 +
              <p>                Since one of the parts of our project is to create a fusion protein system for the bottleneck                reaction of naringenin synthesis, we decided to model it in silico. The model’s primary purpose is                to check whether the shorter distance between active sites leads to the higher production of naringenin.                In the process, we found out that even the modeling part required to cover the main steps of engineering:                design, build, test, and learn. Therefore, we began with the already existing modeling workflow described                for a fusion construct with a malaria pre-erythrocytic vaccine candidate [1].                The described modeling approach was initially designed as follows:             
 +
              </p>
 +
              <ol>
 +
                <li>Choosing the protein candidates
 +
                </li>
 +
                <li>Selecting linkers
 +
                </li>
 +
                <li>Primary structural analysis of the fusion system
 +
                </li>
 +
                <li>Protein modeling
 +
                </li>
 +
                <li>Scoring modeled complexes to choose the model for visualization
 +
                </li>
 +
                <li>Plotting Ramachandran graphs before structure refinement
 +
                </li>
 +
                <li>Structure refinement
 +
                </li>
 +
                <li>Plotting Ramachandran graphs after structure refinement
 +
                </li>
 +
              </ol>
 +
            </div>
 +
            <div>
 +
              <h3>Cycle 1: Build
 +
              </h3>
 +
              <p>                The building stage of the modeling flow consisted of performing the initial design flow.                In this cycle we have raised a hypothesis that homology-based protein modeling approaches                should not be the most suitable method for our case, since there are few fusion models existing.             
 +
              </p>
 +
              <ol>
 +
                <li>The protein candidates were chosen to be 4-coumarate-CoA ligase 2 from Glycine max and chalcone synthase from Arabidopsis thaliana
 +
                </li>
 +
                <li>Seven linkers were chosen for our fusion system. Four of them were flexible glycine and serine linkers (GSG, (GGGGS)n, where n is equal to 1, 2, and 3) and the other three were rigid ((EAAAK)n, where n is equal to 1, 2, and 3)
 +
                </li>
 +
                <li>For a primary structural analysis we studied PDB: 3TSY structure - an experimentally determined structure of the fusion system that has 4CL protein in it. We took this structure as a starting point of what we can expect from our models
 +
                </li>
 +
                <li>Protein modeling was initially attempted to perform using homology-based modeling program SWISS-MODEL[2]
 +
                </li>
 +
                <li>The modeled structures in the first cycle were evaluated using VoroMQA[3], QMEAN[4], and QMEANDisCo[5] scores
 +
                </li>
 +
                <li>The plot was not drawn in this cycle
 +
                </li>
 +
                <li>The structure refinement was not performed in this cycle
 +
                </li>
 +
                <li>The plot was not drawn in this cycle
 +
                </li>
 +
              </ol>
 +
            </div>
 +
            <div>
 +
              <h3>Cycle 1: Test
 +
              </h3>
 +
              <p>                The output of SWISS-MODEL showed that sequence identity between the templates found and the sequence                that is modeled is 66.42 - 69.36%. According to the specialists in protein modeling,                homology-based methods are suitable, when the sequence identity between the template                and the modeled sequence is more than 25%, belonging to the “daylight” zone[7], thus, in theory,                the method could be applied.             
 +
              </p>
 +
              <p>                The modeling flow was tested with PyMOL[6] visualization program using commands                `cealign`, `set seq_view`. We were looking for an accurate representation of the                linked proteins in the fusion system by comparing them to their distinct versions.                The main focus on the system was the linker region, which in the homology-based modeling                case was composed of the uncoiled domain of 4CL that made up a highly disordered massive linker region.                We stopped the flow after the visualization because we decided that structure refinement using molecular                dynamics will not introduce any significant changes to the structure.             
 +
              </p>
 +
            </div>
 +
            <div>
 +
              <h3>Cycle 1: Learn
 +
              </h3>
 +
              <p>                Nonetheless in theory the homology-based modeling method could be applied,                these modeling results proved that this approach could not be applied to our fusion protein system.                Therefore, we decided to try running
 +
                <i>ab initio
 +
                </i> protein modeling programs.             
 +
              </p>
 +
            </div>
 +
            <div>
 +
              <h3>Cycle 2: Design
 +
              </h3>
 +
              <p>                The design (main steps) of the modeling flow stayed the same as it was in the first cycle,                yet also we included one more step - energy minimization with Yasara[10] -                that was inserted after the protein modeling step. The main changes in the second                cycle were the choice of protein modeling programs. In this engineering cycle we took
 +
                <i>ab initio
 +
                </i>                modeling programs trRosetta[8] and RoseTTAFold[9] to model our proteins.             
 +
              </p>
 +
            </div>
 +
            <div>
 +
              <h3>Cycle 2: Build
 +
              </h3>
 +
              <ol>
 +
                <li>Protein candidates stayed the same as in the first cycle
 +
                </li>
 +
                <li>Linkers stayed the same as in the first cycle
 +
                </li>
 +
                <li>Primary structure analysis was not required to be redone in the second cycle
 +
                </li>
 +
                <li>Protein modeling was performed using trRosetta and RoseTTAFold simultaneously
 +
                </li>
 +
                <li>The modeled structures were evaluated using VoroMQA score
 +
                </li>
 +
                <li>Energy minimization with Yasara.
 +
                </li>
 +
                <li>The Ramachandran plots were drawn before molecular dynamics (MD) simulations
 +
                </li>
 +
                <li>We performed short MD simulations for the trivial linker (GSG) case
 +
                </li>
 +
                <li>The Ramachandran plots were drawn before molecular dynamics (MD) simulations
 +
                </li>
 +
              </ol>
 +
            </div>
 +
            <div>
 +
              <h3>Cycle 2: Test
 +
              </h3>
 +
              <p>                The modeled structures visually were not satisfactory - the disordered domain of 4CL                protein was still present in the structure. The energy minimization step with Yasara                and MD simulations did not introduce any significant changes to the structure.             
 +
              </p>
 +
            </div>
 +
            <div>
 +
              <h3>Cycle 2: Learn
 +
              </h3>
 +
              <p>                After this step we decided to consult the bioinformatician who works with protein modeling.                He suggested we include multiple sequence alignment files into our modeling flow. Additionally,                we got advice to use more scoring functions in the evaluation step.                Yet also we consulted the protein molecular dynamics specialist to get a professional                insight into how we should run the MD for our system to get a more significant output.                After the consultation we adjusted the box size of the system and the duration of the simulations.             
 +
              </p>
 +
            </div>
 +
            <div>
 +
              <h3>Cycle 3: Design
 +
              </h3>
 +
              <p>                In the third engineering cycle we included our own generated multiple sequence alignment (MSA)                files as input to the protein modeling programs of our choice.                In addition, we took into account the advice from the specialists and included                QMEAN and QMEANDisCo scores into the evaluation of the structures. The structure                refinement was not performed in this cycle due to the lack of computational resources at the time.             
 +
              </p>
 +
            </div>
 +
            <div>
 +
              <h3>Cycle 3: Build
 +
              </h3>
 +
              <ol>
 +
                <li>Protein candidates stayed the same as in the previous cycle
 +
                </li>
 +
                <li>Linkers stayed the same as in the previous cycle
 +
                </li>
 +
                <li>Primary structure analysis was not required to be redone
 +
                </li>
 +
                <li>Protein modeling was performed using RoseTTAFold
 +
                </li>
 +
                <li>The modeled structures were evaluated using QMEAN, QMEANDisCo, and VoroMQA scores
 +
                </li>
 +
                <li>The plot was not drawn in this cycle
 +
                </li>
 +
                <li>The structure refinement was not performed in this cycle
 +
                </li>
 +
                <li>The plot was not drawn in this cycle
 +
                </li>
 +
                <li>The distances between active sites in fusion protein systems with rigid linkers were calculated
 +
                </li>
 +
              </ol>
 +
            </div>
 +
            <div>
 +
              <h3>Cycle 3: Test
 +
              </h3>
 +
              <p>                The modeled structures were visually satisfactory -                the disordered domain of 4CL protein was less disordered in the modeled structure.             
 +
              </p>
 +
            </div>
 +
            <div>
 +
              <h3>Cycle 3: Learn
 +
              </h3>
 +
              <p>                The multiple sequence alignment (MSA) files have a significant impact on the modeling output.             
 +
              </p>
 +
            </div>
 +
            <div>
 +
              <h3>Cycle 4: Design
 +
              </h3>
 +
              <p>                According to the output of the third cycle, the fourth engineering cycle was not required.                However, after the latter cycle was finished, AlphaFold2[11] became available for public use.                Therefore, we decided to apply this highly evaluated tool in our modeling workflow.                The structure refinement was not performed in this cycle due to the insignificant impact of                MD for structures recorded in the studies[12].             
 +
              </p>
 +
            </div>
 +
            <div>
 +
              <h3>Cycle 4: Build
 +
              </h3>
 +
              <ol>
 +
                <li>Protein candidates stayed the same as in the previous cycle
 +
                </li>
 +
                <li>Linkers stayed the same as in the previous cycle
 +
                </li>
 +
                <li>Primary structure analysis was not required to be redone
 +
                </li>
 +
                <li>Protein modeling was performed using AlphaFold2
 +
                </li>
 +
                <li>The modeled structures were evaluated using QMEAN, QMEANDisCo, ProQ2D, ProQRosCenD, ProQRosFAD, ProQ3D scores
 +
                </li>
 +
                <li>The plots were drawn in this cycle
 +
                </li>
 +
                <li>The structure refinement was not performed in this cycle
 +
                </li>
 +
                <li>The distances between active sites in fusion protein systems with rigid linkers were calculated
 +
                </li>
 +
              </ol>
 +
            </div>
 +
            <div>
 +
              <h3>Cycle 4: Test
 +
              </h3>
 +
              <p>                The output of the fourth cycle had the less disordered domain just as the output of the third cycle.             
 +
              </p>
 +
            </div>
 +
            <div>
 +
              <h3>Cycle 4: Learn
 +
              </h3>
 +
              <p>                We were visually satisfied with the modeled complex.                Nonetheless, AlphaFold2 models do not require the usage of molecular                dynamics for structure refinement, we considered applying them to get a                better insight of the system with flexible linkers.             
 +
              </p>
 +
            </div>
 +
          </div>
 +
          <div class="references-wrapper">
 +
            <div class="breaker">
 +
            </div>
 +
            <h2>References
 +
            </h2>
 +
            <div class="references-container">
 +
              <div class="number">1.
 +
              </div>
 +
              <div>Trundle, K. Teaching Science During the Early Childhood Years. National Geographic Learning (2010).
 +
              </div>
 +
              <div class="number">11.
 +
              </div>
 +
              <div>Trundle, K. Teaching Science During the Early Childhood Years. National Geographic Learning (2010).
 +
              </div>
 +
            </div>
 +
          </div>
 +
        </div>
 +
        <div class="index-container">
 +
          <div class="index-header">
 +
          </div>
 +
          <div class="index-content">
 +
          </div>
 +
        </div>
 +
      </div>
 +
      <footer>
 +
        <div class="logo-igem">
 +
          <object data="https://static.igem.org/mediawiki/2021/f/ff/T--Vilnius-Lithuania--iGEM-2021.svg">
 +
          </object>
 +
        </div>
 +
        <div class="social-container">
 +
          <div>FOLLOW US
 +
          </div>
 +
          <div>
 +
            <a class="placeholder-social-icon" href="https://www.facebook.com/VilniusiGEM">
 +
              <img src="https://static.igem.org/mediawiki/2021/3/36/T--Vilnius-Lithuania--facebook.svg"/>
 +
            </a>
 +
            <a class="placeholder-social-icon" href="https://www.instagram.com/igem_vilnius/">
 +
              <img src="https://static.igem.org/mediawiki/2021/6/64/T--Vilnius-Lithuania--instagram.svg"/>
 +
            </a>
 +
            <a class="placeholder-social-icon" href="https://www.linkedin.com/company/vilnius-igem/">
 +
              <img src="https://static.igem.org/mediawiki/2021/e/e7/T--Vilnius-Lithuania--linkedin.svg"/>
 +
            </a>
 +
          </div>
 +
        </div>
 +
        <div class="mail-container">
 +
          <div>CONTACT US
 +
          </div>
 +
          <a href="mailto:info@vilniusigem.lt">info@vilniusigem.lt
 +
          </a>
 +
        </div>
 +
        <div class="grid-sponsors">
 +
          <div>
 +
            <div>
 +
              <object data="https://static.igem.org/mediawiki/2021/d/dc/T--Vilnius-Lithuania--VU.svg">
 +
              </object>
 +
            </div>
 +
            <div>
 +
              <object data="https://static.igem.org/mediawiki/2021/b/bf/T--Vilnius-Lithuania--Termofisher.svg">
 +
              </object>
 +
            </div>
 +
            <div>
 +
              <object data="https://static.igem.org/mediawiki/2021/1/10/T--Vilnius-Lithuania--CityOfVilnius.svg">
 +
              </object>
 +
            </div>
 +
          </div>
 +
          <div>
 +
            <div>
 +
              <object data="https://static.igem.org/mediawiki/2021/b/bb/T--Vilnius-Lithuania--GMC.svg">
 +
              </object>
 +
            </div>
 +
            <div>
 +
              <object data="https://static.igem.org/mediawiki/2021/9/98/T--Vilnius-Lithuania--Nanodiagnostika.svg">
 +
              </object>
 +
            </div>
 +
            <div>
 +
              <object data="https://static.igem.org/mediawiki/2021/1/16/T--Vilnius-Lithuania--Telesoftas.svg">
 +
              </object>
 +
            </div>
 +
            <div>
 +
              <object data="https://static.igem.org/mediawiki/2021/7/70/T--Vilnius-Lithuania--Kopicentras.svg">
 +
              </object>
 +
            </div>
 +
          </div>
 +
          <div>
 +
            <div>
 +
              <object data="https://static.igem.org/mediawiki/2021/d/df/T--Vilnius-Lithuania--SnapGene.svg">
 +
              </object>
 +
            </div>
 +
            <div>
 +
              <object data="https://static.igem.org/mediawiki/2021/3/3e/T--Vilnius-Lithuania--Laborama.svg">
 +
              </object>
 +
            </div>
 +
            <div>
 +
              <object data="https://static.igem.org/mediawiki/2021/c/c1/T--Vilnius-Lithuania--Biotecha.svg">
 +
              </object>
 +
            </div>
 +
            <div>
 +
              <object data="https://static.igem.org/mediawiki/2021/4/4f/T--Vilnius-Lithuania--Grida.svg">
 +
              </object>
 +
            </div>
 +
          </div>
 +
        </div>
 +
      </footer>
 +
    </div>
 +
    <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/navigationTabs&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
 +
    </script>
 +
    <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/background&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
 +
    </script>
 +
    <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/contentpage&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
 +
    </script>
 +
    <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/navbar&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
 +
    </script>
 +
    <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/drawSineAnimation&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
 +
    </script>
 +
    <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/engineeringSuccess&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
 +
    </script>
 +
    <script>      contentPage(        "Sections",        true,        300,      )    </script>
 +
    <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/GlslCanvas&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
 +
    </script>
 +
    <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/backgroundTransition&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
 +
    </script>
 +
  </body>
 +
</html>

Revision as of 13:25, 16 October 2021

ENGINEERING SUCCESS

Header

Overview

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus ac enim id metus rutrum blandit sed non dolor. Pellentesque feugiat odio eu imperdiet rutrum. Duis consectetur porttitor enim, id elementum nibh tempus in. Nulla ut massa rutrum, ullamcorper dui et, posuere velit. Cras viverra, tortor at porta pulvinar, libero eros pulvinar orci, sed pulvinar neque felis eget dui. Fusce laoreet libero vitae nunc hendrerit consequat. Nunc eget bibendum turpis. Vestibulum pulvinar interdum mauris nec congue. Etiam id nunc ac risus dictum semper sed in nisl.

Fusion protein modeling

Cycle 1: Design

Since one of the parts of our project is to create a fusion protein system for the bottleneck reaction of naringenin synthesis, we decided to model it in silico. The model’s primary purpose is to check whether the shorter distance between active sites leads to the higher production of naringenin. In the process, we found out that even the modeling part required to cover the main steps of engineering: design, build, test, and learn. Therefore, we began with the already existing modeling workflow described for a fusion construct with a malaria pre-erythrocytic vaccine candidate [1]. The described modeling approach was initially designed as follows:

  1. Choosing the protein candidates
  2. Selecting linkers
  3. Primary structural analysis of the fusion system
  4. Protein modeling
  5. Scoring modeled complexes to choose the model for visualization
  6. Plotting Ramachandran graphs before structure refinement
  7. Structure refinement
  8. Plotting Ramachandran graphs after structure refinement

Cycle 1: Build

The building stage of the modeling flow consisted of performing the initial design flow. In this cycle we have raised a hypothesis that homology-based protein modeling approaches should not be the most suitable method for our case, since there are few fusion models existing.

  1. The protein candidates were chosen to be 4-coumarate-CoA ligase 2 from Glycine max and chalcone synthase from Arabidopsis thaliana
  2. Seven linkers were chosen for our fusion system. Four of them were flexible glycine and serine linkers (GSG, (GGGGS)n, where n is equal to 1, 2, and 3) and the other three were rigid ((EAAAK)n, where n is equal to 1, 2, and 3)
  3. For a primary structural analysis we studied PDB: 3TSY structure - an experimentally determined structure of the fusion system that has 4CL protein in it. We took this structure as a starting point of what we can expect from our models
  4. Protein modeling was initially attempted to perform using homology-based modeling program SWISS-MODEL[2]
  5. The modeled structures in the first cycle were evaluated using VoroMQA[3], QMEAN[4], and QMEANDisCo[5] scores
  6. The plot was not drawn in this cycle
  7. The structure refinement was not performed in this cycle
  8. The plot was not drawn in this cycle

Cycle 1: Test

The output of SWISS-MODEL showed that sequence identity between the templates found and the sequence that is modeled is 66.42 - 69.36%. According to the specialists in protein modeling, homology-based methods are suitable, when the sequence identity between the template and the modeled sequence is more than 25%, belonging to the “daylight” zone[7], thus, in theory, the method could be applied.

The modeling flow was tested with PyMOL[6] visualization program using commands `cealign`, `set seq_view`. We were looking for an accurate representation of the linked proteins in the fusion system by comparing them to their distinct versions. The main focus on the system was the linker region, which in the homology-based modeling case was composed of the uncoiled domain of 4CL that made up a highly disordered massive linker region. We stopped the flow after the visualization because we decided that structure refinement using molecular dynamics will not introduce any significant changes to the structure.

Cycle 1: Learn

Nonetheless in theory the homology-based modeling method could be applied, these modeling results proved that this approach could not be applied to our fusion protein system. Therefore, we decided to try running ab initio protein modeling programs.

Cycle 2: Design

The design (main steps) of the modeling flow stayed the same as it was in the first cycle, yet also we included one more step - energy minimization with Yasara[10] - that was inserted after the protein modeling step. The main changes in the second cycle were the choice of protein modeling programs. In this engineering cycle we took ab initio modeling programs trRosetta[8] and RoseTTAFold[9] to model our proteins.

Cycle 2: Build

  1. Protein candidates stayed the same as in the first cycle
  2. Linkers stayed the same as in the first cycle
  3. Primary structure analysis was not required to be redone in the second cycle
  4. Protein modeling was performed using trRosetta and RoseTTAFold simultaneously
  5. The modeled structures were evaluated using VoroMQA score
  6. Energy minimization with Yasara.
  7. The Ramachandran plots were drawn before molecular dynamics (MD) simulations
  8. We performed short MD simulations for the trivial linker (GSG) case
  9. The Ramachandran plots were drawn before molecular dynamics (MD) simulations

Cycle 2: Test

The modeled structures visually were not satisfactory - the disordered domain of 4CL protein was still present in the structure. The energy minimization step with Yasara and MD simulations did not introduce any significant changes to the structure.

Cycle 2: Learn

After this step we decided to consult the bioinformatician who works with protein modeling. He suggested we include multiple sequence alignment files into our modeling flow. Additionally, we got advice to use more scoring functions in the evaluation step. Yet also we consulted the protein molecular dynamics specialist to get a professional insight into how we should run the MD for our system to get a more significant output. After the consultation we adjusted the box size of the system and the duration of the simulations.

Cycle 3: Design

In the third engineering cycle we included our own generated multiple sequence alignment (MSA) files as input to the protein modeling programs of our choice. In addition, we took into account the advice from the specialists and included QMEAN and QMEANDisCo scores into the evaluation of the structures. The structure refinement was not performed in this cycle due to the lack of computational resources at the time.

Cycle 3: Build

  1. Protein candidates stayed the same as in the previous cycle
  2. Linkers stayed the same as in the previous cycle
  3. Primary structure analysis was not required to be redone
  4. Protein modeling was performed using RoseTTAFold
  5. The modeled structures were evaluated using QMEAN, QMEANDisCo, and VoroMQA scores
  6. The plot was not drawn in this cycle
  7. The structure refinement was not performed in this cycle
  8. The plot was not drawn in this cycle
  9. The distances between active sites in fusion protein systems with rigid linkers were calculated

Cycle 3: Test

The modeled structures were visually satisfactory - the disordered domain of 4CL protein was less disordered in the modeled structure.

Cycle 3: Learn

The multiple sequence alignment (MSA) files have a significant impact on the modeling output.

Cycle 4: Design

According to the output of the third cycle, the fourth engineering cycle was not required. However, after the latter cycle was finished, AlphaFold2[11] became available for public use. Therefore, we decided to apply this highly evaluated tool in our modeling workflow. The structure refinement was not performed in this cycle due to the insignificant impact of MD for structures recorded in the studies[12].

Cycle 4: Build

  1. Protein candidates stayed the same as in the previous cycle
  2. Linkers stayed the same as in the previous cycle
  3. Primary structure analysis was not required to be redone
  4. Protein modeling was performed using AlphaFold2
  5. The modeled structures were evaluated using QMEAN, QMEANDisCo, ProQ2D, ProQRosCenD, ProQRosFAD, ProQ3D scores
  6. The plots were drawn in this cycle
  7. The structure refinement was not performed in this cycle
  8. The distances between active sites in fusion protein systems with rigid linkers were calculated

Cycle 4: Test

The output of the fourth cycle had the less disordered domain just as the output of the third cycle.

Cycle 4: Learn

We were visually satisfied with the modeled complex. Nonetheless, AlphaFold2 models do not require the usage of molecular dynamics for structure refinement, we considered applying them to get a better insight of the system with flexible linkers.

References

1.
Trundle, K. Teaching Science During the Early Childhood Years. National Geographic Learning (2010).
11.
Trundle, K. Teaching Science During the Early Childhood Years. National Geographic Learning (2010).