Difference between revisions of "Team:Uppsala/Transcriptomics/Barcoding-Library Preparation"

 
(25 intermediate revisions by 8 users not shown)
Line 22: Line 22:
  
 
     </head>
 
     </head>
<body>
 
  
  
Line 29: Line 28:
  
  
  <div class="svg-wrapper">
+
 
 +
  <div class="svg-wrapper" id="Project_Description">
  
 
      
 
      
Line 164: Line 164:
 
     <div class="body">
 
     <div class="body">
 
         <div class="parallax"></div>
 
         <div class="parallax"></div>
        <div class="igem-icon"><a href="https://2018.igem.org/Main_Page"><img src="https://static.igem.org/mediawiki/2018/b/b0/T--Uppsala--graylogo.png"></a></div>
+
    <div class="igem-icon"><a href="https://2018.igem.org/Team:Uppsala"><img src="https://static.igem.org/mediawiki/2018/c/cf/T--Uppsala--WormBusterLogo_Black.png"></a></div>
 +
     
 +
        <div class= "content blur-box" style="font-size:16px;">
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
<!-- CONTENT OF WHATS ON THE PAGE -->
 +
 
 +
        <div id="toc" class="toc">
 +
            <div id="toctitle"></div>
 +
            <ul>
 +
                <li class="toclevel tocsection"><a href="#Project_Description" class="scroll"> <span id="whereYouAre"> Transcriptomics  </span> </a>
 +
                        <ul>
 +
                            <li class="toclevel nav-item active"><a href="#Bar" class="nav-link scroll"> Barcoding and Library Preparation</a></li>
 +
                            <li class="toclevel nav-item"><a href="#Exp" class="nav-link scroll">  Experiment</a></li>
 +
                            <li class="toclevel nav-item"><a href="#Res" class="nav-link scroll">  Results</a></li>
 +
                            <li class="toclevel nav-item"><a href="#Disc" class="nav-link scroll">  Discussion</a></li>
 +
                            <li class="toclevel nav-item"><a href="#Conc" class="nav-link scroll">  Conclusion</a></li>
  
        <div class ="scroll-down-button">
+
                            <li class="toclevel nav-item"><a href="#References" class="nav-link scroll"> References </a></li>
            <section id="section02" class="demo">
+
                        </ul>
                <h1></h1>
+
                </li>
                <a href="#scrolldown"><span></span></a>
+
           
             </section>
+
             </ul>
 
         </div>
 
         </div>
        <div class= "content blur-box" style="font-size:16px;">
+
 
 +
 
 +
 
 +
 
 
             <div class ="content-text" id="scrolldown" >
 
             <div class ="content-text" id="scrolldown" >
 +
 +
 +
 +
 
                 <div style="height:5em;"></div>
 
                 <div style="height:5em;"></div>
 
                 <!-- FROM THIS POINT DOWNWARDS YOU START ADDING YOUR STUFF -->
 
                 <!-- FROM THIS POINT DOWNWARDS YOU START ADDING YOUR STUFF -->
 
   
 
   
<div class="card-holder">
+
                <div class="card-holder">
 
+
        <h1>Barcoding and Library Preparation</h1>
+
 
+
                 
+
  
 +
                <h1 id="Bar"> Barcoding and Library Preparation </h1>
  
 
                
 
                
  
<p>Each sequencing technology has its own mechanism of sequencing. Third generation of sequencing uses pores through which nucleic acid strand is pulled through to read the genetic information. In order to assure that nucleic acids pass the pore at correct speed and orientation, adaptors with motor proteins need to be attached to ends of cDNA molecules. Motor protein then anneals to the pore and pulls the molecule through (Oxford Nanopore, 2018). <br><br>
+
                    <p>Each sequencing technology has its own mechanism of sequencing. Third generation of sequencing uses pores through which nucleic acid strand is pulled through to read the genetic information. In order to assure that nucleic acids pass the pore at correct speed and orientation, adaptors with motor proteins need to be attached to ends of cDNA molecules. Motor protein then anneals to the pore and pulls the molecule through [1]. <br><br>
  
