Thanks for trying out the SciDB package for R. I hope you enjoy using it.
The current development version of this R package can always be installed directly from GitHub using the devtools package as follows:
library('devtools')
install_github("SciDBR","paradigm4",quick=TRUE)
The SciDB R package requires installation of a simple open-source HTTP network service called on the computer that SciDB is installed on. This service only needs to be installed on the SciDB machine, not on client computers that connect to SciDB from R. It's available in packaged binary form for supported SciDB operating systems, and as source code which can be compiled and deployed on any SciDB installation.
See http://github.com/paradigm4/shim for source code and installation instructions.
Most functions return objects that represent array promises--unevaluated SciDB
query expressions with a result schema. Use the new scidbeval
function or the
optional eval
function argument when available to force evaluation to a
materialized SciDB backing array. Otherwise use the objects normally, deferring
evaluation until required.
The package now supports double-precision valued R sparse matrices
defined via the Matrix
package. Sparse SciDB matrices that are
materialized to R are returned as sparse R matrices and vice-versa.
The package overloads the standard R image
function to plot heatmaps
of SciDB array objects (only applies to objects of class scidb
).
library("devtools")
install_github("SciDBR","Paradigm4")
library("scidb")
scidbconnect() # Fill in your SciDB hostname as required
# Create a SciDB array with some random entries
iquery("store(build(<v:double>[i=0:999,100,0,j=0:999,250,0],random()%100),A)")
# The SciDBR `image` function overloads the usual R image function to produce
# heatmaps using SciDB's `regrid` aggregation operator. The 'grid' argument
# specifies the output array size, and the 'op' argument specifies the
# aggregation operator to apply.
X = image(A, grid=c(100,100), op="avg(v)", useRaster=TRUE)
# Image accepts all the standard arguments to the R `image` function in
# addition to the SciDB-specific `grid` and `op` arguments. The output axes are
# labeled in the original array units. The scidb::image function returns the
# interpolated heatmap array:
dim(X)
[1] 100 100
The package has a completely new implementation of aggregation, merge, and related database functions. The new functions apply to SciDB array and data frame-like objects. A still growing list of the functions includes:
- aggregate
- bind (SciDB
apply
operator--generalizes R'scbind
) - index_lookup
- merge (SciDB
join
andcross\_join
operators) - project
- subset (SciDB
filter
operator) - sort
- unique
- sweep
- apply (the R-style apply, not the SciDB AFL apply--see
bind
for that) - cumulate
- cast, slice, repart, redimension, build (wrappers to SciDB operators)
See for example help("subset", package="scidb")
for help on the subset
function, or any of the other functions.
Perhaps the coolest new feature associated with the functions listed above is
that they can be composed in a way that defers computation in SciDB to avoid
unnecessary creation of intermediate arrays. The new functions all accept an
argument named eval
which, when set to FALSE, returns a new SciDB array
promise object in place of evaluating the query and returning an array or data
frame object.
The eval argument is automatically set to FALSE when any of the above functions
are directly composed in R, unless manually overriden by explicitly setting
eval=TRUE
. Consider the following example:
x = as.scidb(iris)
head(x)
Sepal_Length Sepal_Width Petal_Length Petal_Width Species
1 5.1 3.5 1.4 0.2 setosa
2 4.9 3.0 1.4 0.2 setosa
3 4.7 3.2 1.3 0.2 setosa
4 4.6 3.1 1.5 0.2 setosa
5 5.0 3.6 1.4 0.2 setosa
6 5.4 3.9 1.7 0.4 setosa
a = aggregate(
project(
bind(x,name="PxP", FUN="Petal_Length*Petal_Width"),
attributes=c("PxP","Species")),
by="Species", FUN="avg(PxP)")
a[]
Species_index PxP_avg Species
0 0 0.3656 setosa
1 1 5.7204 versicolor
2 2 11.2962 virginica
The composed aggregate(project(bind(...
functions were carried out in
the above example within a single SciDB transaction, storing only the result
of the composed query.