R Development Page

Contributed R Packages

Below is a list of all packages provided by project biclustGUI.

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

RcmdrPlugin.BiclustGUI	Rcmdr Plug-in GUI for Biclustering
	A plug-in for R Commander (Rcmdr). The package is a Graphical User Interface (GUI) in which several biclustering methods can be executed, followed by diagnostics and plots of the results. Further, the GUI also has the possibility to connect the methods to more general diagnostic packages for biclustering. Biclustering methods from biclust, fabia, s4vd, iBBiG, isa2, BiBitR, rqubic and BicARE are implemented. Additionally, superbiclust and BcDiag are also implemented to be able to further investigate results. The GUI also provides a couple of extra utilities to export, save, search through and plot the results. RcmdrPlugin.BiclustGUI also provides a very specific framework for biclustering in which new methods, diagnostics and plots can be added. Scripts were prepared so that R-package developers can freely design their own dialogs in the GUI which can then be added by the maintainer of RcmdrPlugin.BiclustGUI. These scripts do not required any knowledge of tcltk and Rcmdr and are easy to fill in.
	Version: 1.1.1 | Last change: 2017-07-03 10:08:08+02 | Rev.: 92
	Download: (.tar.gz) | (.zip) | Build status: Current | Stable Release: Get RcmdrPlugin.BiclustGUI 1.1.3.1 from CRAN
	R install command: install.packages("RcmdrPlugin.BiclustGUI", 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)

---

RcmdrPlugin.BiclustGUI.Extra	Title: Rcmdr Plug-in GUI for Biclustering
	A plug-in for R Commander (Rcmdr). The package is a Graphical User Interface (GUI) in which several biclustering methods can be executed, followed by diagnostics and plots of the results. Further, the GUI also has the possibility to connect the methods to more general diagnostic packages for biclustering. Biclustering methods from biclust, fabia, s4vd, iBBiG, isa2, BiBitR, rqubic and BicARE are implemented. Additionally, superbiclust and BcDiag are also implemented to be able to further investigate results. The GUI also provides a couple of extra utilities to export, save, search through and plot the results. RcmdrPlugin.BiclustGUI also provides a very specific framework for biclustering in which new methods, diagnostics and plots can be added. Scripts were prepared so that R-package developers can freely design their own dialogs in the GUI which can then be added by the maintainer of RcmdrPlugin.BiclustGUI. These scripts do not required any knowledge of tcltk and Rcmdr and are easy to fill in.
	Version: 1.1.1 | Last change: 2017-07-03 10:08:08+02 | Rev.: 92
	Download: (.tar.gz) | (.zip) | Build status: Current
	R install command: install.packages("RcmdrPlugin.BiclustGUI.Extra", 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.