R Development Page
Contributed R Packages
Below is a list of all packages provided by project Rniftilib.
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
| Rniftilib | R Interface to nifticlib for Reading and Writing Images in NIfTI-1 and ANALYZE Format | |||||||||||
| Provides functions to read/write images in ANALYZE(TM)7.5 (.img/.hdr) and NIfTI-1 (.nii) data format. The supported image formats are very common for functional brain MRI data analysis, but are also used for other tormographic or volumetric measurement data such as medical images of other body parts. The functions are implemented using the C-based nifticlib, a reference implementation for the NIfTI data format. Currently, this package embeds some slightly modified parts of the public domain library nifticlib-2.0.0 (http://sourceforge.net/projects/niftilib/). The small modifications to the included nifticlib sources were required to comply with the R extensions rules. | ||||||||||||
| Version: 0.0-35 | Last change: 2015-01-21 11:03:39+01 | Rev.: 79 | ||||||||||||
Download:
 (.tar.gz) |
 (.zip) |
Build status: Failed to build | ||||||||||||
R install command:
install.packages("Rniftilib", 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.
