Identification of the micro-organisms in a beer using Nanopore sequencing

Overview
Creative Commons License: CC-BY Questions:
  • How can yeast strains in a beer sample be identified?

  • How can we process metagenomic data sequenced using Nanopore?

Objectives:
  • Inspect metagenomics data

  • Run metagenomics tools

  • Identify yeast species contained in a sequenced beer sample using DNA

  • Visualize the microbiome community of a beer sample

Requirements:
Time estimation: 1 hour
Level: Introductory Introductory
Supporting Materials:
Published: Sep 29, 2022
Last modification: Jun 14, 2024
License: Tutorial Content is licensed under Creative Commons Attribution 4.0 International License. The GTN Framework is licensed under MIT
purl PURL: https://gxy.io/GTN:T00384
rating Rating: 4.5 (2 recent ratings, 5 all time)
version Revision: 4

What is a microbiome? It is a collection of small living creatures. These small creatures are called micro-organisms and they are everywhere. In our gut, in the soil, on vending machines, and even inside the beer. Most of these micro-organisms are actually very good for us, but some can make us very ill.

Micro-organisms come in different shapes and sizes, but they have the same components. One crucial component is the DNA, the blueprint of life. The DNA encodes the shape and size and many other characteristics unique to a species. Because DNA is so species-specific, reading the DNA can be used to identify what kind of micro-organism the it is from. Therefore, within a metagenomic specimen, e.g. a sample form soil, gut, or beer, one can identify what kind of species are inside the sample.

In this tutorial, we will use data of beer microbiome generated via the BeerDEcoded project.

The BeerDEcoded Project is a series of workshops organized with and for schools as well as the general audience, aiming to introduce biology and genomic science. People learn in an interactive way about DNA, sequencing technologies, bioinformatics, open science, how these technologies and concepts are applied and how they are impacting their daily life.

Beer is alive and contains many microorganisms. It can be found in many places and there are many of them. It is a fun media to bring the people to the contact of molecular biology, data-analysis, and open science.

A BeerDEcoded workshop includes the following steps:

  1. Extract yeasts and their DNA from beer bottle,
  2. Sequence the extracted DNA using a MinION sequencer to obtain the sequence of bases/nucleotides (A, T, C and G) for each DNA fragment in the sample,
  3. Analyze the sequenced data in order to know which organisms this DNA is from

The image represents a BeerDEcoded workshop. On the left, there is a beer glass. An arrow goes from the bottle to DNA with "Extraction" written on the below. An arrow goes from DNA to DNA sequences with "Sequencing" written on the below. An arrow goes from the DNA sequences to Yeasts with "Data analysis" written on the below.

Comment: Beer microbiome

Beer is alive! It contains microorganisms, in particular yeasts.

Indeed, grain and water create a sugary liquid (called wort). The beer brewer adds yeasts to it. By eating the sugar, yeast creates alcohol, and other compounds (esters, phenols, etc.) that give beer its particular flavor.

Yeasts are microorganisms, more precisely unicellular fungi. The majority of beers use a yeast genus called Saccharomyces, which in Greek means “sugar fungus”. Within that genus, two specific species of Saccharomyces are the most commonly used:

  • Saccharomyces cerevisiae: a top-fermenting (i.e. yeast which rise up to the top of the beer as it metabolizes sugars, delivering alcohol as a by-product), ale yeast responsible for a huge range of beer styles like witbiers, stouts, ambers, tripels, saisons, IPAs, and many more. It is most likely the yeast that the early brewers were inadvertently brewing with over 3,000 years ago.
  • Saccharomyces pastorianus: a bottom-fermenting (i.e. it sits on the bottom of the tank as it ferments) lager yeast, responsible for beer styles like Pilsners, lagers, märzens, bocks, and more. This yeast was originally found, and cultivated, by Bavarian brewers a little over 200 years ago. It is the most commonly used yeast in terms of the raw amount of beer produced around the world.

Since yeast is all around us, we can actually brew spontaneously fermented beer by using wild yeasts and souring microbiota floating through the air.

During one BeerDEcoded workshop, we extracted yeasts out of a bottle of Chimay. We then extracted the DNA of these yeasts and sequenced it using a MinION to obtain the DNA sequences. Now, we would like to identify the yeast species sequenced there, and thereby outline the diversity of microorganisms (the microbiome community) in the beer sample.

To get this information, we need to process the sequenced data in a few steps:

  1. Check the quality of the data
  2. Assign a taxonomic label, i.e. assign ‘species’ to each sequence
  3. Visualize the distribution of the different species

This type of data analysis requires running several bioinformatics tools and usually requires a computer science background. Galaxy is an open-source platform for data analysis that enables anyone to use bioinformatics tools through its graphical web interface, accessible via any Web browser.

