Difference between revisions of "Phylogenetics: RevBayes Lab"

From EEBedia
Jump to: navigation, search
(Creating a control file for indelible)
(Creating a control file for indelible)
Line 61: Line 61:
  [TREE] mytree  
  [TREE] mytree  
   [rooted] 20 3.0 0.0 1.0 2.0  // ntaxa, birth rate, death rate, sampling fraction, clock rate
   [rooted] 20 3.0 0.0 1.0 2.0  // ntaxa, birth rate, death rate, sampling fraction, clock rate
  [treedepth] 1.0              // tree rescaled to have this depth (root to tip time)
  [PARTITIONS] mypartition  
  [PARTITIONS] mypartition  

Revision as of 17:19, 19 April 2020

Adiantum.png EEB 5349: Phylogenetics
The goal of this lab exercise is to introduce you to Bayesian divergence time estimation using RevBayes. There are other programs that are currently more popular than RevBayes for doing this (notably BEAST2), but I prefer RevBayes for this lab because it is less of a black box: every aspect of the model is very explicitly defined in RevBayes.

Getting started

Login to Xanadu

Login to Xanadu and request a machine as usual:

srun --pty -p mcbstudent --qos=mcbstudent bash

Once you are transferred to a free node, type

module load RevBayes/xxx

Create a directory

Use the unix mkdir command to create a directory to play in today:

cd ~            # you can omit this if you are already in your home directory
mkdir rblab

Downloading and compiling indelible

We will use the program indelible to simulate trees and data. Start by filling out the web form and downloading the software from the indelible web site.

Transfer the INDELibleV1.03.tar.gz file to the Xanadu cluster and unpack it using tar:

tar zxvf INDELibleV1.03.tar.gz

Navigate into the folder INDELibleV1.03/src and enter the following command to compile the program:

g++ -o indelible -O4 indelible.cpp

Once this command has finished, you will find a file named 'indelible' in that same src directory. Move that file to your rblab folder as follows:

cd ~
mv INDELibleV1.03/src/indelible rblab

Simulating and analyzing under the strict clock model

Divergence time analyses are the most tricky type of analysis we will do in this course. That's because the sequences do not contain information about substitution rates or divergence times per se; they contain information about the number of substitutions that have occurred, and the number of substitutions is the product of rate and time. Thus, maximum likelihood methods cannot separate rates from times; this requires a Bayesian approach and considered use of priors, which constrain the range of rate and time scenarios considered plausible.

We will thus start slowly, and we will simulate data so that we know the truth. This will help guide your expectations when conducting divergence time analyses on real data.

Let's simulate data for 10000 sites on a 20-taxon pure birth (Yule) tree using a strict clock. This will allow us to know everything: the birth rate of the tree generating process, and the "clock" rate (i.e. the substitution rate that applies to the entire tree), as well as the model used for simulation.

Creating a control file for indelible

Indelible requires a control file specifying everything it needs to know to perform your simulation.

Create a control file named control.txt with the following contents:

[TYPE] NUCLEOTIDE 1            // simulate nucldeotides using method 1 for indels

  [output]      NEXUS          // output alignment in NEXUS format
  [randomseed]  13579          // the pseudorandom number seed
[MODEL] mymodel
  [submodel]  HKY  5           // HKY model with kappa = 5
  [rates]     0.0 0.5 10       // pinvar. gamma shape, number of categories
  [statefreq] 0.3 0.2 0.3 0.2  // T, C, A, G
[TREE] mytree 
  [rooted] 20 3.0 0.0 1.0 2.0  // ntaxa, birth rate, death rate, sampling fraction, clock rate

[PARTITIONS] mypartition 
  [mytree mymodel 10000]       // 10000 sites using mytree and mymodel

[EVOLVE] mypartition 1 strict  // 1 replicate using mypartition saved to file strict_TRUE.nex

These options are explained in the [online indelible manual] and the comments should help you figure out what each command does. The resulting data will be saved in a file named strict_TRUE.nex, with the TRUE indicating that this is the true alignment (which is meaningless in our case because we chose not to add any insertions or deletions).