Biology experiments are hard, and so they go wrong, a lot.
For this reason, it is wise to verify that certain steps are correct whenever possible.
And so this is the first thing we did on the second day!
Gel electrophoresis separates molecules by their charge-to-mass ratio. It is one of those ultra common lab procedures!
This allows us to determine how long are the DNA fragments present in our solution.
Since we know that we amplified the 16S regions which we know the rough size of (there might be a bit of variability across species, but not that much), we were expecting to see a big band at that size.
And that is exactly what we saw!
First we had to prepare the gel, put the gel comb, and pipette the samples into wells present in the gel:
Figure 1.
Gel electrophoresis insert comb.
Source.
Figure 2.
Gel electrophoresis top view with wells visible.
Source.
Figure 3.
Gel electrophoresis pipette sample into wells.
Source.
To see the DNA, we added ethidium bromide to the samples, which is a substance that that both binds to DNA and is fluorescent.
Because it interacts heavily with DNA, ethidium bromide is a mutagen, and the biology people sure did treat the dedicated electrophoresis bench area with respect! Figure 4. "Gel electrophoresis dedicated bench area to prevent ethidium bromide contamination.".
Figure 4.
Gel electrophoresis dedicated bench area to prevent ethidium bromide contamination.
Source.
Figure 5.
Gel electrophoresis dedicated waste bin for centrifuge tubes and pipette tips contaminated with ethidium bromide.
Source.
The UV transilluminator we used to shoot UV light into the gel was the Fisher Scientific UVP LM-26E Benchtop 2UV Transilluminator. The fluorescent substance then emitted a light we can see.
As barely seen at Figure 8. "Fischer Scientific UVP LM-26E Benchtop 2UV Transilluminator illuminated gel." due to bad photo quality due to lack of light, there is one strong green line, which compared to the ladder matches our expected 16S length. What we saw it with the naked eyes was very clear however.
Figure 6.
Fischer Scientific UVP LM-26E Benchtop 2UV Transilluminator
. Source.
Figure 7.
Fischer Scientific UVP LM-26E Benchtop 2UV Transilluminator loading gel.
Source.
Figure 8.
Fischer Scientific UVP LM-26E Benchtop 2UV Transilluminator illuminated gel.
Source.
With all this ready, we opened the Nanopore flow cell, which is the 500 dollar consumable piece that goes in the sequencer.
We then had to pipette the final golden Eppendorf into the flow cell. My anxiety levels were going through the roof: Figure 4. "Oxford nanopore MinION flow cell pipette loading.".
Figure 1.
Oxford nanopore MinION flow cell package.
Source.
Figure 2.
Oxford nanopore MinION flow cell front.
Source.
Figure 3.
Oxford nanopore MinION flow cell back.
Source.
Figure 4.
Oxford nanopore MinION flow cell pipette loading.
Source.
At this point bio people start telling lab horror stories of expensive solutions being spilled and people having to recover them from fridge walls, or of how people threw away golden Eppendorfs and had to pick them out of trash bins with hundreds of others looking exactly the same etc. (but also how some discoveries were made like this). This reminded Ciro of: youtu.be/89UNPdNtOoE?t=919 Alfred Maddock's plutonium spill horror story.
Luckily this time, it worked out!
We then just had to connect the MinION to the computer, and wait for 2 days.
During this time, the DNA would be sucked through the pores.
As can be seen from Video 1. "Oxford Nanopore MinION software channels pannel on Mac." the software tells us which pores are still working.
Figure 5.
Oxford Nanopore MinION connected to a Mac via USB.
Source.
Video 1.
Oxford Nanopore MinION software channels pannel on Mac.
Source.
Pores go bad sooner or later randomly, until there are none left, at which point we can stop the process and throw the flow cell away.
48 hours was expected to be a reasonable time until all pores went bad, and so we called it a day, and waited for an email from the PuntSeq team telling us how things went.
We reached a yield of 16 billion base pairs out of the 30Gbp nominal maximum, which the bio people said was not bad.
Because Ciro's a software engineer, and he's done enough staring in computers for a lifetime already, and he believes in the power of Git, he didn't pay much attention to this part ;-)
According to the eLife paper, the code appears to have been uploaded to: github.com/d-j-k/puntseq. TODO at least mention the key algorithms used more precisely.
Ciro can however see that it does present interesting problems!
Because it was necessary to wait for 2 days to get our data, the workshop first reused sample data from previous collections done earlier in the year to illustrate the software.
First there is some signal processing/machine learning required to do the base calling, which is not trivial in the Oxford Nanopore, since neighbouring bases can affect the signal of each other. This is mostly handled by Oxford Nanopore itself, or by hardcore programmers in the field however.
After the base calling was done, the data was analyzed using computer programs that match the sequenced 16S sequences to a database of known sequenced species.
This is of course not just a simple direct string matching problem, since like any in experiment, the DNA reads have some errors, so the program has to find the best match even though it is not exact.
The PuntSeq team would later upload the data to well known open databases so that it will be preserved forever! When ready, a link to the data would be uploaded to: www.puntseq.co.uk/data
Protocols are the biologist term for "recipe".
I found that a lot of biology comes down to this: get the right recipe, follow it well even though you don't understand all the proprietary details, and pray.

Pinned article: Introduction to the OurBigBook Project

Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
We have two killer features:
  1. topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculus
    Articles of different users are sorted by upvote within each article page. This feature is a bit like:
    • a Wikipedia where each user can have their own version of each article
    • a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
    This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.
    Figure 1.
    Screenshot of the "Derivative" topic page
    . View it live at: ourbigbook.com/go/topic/derivative
  2. local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:
    This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
    Figure 2.
    You can publish local OurBigBook lightweight markup files to either https://OurBigBook.com or as a static website
    .
    Figure 3.
    Visual Studio Code extension installation
    .
    Figure 4.
    Visual Studio Code extension tree navigation
    .
    Figure 5.
    Web editor
    . You can also edit articles on the Web editor without installing anything locally.
    Video 3.
    Edit locally and publish demo
    . Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension.
    Video 4.
    OurBigBook Visual Studio Code extension editing and navigation demo
    . Source.
  3. https://raw.githubusercontent.com/ourbigbook/ourbigbook-media/master/feature/x/hilbert-space-arrow.png
  4. Infinitely deep tables of contents:
    Figure 6.
    Dynamic article tree with infinitely deep table of contents
    .
    Descendant pages can also show up as toplevel e.g.: ourbigbook.com/cirosantilli/chordate-subclade
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact