R Development Page
Contributed R Packages
Below is a list of all packages provided by project Fault Tree and Event Tree 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
EventTree | Event Trees for Hazard and Risk Analysis |
A package for constructing, calculating and displaying event trees. | |
Version: 0.0.3 | Last change: 2016-05-05 16:27:27+02 | Rev.: 6 | |
Download:
![]() ![]() | |
R install command:
install.packages("EventTree", repos="http://R-Forge.R-project.org") | |
FaultTree | Fault Trees for Risk and Reliability Analysis |
Construction, calculation and display of fault trees. Methods derived from Clifton A. Ericson II (2005, ISBN: 9780471739425) | |
Version: 1.0 | Last change: 2023-06-08 02:13:12+02 | Rev.: 90 | |
Download:
![]() ![]() | |
R install command:
install.packages("FaultTree", repos="http://R-Forge.R-project.org") | |
FaultTree.SCRAM | Interaction Between FaultTree on R and "SCRAM" |
Fault trees parepared using package FaultTree are given access to advanced calculations on SCRAM. | |
Version: 0.2.8.2 | Last change: 2020-03-09 16:43:00+01 | Rev.: 77 | |
Download:
![]() ![]() | |
R install command:
install.packages("FaultTree.SCRAM", repos="http://R-Forge.R-project.org") | |
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.