An R Interface for PHYLIP

An R Interface for PHYLIP

Methods in Ecology and Evolution 2014, 5, 976–981 doi: 10.1111/2041-210X.12233 APPLICATION Rphylip: an R interface for PHYLIP Liam J. Revell1* and Scott A. Chamberlain2 1Department of Biology, University of Massachusetts Boston, Boston, MA 02125, USA; and 2Department of Biological Sciences, Simon Fraser University, Vancouver, BC V5A 1S6, Canada Summary 1. The phylogeny methods software package PHYLIP has long been among the most widely used packages for phylogeny inference and phylogenetic comparative biology. Numerous methods available in PHYLIP, including several new phylogenetic comparative analyses of considerable importance, are not implemented in any other software. 2. Over the past decade, the popularity of the R statistical computing environment for many different types of phylogenetic analyses has soared, particularly in phylogenetic comparative biology. There are now numerous packages and methods developed for the R environment. 3. In this article, we present Rphylip, a new R interface for the PHYLIP package. Functions of Rphylip interface seamlessly with all of the major analysis functions of the PHYLIP package. This new interface will enable the much easier use of PHYLIP programs in an integrated R workflow. 4. In this study, we describe our motivation for developing Rphylip and present an illustration of how functions in the Rphylip package can be used for phylogenetic analysis in R. Key-words: phylogeny, statistics, computational biology, evolution PHYLIP contains a wide diversity of methods. These meth- Introduction ods cover both phylogeny inference and evolutionary analysis Over the past several decades, phylogenetics has assumed a using phylogenies, including a range of analyses not imple- central role in evolutionary study (Felsenstein 1985b, 2004; mented (so far as we know) in any other software (e.g. Cavalli- Harvey & Pagel 1991; Harvey et al. 1996; Hillis, Moritz & Sforza & Edwards 1967; Inger 1967; Le Quesne 1969; Felsen- Mable 1996; Losos 2011; Baum & Smith 2012). This growth stein 1973, 1979, 1981b, 2008, 2012; Estabrook, Johnson & and importance has been coincident with the development and McMorris 1976; Farris 1978; Cavender & Felsenstein 1987; widespread use of sophisticated computer software for infer- Kuhner & Felsenstein 1994). Consequently, it is reasonable to ring phylogenies and for using phylogenetic trees in evolution- presume that PHYLIP will continue to be an important soft- ary analyses (Hillis, Moritz & Mable 1996; Felsenstein 2004; ware package for many years to come. Paradis 2012). R (R Core Team 2013), which is simultaneously a com- Since its first release over 33 years ago in October 1980, and mand-line-driven statistical computing environment and an through numerous subsequent editions, Joseph Felsenstein’s interpreted computer programming language, has slowly but software package PHYLIP (the PHYLogeny Inference Pack- steadily grown in popularity among scientists, and especially age; Felsenstein 1989, 2013) has accumulated over 25 000 cita- among evolutionary biologists and ecologists (e.g. Paradis tions (summed over all versions) as of February, 2014. The 2006, 2012; Bolker 2008; Swenson 2014). The flexibility and citation rate of PHYLIP has declined slightly in recent years as utility of R is built on its contributed function libraries, called other phylogenetic analysis programs have gained in popular- packages. R packages, which can be built and contributed by ity, but it nonetheless remains very high. For instance, in 2013 any developer, contain an enormous range of computational (the most recent complete year in the data base), Google Scho- and statistical methods. Among phylogeneticists, the impor- lar indicates that PHYLIP was cited on well over 1000 occa- tance of R has increased significantly in the past decade – par- sions. In our experience, citations only account for a subset of ticularly since the development of the important core R the number of times a software package is employed in publi- phylogenetics package ‘ape’ (Paradis, Claude & Strimmer cation – particularly for packages that are highly popular and 2004; Paradis 2006, 2012). (The package name ape is an acro- widely used. Thus, this tally probably underestimates the true nym for Analysis of Phylogenetics and Evolution; Paradis, impact that PHYLIP has had on the inference and use of Claude & Strimmer 2004). Subsequent years have seen the phylogenies in scientific research. development and release of a variety of other contributed packages for phylogenetic analysis in the R environment (e.g. Harmon et al. 2008; King & Butler 2009; Kembel et al. 2010; *Correspondence author. E-mail: [email protected] Schliep 2011; Bapst 2012; Beaulieu et al. 2012; Fitzjohn 2012; © 2014 The Authors. Methods in Ecology and Evolution © 2014 British Ecological Society Rphylip: phylogeny package 977 Revell 2012; Orme et al. 2013; Stadler 2013), most of which to be used seamlessly in an integrated R workflow. This build on the functions and data structures of ape. means that once PHYLIP has been installed locally, Rphy- In this short note, we announce and describe a new package lip migrates all control of PHYLIP programs to the R envi- that acts as an R interface for the important phylogenetics soft- ronment. In the development of Rphylip, we have done our ware package, PHYLIP. This package is called ‘Rphylip’ (An absolute best to maximize the interoperability of Rphylip R interface for PHYLIP) and can be downloaded and installed with other R phylogeny methods packages, such as the from the Comprehensive R Archive Network, CRAN. Rphy- important core phylogenetics package, ape (Paradis, Claude lip contains R functions that interface with almost all of the & Strimmer 2004). For instance, Rphylip uses the same programs of the PHYLIP software package and that migrate data structure to store a phylogeny in memory as ape, almost all user control of PHYLIP programs to the R environ- meaning that inferred trees from Rphylip can be plotted, ment. Rphylip thus allows for a nearly seamless integration of analysed, manipulated or written to file using the functions the PHYLIP package into R phylogeny analysis workflows of ape. Rphylip functions that take a tree as input can use and permits smooth interoperability with many other R phy- a phylogeny that has been read into memory using ape. logenetics packages. Other advantages of using Rphylip as an interface to PHY- In the sections that follow, we will first provide some addi- LIP include not needing to be concerned about the format tional detail on the motivation for developing Rphylip; then requirements or taxon label limits imposed by PHYLIP we will describe the range of capabilities of PHYLIP (and thus software. For example, PHYLIP input data files require Rphylip); and finally, we will demonstrate the use of Rphylip taxon labels that are exactly 10 characters in length (includ- for phylogeny inference and comparative analysis via a pair of ing whitespace). This constraint is removed using Rphylip brief examples. to interface with PHYLIP programs. Furthermore, possibly because PHYLIP was developed over more than three dec- ades, different PHYLIP programs (even those analysing the Motivation same type of data) sometimes require different input file Joseph Felsenstein is inarguably one of the most influential liv- formats. For instance, CONTML (for continuous character ing evolutionary biologists. His contributions span a range of phylogeny estimation) and CONTRAST (with multiple disciplines, including evolutionary quantitative genetics and samples per species) use different input files. Rphylip, by theoretical population genetics (e.g. Felsenstein 1965, 1971, contrast, takes standard R data objects as input, such as 1972, 1974, 1992a; Bodmer & Felsenstein 1967; Crow & Fel- matrices, vectors, lists and data frames. Although R, being senstein 1968), and statistics (e.g. Lewontin & Felsenstein a command-line-driven scientific computing environment, 1965). However, his biggest scientific influence has undoubt- has an initially steep learning curve, scientists already com- edly come via his extensive work over many years on statistical fortable in R should find using Rphylip to be a breeze. phylogeny methods, including maximum likelihood phylogeny Finally, Rphylip does not need the user to supply a path to inference from both DNA sequences (Felsenstein 1981a) and the PHYLIP executable files. Rather, if the Rphylip user continuous characters (Felsenstein 1973, 1981b), the nonpara- has locally installed PHYLIP in any of the typical locations metric bootstrap (Felsenstein 1985a) and phylogenetic com- (such as in the directory C:\Program Files in Windows; or parative methods (Felsenstein 1985b, 1988, 2005, 2008, 2012). in the /Applications folder in Mac OS X), Rphylip will Phylogenetics is inherently a computationally intensive dis- search for and locate the path to the PHYLIP executables. cipline, and Felsenstein has also been central in the implemen- Alternatively,ifPHYLIPhasbeeninstalledinanuncon- tation of phylogeny methods in computer software. In ventional location on the disk, the user can supply the path particular, his package of phylogeny programs, PHYLIP (Fel- to the PHYLIP executables once per R session (via the senstein 1989, 2013), first released in 1980, is among the most function setPath), and then a path will no longer be highly cited phylogeny method packages ever developed. Not required for any subsequent calls to functions in the Rphy- only is PHYLIP still an important package for phylogenetic lip

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    6 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us