R Development Page
Contributed R Packages
Below is a list of all packages provided by project Fish Migration Monitoring (stacomiR).
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).
Fish Migration Monitoring (stacomiR)
|Graphical outputs and treatment for a database of fishway monitoring. It is a part of the STACOMI open source project developed in France by the French Agency for Biodiversity (AFB) institute to centralize data obtained by fishway monitoring. Version 0.5.3 is available in French and English.|
|Version: 0.5.3 | Last change: 2017-06-22 14:12:40+02 | Rev.: 413|
|Download: (.tar.gz) | (.zip) | Build status: Failed to build|
R install command:
ODBC Connection Class for Package stacomiR
|This package provides S4 class wrappers for the ODBC connection, it also provides some utilities to paste small datasets to clipboard, rename columns. It is used by the package stacomiR for connections to the database.|
|Version: 0.5.2 | Last change: 2017-06-22 07:56:35+02 | Rev.: 411|
|Download: (.tar.gz) | (.zip) | Build status: Current | Stable Release: Get stacomirtools 0.5.0 from CRAN|
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.