R Development Page
Contributed R Packages
Below is a list of all packages provided by project DetSel.
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).
A computer program to detect markers responding to selection
|In the new era of population genomics, surveys of genetic polymorphism ("genome scans") offer the opportunity to distinguish locus-specific from genome wide effects at many loci. Identifying presumably neutral regions of the genome that are assumed to be influenced by genome-wide effects only, and excluding presumably selected regions, is therefore critical to infer population demography and phylogenetic history reliably. Conversely, detecting locus-specific effects may help identify those genes that have been, or still are, targeted by natural selection. The software package DetSel has been developed to identify markers that show deviation from neutral expectation in pairwise comparisons of diverging populations.|
|Version: 1.0.2 | Last change: 2013-04-24 13:41:34+02 | Rev.: 13|
|Download: (.tar.gz) | (.zip) | Build status: Current | Stable Release: Get DetSel 1.0.2 from CRAN|
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.