R Development Page
Contributed R Packages
Below is a list of all packages provided by project marelac: Tools for Aquatic Science.
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).
Tools for Aquatic Sciences
|Datasets, constants, conversion factors, and utilities for MArine, Riverine, Estuarine, LAcustrine and Coastal science. The package contains among others: (1) chemical and physical constants and datasets, e.g. atomic weights, gas constants, the earths bathymetry; (2) conversion factors (e.g. gram to mol to liter, barometric units, temperature, salinity); (3) physical functions, e.g. to estimate concentrations of conservative substances, gas transfer and diffusion coefficients, the Coriolis force and gravity; (4) thermophysical properties of the seawater, as from the UNESCO polynomial or from the more recent derivation based on a Gibbs function.|
|Version: 2.1.6 | Last change: 2017-07-09 11:15:18+02 | Rev.: 194|
|Download: (.tar.gz) | (.zip) | Build status: Current | Stable Release: Get marelac 2.1.6 from CRAN|
R install command:
Datasets and tutorials for use in aquatic sciences
|Datasets and tutorials for use in the MArine, Riverine, Estuarine, LAcustrine and Coastal sciences|
|Version: 1.1.2 | Last change: 2017-07-09 11:15:18+02 | Rev.: 194|
|Download: (.tar.gz) | (.zip) | Build status: Current|
R install command:
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.