Other the adaptors, barcodes are also attached to the cDNA sample. In our application, two different samples are sequenced simultaneously using one flow cell. In order to distinguish which molecule belongs to what sample, barcodes (short DNA fragments with known sequence) are ligated to the cDNA. Subsequent bioinformatic analysis allows sorting the reads according to the barcodes and assign them into two distinct samples.  
+
                        In addition to adaptors, barcodes are also attached to the cDNA sample. In our application, two different samples are sequenced simultaneously using one flow cell. In order to distinguish which molecule belongs to what sample, barcodes (short DNA fragments with known sequence) are ligated to the cDNA. Subsequent bioinformatic analysis allows sorting of the reads according to the barcodes and assign them into two distinct samples.  
</p>  
+
                    </p>  
  
<h2>Experiment</h2>
+
                    <h2 id="Exp">Experiment</h2>
  
<p>Initially, cDNA is treated with Ultra II End Prep (NEB), which performs end-repair and tailing. End-prep assures that all fragments end in blunt ends and that there are no overhangs, end-tailing adds non-template dAMP to 3´end, which is complementary with dT on barcodes, which are ligated in the subsequent step using Blunt/TA ligase. After barcode ligation, adaptors are ligated using Quick T4 Ligation Kit. Library is then ready to be loaded into the flow cell after passing through the checkpoint. </p>
+
                    <p>Initially, cDNA is treated with Ultra II End Prep (NEB), which performs end-repair and tailing. End-prep assures that all fragments end in blunt ends and that there are no overhangs, end-tailing adds non-template dAMP to 3'end, which is complementary with dT on barcodes, which are ligated in the subsequent step using Blunt/TA ligase. After barcode ligation, adaptors are ligated using Quick T4 Ligation Kit. Library is then ready to be loaded into the flow cell after passing through the checkpoint. </p>
  
<h2>Results</h2>
+
                    <h2 id="Res">Results</h2>
