r8s version 1.71

Analysis of rates ("r8s") of evolution

programmed by

Mike Sanderson

Section of Evolution and Ecology

UC Davis, Davis CA 95616

May 16, 2006

 

Introduction

This is a program for estimating absolute rates ("r8s") of molecular evolution and divergence times on a phylogenetic tree. It implements several methods for estimating these parameters ranging from fairly standard maximum likelihood methods in the context of global or local molecular clocks to more experimental semiparametric and nonparametric methods that relax the stringency of the clock assumption using smoothing methods. Its starting point is a given phylogenetic tree and a given set of estimated branch lengths (numbers of substitutions along each branch). In addition one or more calibration points can be added to permit scaling of rates and times to real units. These calibrations can take one of two forms: assignment of a fixed age to a node, or enforcement of a minimum or maximum age constraint on a node, which is generally a better reflection of the information content of fossil evidence. Terminal nodes are permitted to occur at any point in time, allowing investigation of rate variation in phylogenies such as those obtained from "serial" samples of viral lineages through time. Finally, it is possible to assign all divergence times (perhaps based on outside estimates of divergence times) and examine molecular rate variation under several models of smoothing.

The program reads "NEXUS" formatted data (ASCII) files, the standard used by PAUP, MacClade, Component and some other phylogenetic programs (Maddison et al. 1997).


What’s new in 1.71

This version fixes some minor bugs and compilation problems on various platforms

What’s new in 1.70

This version improves the robustness of the previous implementation of divergence time estimation routines and adds some entirely new features.


Platforms

The current version of the program available in two forms

Some users have had success compiling for Solaris and other UNIX platforms.

 

Download and Installation

Follow the directions in the manual to compile and test the software. The manual has been completely updated for this release!

Linux and OS X versions

Everything is now distributed as one compressed 'tar' (archive) file. It contains source code (with makefile), sample data sets, the manual, and for Mac OS X users, the bin/ directory contains a precompiled executable file (compiled using libraries in OS X 10.3). Obviously, this won't be of much use on Linux or other UNIX systems. Those users will have to compile the code themselves using the makefile (check with your system administrator if you do not know how to do this).

Download r8s vers. 1.71

 Once you have downloaded the file, which is called r8s1.7.dist.tar.Z, get into a UNIX shell (e.g., on OS X use the Terminal utility program), copy the file to some working directory and then type

uncompress r8s1.71.dist.tar.Z
tar xvf r8s1.71.dist.tar

and you should see the four subdirectories, doc, src, bin, and sample magically appear...

Note to users compiling on newer Linux distributions: You may have to find the location of the g2c library in your linux distribution and change the 'LPATH = -Lpath_to_library' line in the Makefile accordingly.

Download r8s vers. 1.71 OS 10.4 executable binary for Mac users interested in a recent compiled binary

 

Help and documentation

The user manual is available as a PDF file.

Several sample data files are included in the distribution subdirectory called sample/, including a file that illustrates the new features of version 1.7.

 

Why "r8s"?

The program is called "r8s" for two reasons: my long-time colleague, Marty Wojciechowski, thought it was an appropriately geeky play on words, and, after the fact, I've noticed that it's disambiguated from a bunch of other hits on the word "rate" in internet search databases. Besides, evidently it's too late to think of a good name now...

  

Acknowledgments

Thanks to everyone for putting up with all the bugs and slow email responses. I appreciate bug reports even if I don't deal with them immediately--or at least I appreciate them more than you appreciate the bugs.