The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
This was made to allow people (like me) to specify lower triangular matrices similar to the domain specific language implemented in nlmixr. Originally I had it included in RxODE
, but thought it may have more general applicability, so I separated it into a new package.
For me, specifying the matrices in this way is easier than specifying them using R’s default matrix. For instance to fully specify a simple 2x2 matrix, in R you specify:
matrix(c(1, 0.5, 0.5, 1),nrow=2,ncol=2,dimnames=list(c("a", "b"), c("a", "b"))) mat <-
With lotri
, you simply specify:
library(lotri)
library(microbenchmark)
library(ggplot2)
lotri(a+b ~ c(1,
mat <-0.5, 1))
I find it more legible and easier to specify, especially if you have a more complex matrix. For instance with the more complex matrix:
lotri({
mat <-+b ~ c(1,
a0.5, 1)
~ 1
c +e ~ c(1,
d 0.5, 1)
})
To fully specify this in base R you would need to use:
matrix(c(1, 0.5, 0, 0, 0,
mat <-0.5, 1, 0, 0, 0,
0, 0, 1, 0, 0,
0, 0, 0, 1, 0.5,
0, 0, 0, 0.5, 1),
nrow=5, ncol=5,
dimnames= list(c("a", "b", "c", "d", "e"), c("a", "b", "c", "d", "e")))
Of course with the excellent Matrix
package this is a bit easier:
library(Matrix)
matrix(c(1, 0.5, 0.5, 1),nrow=2,ncol=2,dimnames=list(c("a", "b"), c("a", "b")))
mat <- bdiag(list(mat, matrix(1), mat))
mat <-## Convert back to standard matrix
as.matrix(mat)
mat <-##
dimnames(mat) <- list(c("a", "b", "c", "d", "e"), c("a", "b", "c", "d", "e"))
Regardless, I think lotri
is a bit easier to use.
lotri
also allows lists of matrices to be created by conditioning on an id
with the |
syntax.
For example:
lotri({
mat <-+b ~ c(1,
a0.5, 1) | id
~ 1 | occ
c +e ~ c(1,
d 0.5, 1) | id(lower=3, upper=2, omegaIsChol=FALSE)
})
print(mat)
#> $id
#> d e
#> d 1.0 0.5
#> e 0.5 1.0
#>
#> $occ
#> c
#> c 1
#>
#> Properties: lower, upper, omegaIsChol
print(mat$lower)
#> $id
#> d e
#> 3 3
#>
#> $occ
#> c
#> -Inf
print(mat$upper)
#> $id
#> d e
#> 2 2
#>
#> $occ
#> c
#> Inf
print(mat$omegaIsChol)
#> $id
#> [1] FALSE
This gives a list of matrix(es) conditioned on the variable after the |
. It also can add properties to each list that can be accessible after the list of matrices is returned, as shown in the above example. To do this, you simply have to enclose the properties after the conditional variable. That is et1 ~ id(lower=3)
.
Now there is even a faster way to do a similar banded matrix concatenation with lotriMat
list(lotri({et2 + et3 + et4 ~ c(40,
testList <-0.1, 20,
0.1, 0.1, 30)}),
lotri(et5 ~ 6),
lotri(et1+et6 ~c(0.1, 0.01, 1)),
matrix(c(1L, 0L, 0L, 1L), 2, 2,
dimnames=list(c("et7", "et8"),
c("et7", "et8"))))
function(.mats){
matf <- as.matrix(Matrix::bdiag(.mats))
.omega <- unlist(lapply(seq_along(.mats),
.d <-function(x) {
dimnames(.mats[[x]])[2]
}))dimnames(.omega) <- list(.d, .d)
return(.omega)
}
print(matf(testList))
#> et2 et3 et4 et5 et1 et6 et7 et8
#> et2 40.0 0.1 0.1 0 0.00 0.00 0 0
#> et3 0.1 20.0 0.1 0 0.00 0.00 0 0
#> et4 0.1 0.1 30.0 0 0.00 0.00 0 0
#> et5 0.0 0.0 0.0 6 0.00 0.00 0 0
#> et1 0.0 0.0 0.0 0 0.10 0.01 0 0
#> et6 0.0 0.0 0.0 0 0.01 1.00 0 0
#> et7 0.0 0.0 0.0 0 0.00 0.00 1 0
#> et8 0.0 0.0 0.0 0 0.00 0.00 0 1
print(lotriMat(testList))
#> et2 et3 et4 et5 et1 et6 et7 et8
#> et2 40.0 0.1 0.1 0 0.00 0.00 0 0
#> et3 0.1 20.0 0.1 0 0.00 0.00 0 0
#> et4 0.1 0.1 30.0 0 0.00 0.00 0 0
#> et5 0.0 0.0 0.0 6 0.00 0.00 0 0
#> et1 0.0 0.0 0.0 0 0.10 0.01 0 0
#> et6 0.0 0.0 0.0 0 0.01 1.00 0 0
#> et7 0.0 0.0 0.0 0 0.00 0.00 1 0
#> et8 0.0 0.0 0.0 0 0.00 0.00 0 1
microbenchmark(matf(testList),lotriMat(testList))
mb <-
print(mb)
#> Unit: microseconds
#> expr min lq mean median uq max
#> matf(testList) 997.946 1016.782 1183.27561 1039.1140 1399.6615 4998.357
#> lotriMat(testList) 2.355 3.116 4.76219 5.0595 5.5205 20.418
#> neval
#> 100
#> 100
autoplot(mb)
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.