<p>At this stage, the limited amount of material limits ways of assuring that the library preparation was successful. Under normal circumstances, it would be possible to check quality of cDNA library with Nanodrop. But due to rather small volume and concentration, it was decided that only quantity will be measured using Qubit ( (as Nanodrop has shown to not being very accurate below concentrations of 30 ng/µl). <b>Table 1</b> shows the usual yield in various steps. </p><br><br>
+
                    <p>At this stage, the limited amount of material limits ways of assuring that the library preparation was successful. Under normal circumstances, it would be possible to check quality of cDNA library with Nanodrop. But due to rather small volume and concentration, it was decided that only quantity will be measured using Qbit (as Nanodrop has shown to not being very accurate below concentrations of 30 ng/µl). Table 1 shows the usual yield in various steps. </p><br><br>
  
<table class=” pgrouptable tablesorter our-table” style=“width: 100%;” cellspacing="15"; cellpadding=“0”>
 
    <thead><tr>
 
<th style= “width: auto”>Step</th>
 
<th style=“width: auto” >Amount [ng]</th>
 
</tr></thead>
 
<tbody><tr>
 
  
<td>
 
Input mRNA (per sample)
 
</td>
 
<td >
 
250
 
</td>
 
</tr><tr>
 
  
<td>
+
                    <p><b>Table 1.</b> Approximate yields of material at various steps of library prep. Values show most common yield that were obtained throughout the different library preparations. Measured by Qubit</p>
Output cDNA (per sample)
+
                    <table class="pgrouptable tablesorter our-table" style="width: 100%;" cellspacing="15" cellpadding="0">
</td>
+
                        <thead><tr>
<td >
+
                    <th style= “width: auto”>Step</th>
550
+
                    <th style=“width: auto” >Amount [ng]</th>
</td>
+
                    </tr></thead>
</tr><tr>
+
                    <tbody><tr>
  
 +
                    <td>
 +
                    Input mRNA (per sample)
 +
                    </td>
 +
                    <td >
 +
                    250
 +
                    </td>
 +
                    </tr><tr>
  
<td>
+
                    <td>
After End-Prep (per sample)
+
                    Output cDNA (per sample)
</td>
+
                    </td>
<td >
+
                    <td >
400
+
                    550
</td>
+
                    </td>
</tr><tr>
+
                    </tr><tr>
  
<td>
 
After barcoding (per sample)
 
</td>
 
<td >
 
350
 
</td>
 
</tr><tr>
 
  
<td>
+
                    <td>
Pooled (both samples)
+
                    After End-Prep (per sample)
</td>
+
                    </td>
<td >
+
                    <td >
700
+
                    400
</td>
+
                    </td>
</tr><tr>
+
                    </tr><tr>
  
 +
                    <td>
 +
                    After barcoding (per sample)
 +
                    </td>
 +
                    <td >
 +
                    350
 +
                    </td>
 +
                    </tr><tr>
  
<td>
+
                    <td>
 +
                    Pooled (both samples)
 +
                    </td>
 +
                    <td >
 +
                    700
 +
                    </td>
 +
                    </tr><tr>
  
Library (both samples)
 
  
</td>
+
                    <td>
<td >
+
350
+
</td>
+
</tr></tbody></table>
+
  
 +
                    Library (both samples)
  
 +
                    </td>
 +
                    <td >
 +
                    350
 +
                    </td>
 +
                    </tr></tbody></table>
  
<!-- End of Code For TABLE -->
 
  
<p><b>Table 1:</b> Approximate yields of material at various steps of library prep. Values show most common yield that were obtained throughout the different library preparations. Measured by Qubit</p><br><br>
 
  
 +
                    <!-- End of Code For TABLE -->
  
<h3>Troubleshooting: Are adaptors/barcodes attached properly?</h3>
+
                    <br><br>
  
<p>During the library prep, usually about 20% of material was lost in the beads purification step. Interestingly, 50% of all material was lost in the final purification of the library. This step should potentially be optimized as this could be one of the reasons for low throughput. </p>
 
  
<h4>Hypothesis</h4>
+
                    <h3>Troubleshooting: Are adaptors/barcodes attached properly?</h3>
<p>It was not certain whether the barcodes and adaptors were attached properly. If some of these steps fails, all the subsequent part would most likely fail as well and therefore lead to low sequencing throughput. In order to test if the library preparation has been done correctly, we prepared a library of standard lambda phage DNA (provided with the kit for troubleshooting). <b>Table 2</b> shows the yields at the various steps. Interestingly, large amount of material is lost at the adaptor ligation step. </p>
+
  
<h4>Result</h4>
+
                    <p>During the library prep, usually about 20% of material was lost in the beads purification step. Interestingly, 50% of all material was lost in the final purification of the library. This step should potentially be optimized as this could be one of the reasons for low throughput. </p>
  
 +
                    <h4>Hypothesis</h4>
 +
                    <p>It was not certain whether the barcodes and adaptors were attached properly. If some of these steps fails, all the subsequent part would most likely fail as well and therefore lead to low sequencing throughput. In order to test if the library preparation has been done correctly, we prepared a library of standard lambda phage DNA (provided with the kit for troubleshooting). Table 2 shows the yields at the various steps. Interestingly, large amount of material is lost at the adaptor ligation step. </p>
  
<br>
+
                 
  
<table class=” pgrouptable tablesorter our-table” style=“width: 100%;” cellspacing="15"; cellpadding=“0” >
 
    <thead><tr>
 
<th style= “width: auto”>Step</th>
 
<th style=“width: auto” >Yield [ng]</th>
 
</tr></thead>
 
<tbody><tr>
 
  
<td>
 
Input gDNA
 
</td>
 
<td >
 
870
 
</td>
 
</tr><tr>
 
  
<td>
+
                    <p><b>Table 2.</b> Yields at the various steps.</p>
After End-prep
+
</td>
+
<td >
+
750
+
</td>
+
</tr><tr>
+
  
 +
                  <table class="pgrouptable tablesorter our-table" style="width: 100%;" cellspacing="15" cellpadding="0">
 +
                    <thead><tr>
 +
                    <th style= “width: auto”>Step</th>
 +
                    <th style=“width: auto” >Yield [ng]</th>
 +
                    </tr></thead>
 +
                    <tbody><tr>
  
<td>
+
                    <td>
Adaptor ligation
+
                    Input gDNA
</td>
+
                    </td>
<td >
+
                    <td >
450
+
                    870
</td>
+
                    </td>
</tr></tbody></table>
+
                    </tr><tr>
  
 +
                    <td>
 +
                    After End-prep
 +
                    </td>
 +
                    <td >
 +
                    750
 +
                    </td>
 +
                    </tr><tr>
  
  
<!-- End of Code For TABLE -->
+
                    <td>
<p><b>Table 1:</b> Yields at the various steps.</p>
+
                    Adaptor ligation
<br>
+
                    </td>
 +
                    <td >
 +
                    450
 +
                    </td>
 +
                    </tr></tbody></table>
  
</div>
 
               
 
               
 
               
 
 
<div class="card-holder">
 
    <div class="content-card-heading">
 
       
 
    </div>
 
                 
 
               
 
               
 
               
 
  
<img src="https://static.igem.org/mediawiki/2018/2/2a/T--Uppsala--library-throughput.png" class="center" height="70%" width="70%">
 
<p align="center"><b>Figure 1:</b> Sequencing throughput. In light green, the actively sewuencing pores are show, dark green are currently empty pores waiting for a molecule, blue and other pores are inactive.</p><br><br>
 
<p> Results in <b>figure 1</b> suggest that there is relatively small amount of DNA (low sequencing throughput), which can be caused by loss of material during the bead purification step.</p><br>
 
  
<img src="https://static.igem.org/mediawiki/2018/b/b9/T--Uppsala--library-quality.png" class="center" height="70%" width="70%">
+
                    <!-- End of Code For TABLE -->
<p align="center"><b>Figure 2:</b> Quality score of obtained reads.</p><br><br>
+
                    <br>
  
 +
                    </div>
  
<p>Graph shown in <b>figure 2</b> shows that reads are of high quality. In our actual sequencing runs, reads were always of very low quality. This result suggests that low quality / amount of passed reads is most likely due to input material (cDNA library) rather than to the library preparation itself. </p>
 
  
<h4>Discussion</h4>
 
  
  
<p>We have seen that when library from genomic DNA is performed, sequencing is of decent quality. The throughput is also rather low, but quality of reads is high, something that has never been achieved with our library. We can therefore assume that in general, library preparation has one issue which is common across all experiments. The issue is most likely loss of material during bead purification which leads to lower throughout as not all pores are occupied at all times. </p>
+
                    <div class="card-holder">
 +
                        <div class="content-card-heading">
  
<h2>Discussion</h2>
+
                        </div>
  
<p>Library preparation is a complex procedure involving multiple enzymes and purification steps. Decreased efficiency of library preparation can be due to malfunctioning of any of the steps. The major issue in prepared libraries has been low sequencing throughput and low quality of reads. We have therefore tested if the issue is somehow connected to our samples or to the actual library prep. Since preparing library from supplied phage DNA was successful (high quality reads, decent throughput), we concluded that the issue was in fact in our input material. This has later proven to be true due to RNA contamination of the libraries as described in cDNA synthesis. <br><br>
 
  
Even with RNA contamination as the potential explanation for low quality reads (RNA is being sequenced using algorithm for DNA and therefore the bases are not being recognized) the problem of low throughput persisted. Major losses are seen during the library prep (up to 75%). According to Oxford Nanopore, this loss is expected, Question is whether it would be worth to increase input material above the recommendation of a manufacturer to achieve higher throughput. <br><br>
 
 
Sequencing using Oxford Nanopore has been used mainly for long fragments of genomic DNA. In our application we aimed to sequenced very short reads (average about 1 kb) of cDNA. As this application is relatively new, we assume the process might not be fully optimized (eg. retention of small fragments by beads, amount of input library, etc.) for our application. <br><br>
 
  
Additional troubleshooting would need to be performed to adjust the protocols provided by Oxford Nanopore to our application, which was unfortunately not possible in the course of this project due to budgetary and time restrictions. </p>
 
  
<h2>Conclusion</h2>
 
  
<p>Most issues connected with low sequencing throughput link back to contamination of the library with RNA. If this issue was to be removed, sequencing in sufficient throughput and quality would be possible as shown on the example of sequencing lambda phage gDNA.<br></p>
+
                    <img src="https://static.igem.org/mediawiki/2018/2/2a/T--Uppsala--library-throughput.png" class="center" height="70%" width="70%">
 +
                    <p align="center"><b>Figure 1.</b> Sequencing throughput. In light green, the actively sewuencing pores are show, dark green are currently empty pores waiting for a molecule, blue and other pores are inactive.</p><br><br>
 +
                    <p> Results in figure 1 suggest that there is relatively small amount of DNA (low sequencing throughput), which can be caused by loss of material during the bead purification step.</p><br>
 +
 
 +
                    <img src="https://static.igem.org/mediawiki/2018/b/b9/T--Uppsala--library-quality.png" class="center" height="70%" width="70%">
 +
                    <p align="center"><b>Figure 2.</b> Quality score of obtained reads.</p><br><br>
 +
 
 +
 
 +
                    <p>Graph shown in figure 2 shows that reads are of high quality. In our actual sequencing runs, reads were always of very low quality. This result suggests that low quality/amount of passed reads is most likely due to input material (cDNA library) rather than to the library preparation itself. </p>
 +
 
 +
                   
 +
 
 +
 
 +
                    <p>We have seen that when library from genomic DNA is performed, sequencing is of decent quality. The throughput is also rather low, but quality of reads is high, something that has never been achieved with our library. We can therefore assume that in general, library preparation has one issue which is common across all experiments. The issue is most likely loss of material during bead purification which leads to lower throughout as not all pores are occupied at all times. </p>
 +
 
 +
                    <h2 id="Disc">Discussion</h2>
 +
 
 +
                    <p>Library preparation is a complex procedure involving multiple enzymes and purification steps. Decreased efficiency of library preparation can be due to malfunctioning of any of the steps. The major issue in prepared libraries has been low sequencing throughput and low quality of reads. We have therefore tested if the issue is somehow connected to our samples or to the actual library prep. Since preparing library from supplied phage DNA was successful (high quality reads, decent throughput), we concluded that the issue was in fact in our input material. This has later proven to be true due to RNA contamination of the libraries as described in cDNA synthesis. <br><br>
 +
 
 +
                    Even with RNA contamination as the potential explanation for low quality reads (RNA is being sequenced using algorithm for DNA and therefore the bases are not being recognized) the problem of low throughput persisted. Major losses are seen during the library prep (up to 75%). According to Oxford Nanopore, this loss is expected, Question is whether it would be worth to increase input material above the recommendation of the manufacturer to achieve higher throughput. <br><br>
 +
 
 +
                    Sequencing using Oxford Nanopore has been used mainly for long fragments of genomic DNA. In our application we aimed to sequence very short reads (average about 1 kb) of cDNA. As this application is relatively new, we assume the process might not be fully optimized (eg. retention of small fragments by beads, amount of input library, etc.) for our application. <br><br>
 +
 
 +
                    Additional troubleshooting would need to be performed to adjust the protocols provided by Oxford Nanopore to our application, which was unfortunately not possible in the course of this project due to budgetary and time restrictions. </p>
 +
 
 +
                    <h2 id="Conc">Conclusion</h2>
 +
 
 +
                    <p>Most issues connected with low sequencing throughput link back to contamination of the library with RNA. If this issue was to be removed, sequencing in sufficient throughput and quality would be possible as shown on the example of sequencing lambda phage gDNA.<br></p>
  
<h1>References</h1>
 
  
<p><b>[1]</b> Oxford Nanopore, DNA: nanopore sequencing, [online], 2018, https://nanoporetech.com/applications/dna-nanopore-sequencing</p><br>
 
  
  
 
                 </div>
 
                 </div>
 +
 +
<div class="card-holder">
 +
<h2 id="References">References</h2>
 +
 +
<p><b>[1]</b> Oxford Nanopore, DNA: nanopore sequencing, [online], 2018, <a href="https://nanoporetech.com/applications/dna-nanopore-sequencing">https://nanoporetech.com/applications/dna-nanopore-sequencing</a></p><br>
 +
</div>
 +
 +
 +
 +
 
                 <!-- HERE ENDS THE PORTION WHERE YOU PUT IN YOUR CONTENT-->
 
                 <!-- HERE ENDS THE PORTION WHERE YOU PUT IN YOUR CONTENT-->
 
                 <div style="height:5em;"></div>
 
                 <div style="height:5em;"></div>
Line 368: Line 406:
 
         </div>
 
         </div>
 
     </div>
 
     </div>
    </body>
 
 
</html>
 
</html>

Latest revision as of 16:13, 3 December 2018