So, in this tutorial, we will use Galaxy to extract and visualize the community of yeasts from a bottle of beer.

Agenda

In this tutorial, we will cover:

  1. Prepare Galaxy and data
    1. Get familiar with Galaxy
    2. Get data
  2. Data quality
    1. Assess data quality
    2. Improve the dataset quality
  3. Assign taxonomic classification
  4. Visualize the community
  5. Investigate the beer microbiome
  6. (Optional) Sharing your history
  7. Conclusion

Prepare Galaxy and data

First of all, this tutorial will get you hands on with some basic Galaxy tasks, including creating a history and importing data.

Get familiar with Galaxy

Hands-on: Open Galaxy
  1. Open your favorite browser (Works on Chrome, Firefox, Safari but not Internet Explorer!)
  2. Create a Galaxy account if you do not have one

    1. To create an account at any public Galaxy instance, choose your server from the available list of Galaxy Platforms.

      There are several UseGalaxy servers:

    2. Click on “Login or Register” in the masthead on the server.

      Login or Register on the top panel

    3. On the login page, find the Register here link and click on it.

    4. Fill in the the registration form, then click on Create.

      Your account should now get created, but will remain inactive until you verify the email address you provided in the registration form.

      Banner warning about account with unverified email address

    5. Check for a Confirmation Email in the email you used for account creation.

      Missing? Check your Trash and Spam folders.

    6. Click on the Email confirmation link to fully activate your account.

      galaxy-info Delivery of the confimation email is blocked by your email provider or you mistyped the email address in the registration form?

      Please do not register again, but follow the instructions to change the email address registered with your account! The confirmation email will be resent to your new address once you have changed it.

      Trouble logging in later? Account email addresses and public names are caSe-sensiTive. Check your activation email for formats.

The Galaxy homepage is divided into three panels:

  • Tools on the left
  • Viewing panel in the middle
  • History of analysis and files on the right
Galaxy interface screenshot showing history panel on the right, tools panel on the left, and main panel at the center. Open image in new tab

Figure 1: The Galaxy interface

The first time you use Galaxy, there will be no files in your history panel.

Any analysis should get its own Galaxy history. So let’s start by creating a new one:

Hands-on: Prepare the Galaxy history
  1. Create a new history for this analysis

    To create a new history simply click the new-history icon at the top of the history panel:

    UI for creating new history

  2. Rename the history

    1. Click on galaxy-pencil (Edit) next to the history name (which by default is “Unnamed history”)
    2. Type the new name
    3. Click on Save
    4. To cancel renaming, click the galaxy-undo “Cancel” button

    If you do not have the galaxy-pencil (Edit) next to the history name (which can be the case if you are using an older version of Galaxy) do the following:

    1. Click on Unnamed history (or the current name of the history) (Click to rename history) at the top of your history panel
    2. Type the new name
    3. Press Enter

Get data

Before we can begin any Galaxy analysis, we need to upload the input data: FASTQ files

Hands-on: Upload your dataset
  1. Import the sequenced data including fastq in the name

    • Option 1 video: Your own local data using Upload Data (recommended for 1-10 datasets).

      1. Click on Upload Data on the top of the left panel
      2. Click on Choose local file and select the files or drop the files in the Drop files here part
      3. Click on Start
      4. Click on Close

    • Option 2: From Zenodo, an external server, via URL

      https://zenodo.org/record/7093173/files/ABJ044_c38189e89895cdde6770a18635db438c8a00641b.fastq
      
      • Copy the link location
      • Click galaxy-upload Upload Data at the top of the tool panel

      • Select galaxy-wf-edit Paste/Fetch Data
      • Paste the link(s) into the text field

      • Press Start

      • Close the window

    Your uploaded file is now in your current history. When the file is fully uploaded to Galaxy, it will turn green. But, what is this file?

  2. Click on the galaxy-eye (eye) icon next to the dataset name to look at the file contents.

The contents of the file will be displayed in the central Galaxy panel.

This file contains the sequences, also called reads, of DNA, i.e. succession of nucleotides, for all fragments from the yeasts in the beer, in FASTQ format.

Although it looks complicated (and maybe it is), the FASTQ format is easy to understand with a little decoding. Each read, representing a fragment of DNA, is encoded by 4 lines:

Line Description
1 Always begins with @ followed by the information about the read
2 The actual nucleic sequence
3 Always begins with a + and contains sometimes the same info in line 1
4 Has a string of characters which represent the quality scores associated with each base of the nucleic sequence; must have the same number of characters as line 2

So for example, the first sequence in our file is:

