R Development Page
Contributed R Packages
Below is a list of all packages provided by project Species identity and evolution in R.
Important note for package binaries: R-Forge provides these binaries only for the most recent version of R, but not for older versions. In order to successfully install the packages provided on R-Forge, you have to switch to the most recent version of R or, alternatively, install from the package sources (.tar.gz).
Species Identity and Evolution in R
Provides functions for the analysis of species limits and DNA barcoding data. Included are functions for generating important summary statistics from DNA barcode data, assessing specimen identification efficacy, testing and optimizing divergence threshold limits, assessment of diagnostic nucleotides, and calculation of the probability of reciprocal monophyly. Additionally, a sliding window function offers opportunities to analyse information across a gene, often used for marker design in degraded DNA studies. Further information on the package has been published in Brown et al (2012) |
|Version: 1.4-2 | Last change: 2017-05-16 05:13:44+02 | Rev.: 66|
|Download: (.tar.gz) | (.zip) | Build status: Current | Stable Release: Get spider 1.5.0 from CRAN|
R install command:
Species Identity and Evolution in R--development
|A package for the analysis of species limits and DNA barcoding data. Development area for functions that will eventually be included in spider proper.|
|Version: 0.0-10 | Last change: 2016-04-01 12:18:47+02 | Rev.: 58|
|Download: (.tar.gz) | (.zip) | Build status: Current|
R install command:
Build status codes
0 - Current: the package is available for download. The corresponding package passed checks on the Linux and Windows platform without ERRORs.
1 - Scheduled for build: the package has been recognized by the build system and provided in the staging area.
2 - Building: the package has been sent to the build machines. It will be built and checked using the latest patched version of R. Note that it is included in a batch of several packages. Thus, this process will take some time to finish.
3 - Failed to build: the package failed to build or did not pass the checks on the Linux and/or Windows platform. It is not made available since it does not meet the policies.
4 - Conflicts: two or more packages of the same name exist. None of them will be built. Maintainers are asked to negotiate further actions.
5 - Offline: the package is not available. The build system may be offline or the package maintainer did not trigger a rebuild (done e.g., via committing to the package repository).
If your package is not shown on this page or not building, then check the build system status report.