R Development Page

Contributed R Packages

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

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



Data and functions for Geotechnical Risk Assessment

  Data sets and functions for geotechnical reliability analysis. The GeoRiskR develops for geotechnical engineers to perform reliability analysis, in which several existing data sets (soil shear strengths, rock shear strengths, GCL shear strengths, soil texture, and the relation between initial void ratio and compression index) are compiled. The collected datasets are adopted from the existing literature, for instance,the data of shear strength parameters of soils composed by 509 paired parameters (including cohesion and inner friction angle) observed at 22 locations from 12 published papers.
  Version: 1.5 | Last change: 2013-11-27 04:32:43+01 | Rev.: 7
  Download: linux(.tar.gz) | windows(.zip) | Build status: Current
  R install command: install.packages("GeoRiskR", repos="")
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 Powered By FusionForge