Difference between revisions of "Team:Uppsala/Transcriptomics/Sequencing"
Elinramstrom (Talk | contribs) |
|||
| Line 675: | Line 675: | ||
<p>An ideal sequencing run would mean that a lot of the material (depending on run time) has been read and converted into large amounts of ”passed reads” data files containing lines and lines of base sequences. However during our multiple sequencing runs a couple of re-emergin issues consistently showed up, therefore a lot of time was dedicated to troubleshooting this. It was later hypothesized that the source of poor sequencing was because of mRNA left in the samples due to inadequate reverse transcription. See cDNA synthesis </p> | <p>An ideal sequencing run would mean that a lot of the material (depending on run time) has been read and converted into large amounts of ”passed reads” data files containing lines and lines of base sequences. However during our multiple sequencing runs a couple of re-emergin issues consistently showed up, therefore a lot of time was dedicated to troubleshooting this. It was later hypothesized that the source of poor sequencing was because of mRNA left in the samples due to inadequate reverse transcription. See cDNA synthesis </p> | ||
| − | <h3>Low | + | <h3>Low Throughput</h3> |
<p>Because it is impossible to have a 100% purely adaptor ligated mRNA sample we initially decided on that it would be acceptable to run the sequencing for a longer time with a below average throughput. However it was noted during repeated sequencing runs that the throughput was actually sub-par, showing that something in the sample(s) was consistently clogging the pores. This meant that only a fraction of our total material was actually being sequenced, eventually leading to near-zero throughputs.</p> | <p>Because it is impossible to have a 100% purely adaptor ligated mRNA sample we initially decided on that it would be acceptable to run the sequencing for a longer time with a below average throughput. However it was noted during repeated sequencing runs that the throughput was actually sub-par, showing that something in the sample(s) was consistently clogging the pores. This meant that only a fraction of our total material was actually being sequenced, eventually leading to near-zero throughputs.</p> | ||
| − | <h3>Failed | + | <h3>Failed Reads</h3> |
<p>Another reoccuring theme was the issues with ”failed” reads. A failed read consitutes a failed characterization of the base passing through the pores, effectively discarding it. What this means is that whatever came through the pore was actually not cDNA but something foreign.<p><br> | <p>Another reoccuring theme was the issues with ”failed” reads. A failed read consitutes a failed characterization of the base passing through the pores, effectively discarding it. What this means is that whatever came through the pore was actually not cDNA but something foreign.<p><br> | ||
Revision as of 22:21, 17 October 2018
Sequencing
Sequencing is the final step of the journey and generally makes up a lot of different and varying methods with the common purpose of determining the primary atomic-level structure of what you’re interested in, resulting in sequences of bases making it all up. Most often this includes proteins, polymers or as in our case the keys to life: genetic material; enabling us to read it like a book of sorts.
Oxford Nanopore’s MinION third generation sequencing device makes use of nano-sized holes called nanopores with an applied voltage across them. In essence: when you’re material of choice passes through one of this pores, each base fluctuates this current by a given amount which acts as a fingerprint to identify the given base [1].
Figure 1. The MinION device.
Experiment
Sequencing the final library-prepped RNA includes three primary steps: Priming, loading and sequencing.
Priming the Flowcell
The flow cell is essentially where the magic happens. Before the sequencing can take place, a type of storing liquid which protects the flow cell has to be emptied and replaced with a mixture that primes the flow cell, essentially making it ready to sequence. A scan is also performed during this step which tells you how many pores are actually working.
Loading the Flowcell
Loading the flow cell is a bit tricky, as the wrong action can completely destroy the whole cell. By sucking up the primer mixture carefully with a pipette through a disposal vent, a kind of suction is created over the actuall pore-membrane area which lets you (with some quick manouvering skills) drop by drop load your sample into that chamber with the help of a pipette which sucks it all down.
Being to slow in this process can result in bubbles forming across the membrane which effectively kills all of the pores.
Sequencing
At this step the sequencing can be started, as the software essentially takes care of everything!
Result
Down below are some example pictures from one of our sequencing runs, giving a clue as of what kind of information that can be gathered.
Figure 2. State of the sequencing pores after a full sequencing. Notice the amount of sequencing pores (light green) dropping off as issues like saturation (black, orange) start to increase.
Figure 3. Passed versus failed reads.
Figure 4. Distribution of read lengths.
Figure 5. Quality score distribution for the different read lengths, were a quality score of at least 7 is acceptable.
Down below are the total of all of our sequencing runs summarised with each run showing runtime, reads, read bases as well as an attached quality score distribution.
Run 1
| Runtime (D:HH:MM) | Reads (k) [ng] | Bases (MB) |
|---|---|---|
| 0:01:37 | 20.21 | 9.26 |
Run 2
| Runtime (D:HH:MM) | Reads (k) [ng] | Bases (MB) |
|---|---|---|
| 0:00:22 | 10.36 | 3.92 |
Run 3
| Runtime (D:HH:MM) | Reads (k) [ng] | Bases (MB) |
|---|---|---|
| 0:01:05 | 52.9 | 8.2 |
Run 4
| Runtime (D:HH:MM) | Reads (k) [ng] | Bases (MB) |
|---|---|---|
| 0:00:33 | 9.57 | 2.4 |
Run 5
| Runtime (D:HH:MM) | Reads (k) [ng] | Bases (MB) |
|---|---|---|
| 0:01:35 | 33.98 | 6.29 |
Conclusion
An ideal sequencing run would mean that a lot of the material (depending on run time) has been read and converted into large amounts of ”passed reads” data files containing lines and lines of base sequences. However during our multiple sequencing runs a couple of re-emergin issues consistently showed up, therefore a lot of time was dedicated to troubleshooting this. It was later hypothesized that the source of poor sequencing was because of mRNA left in the samples due to inadequate reverse transcription. See cDNA synthesis
Low Throughput
Because it is impossible to have a 100% purely adaptor ligated mRNA sample we initially decided on that it would be acceptable to run the sequencing for a longer time with a below average throughput. However it was noted during repeated sequencing runs that the throughput was actually sub-par, showing that something in the sample(s) was consistently clogging the pores. This meant that only a fraction of our total material was actually being sequenced, eventually leading to near-zero throughputs.
Failed Reads
Another reoccuring theme was the issues with ”failed” reads. A failed read consitutes a failed characterization of the base passing through the pores, effectively discarding it. What this means is that whatever came through the pore was actually not cDNA but something foreign.
Even though some progress was made creating read-data that passed, the amount of data as well as the issue with consistency in form of duplicate or triplicate sequencing runs made it deemed as not significant enough to carry over to the bioinformatics.
References
[1] Oxford Nanopore, 2018. How does Nanopore DNA/RNA sequencing work? https://nanoporetech.com/how-it-works Date of visit 2018-10-15