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.

SparseChol: Sparse Matrix C++ Classes Including Sparse Cholesky LDL Decomposition of Symmetric Matrices

'C++' classes for sparse matrix methods including implementation of sparse LDL decomposition of symmetric matrices and solvers described by Timothy A. Davis (2016) <https://fossies.org/linux/SuiteSparse/LDL/Doc/ldl_userguide.pdf>. Provides a set of C++ classes for basic sparse matrix specification and linear algebra, and a class to implement sparse LDL decomposition and solvers. See <https://github.com/samuel-watson/SparseChol> for details.

Version: 0.3.2
Depends: R (≥ 3.4.0), Matrix (≥ 1.3-4)
Imports: Rcpp (≥ 1.0.7)
LinkingTo: Rcpp (≥ 1.0.7), RcppEigen
Suggests: testthat
Published: 2024-12-08
DOI: 10.32614/CRAN.package.SparseChol
Author: Sam Watson [aut, cre], Timothy A. Davis [aut, ctb]
Maintainer: Sam Watson <S.I.Watson at bham.ac.uk>
BugReports: https://github.com/samuel-watson/SparseChol/issues
License: GPL-2 | GPL-3 [expanded from: GPL (≥ 2)]
URL: https://github.com/samuel-watson/SparseChol
NeedsCompilation: yes
SystemRequirements: GNU make
Materials: README
CRAN checks: SparseChol results

Documentation:

Reference manual: SparseChol.pdf

Downloads:

Package source: SparseChol_0.3.2.tar.gz
Windows binaries: r-devel: SparseChol_0.3.2.zip, r-release: SparseChol_0.3.2.zip, r-oldrel: SparseChol_0.3.2.zip
macOS binaries: r-release (arm64): SparseChol_0.3.2.tgz, r-oldrel (arm64): SparseChol_0.3.2.tgz, r-release (x86_64): SparseChol_0.3.2.tgz, r-oldrel (x86_64): SparseChol_0.3.2.tgz
Old sources: SparseChol archive

Reverse dependencies:

Reverse linking to: glmmrBase, glmmrOptim, rts2

Linking:

Please use the canonical form https://CRAN.R-project.org/package=SparseChol to link to this page.

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.