@03dd2268-71ef-4635-8bce-a42a0439ba9a runid=8711537cc800b6622b9d76d9483ecb373c6544e5 read=252 ch=179 start_time=2019-12-08T11:54:28Z flow_cell_id=FAL10820 protocol_group_id=la_trappe sample_id=08_12_2019
AGTAAGTAGCGAACCGGTTTCGTTTGGGTGTTTAACCGTTTTCGCATTTATCGTGAAACGCTTTCGCGTTTTCGTGCGGAAGGCGCTTCACCCAGGGCCTCTCATGCTTTGTCTTCCTGTTTATTCAGGATCGCCCAAAGCGAGAATCATACCACTAGACCACACGCCCGAATTATTGTTGCGTTAATAAGAAAAGCAAATATTTAAGATAGGAAGTGATTAAAGGGAATCTTCTACCAACAATATCCATTCAAATTCAGGCA
+
$'())#$$%#$%%'-$&$%'%#$%('+;<>>>18.?ACLJM7E:CFIMK<=@0/.4<9<&$007:,3<IIN<3%+&$(+#$%'$#$.2@401/5=49IEE=CH.20355>-@AC@:B?7;=C4419)*$$46211075.$%..#,529,''=CFF@:<?9B522.(&%%(9:3E99<BIL?:>RB--**5,3(/.-8B>F@@=?,9'36;:87+/19BAD@=8*''&''7752'$%&,5)AM<99$%;EE;BD:=9<@=9+%$

It means that the fragment named @03dd2268-71ef-4635-8bce-a42a0439ba9a (ID given in line1) corresponds to:

  • the DNA sequence AGTAAGTAGCGAACCGGTTTCGTTTGGGTGTTTAACCGTTTTCGCATTTATCGTGAAACGCTTTCGCGTTTTCGTGCGGAAGGCGCTTCACCCAGGGCCTCTCATGCTTTGTCTTCCTGTTTATTCAGGATCGCCCAAAGCGAGAATCATACCACTAGACCACACGCCCGAATTATTGTTGCGTTAATAAGAAAAGCAAATATTTAAGATAGGAAGTGATTAAAGGGAATCTTCTACCAACAATATCCATTCAAATTCAGGCA (line2)
  • this sequence has been sequenced with a quality $'())#$$%#$%%'-$&$%'%#$%('+;<>>>18.?ACLJM7E:CFIMK<=@0/.4<9<&$007:,3<IIN<3%+&$(+#$%'$#$.2@401/5=49IEE=CH.20355>-@AC@:B?7;=C4419)*$$46211075.$%..#,529,''=CFF@:<?9B522.(&%%(9:3E99<BIL?:>RB--**5,3(/.-8B>F@@=?,9'36;:87+/19BAD@=8*''&''7752'$%&,5)AM<99$%;EE;BD:=9<@=9+%$ (line 4).

But what does this quality score mean?

The quality score for each sequence is a string of characters, one for each base of the nucleotide sequence, used to characterize the probability of misidentification of each base. The score is encoded using the ASCII character table (with some historical differences):

Encoding of the quality score with ASCII characters for different Phred encoding. The ascii code sequence is shown at the top with symbols for 33 to 64, upper case letters, more symbols, and then lowercase letters. Sanger maps from 33 to 73 while solexa is shifted, starting at 59 and going to 104. Illumina 1.3 starts at 54 and goes to 104, Illumina 1.5 is shifted three scores to the right but still ends at 104. Illumina 1.8+ goes back to the Sanger except one single score wider. Illumina

So there is an ASCII character associated with each nucleotide, representing its Phred quality score, the probability of an incorrect base call:

Phred Quality Score Probability of incorrect base call Base call accuracy
10 1 in 10 90%
20 1 in 100 99%
30 1 in 1000 99.9%
40 1 in 10,000 99.99%
50 1 in 100,000 99.999%
60 1 in 1,000,000 99.9999%

Data quality

Assess data quality

Before starting to work on our data, it is necessary to assess its quality. This is an essential step if we aim to obtain a meaningful downstream analysis.

FastQC is one of the most widely used tools to check the quality of data generated by High Throughput Sequencing (HTS) technologies.

Hands-on: Quality check
  1. FASTQC ( Galaxy version 0.73+galaxy0) with the following parameters
    • param-file “Raw read data from your current history”: Reads
  2. Inspect the generated HTML file
Question

Given the Basic Statistics table on the top of the page:

Screenshot of the FastQC Basic Statistics with filename, file type (Conventional base calls), encoding (Sanger / Illumina 1.9), total Sequences (1876), sequences flagged as poor quality (0), sequence length (130-2327) and %GC (29).

  1. How many sequences are in the FASTQ file?
  2. How long are the sequences?
  1. There are 1876 sequences.
  2. The sequences range from 130 nucleotides to 2327 nucleotides. Not all sequences have then the same length.

FastQC provides information on various parameters, such as the range of quality values across all bases at each position:

FastQC Per base sequence quality with scores below 20. Open image in new tab

Figure 2: Per base sequence quality. X-axis: position in the reads (in base pair). Y-axis: quality score, between 0 and 40 - the higher the score, the better the base call. For each position, a boxplot is drawn with: the median value, represented by the central red line;the inter-quartile range (25-75%), represented by the yellow box; the 10% and 90% values in the upper and lower whiskers; and the mean quality, represented by the blue line. The background of the graph divides the y-axis into very good quality scores (green), scores of reasonable quality (orange), and reads of poor quality (red).

We can see that the quality of our sequencing data grows after the first few bases, stays around a score of 18 and then decreases again at the end of the sequences. MinION and Oxford Nanopore Technologies (ONT) are known to have a higher error rate compared to other sequencing techniques and platforms (Delahaye and Nicolas 2021).

For more detailed information about the other plots in the FASTQC report, check out our dedicated tutorial.

Improve the dataset quality

In order to improve the quality of our data, we will use two tools:

  • porechop (Wick 2017) to remove adapters that were added for sequencing and chimera (contaminant)
  • fastp (Chen et al. 2018) to filter sequences with low quality scores (below 10)
Hands-on: Improve the dataset quality
  1. Porechop ( Galaxy version 0.2.4+galaxy0) with the following parameters:
    • param-file “Input FASTA/FASTQ”: Reads
    • “Output format for the reads”: fastq
  2. fastp ( Galaxy version 0.23.2+galaxy0) with the following parameters:
    • “Single-end or paired reads”: Single-end
      • param-file “Input 1”: output of Porechop
      • In “Adapter Trimming Options”:
        • “Disable adapter trimming”: Yes
    • In “Filter Options”:
      • In “Quality filtering options”:
        • “Qualified quality phred”: 10
    • In “Read Modification Options”:
      • “PolyG tail trimming”: Disable polyG tail trimming
  3. Inspect the HTML report of fastp to see how the quality has been improved
Question
  1. How many sequences are there before filtering? Is it the same number as in FASTQC report?
  2. How many sequences are there after filtering? How many sequences have then been removed by filtering?
  3. What is the mean length before filtering? And after filtering?
  1. There are 1,869 reads before filtering. The number is lower than in the FASTQC report. Some reads may have been discarded via Porechop
  2. There are 1,350 reads after filtering. So the filtering step has removed \(1869-1350 = 519\) sequences.
  3. The mean length is 314 nucleotide before filtering and 316bp after filtering.

Assign taxonomic classification

One of the main aims in microbiome data analysis is to identify the organisms sequenced. For that we try to identify the taxon to which each individual read belong.

Taxonomy is the method used to naming, defining (circumscribing) and classifying groups of biological organisms based on shared characteristics such as morphological characteristics, phylogenetic characteristics, DNA data, etc. It is founded on the concept that the similarities descend from a common evolutionary ancestor.

Defined groups of organisms are known as taxa. Taxa are given a taxonomic rank and are aggregated into super groups of higher rank to create a taxonomic hierarchy. The taxonomic hierarchy includes eight levels: Domain, Kingdom, Phylum, Class, Order, Family, Genus and Species.

Example of taxonomy. It starts, top to bottom, with Kingdom "Animalia", Phylum "Chordata", Class "Mammalia", and Order "Carnivora". Then it splits in 3. On the left, Family "Felidae", with 2 genus "Felis" and "Panthera" and below 3 species "F. catus" and "F. pardalis" below "Felis", "P. pardus" below "Panthera". In the middle, Family "Canidae", genus "Canis" and 2 species "C. familiaris" and "C. lupus". On the right, Family "Ursidae", Genus "Ursus" and 2 species "U. arctos" and "U. horribilus". Below each species is a illustration of the species

The classification system begins with 3 domains that encompass all living and extinct forms of life

  • The Bacteria and Archae are mostly microscopic, but quite widespread.
  • Domain Eukarya contains more complex organisms

When new species are found, they are assigned into taxa in the taxonomic hierarchy. For example for the cat:

Level Classification
Domain Eukaryota
Kingdom Animalia
Phylum Chordata
Class Mammalia
Order Carnivora
Family Felidae
Genus Felis
Species F. catus

From this classification, one can generate a tree of life, also known as a phylogenetic tree. It is a rooted tree that describes the relationship of all life on earth. At the root sits the “last universal common ancestor” and the three main branches (in taxonomy also called domains) are bacteria, archaea and eukaryotes. Most important for this is the idea that all life on earth is derived from a common ancestor and therefore when comparing two species, you will -sooner or later- find a common ancestor for all of them.

Let’s explore taxonomy in the Tree of Life, using Lifemap

Question
  1. Which microorganisms do we expect to identify in our data?
  2. What is the taxonomy of the main expected microorganism?
  1. The sequences are supposed to be yeasts extracted from a bottle of beer. The majority of beers contain a yeast genus called Saccharomyces and 2 species in that genus: Saccharomyces cerevisiae (ale yeast) and Saccharomyces pastorianus (lager yeast). The used beer is an ale beer, so we expect to find Saccharomyces cerevisiae. But other yeasts can also have been used and then found. We could also have some DNA left from other beer components, but also contaminations by other microorganisms and even human DNA from people who manipulated the beer or did the extraction.

  2. The main expected microorganism is Saccharomyces cerevisiae with its taxonomy:

    Level Classification
    Domain Eukaryota
    Kingdom Fungi
    Phylum Ascomycota
    Class Saccharomycetes
    Order Saccharomycetales
    Family Saccharomycetaceae
    Genus Saccharomyces
    Species S. cerevisiae

Taxonomic assignment or classification is the process of assigning an Operational Taxonomic Unit (OTUs, that is, groups of related individuals / taxon) to sequences. To assign an OTU to a sequence it is compared against a database, but this comparison can be done in different ways, with different bioinformatics tools. Here we will use Kraken2 (Wood et al. 2019).

In the \(k\)-mer approach for taxonomy classification, we use a database containing DNA sequences of genomes whose taxonomy we already know. On a computer, the genome sequences are broken into short pieces of length \(k\) (called \(k\)-mers), usually 30bp.

Kraken examines the \(k\)-mers within the query sequence, searches for them in the database, looks for where these are placed within the taxonomy tree inside the database, makes the classification with the most probable position, then maps \(k\)-mers to the lowest common ancestor (LCA) of all genomes known to contain the given \(k\)-mer.

Kraken2

Kraken2 uses a compact hash table, a probabilistic data structure that allows for faster queries and lower memory requirements. It applies a spaced seed mask of s spaces to the minimizer and calculates a compact hash code, which is then used as a search query in its compact hash table; the lowest common ancestor (LCA) taxon associated with the compact hash code is then assigned to the k-mer.

You can find more information about the Kraken2 algorithm in the paper Improved metagenomic analysis with Kraken 2.

Hands-on: Kraken2
  1. Kraken2 ( Galaxy version 2.1.1+galaxy1) with the following parameters:
    • “Single or paired reads”: Single
      • param-file “Input sequences”: Output of fastp
    • “Print scientific names instead of just taxids”: Yes
    • In “Create Report”:
      • “Print a report with aggregrate counts/clade to file”: Yes
    • “Select a Kraken2 database”: Prebuilt Refseq indexes: PlusPF

      The database here contains reference sequences and taxonomies. We need to be sure it contains yeasts, i.e. fungi.

  2. Inspect the report file

The Kraken report is a tabular files with one line per taxon and 6 columns or fields:

  1. Percentage of fragments covered by the clade rooted at this taxon
  2. Number of fragments covered by the clade rooted at this taxon
  3. Number of fragments assigned directly to this taxon
  4. A rank code, indicating
    • (U)nclassified
    • (R)oot
    • (D)omain
    • (K)ingdom
    • (P)hylum
    • (C)lass
    • (O)rder
    • (F)amily
    • (G)enus, or
    • (S)pecies

    Taxa that are not at any of these 10 ranks have a rank code that is formed by using the rank code of the closest ancestor rank with a number indicating the distance from that rank. E.g., G2 is a rank code indicating a taxon is between genus and species and the grandparent taxon is at the genus rank.

  5. NCBI taxonomic ID number
  6. Indented scientific name
Column 1	Column 2	Column 3	Column 4	Column 5	Column 6
38.00 	513 	513 	U 	0 	unclassified
62.00 	837 	1 	R 	1 	root
61.93 	836 	27 	R1 	131567 	cellular organisms
56.00 	756 	3 	D 	2759 	Eukaryota
55.33 	747 	3 	D1 	33154 	Opisthokonta
29.78 	402 	0 	K 	33208 	Metazoa
29.78 	402 	0 	K1 	6072 	Eumetazoa
29.78 	402 	0 	K2 	33213 	Bilateria
29.78 	402 	0 	K3 	33511 	Deuterostomia
29.78 	402 	0 	P 	7711 	Chordata
29.78 	402 	0 	P1 	89593 	Craniata
29.78 	402 	0 	P2 	7742 	Vertebrata
29.78 	402 	0 	P3 	7776 	Gnathostomata
29.78 	402 	0 	P4 	117570 	Teleostomi
29.78 	402 	0 	P5 	117571 	Euteleostomi
29.78 	402 	0 	P6 	8287 	Sarcopterygii
29.78 	402 	0 	P7 	1338369 	Dipnotetrapodomorpha
29.78 	402 	0 	P8 	32523 	Tetrapoda
29.78 	402 	0 	P9 	32524 	Amniota
29.78 	402 	0 	C 	40674 	Mammalia 
Question
  1. How many taxons have been identified?
  2. How much reads have been classified?
  3. Which domains were found and with how many reads?
  4. How much reads have been assigned by fungi Kingdom?
  1. The file contains 300 lines (information visible when expanding the report dataset in the history panel). So 300-2 = 298 taxons have been identified.

  2. On the 1350 sequences in the input, 837 (62%) were classified (or identified as a taxon) and 513 unclassified (38%). Information visible when expanding the report dataset in the history panel, and scrolling in the small box starting with “Loading database information” below the format information, but also on the top of the report.

  3. The domains are identified by a D in colum 4.

    To get the domains (or other taxonomic level), we can use Filter with the following parameters:

    • param-file “Filter”: report outpout of Kraken2
    • “With following condition”: c4=='D'

    The 3 domains were found:

    • Eukaryota with 756 (56%) reads assigned to it
    • Bacteria with 51 (3.78%) reads
    • Archaea with 2 (0.15%) reads
  4. 342 (25.33%) reads are assigned to fungi.

Other taxons than yeast have been identified. They could be contamination or misidentification of reads. Indeed, many taxons have less than 5 reads assigned. We will filter these reads out to get a better view of the possible contaminations.

Hands-on: Filter taxons with low assignements
  1. Filter with the following parameters:
    • param-file “Filter”: report outpout of Kraken2
    • “With following condition”: c2>5

      We want to keep only taxons with more than 5 reads assigned, i.e. the value in the 2nd column, is higher than 5.

  2. Inspect the output
Question
  1. How many taxons have been removed? How many were kept?
  2. What are the possible contaminations?
  1. 59 lines are now in the file so \(300 - 59 = 241\) taxons have been removed because low assignment rates.

  2. Most of the reads (402) were assigned to humans (Homo sapiens). This is likely a contamination either during the beer production or more likely during DNA extraction.

    Bacteria were also found: Firmicutes, Proteobacteria and Bacteroidetes. But the identified taxons are not really precise (not below order level). So difficult to identify the possible source of contamination.

Visualize the community

Once we have assigned the corresponding taxa to the sequences, the next step is to properly visualize the data: visualize the diversity of taxons at different levels.

To do that, we will use the tool Krona (Ondov et al. 2011). But before that, we need to adjust the output from Kraken2 to the requirements of Krona. Indeed, Krona expects as input a table with the first column containing a count and the remaining columns describing the hierarchy. Currently, we have a report tabular file with the first column containing the taxonomy and the second column the number of reads. We will now use another tool, which also provides taxonomic classification, but it produces the exact formatting Krona needs.

Hands-on: Prepare dataset for Krona
  1. Krakentools: Convert kraken report file ( Galaxy version 1.2+galaxy0) with the following parameters:
    • param-collection “Kraken report file”: Report output of Kraken
  2. Inspect the output file

    Question
    Column 1	Column 2	Column 3	Column 4	Column 5	Column 6	Column 7	Column 8
    513 	Unclassified 						
    7 	k__Eukaryota 						
    0 	k__Eukaryota 	p__Chordata 					
    0 	k__Eukaryota 	p__Chordata 	c__Mammalia 				
    0 	k__Eukaryota 	p__Chordata 	c__Mammalia 	o__Primates 			
    0 	k__Eukaryota 	p__Chordata 	c__Mammalia 	o__Primates 	f__Hominidae 		
    0 	k__Eukaryota 	p__Chordata 	c__Mammalia 	o__Primates 	f__Hominidae 	g__Homo 	
    402 	k__Eukaryota 	p__Chordata 	c__Mammalia 	o__Primates 	f__Hominidae 	g__Homo 	s__Homo_sapiens					
    
    1. What are the columns in the file?
    1. 8 columns: one with the number of reads and one for each of the 7 levels of taxonomy.

We can now run Krona. This tool creates an interactive report that allows hierarchical data (like taxonomy) to be explored with zooming, as multi-layered pie charts. With this tool, we can easily visualize the composition of a microbiome community.

Hands-on: Krona pie chart
  1. Krona pie chart ( Galaxy version 2.7.1+galaxy0) with the following parameters:
    • “What is the type of your input data”: Tabular
      • param-file “Input file”: output of Krakentools tool
  2. Inspect the generated file

Let’s take a look at the result.

Question
  1. What is the percentage of reads assigned to Homo sapiens?
  2. To Archaea?
  1. 30% of reads are assigned to Homo sapiens
  2. 0.08% of Archaea

Investigate the beer microbiome

Let’s come back to our original question: characterization of the beer microbiome, specially looking at the yeasts.

Yeasts do not form a single taxonomic group (Kurtzman 1994). They are parts of the fungi kingdom but belong two separate phyla: the Ascomycota and the Basidiomycota. But the “true yeasts” are classified in the order Saccharomycetales.

Question
  1. Click on o__Saccharomycetales in the graph (Krona pie chart). Which yeast species have been identified? Are they the expected in beer?
  2. Click on Saccharomyces in the graph. What are the percentages of identified reads assigned to Saccharomyces for different levels?
  3. Click a second time on Saccharomyces in the graph. What is the repartition between the different Saccharomyces species?
  1. 6 species from the Saccharomycetales order have been identified:
    • Saccharomycetaceae family
      • Saccharomyces genus
        • Saccharomyces cerevisiae species, the most abundant identified yeast species with 293 reads and the one expected given the type of beers
        • Saccharomyces paradoxus species, a wild yeast and the closest known species to Saccharomyces cerevisiae

          These reads might have been misidentified to Saccharomyces paradoxus instead of Saccharomyces cerevisiae because of some errors in the sequences, as Saccharomyces cerevisiae and Saccharomyces paradoxus are close species and should share then a lot of similarity in their sequences.

        • Saccharomyces eubayanus species, most likely the parent of the lager brewing yeast, Saccharomyces pastorianus (Sampaio 2018)

          Similar to Saccharomyces paradoxus, these reads might have been misassigned.

      • Kluyveromyces genus - Kluyveromyces marxianus species: only 1 read
    • Trichomonascaceae family - Sugiyamaella genus - Sugiyamaella lignohabitans species: only 1 read
    • Debaryomycetaceae family - Candida genus - Candida dubliniensis species: only 1 read

    Everything except Saccharomyces cerevisiae are probably misindentified reads.

  2. Reads are assigned to Saccharomyces
    • 25% out of total reads (root)
    • 44% out of identified reads for Eukaryota domain
    • 96% out of identified reads for Ascomycota phylum
    • 98% out of identified reads for Saccharomycetales order
    • 99% out of identified reads for Saccharomycetaceae family

    Krona chart with multi-layered pie chart representing the community profile with in the center the higher taxonomy levels (i.e. domain) and on the exterior the more detailed ones (i.e. species). *Saccharomyces* is highligthed with on the right the percentages of identified reads assigned to *Saccharomyces* for the different taxonomic levels.

  3. 92% of Saccharomyces reads are assigned to Saccharomyces cerevisiae, 5% to Saccharomyces paradoxus and 3% to Saccharomyces eubayanus,.

    Krona chart with the community profile for *Saccharomyces* with the different species.

Microbiome of several beers, including Chimay beers, have been previously investigated by targeting specifically the fungi, in which we can find yeasts (Sobel et al. 2017):

Heatmap with rows being type of beers and columns fungi species. For the rows, the name of beers are on the right and clustering tree on the left side of the heatmap. For the columns, the name of the species are on the bottom and the clustering tree on the top. The fungi species are sorted from the least abundant on the left to the most abundant on the right.Open image in new tab

Figure 3: Heatmap of the number of reads per internal transcribed spacer (ITS) sequencing of fungal species per beer. Source Sobel et al. 2017

The species identified for Chimay beers are (from the most abundant to the least one):

  • Saccharomyces cerevisiae
  • Saccharomyces mikatea: a species generally used in winemaking (Bellon et al. 2013)
  • Kazachstania martiniae: Kazachstania is a genus from the family Saccharomycetaceaethe.

  • Saccharomyces kudriavzevii
  • Brettanomyces bruxellensis

    Brettanomyces is a non-spore forming genus of yeast in the family Saccharomycetaceae, and is important to both the brewing and wine industries due to the sensory compounds it produces.

    Brettanomyces bruxellensis is typically used for the production of the Belgian beers.

  • Saccharomyces paradoxus: a wild yeast species closely related to Saccharomyces cerevisiae
  • Kazachstania kunashirensis
  • Saccharomyces cariocanus: a wild yeast species closely related to Saccharomyces cerevisiae
  • Filobasidium magnum
  • Malasseria restricta
  • Pichia kudriavzevii
  • Aureobasidium pullulans
  • Sporidiobolus metaroseus

In a structured way:

Phylum Class Order Family Genus Species
Ascomycota Saccharomycetes Saccharomycetales Saccharomycetaceae Saccharomyces Saccharomyces cerevisiae
Ascomycota Saccharomycetes Saccharomycetales Saccharomycetaceae Saccharomyces Saccharomyces mikatea
Ascomycota Saccharomycetes Saccharomycetales Saccharomycetaceae Saccharomyces Saccharomyces kudriavzevii
Ascomycota Saccharomycetes Saccharomycetales Saccharomycetaceae Saccharomyces Saccharomyces paradoxus
Ascomycota Saccharomycetes Saccharomycetales Saccharomycetaceae Saccharomyces Saccharomyces cariocanus
Ascomycota Saccharomycetes Saccharomycetales Saccharomycetaceae Kazachstania Kazachstania martiniae
Ascomycota Saccharomycetes Saccharomycetales Saccharomycetaceae Kazachstania Kazachstania kunashirensis
Ascomycota Saccharomycetes Saccharomycetales Saccharomycetaceae Brettanomyces Brettanomyces bruxellensis
Ascomycota Saccharomycetes Saccharomycetales Saccharomycetaceae   Pichia kudriavzevii
Ascomycota Dothideomycetes Dothideales Dothioraceae Aureobasidium Aureobasidium pullulans
Basidiomycota Tremellomycetes Filobasidiales Filobasidiaceae Filobasidium Filobasidium magnum
Basidiomycota Malasseziomycetes Malasseziales Malasseziaceae Malassezia Malasseria restricta
Basidiomycota Sporidiobolales Sporidiobolales Sporidiobolaceae Sporidiobolus Sporidiobolus metaroseus
Question

By looking at the output of Krakentools, which fungi species identified for the Chimay beers in Sobel et al. 2017 are also identified in our data? And vice versa?

Phylum Class Order Family Genus Species Sobel et al. 2017 Our data
Ascomycota Saccharomycetes Saccharomycetales Saccharomycetaceae Saccharomyces Saccharomyces cerevisiae X X
Ascomycota Saccharomycetes Saccharomycetales Saccharomycetaceae Saccharomyces Saccharomyces mikatea X  
Ascomycota Saccharomycetes Saccharomycetales Saccharomycetaceae Saccharomyces Saccharomyces kudriavzevii X  
Ascomycota Saccharomycetes Saccharomycetales Saccharomycetaceae Saccharomyces Saccharomyces paradoxus X X
Ascomycota Saccharomycetes Saccharomycetales Saccharomycetaceae Saccharomyces Saccharomyces cariocanus X  
Ascomycota Saccharomycetes Saccharomycetales Saccharomycetaceae Saccharomyces Saccharomyces eubayanus   X
Ascomycota Saccharomycetes Saccharomycetales Saccharomycetaceae Kazachstania Kazachstania martiniae X  
Ascomycota Saccharomycetes Saccharomycetales Saccharomycetaceae Kazachstania Kazachstania kunashirensis X  
Ascomycota Saccharomycetes Saccharomycetales Saccharomycetaceae Kluyveromyces Kluyveromyces marxianus   X
Ascomycota Saccharomycetes Saccharomycetales Saccharomycetaceae Brettanomyces Brettanomyces bruxellensis X  
Ascomycota Saccharomycetes Saccharomycetales Saccharomycetaceae   Pichia kudriavzevii X  
Ascomycota Saccharomycetes Saccharomycetales Debaryomycetaceae Candida Candida dubliniensis   X
Ascomycota Dothideomycetes Dothideales Dothioraceae Aureobasidium Aureobasidium pullulans X  
Ascomycota Sordariomycetes Sordariales Sordariaceae Neurospora Neurospora crassa   X
Basidiomycota Tremellomycetes Filobasidiales Filobasidiaceae Filobasidium Filobasidium magnum X  
Basidiomycota Malasseziomycetes Malasseziales Malasseziaceae Malassezia Malasseria restricta X  
Basidiomycota Sporidiobolales Sporidiobolales Sporidiobolaceae Sporidiobolus Sporidiobolus metaroseus X  

Some interesting yeast have been found in Sobel et al. 2017 and not in our data (e.g. Brettanomyces bruxellensis), and vice versa.

(Optional) Sharing your history

One of the most important features of Galaxy comes at the end of an analysis: sharing your histories with others so they can review them.

Sharing your history allows others to import and access the datasets, parameters, and steps of your history.

Access the history sharing menu via the History Options dropdown (galaxy-history-options), and clicking “history-share Share or Publish”

  1. Share via link
    • Open the History Options galaxy-history-options menu at the top of your history panel and select “history-share Share or Publish”
      • galaxy-toggle Make History accessible
      • A Share Link will appear that you give to others
    • Anybody who has this link can view and copy your history
  2. Publish your history
    • galaxy-toggle Make History publicly available in Published Histories
    • Anybody on this Galaxy server will see your history listed under the Published Histories tab opened via the galaxy-histories-activity Histories activity
  3. Share only with another user.
    • Enter an email address for the user you want to share with in the Please specify user email input below Share History with Individual Users
    • Your history will be shared only with this user.
  4. Finding histories others have shared with me
    • Click on the galaxy-histories-activity Histories activity in the activity bar on the left
    • Click the Shared with me tab
    • Here you will see all the histories others have shared with you directly

Note: If you want to make changes to your history without affecting the shared version, make a copy by going to History Options galaxy-history-options icon in your history and clicking Copy this History

Conclusion