The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
Methods for fitting macroevolutionary models to phylogenetic trees Pennell (2014) <doi:10.1093/bioinformatics/btu181>.
| Version: | 2.0.11 |
| Depends: | ape (≥ 3.0-6), R (≥ 2.15.0), phytools (≥ 1.5-1) |
| Imports: | MASS, mvtnorm, subplex, deSolve (≥ 1.7), digest, Rcpp (≥ 0.11.0), coda, ncbit, colorspace, methods |
| LinkingTo: | Rcpp |
| Suggests: | TreeSim |
| Published: | 2023-04-03 |
| DOI: | 10.32614/CRAN.package.geiger |
| Author: | Luke Harmon, Matthew Pennell, Chad Brock, Joseph Brown, Wendell Challenger, Jon Eastman, Rich FitzJohn, Rich Glor, Gene Hunt, Liam Revell, Graham Slater, Josef Uyeda, Jason Weir and CRAN team (corrections in 2022) |
| Maintainer: | Luke Harmon <lukeh at uidaho.edu> |
| License: | GPL-2 | GPL-3 [expanded from: GPL (≥ 2)] |
| NeedsCompilation: | yes |
| Citation: | geiger citation info |
| Materials: | README ChangeLog |
| In views: | Phylogenetics |
| CRAN checks: | geiger results |
| Reference manual: | geiger.pdf |
| Package source: | geiger_2.0.11.tar.gz |
| Windows binaries: | r-devel: geiger_2.0.11.zip, r-release: geiger_2.0.11.zip, r-oldrel: geiger_2.0.11.zip |
| macOS binaries: | r-release (arm64): geiger_2.0.11.tgz, r-oldrel (arm64): geiger_2.0.11.tgz, r-release (x86_64): geiger_2.0.11.tgz, r-oldrel (x86_64): geiger_2.0.11.tgz |
| Old sources: | geiger archive |
| Reverse depends: | convevol, OUwie, surface, TreeSim, windex |
| Reverse imports: | evobiR, FishPhyloMaker, hilldiv, hillR, hisse, markophylo, nichevol, nodeSub, pmc, ppgm, ratematrix, RPANDA, secsse, sensiPhy, treats |
| Reverse suggests: | cauphy, diversitree, fishtree, pcmabc, phytools, RNeXML, treestats |
Please use the canonical form https://CRAN.R-project.org/package=geiger to link to this page.
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.