SCM

R Development Page

Contributed R Packages

Below is a list of all packages provided by project Atlas and Analysis.

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

A2

Atlas and Analysis of Systems-Biology-Led Pathways

  Pathway-level analysis is supported using a collection of curated pathways (A2). Taking as inputs user-defined list of genes or genomic regions, it outputs pathways regulated and details gene members involved as well. Transforming genomic regions into pathways is enabled by defining modulated genes based on conformation evidence, expression quantitative trait loci mapping, enhancer-promoter expression and genomic proximity. Together with its web-app, A2 aids in understanding molecular circuits such as resulted from differential studies at the gene and genomic region level.
  Version: 1.0.0 | Last change: 2018-04-03 15:45:54+02 | Rev.: 12
  Download: linux(.tar.gz) | windows(.zip) | Build status: Failed to build
  R install command: install.packages("A2", 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)


Old Version: 1.0.0 | Last change: 2018-03-06 23:00:02
Old Version Download: linux(.tar.gz) | windows(.zip)

 

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