R Development Page
Contributed R Packages
Below is a list of all packages provided by project ReacTran.
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
| ReacTran | Reactive Transport Modelling in 1d, 2d and 3d | |||||||||
| Routines for developing models that describe reaction and advective-diffusive transport in one, two or three dimensions. Includes transport routines in porous media, in estuaries, and in bodies with variable shape. | ||||||||||
| Version: 1.4.3.2 | Last change: 2019-12-17 14:50:34+01 | Rev.: 103 | ||||||||||
Download:
 (.tar.gz) |
 (.zip) |
Build status: Current | Stable Release: Get ReacTran 1.4.3.1 from CRAN | ||||||||||
R install command:
install.packages("ReacTran", repos="http://R-Forge.R-project.org") | ||||||||||
|
| ReacTran.examples | Reactive transport model examples | |||||||||
| Examples of reactive transport models | ||||||||||
| Version: 1.0 | Last change: 2010-09-16 15:07:34+02 | Rev.: 66 | ||||||||||
|
Download:
(.tar.gz) |
(.zip) |
Build status: Current | ||||||||||
R install command:
install.packages("ReacTran.examples", 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.
