SCM

R Development Page

Contributed R Packages

Below is a list of all packages provided by project Eagle for Genome-Wide Association Mappin.

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).

Packages

Eagle

Multiple Locus Association Mapping on a Genome-Wide Scale

  An implementation of multiple-locus association mapping on a genome-wide scale. Eagle can handle inbred or outbred study populations, populations of arbitrary unknown complexity, and data larger than the memory capacity of the computer. Since Eagle is based on linear mixed models, it is best suited to the analysis of data on continuous traits. However, it can tolerate non-normal data. Eagle reports, as its findings, the best set of snp in strongest association with a trait. To perform an analysis, run OpenGUI(). This opens a web browser to the menu-driven user interface for the input of data, and for performing genome-wide analysis.
  Version: 1.0.0 | Last change: 2017-08-24 01:38:45+02 | Rev.: 17
  Download: linux(.tar.gz) | windows(.zip) | Build status: Current | Stable Release: Get Eagle 1.0.2 from CRAN
  R install command: install.packages("Eagle", repos="http://R-Forge.R-project.org")
 
Logs:  
Package build: Source package (Linux x86_64) Windows binary (x86_64/i386)
Package check: Linux x86_64 (patched) | Linux x86_64 (devel) Windows (patched) | Windows (devel)

 

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.

Thanks to:
Vienna University of Economics and Business University of Wisconsin - Madison Powered By FusionForge